Newbie with pronto

[visar]

Hi
I've successfully installed USB-UIRT on my computer (windows xp, girder...)
Basic test is okay...status bar in girder shows me an ir value when pressing the pronto (Marantz RC5000).

Now I played with some zoomplayer presets from AVS (ccf and gml). Seems not compatible with USB-UIRT, so I learned some codes. For the pronto codes I used some predefined gencode ccf files. Unfortunately, this with not much luck. Some codes worked, some not.

Now, I tried to do it from scratch. Created some RC5 codes (system 13 command 0,1,2,3...). After about 20 codes I assigned (learning) some of these codes in girder to some zoomplayer functions.

It works 80%, but not very good. Sometimes, I have to press several times, sometimes nothing happens and sometimes it works very good. Don't know, if it's a Zoomplayer problem or an IR/girder problem.

Does anybody have some tips for creating own IR-codes in pronto from scratch for use with USB-UIRT? And what settings (USB-UIRT plugin) should I use in girder for accurate performance?

example: I assigned the "next frame" function from zp in girder. When I send the pronto IR code, the USB-UIRT LED flashes, but the picture jumps not only one frame but most time several frames. If I have luck, I got it to jump only one frame (as expected), but that's really rare....so, the code seems to be correct, but it sends to much data??

All testings are done in short distance.

Thanks for any help
Visar

[JimHugh]

example: I assigned the "next frame" function from zp in girder. When I send the pronto IR code, the USB-UIRT LED flashes, but the picture jumps not only one frame but most time several frames. If I have luck, I got it to jump only one frame (as expected), but that's really rare....so, the code seems to be correct, but it sends to much data??

Increase the Antirepeat setting in Girder to prevent the same command from being triggered multiple times. Try 250ms and adjust as required.

[visar]

Jim,

Thanks for helping. I guess I found the source of the problem (unfortunately not the solution):

When pressing 2x the same pronto key, girder receives always 2 different ir codes. Of course, in Girder I learned only one code for the command, so I always have to press 2 times...

Why is pronto sending two different codes? It seems like a toggle mode....hmm...I read some threads about this problem, but don't know exactly in what topic....

Is there not an easy newbie "from scratch" tutorial for the pronto/girder/usb-uirt combo? Only for the basic settings to bring the combo in a stable state (and some samples). If one code has learned and is working correctly, rest is learning by doing (or reading lots of messages). But I miss these basics (every tool alone has its "first steps" tutorials, but not for the combo).

Best
Visar

[salsbst]

...When pressing 2x the same pronto key, girder receives always 2 different ir codes. Of course, in Girder I learned only one code for the command, so I always have to press 2 times...

You can add a second EventString to a command or multigroup in Girder. Then learn in the second IR code. Right click the command and choose "Add EventString".

[visar]

okay, will try this...but it's only a workaround. Why using two EventString for only one command? That's double work to do. I want to bring pronto sending only one ir code...that would be better.

btw...I found a good beginners thread in the AVS forum for pronto/girder/usb-uirt/uirt2 combo....it's long and I didn't read the whole thread, so I don't know if my problem will be mentioned.

Here the link: http://www.avsforum.com/avs-vb/showthread.php?threadid=224077&referrerid=0

best
Visar

[salsbst]

okay, will try this...but it's only a workaround. Why using two EventString for only one command?...

I have a Phillips MCE remote that alternates IR for every button on the remote. I think Girder and the USB-UIRT are not at fault here. Girder enables this workaround. The issue is really that Phillips is designing their remotes, and apparently also the Pronto, to alternate IR commands, probably for a semi-good reason, but I don't know. Sure it's a pain to learn two remote eventstrings, but the alternative would be for it not to work at all. Girder and USB-UIRT are your friends in this case, methinks.

Regards,
Stuart

[jrhees]

To avoid getting two different IR events for the same button, avoid using RC5 codes. RC5 codes are designed by nature to toggle between two codes. This is a 'debounce' tactic employed by RC5.

-Jon

[Guest]

Jon, you're right. It was the RC5 code.

I tried again a predefined ccf file with 24 IR codes (made with codegen, I guess) and they worked all fine (no "toggle" mode).

I did this test before with no success, but then I had some other problems (enabled UIRT-X compatibility mode, which should be off). After this first negative test, I tried doing from scratch, but unfortunately didn't know the important issue with RC5 code.

But at the moment, I'm happy with the working ccf files (predefined codes) and I guess, creating my own RC5x codes would also be fine know (will test this today too).

Thanks for all your hints

Best
Visar