|
Slink-e / CDJ Discussion Archive #1 Re: How to decode unknown commands with OCXPosted By: Colby Boles <cboles@s...> In Response To: Re: How to decode unknown commands with OCX (Jon Welfringer)
The data you are seeing is the raw Slink-e output, showing you the IR on an off periods in microseconds. This may not be what you want. The Slink-e software does a lot of processing to convert these numbers into binary for a particular device. If your goal is to create device files, you don't need to load lowlevel.cde. Instead what you want to do is load a device file containing the timing information for the device you want to decode. These are the .cde files like sonyir.cde. I have made these for most brands. Once you do this, you should get a nomatch:irX(group)[100111....] message when you push a remote button. This is the binary info you want to create device file commands. Sorry I'm being so short - I'm in the process of writing a program to do this stuff for you, so I don't want to take too long explaining it. This process is detail more on some other threads on the website. Colby
Slink-e / CDJ Discussion Archive #1 is maintained by slinke-bbs-owner@nirvis.com with WebBBS 3.21. |