PVR 150 IR blaster problem if last digit of last channel same as first of next!!

[sub]

Sorry, I'm not really sure. As far as I know, if it works in the Hauppauge BlastCfg, then it should work exactly the same when called from HaupBlast.exe

[martint123]

When I had the Sky problems and was capturing the IR signals, there was no visible difference between the blastcfg and the haupblast codes being sent.

p.s. when sub says haupblast asks irblastercfg, I think it is more probably hcwzblast.dll as that is the module that talks to the hardware and haupblast works when the config program isn't there.

I can't think of anything to cause the behaviour that you're getting.

Martin

[thawk]

Hmm looks like I am stuck!!

Thanks for help so far

I guess I may need to speak to Hauppauge

Cheers

Tim

[sub]

I have also email my Hauppauge contact to ask if there has been any changes on that front, but havnt heard back yet.

[sub]

I heard back from Hauppauge that there have been no changes, and GB-PVR is still doing the correct thing.

I actually think your problem relates to what is referred to as the 'toggle bit'. A toggle bit is a single bit of data that is toggled between '0' and '1' each time the button is pressed on the remote. Its used one some IR devices to cleanly delineate one keypress from the next. This often causes problems for IR blasters (in all apps that use them), since they usually work by recording a devices IR signals, then playing them back, which doesnt contain the smarts to adjust this toggle bit.

You might be able to get around it by configuring the Hauppauge BlasCFG app to send enter after the channel number, or something similar.

If you want more info on the problem, you could probably try googling on 'remote toggle bit' or something like that.

[sub]

Hauppauge asked exactly which box you've got selected in blastcfg? Can you post a screenshot for me? I dont have the Hauppauge blaster software installed, so cant remember exact terminology used in that app.

[thawk]

Hi

I dont think it is a 'remote toggle bit' problem since if I send e.g. '444' it works fine, it's just if send 144 then some time later 444.

Also wouldnt the remote toggle bit problem also occur in the blastcfg program? My problem is just through haupblast access of the Hauppauge code.

Regarding my settings in irblastercfg (box selected) I have settings North America, Cable Box, Samsung - codeset 384 - I can't select to send anything after channel number in the cfg program - it says it doesnt apply to this cablebox!

I will be back home again on Thur or friday (off traveling on work again at the moment) and can get a screenshot then if that will help

Thanks for following up on this!!

Tim

[sub]

Sorry, I'm not really sure then. As I said above I pretty much just tell the Hauppauge software to change to channel number X, and it takes care of the rest.