Selecting FM Radio brings TV sound, not radio (WinTV-500)

[brightcynic]

I have a WinTV-500. I am having a variety of issues with GBPVR freezing here and there, though I have it on a dedicated disk.

Nevertheless, the big issue at the moment is that when I go to select an FM Radio station, instead of turning on the radio, it starts pumping in whatever tv channel I was last on. I noticed that this may not occur when in LIVE TV mode.

Thoughts?

[bendsley]

I have the same problem with FM Radio, instead of turning on the radio, it starts pumping in whatever tv channel I was last on.

Any help would be appreciate

[sub]

What this most likely relates to, is only one of the two tuners on the PVR500 support FM Radio (this may be a driver limitation), and its likely GB-PVR is trying to use the wrong one.

To work around this, you could copy the [Hauppauge PVR500] section to [Hauppauge PVR500 (with FM)]. Set the former to SUPPORTS_FM_RADIO=0 and later to SUPPORTS_FM_RADIO=1.

Modify you capture source settings to set only device #1 to the 'Hauppauge PVR500 (with FM)' device.

Now when you try to listen to the radio, this should force GB-PVR to only use the correct tuner.

[SickBoy]

A suggestion - since this seems to be a common issue amongst PVR500MCE users... maybe this should be either formally documented or added to the out-of-the-box default.ini file.

This works great for me. Thanks.

[rtiangha]

Hi, just got a PVR-500 myself and I was wondering where and how to do this change? It works great with my PVR-250, the only problem is with the FM tuner (my first instance of the PVR-500 has it, while the second one does not).

[sub]

Hi, just got a PVR-500 myself and I was wondering where and how to do this change? It works great with my PVR-250, the only problem is with the FM tuner (my first instance of the PVR-500 has it, while the second one does not).

See my post above which describes changing the direct.ini file.

A suggestion - since this seems to be a common issue amongst PVR500MCE users... maybe this should be either formally documented or added to the out-of-the-box default.ini file.

I've added this change to the direct.ini for the next release. I changed it as soon as I became aware of the issue, but there hasn't been a release since then.