beta net2hipsend

[pBS]

excellent, i think i'll let the HIP guy know, as this is a weird variance that could have been avoided if he used a literal period instead of a localizable number...
[meaning force it to use a '.' every time, regardless of locale]

cuz technically it's not a number "one and one one-thousandth" it's just 1 and a 001 separated by a period...

[ElihuRozen]

and I saw that some of them have a line for the decimal character.

The .hip and the .v1 files have the following lines

Code:

[VERSION]
Decimal=.

I don't know how it is used, but I just thought I'd mention it in case you find it helpful.

[pBS]

wow,i hadn't noticed that at all...and after all my messing with the hip files..

but i didn't see any changes when i changed it to a comma, still seems to be locked into locale..
[i created a new ir blast digit,still came out with a period]
that may be for other areas of the program...

maybe it just is storage of what HIP reads from registry for decimal, so it will blast accordingly..so changing it won't do anything..

[Uisge]

I have been using the net2hipsend I think since the day pBS told us about it with no problems. Now suddenly I have occasional missed channel changes. It missed two tonight. My htpc system has been static with no hardware, software, or config changes.

When it misses the channel changes, it is always the first digit that is getting lost somewhere.

Any ideas?

-Uisge

[pBS]

are you using 3 digit padding? i had problems with numbers leading with '0' so i turn off padding as it will blast from 1 to 4 digits, no padding needed..
was it after a long period of inactivity?

here's a slight modification that puts an additional delay before running first digit...
[normally it was only after each digit]
could be other things beyond my control tho..

[Uisge]

No not doing three digit padding stopped that a while back when I saw your post that it was not needed.

The channel changes that missed last night where for HB0-Channel 300 and the 3 just didn't make it and the receiver only got a 00, and for ABC - Channel 13 and a the one didn't make it so the reciever only got a 3.

Now there is a new wrinkle. Last night after my post it missed another channel change. This time changing to HBOP channel 303 but the difference is that it didn't missed the first character it missed the last and the receiver simply got 30.

I'll try the het binary and see if playing with the delay will help at all but I am puzzled as to why the behavior has suddenly started. I guess it's a possibility that the IR emitter or dongle hardware is going bad or that my STBs IR receiver is going bad.

This is not just happening with scheduled recordings but is also happening on manual channel changes.

Thanks.

-Uisge

[pBS]

hmmm, any changes in anti-virus/spyware, firewall, or gbpvr recording service lately?
do you use ultraXMLTV?
anything running that shouldn't be?

sometimes it happens when the eye placement has changed slightly..
try it from command line to see if you can get it to fail there..

[Uisge]

There haven't been any changes at all in quite a while that I am aware of. The antivirus is updating regularly but looking at the logs there doesn't show anything If I get it figured out I'll let ya know.

-Uisge

[pBS]

may possibly be dns slowness...i arranged the default server to be 127.0.0.1 instead of localhost so a dns lookup won't slow it down anymore...
you might try setting the server to 127.0.0.1 manually to see if it helps...

[pBS]

i rewrote a few bits to get rid of logging as it was stopping changes under certain accounts, so now back to working under any account...
still fast as ever and now won't stop on errors..
using 127.0.0.1 as default server to avoid dns lookups and broken hosts file..
i don't foresee any changes so it should be locked in for quite some time..
not a single error yet...