Lifeview TVWalker Twin (Streaming HD)

[keith_leitch]

I have done a system restore, which got rid of it. I'll be making another attempt to install the Lifeview, which may bring it back, and I will report it to you then.

In the meantime, it was a pretty nondescript Windows error: "PVRx2 has encountered an error and needs to close." That sort of thing. It always happened almost immediately upon the station video starting, and two or three seconds of the video would play in the background behind it before freezing.

I'm hoping this thread might still get some attention. If not, I will create another.

I have finally found an afternoon to reinstall the Lifeview TV Walker Twin. This is the more recent Dual BDA device, not the earlier one that caused so much trouble for so many.

PVRx2 is no longer crashing as I cited above. It runs the first tuner on the Lifeview with no problems, even simultaneous to my original (Blaze) tuner.

However, when I try to scan for stations on the second Lifeview Tuner, the .NET framework crashes. There is a message from GBPVR Config that indicates I should "ensure my tuner is installed and not in use." .NET says it cannot find the tuner.

The second tuner shows up in my system devices with an identical name to the first: "Lifeview TV Walker Twin DVB-T". However, in the Digital Source Configuration dialog of GBPVR Convig, with "show only detected devices" ticked, the first tuner shows as "Lifeview Twin USB", and the second as "MSI DigiVOX mini II".

I also have a second, identical Lifeview unit. I plugged it in and attempted to install either tuner, but both produce the .NET error as above.

Is this just a conflict of names? Is there some way I can resolve it?

[sub]

However, when I try to scan for stations on the second Lifeview Tuner, the .NET framework crashes. There is a message from GBPVR Config that indicates I should "ensure my tuner is installed and not in use." .NET says it cannot find the tuner.

Try doing a starting a scan to get this message, then zip and attach the config.exe.log and config.exe-native.log and I'll take a look.

Also run filtercheck.exe from the gbpvr directory, and post the fietcheck.log that gets created.

[keith_leitch]

Try doing a starting a scan to get this message, then zip and attach the config.exe.log and config.exe-native.log and I'll take a look.

Also run filtercheck.exe from the gbpvr directory, and post the fietcheck.log that gets created.

Thanks as always for your quick offer of help. Logs are attached, along with a screen capture with (most of) both error messages showing. I zipped these immediately after attempting a channel scan; HOWEVER, I am recording something I don't want to interrupt, so I actually cancelled my way out of Config. Let me know if you need this again with the Configs saved, and I will get that done first thing tomorrow.

I should mention that the vendor, who strikes me as honest, swears that he has this device running both tuners on Mediaportal. Given that, combined with the fact that they are BDA devices, I am pretty sure I must just be missing something.

[sub]

In you logs it shows the device numbers are set incorrectly on your capture sources.

You should have two capture sources for the lifeview devices with device numbers set to #1 and #2, and one capture source for the other device also set for device #1 (since it uses different drivers).

If that doesnt work for you repost those same logs after trying the same thing, so I can check you've got it set correctly.

[keith_leitch]

In you logs it shows the device numbers are set incorrectly on your capture sources.

You should have two capture sources for the lifeview devices with device numbers set to #1 and #2, and one capture source for the other device also set for device #1 (since it uses different drivers).

If that doesnt work for you repost those same logs after trying the same thing, so I can check you've got it set correctly.

Thanks. I will try it in a few minutes. I have been assuming that the device numbers need to be unique for the purposes of conflict resolution.

Just out of curiousity: If I were going to plugh in the second identical twin tuner, how would I distinguish the two from each other given that they use identical drivers? (I don't necessarily need to do this; I am mostly just curious).

[keith_leitch]

In you logs it shows the device numbers are set incorrectly on your capture sources.

You should have two capture sources for the lifeview devices with device numbers set to #1 and #2, and one capture source for the other device also set for device #1 (since it uses different drivers).

This appears to have solved the problem of the twin tuners working together. Thanks, Sub!