GC-IRL IR Learner from global cache is cheap and works.
I've been using the GC-IRL for other systems (Savant), and I have to chime in that it's terrible. It decides the length of the IR pulse on it's own, and it's often wrong, resulting in captures that are unusable and cannot be recaptured in any other manner. For remotes that fall within it's design parameters (whatever they may be), it's fine, but you are totally out of luck if your remote doesn't fit that bill. In particular, I have had an impossible time capturing some older Pioneer LD and DVD transports.
I've been using the GC-IRL for other systems (Savant), and I have to chime in that it's terrible. It decides the length of the IR pulse on it's own, and it's often wrong, resulting in captures that are unusable and cannot be recaptured in any other manner. For remotes that fall within it's design parameters (whatever they may be), it's fine, but you are totally out of luck if your remote doesn't fit that bill.
I can confirm all of this behaviour. The learner generally produces "dirty" timing sequences and because the learner software doesn't use a capture -> recapture -> compare process like IREdit, you never know if the signal was captured properly.
I liked the small size of the GC-IRL but hated the functionality to the point where I built my own USB learner in a keyfob remote style case, then wrote a software package that allows me to read and edit AMX and Cr3stron IR files, convert between them and learn codes directly rather than having to go through the rigmarole of importing CCF codes.
The learner also has the capability of replaying IR codes from files at or after the time they are learnt so that you can check straight away whether a code will work correctly as learnt without the need to send it to a control system.
I can't understand why AMX can't produce a similar device. The world has moved on from computers the size of rooms and IR learners the size of, well, IRIS's.
That is so clean it brought a tear to my eye, that level of fab @ the DIY level is what makes me look at bigger companies and shake my head. I have been producing super clean PCBs for years, but case design has always been my bane.
So I looked more at the GC-IRL IR Learner, the biggest downside is that it's serial - something a lot of laptops (and desktops) seem to be getting away from. Sure, you could probably use a USB-to-Serial converter, but that's just another cable you need to carry with ya. Please don't think I'm dismissing the value of the GC-IRL, I'm sure it has its place, but when compared to the USB-UIRT (or the Engo piece), having a USB only solution is nice. Global Cache does have a USB solution (GB-RG1), but apparently no API driver, however the 30-72KHz learning range does make it appealing - the USB-UIRT only has a 34-40KHz and optional 56KHz receiver. Now if it had an API driver, I'd consider writing a program for it if someone bought me a piece to use / test, I just don't feel like spending another $50+ on a device for a program I'd release for free.
As we can see, there are several options out there for IR learners, we're (I'm) just limited by what kind of API there is. I'm not one for round-about hack-jobs using macros to copy and paste the Pronto hex into IREdit.
JJames,
First I'd like to thank you for writing this software and allowing us to use it free of charge. I'm posting this in order to help you develop it and improve it. I hope this can be of some value.
I've been following this thread for a while as I've recently become more "independent", and I'd like to be able to learn remotes without the hassle of getting an IRIS.
The company I used to work for had purchased the Engo Branded USB-UIRT product and we used them for years without issue. (And for those that say the Engo Product is no different, you are mistaken. The Engo software only recognizes the devices that have the altered FW from Engo). So I opted just purchase the Normal USB-UIRT (not Engo) and use your software.
I recently had a chance to use your IR program with a newly purchased USB-UIRT. I did not get the response I expected from the IR device, so I looked at the HEX code. All seemed to be well, and on multiple learnings, there were only minor differences between recaptures of the same function. After multiple unsuccessful attempts to control this IR device, I was able to find the IR file for the device and used that instead. This all got me to thinking, what exactly is going on with this IR learning system? Was it a failure of the USB-UIRT, the software, or did I somehow screw this all up?
Because I have a problem in that I need to know what's going on, with the help of a colleague, I set up a test. I used my new USB-UIRT and an Engo branded USB-UIRT with your Infraedit Software (ALPHA v 0.0.11.145) and the Engo Software on his device (v 1.04). I used the power function from the IR remote for a Samsung LN46E550 TV for this test. Here are my results: (added as code to keep it manageable)
As you can see, there were marginal differences between the IR captured using your software between devices BUT they are both different from the IR captured using the Engo Software in length. Plus the IR bursts captured by the Engo Software work in powering on and off the display, whereas none of the captured IR codes gotten using the Infraedit software worked for me.
Like I wrote JJames, I'm hoping this helps you develop the software.
Thanks for all your hard work.
(PS- the website url in the About banner in the software always gives me the "403- Forbidden" response)
I figured I'd chime in: development has stopped and has been stopped for some time. There are future plans to rewrite it, but nothing at the moment. I cannot / will not make it open source or share the code, by the way. I did this with another personal project, and have yet to hear back from the person who I gave the code to and thought I'd be collaborating with. Needless to say, it has left a bad impression on working with others.
I figured I'd chime in: development has stopped and has been stopped for some time. There are future plans to rewrite it, but nothing at the moment. I cannot / will not make it open source or share the code, by the way. I did this with another personal project, and have yet to hear back from the person who I gave the code to and thought I'd be collaborating with. Needless to say, it has left a bad impression on working with others.
Thanks for everyone's understanding.
No worries. I personally appreciate all the work you have already done, and look forward to seeing what comes of it.
Comments
I've been using the GC-IRL for other systems (Savant), and I have to chime in that it's terrible. It decides the length of the IR pulse on it's own, and it's often wrong, resulting in captures that are unusable and cannot be recaptured in any other manner. For remotes that fall within it's design parameters (whatever they may be), it's fine, but you are totally out of luck if your remote doesn't fit that bill. In particular, I have had an impossible time capturing some older Pioneer LD and DVD transports.
I can confirm all of this behaviour. The learner generally produces "dirty" timing sequences and because the learner software doesn't use a capture -> recapture -> compare process like IREdit, you never know if the signal was captured properly.
I liked the small size of the GC-IRL but hated the functionality to the point where I built my own USB learner in a keyfob remote style case, then wrote a software package that allows me to read and edit AMX and Cr3stron IR files, convert between them and learn codes directly rather than having to go through the rigmarole of importing CCF codes.
The learner also has the capability of replaying IR codes from files at or after the time they are learnt so that you can check straight away whether a code will work correctly as learnt without the need to send it to a control system.
I can't understand why AMX can't produce a similar device. The world has moved on from computers the size of rooms and IR learners the size of, well, IRIS's.
JJames,
First I'd like to thank you for writing this software and allowing us to use it free of charge. I'm posting this in order to help you develop it and improve it. I hope this can be of some value.
I've been following this thread for a while as I've recently become more "independent", and I'd like to be able to learn remotes without the hassle of getting an IRIS.
The company I used to work for had purchased the Engo Branded USB-UIRT product and we used them for years without issue. (And for those that say the Engo Product is no different, you are mistaken. The Engo software only recognizes the devices that have the altered FW from Engo). So I opted just purchase the Normal USB-UIRT (not Engo) and use your software.
I recently had a chance to use your IR program with a newly purchased USB-UIRT. I did not get the response I expected from the IR device, so I looked at the HEX code. All seemed to be well, and on multiple learnings, there were only minor differences between recaptures of the same function. After multiple unsuccessful attempts to control this IR device, I was able to find the IR file for the device and used that instead. This all got me to thinking, what exactly is going on with this IR learning system? Was it a failure of the USB-UIRT, the software, or did I somehow screw this all up?
Because I have a problem in that I need to know what's going on, with the help of a colleague, I set up a test. I used my new USB-UIRT and an Engo branded USB-UIRT with your Infraedit Software (ALPHA v 0.0.11.145) and the Engo Software on his device (v 1.04). I used the power function from the IR remote for a Samsung LN46E550 TV for this test. Here are my results: (added as code to keep it manageable)
As you can see, there were marginal differences between the IR captured using your software between devices BUT they are both different from the IR captured using the Engo Software in length. Plus the IR bursts captured by the Engo Software work in powering on and off the display, whereas none of the captured IR codes gotten using the Infraedit software worked for me.
Like I wrote JJames, I'm hoping this helps you develop the software.
Thanks for all your hard work.
(PS- the website url in the About banner in the software always gives me the "403- Forbidden" response)
Thanks for everyone's understanding.
No worries. I personally appreciate all the work you have already done, and look forward to seeing what comes of it.
And really, I hope that my post helped.