Girder Channel Changer

[Bluethunder]

Just wondering if there are any plans to put the girder channel changer back in?

[sub]

No, not directly built in. You'd need to use a .exe channel changer instead.

[Bluethunder]

Due to the stupid STB IR protocols (they send 2 different codes per #, so if you send the same code twice, it ignores it), I'm stuck using girder.

The old girder changer, used to send single numbers (# pause # pause #) to girder. ievent.exe {channel} sends ### into girder, so its looking for event 201, instead of event 2, event 0, and event 1.

Is there any way to get the individual #s instead of {channel}, so I could use a batch file to send
ievent %1
ievent %2
ievent %3

Thanks

[sub]

Aswell as {channel}, the attached update will allow you to use {channel_d1} {channel_d2} {channel_d3} and {channel_d4}. If the number is less than four digits, it'll be zero padded. You can then specify these on the command line to your .exe changer (.bat file or .exe).

[Bluethunder]

Awesome, I'll try that out right away.

Thanks for all the work

Edit:

Yup, works great!

[markbb1]

Aswell as {channel}, the attached update will allow you to use {channel_d1} {channel_d2} {channel_d3} and {channel_d4}. If the number is less than four digits, it'll be zero padded. You can then specify these on the command line to your .exe changer (.bat file or .exe).

Sub

Is there any way to make the zero padding configurable? My STB wants three digits. If it gets more than three, it ignores the first three and only acts on the last digit(s). When it gets only one or two digits, it goes to the closest subscribed channel number. I was blasting "0042" and I watched as "0" "0" "4" scrolled right to left to become displayed as "004", then, when it got the "2", it cleared the "004" and just displayed the "2", then changed itself to channel 6.

[obiwan]

I do not know where you are in the Good Old USA but here in the midwest we are taught that is good math

[sub]

Sub

Is there any way to make the zero padding configurable? My STB wants three digits. If it gets more than three, it ignores the first three and only acts on the last digit(s). When it gets only one or two digits, it goes to the closest subscribed channel number. I was blasting "0042" and I watched as "0" "0" "4" scrolled right to left to become displayed as "004", then, when it got the "2", it cleared the "004" and just displayed the "2", then changed itself to channel 6.

If you're using {channel}, then NPVR doesnt do any zero padding, and any padding problems is being created by your existing executable.

If you're tring to use these new {channel_d1} {channel_d2} {channel_d3} and {channel_d4}, added in this patch for bluethunder, then just use {channel_d2} {channel_d3} and {channel_d4} on your command line and it wont use the leading zero. This effectively gives you three digits.

[markbb1]

If you're using {channel}, then NPVR doesnt do any zero padding, and any padding problems is being created by your existing executable.

If you're tring to use these new {channel_d1} {channel_d2} {channel_d3} and {channel_d4}, added in this patch for bluethunder, then just use {channel_d2} {channel_d3} and {channel_d4} on your command line and it wont use the leading zero. This effectively gives you three digits.

Sub

Thanks for the great solution. I am not using Girder, but my STB is a Dish Network analog reeceiver that is very common in the US and I would bet there are thousands, maybe tens (or even hundreds) of thousands of them around. Just thought I would head off any troubles that US users might have if they try to use Girder the way bluethinder is doing.

[sub]

By doing it these {channel_d1}-{channel_d4} the way I did, it'll cater for those that user set top boxes with 4 digit, or 3 digit, or 2 digit. They just have to not use the leading digits if they're not intersted in them.