Haupblast Trying to change ATSC channels

[amadams]

I am using GBPVR ver 1.2.13 with a Hauppauge HVR-1600. I set up the ATSC channels according to the instructions in the Wiki. When I try to change to an ATSC channel in the guide, the IR commands are sent to my satellite STB. I have tried emptying the EPG's and removing all the channels from the guide setup for the STB and the ATSC devices. I then updated the EPG's and remapped all of the ATSC channels with no luck. I have created separate channel listings with Schedulesdirect and have set the logins appropriately when setting up the guides for the STB and the ATSC tuner.

[Braklet]

Is your hybrid card set up as one or two recording sources (one for analog STB interface, another for ATSC)? The channel change procedure is common through a single recording source.

[amadams]

Two different sources in the setup.

[Braklet]

How is Haupblast triggered in the STB recording source? Can you remove the trigger from the ATSC recording source?

Does Hauppauge provide a driver underneath GB-PVR, shared by both recording sources? Perhaps there is some driver configuration to distinguish analog vs. digital channels based on number range or something similar.

I'm kind of grasping at straws because I'm unfamiliar with the hybrid cards. I use two separate cards for analog capture vs. ATSC tuning.

[amadams]

Some more information: The ATSC channels show in the list of channels when I edit the STB's channel listing. If I remove the ATSC channels in that listing they are removed from the channel listing under the ATSC capture device.

[amadams]

According to the wiki and in my setup, the ATSC capture device is set for manual channel changing which I assume should disable Haupblast from sending the IR codes.

[Braklet]

The ATSC channels show in the list of channels when I edit the STB's channel listing.

Ah, a shared channel pool. That sounds familiar... I think I ran into something like that when I first added my ATSC tuner. The fact that your changes cascade to both recording sources is definitely a problem.

One issue is that GB-PVR will assign (and display) internal channel numbers from whatever source into the same number pool. That won't necessarily cause your problem, but it can cause the analog/digital channels to get mixed up in the EPG.

I ended up solving that particular problem in my case by coming up with a display numbering scheme for digital channels (all in the 1xxx range, where 1mmn ==> 1 <major channel #> <subchannel #>) and manually editing the digital channels in the gbpvr.db3 database with a SQLite admin tool to make the display work right.

Obviously I do not recommend that you edit your database since I have no idea if this is the source of your problem. But the channel pool shared between the two sources is definitely a clue.

[sub]

Haupblast Trying to change ATSC channels

The only reason it'd do this is if you'd setup your ATSC capture source to use the ".exe channel changer" and pointed it at hauppauge blast.exe (it should have the Channel Changer set to 'None'), or because you've got the digital channels listed and enabled in your analog capture source and its trying to use the analog side device not the digital side.

If you reproduce the problem then zip and attach the logs, I'll be able to tell you which of these is occurring.

[amadams]

I found the problem. I somehow got a hidden character in the STB specific login for Schedulesdirect. I ended up deleting all of my capture sources and adding and configuring them again. Apparently the ATSC channels showing in the STB's channel lineup should have clued me in that the login was incorrect.

Thank you for all your help.