very slow recording start on some of my Digital tuners (1 Viewer)

[guytpetj]

TV-Server Version: 1.0.0.0RC1
MediaPortal Version: 1.0.0.0RC1
MediaPortal Skin: LCARS & B2
Windows Version: XP Pro Sp3
CPU Type: Pentium D - 3.4Ghz
HDD: 500GB + 500GB + 320GB +320GB + 250 GB + 250GB + 80GB
Memory: 2GB DDR (2 x 1GB)
Motherboard: 8I945P Pro (Gigabyte Technology Co., Ltd.)
Motherboard Chipset: Intel® 945P Express Chipset
Motherboard Bios: Award Software International, Inc. F10, 04-Jan-06 - Ver: 2.3
Video Card: Nvidia Geforce 6600 GT (128 MB)
Video Card Driver: 7.7.7.2
Sound Card: Realtek High Definition Audio
Sound Card AC3: Optical out
Sound Card Driver: 5.10.0.5172
1. TV Card: Hauppauge PVR500MCE
1. TV Card Type: Analog, Hardware
1. TV Card Driver: 2.0.48.25037
2. TV Card: Hauppauge HVR 2200
2. TV Card Type: Digital/Analog, Hardware
2. TV Card Driver: 7.1.22.26025
3. TV Card: DigitalNow TwinDVB-T Tuner 1 (USB2)
3. TV Card Type: DVB-T (HD)
3. TV Card Driver: 1.0.6.4
4. TV Card: DigitalNow TwinDVB-T Tuner 2 (USB2)
4. TV Card Type: DVB-T (HD)
4. TV Card Driver: 1.0.6.4
MPEG2 Video Codec: MPV
MPEG2 Audio Codec: MPA
Satelite/CableTV Provider: N/A
HTPC Case: Cooler Master Stacker EVO 830
Cooling: 4 x 12cm fan regulated @7vdc. Standard CPU cooler
Power Supply: 550 Watt
Remote: Logitech Harmony 1000i
TV: Sony Bravia 52" LCD & 19" LCD
TV - HTPC Connection: DVI to HDMI


Hardware:
Hauppauge HVR 2200 (2 x Digital/Analog) (card 1&5, 2&6)
DNTV Live! Tiny USB2 (1 x Digital) (card 3)
DNTV Live! Tiny USB2 (1 x Digital) (card 4)
Hauppauge PVR 500 (2 x Analog) (card 7, 8)
All cards with the latest drivers, downloaded from the web.

MediaPortal internal TV Engine:
======================
All cards work OK except the 2nd digital tuner on the HVR 2200 due to TV Engine limitations.
All recordings start almost immediately.

MediaPortal / TV-Server:
=================
Here is where the problems start. If I schedule multiple recordings, for instance 1 recording for each card, lets say --starting at 20:30, the the following happens.
-- HVR 2200 card 1 – starts recording at 20:30
-- HVR 2200 card 2 – starts recording at 20:30
-- DNTV 1 – starts recording between 2 and 5 minutes later
-- DNTV 2 – starts recording between 2 and 5 minutes later
-- PVR 500 card 1 – starts recording after DNTV 2 started
-- PVR 500 card 2 – does bugger all

Additional Information:
================
-- In the TV-Server I can see all cards, and can tune all cards except for the analog part of the HVR 2200. (which I don't care about that much)
-- I have disabled the EPG grabbing for all cards in TV-Server
-- If I change the card priority to DNTV being card 1 and 2 for recording, than it still takes between 2 and 5 minutes to start a recording on the first and second DNTV cards, all other cards follow immediately.
-- Before I had the HVR 2200 installed, the DNTV tuners would start immediately.
-- And again, using the MP internal TV Engine all works fine.

Can anybody tell me what might be wrong causing the scheduled recordings to start late on the DNTV tuners, and how to fix this problem.

Attached are the logs of one of my attemps to get it to work. in this case I scheduled recordings on 5 cards.

 

[SciDoctor]

I have seen this BIG delay when looking for BDA receiver filters (single filter BDA cards) , yours is espeacialy long.

If a DEV looks at the timestamp from

2008-04-19 23:10:20.443905 [6]: dvb: Find BDA receiver

to

2008-04-19 23:12:23.303280 [6]: dvb: using only tv tuner filter...


This routine took two minutes to get a result before the graph building could continue.

My setup can take 10-30 seconds to do this (sorry no logs atm) pre RC1 this wasn't an issue. Doesn't affect my single filter USB tuners but does my pci and pci-e single filter tuners.

 

[guytpetj]

Could this be a bug?

Could this be a bug ?

If a DEV looks at the timestamp from

2008-04-19 23:10:20.443905 [6]: dvb: Find BDA receiver

to

2008-04-19 23:12:23.303280 [6]: dvb: using only tv tuner filter...


This routine took two minutes to get a result before the graph building could continue.

Can one of the testers / developers have a look at this?