<p dir="ltr"><br>
On 1 Oct 2013 13:16, "Erik Hjertén" <<a href="mailto:erik@hjerten.com">erik@hjerten.com</a>> wrote:<br>
><br>
> Ok, then we know it's transmitting. Are they blinking roughly at the same rate?</p>
<p dir="ltr">I think so... But I might need to look more closely. It's also possible that the camera shutter/sensor/whatever isn't fast enough to capture the flickering... I'll try to check... <br></p>
<p dir="ltr">><br>
> Did you test with different keys? Like power on/off, changing channel, numbers etc? Did you also try at with the USB-UIRT further away?</p>
<p dir="ltr">While testing the emitting portion, I was using mail the "select" key, since that's used to turn the box "on", and therefore would be the easiest to see whether it's responding. I was planning to record only the numbers, Select, and maybe Exit. </p>
<p dir="ltr">Power is actually slightly more difficult to record because it is programmed (by the Bell guy who installed everything) to transmit to the box and the TV. And I haven't looked into disabling that "feature" :-) </p>
<p dir="ltr">I think the first time I tried recording I had the remote pretty close to the receiver, to avoid the box responding to the button presses. When I tried it again yesterday I was further back, maybe half a metre or so. <br>
</p>
<p dir="ltr">><br>
> There is a -a switch for irrecord to "analyse" the RAW codes. I don't really know what that does, but I recall reading something about that being important. Grasping here...</p>
<p dir="ltr">I think I tried that too. It did "something" (generated a new file, I think) but it didn't help. </p>
<p dir="ltr">><br>
> When you run irrecord (not in RAW mode), does it seem to "get it" right away or do you need to press the buttons for a long time? I had some issues before with different remotes that didn't really worked right away. Fiddling with parameters in the config file helped a bit then.</p>
<p dir="ltr">I found I had to hold the button for a long time. It would often fail immediately and as I held the button it would retry and retry and eventually get it. </p>
<p dir="ltr">The Select button took the longest to finally "get". </p>
<p dir="ltr">><br>
> Fresh batteries in the remote?</p>
<p dir="ltr">Relatively... I've only had it for four or five months, and presumably the batteries were fresh at that point. </p>
<p dir="ltr">That reminds me I need new batteries for my Hauppauge remote, though :-) </p>
<p dir="ltr">><br>
> I'm running out of ideas. Was it the vip2262 you have there? Google is our friend...</p>
<p dir="ltr">I believe that's the model, yes. Up until very recently I've not been very successful with Google searching for these terms, but I seem to be getting more useful results of late.. Or at least more relevant... </p>
<p dir="ltr">Thank you for your suggestions. At least I know I'm not missing something silly :-) </p>
<p dir="ltr">I noticed that irrecord always seems to be using the uirt2_raw driver (I think), although I've seen mention that it should be using usb_uirt_raw. I wonder if that has anything to do with it... I thought I found a bug report saying it's using the wrong driver, but maybe I misread... </p>
<p dir="ltr">I was thinking maybe I could use the Hauppauge in sensor to record the keys... But I recall reading here that it only recognises the Hauppauge protocol.... RC5? Something like that. </p>
<p dir="ltr">Aaron<br>
</p>