Terratec Cinergy 2400i DT initial configuration problems

[nia]

I'm really frustrated trying to get my new Terratec Cinergy 2400i DT to run in my setup.

However, I have still after several days of trying to make it run yet to get the recording service to truly accept the card, and start recording.

During setup an channel scanning in Config, I got hangs/crashes that either locked the entire machine up, or at least forced a reboot.

Currently the tuning assistant is actually able to show the first recieved channel in the tuning window in the "Mapping ..." submenu in Config, so there is some kind of 'life'.

That just adds to the frustration of not getting the channels in GBPVR after mapping them into the EPG.

I simply get no TV through, and makes GBPVR recording unreliable even for my remaining PVR-350.

I've moved the card physically between the two PCI-E slots to no avail.

I'm using the latest drivers from Terratecs website.

This is an extract from the recordingservice.exe-native log with some suspicious looking lines in it, but all logs are zipped and attached..

Also see this thread for a filtercheck log

I'm now at a dead end, so any help or inspiration is greatly appreciated.

TIA

Niels

PS: To add insult to injury I have somhow lost all sound on the PC thats running GBPVR in connection with this installation (although I have a slight doubt that it may be already introduces when I upgraded to my Broadcom RAID.

PHP Code:

2007-03-28 22:58:00.203    VERBOSE    get_VideoFrequency() returns 831250000
2007-03-28 22:58:00.203    VERBOSE    get_CountryCode() returns 45
2007-03-28 22:58:00.218    VERBOSE    SetFilterProperty - IKsPropertySet->Set propertry failed
2007-03-28 22:58:00.218    VERBOSE    SetFilterProperty - IKsPropertySet->Set propertry failed
2007-03-28 22:58:00.359    VERBOSE    GetFilterProperty - IKsPropertySet->Get propertry failed
2007-03-28 22:58:00.359    VERBOSE    Hardware Revision: 0x391efe
2007-03-28 22:58:00.359    VERBOSE    GetFilterProperty - IKsPropertySet->Get propertry failed
2007-03-28 22:58:00.359    VERBOSE    Product ROM: 0x391efe
2007-03-28 22:58:00.359    VERBOSE    Unknown MSP Product ROM Code
2007-03-28 22:58:00.359    VERBOSE    SetFilterProperty - IKsPropertySet->Set propertry failed
2007-03-28 22:58:00.359    VERBOSE    SetFilterProperty - IKsPropertySet->Set propertry failed
2007-03-28 22:58:00.359    VERBOSE    SetFilterProperty - IKsPropertySet->Set propertry failed
2007-03-28 22:58:00.375    VERBOSE    SetFilterProperty - IKsPropertySet->Set propertry failed
2007-03-28 22:58:00.375    VERBOSE    SetFilterProperty - IKsPropertySet->Set propertry failed
2007-03-28 22:58:00.375    VERBOSE    SetFilterProperty - IKsPropertySet->Set propertry failed
2007-03-28 22:58:00.375    VERBOSE    Attempting to auto detect MSP Standard
2007-03-28 22:58:00.375    VERBOSE    GetFilterProperty - IKsPropertySet->Get propertry failed 


[sub]

Isnt this a DVB card? The log snippet above is for analog card (incorrectly set to INIT_MODE=IVAC).

[nia]

Yes it's at DVB-T card.

Well - I guess it's better just to let you look in the logs yourself... :o

Please let me know if anything pops out of the logs.

[nia]

The issue with the analog might be that I have reordered the tuner sequence in the process a few times.

[sub]

Where are the logs?

What capture sources do you have set up? You should have one using the Direct Recording Plugin for the PVR350 (device #1), and two using the BDA Recording Plugin for each of the DT tuners (both also device #1).

[nia]

Sorry about the logs - I guess the upload didn't complete before posting :o

Capture sources are all #1 (referring to earlier thread linked above). That enabled me to do any tuning at all.

The 350 is the direct recording plugin, and is one of previously two cards that have worked for years. Nothing changed in that configuration other than removing one card to make place for RAID, and reordering sequence of cards using the new tuner seq. feature (thank you for that BTW )

The Cinergy tuners are both set for BDA, and they do the initial tuning OK.

Log-zip don't complete in either Firefox or IE (it's about 3 MB) Which logs are the ones you specifically need for diagnostics - I just zip them for starters.

[sub]

If the machine is locking up or rebooting, then its got to really be the drivers (or some hardware instability). All I can really suggest is trying a different version of the drivers and hoping you get lucky.

[nia]

Well - I have now passed the rebooting stage after finally getting the tuning to behave. The #1-device hint was part of the tuning solution, but even so it struggled.

Now, it seems to even ignore my 350 that was working earlier today. This has been the consequence after moving the device physically and reordering tuners in config.

I'll keep digging but again - any specific logs that may be useful?

[sub]

Now, it seems to even ignore my 350 that was working earlier today. This has been the consequence after moving the device physically and reordering tuners in config.

Reproduce the problem and post the logs and I'll take a look.

[nia]

Logs attached.

Hope you can help!