New Inteset / Insignia / Sanyo / Nexus JP1 remote

omgomg · Post by **omgomg** » Fri Feb 24, 2017 9:46 am

3FG wrote:making a new RDF will take a little bit of time.

Is there anything else I can do to help?

3FG · Post by **3FG** » Fri Feb 24, 2017 10:44 am

Yes, check your private messages.

3FG · Post by **3FG** » Sun Feb 26, 2017 12:10 am

Candidate RDF file for the Inteset INT-422-3. Previous version of the Inteset remote have had Device Specific Macro capability, so this RDF assumes that the -3 remote can also do DSMs. This should be checked.

omgomg · Post by **omgomg** » Wed Mar 01, 2017 10:47 am

Here's two recent downloads from the remote using 3FG's RDF candidate.

Raw Download: http://www.hifi-remote.com/forums/dload ... e_id=14432

RMIR: http://www.hifi-remote.com/forums/dload ... e_id=14462

Thanks![/url]

Post by **mathdon** » Thu Mar 02, 2017 12:05 pm

@omgomg
I have posted here a development build 11 of RMIR v2.04 for you to test. There are two files in that package, a replacement RemoteMaster.jar file and a revised version of 3FG's RDF. This development build supports (I hope

) the new learned signal format used by your remote. I have added an entry to 3FG's RDF to select this new format, so don't try build 11 without also using this revised RDF.

omgomg · Post by **omgomg** » Fri Mar 03, 2017 9:52 am

@mathdon
Thank you! I put those files in place, and it looks like almost all of my learned signals were recognized properly. I did notice that the "Left" signal on device D (Sony DH-520 receiver) still says protocol none, but the learned signal does work on my DH-520. I've updated my RMIR save file at http://www.hifi-remote.com/forums/dload ... e_id=14462

3FG · Post by **3FG** » Fri Mar 03, 2017 10:21 am

omgomg,
Bear in mind that decoding an unknown IR signal is intrinsically more difficult compared to a component recognizing a signal. Your Sony only needs to decide if it can interpret an incoming learned signal, even if the durations of the on and off bursts are different to the design spec. DecodeIR.dll has to try to identify the learned signal from a large set of candidate IR protocols.

I think you'll find that if you experiment a bit using various distances between the OEM remote and the learning remote, there will be an optimal distance that gives reliable decodes. Some of us IR enthusiasts have IR widgets, which allow immediate feedback on the quality of the learn, so it is easy to see that too weak or too strong signals are a problem. Either way, the durations get recorded incorrectly. Your Sony learns should have only 4 burst pairs -- lead in, 0, 1, and lead out. Two of your learns had 18 burst pairs captured. I guess that means the remotes were too close together and the IR capturing circuit was overloaded.

mikek · Post by **mikek** » Fri Apr 14, 2017 6:04 pm

I edited a map and image for the AOC version of this remote.

RDF:
http://www.hifi-remote.com/forums/dload ... e_id=14510

Map
http://www.hifi-remote.com/forums/dload ... e_id=14509

Image:
http://www.hifi-remote.com/forums/dload ... e_id=14508

Better late than never I guess.

3FG · Post by **3FG** » Sat Apr 15, 2017 12:20 pm

Those file names conflicted with existing rdf and image files, so I renamed then to AOC-67100 and 31473147(AOC 67100).rdf. I've checked these renamed files into SourceForge.

unclemiltie · Post by **unclemiltie** » Sat Apr 15, 2017 12:26 pm

Is the difference on these remotes only the names on the buttons?

Do you know if these use the "same" firmware as the Nexus 3147 remote? If so I can add this as a supported remote for the extender.

has anyone tried the extender on this remote?

mikek · Post by **mikek** » Sat Apr 15, 2017 1:30 pm

3FG wrote:Those file names conflicted with existing rdf and image files, so I renamed then to AOC-67100 and 31473147(AOC 67100).rdf. I've checked these renamed files into SourceForge.

OK. Thanks

rbautch · Post by **rbautch** » Sat Dec 02, 2017 4:16 pm

I have several versions of this Inteset remote, and I recently bought two of the INT-422-3 version. When I try to upload my RMIR file (previously developed on my 422-1 or 422-2 remotes) to the new remote, I get an error that says "writeRemote returned -1". I've run into this same error previously when moving from the original INT-422 version to the INT-422-1 version. Is there a way to use my existing RMIR file without starting from scratch with the 422-3 remote?

I'm using RemoteMaster v2.05 build 9

mdavej · Post by **mdavej** » Sat Dec 02, 2017 9:08 pm

The 422-3 is vastly different from the -1 and -2 internally. You'll have to start from scratch. You can save all your devices as -3 versions, but you'll have to rebuild all your macros from scratch. When I want to copy from one remote model to another, I open 2 sessions of RMIR side by side.

rbautch · Post by **rbautch** » Sun Dec 03, 2017 10:28 am

Good to know, thanks! I don't mind rebuilding everything, especially since it sound like the new file will be backward compatible with my older version remotes.

mdavej · Post by **mdavej** » Sun Dec 03, 2017 10:55 am

I didn’t mean to imply that. Each version needs its own set of RMIR and RMDU files. It’s the RMDU files that are easy to change to different models using the Remote drop down list.