JP1 Remotes

Because the set always defaults to HDMI-1 when it was previously on some input other than HDMI-1/HDMI-2 when the 'HDMI' button is received, the two button sequence:

<comp>, <HDMI>

works just as well as the 4 button sequence above to get to HDMI-1 regardless of the starting state. The sequence to ...

On my Vizio M190 the HDMI obc=198, but it's a toggle for HDMI-1 and HDMI-2.

Right. Same for my set - but I need something foolproof that gets me to HDMI-1 regardless of the current input setting. The button sequence that I gave accomplishes this. If you want to get to HDMI-2, adding a 2nd <down ...

This link:

https://www.hifi-remote.com/forums/viewtopic.php?t=11961&sid=c1713ab442741ffdd1bed55989e8f852

suggests that such a discrete code may not exist. However it does suggest a solution via a macro:

<comp>,<input>,<down-arrow>,<OK>

I tried this and it consistently selected HDMI-1 regardless ...

I'm trying to find codes for an old smaller Vizio set -- an M220-MV. Specifically a discrete code for 'HDMI-1' (rather than the single button on the OEM remote that cycles between HDMI-1 and HDMI-2).

The closest upgrade file is:

https://www.hifi-remote.com/forums/dload.php?action=file&file_id=9205 ...

Thanks for the settings.bin file agruber11, that does confirm that there are 2 versions of this remote, yours with sig 257502 and the original with sig 257501. I have modified my RDF zip file to include RDFs for both versions.

But I think your RDF is good to go, let me know if you have any ...

Point is long press sends different commands than short. So those buttons have 2 commands each. So you need to test both.

You are right. I just tried it and long press vs short press does seem to give different results. But the problem is that the bindings are reversed -- i.e. 'long press' gives ...

"Long press of ffwd and req are the skips. So those are correct."

Well I didn't 'long press' the ffwd or rwd buttons -- but the skip codes (i.e. the codes that I bound to the 'skip' buttons in the Device Editor) were what were transmitted on short presses of ffwd or rwd.

As far as I can tell -- the .rdf has 'skip forward' and 'skip back' buttons which are not present on my remote.

The 'rewind' button appears to get the 'skip back' code
The 'fast fwd' button appears to get the 'skip forward' code



Other buttons appear to work as expected.

Hope this helps.

Thanks Rob for your efforts. I can't say whether the .rdf you created was fully functional -- but it was functional enough for me to perform the mappings that I needed. Now what do I do with the OAR04G that I ordered?

Raw File downloaded

https://www.hifi-remote.com/forums/dload ... e_id=25874

Thanks for your offer of help. I did try to figure out how 'macros' were programmed on the device -- but was unsuccessful.

I decided to order the 04G version instead which does have .rdf file available. If that doesn't work either, I'll post again.

I had done nothing like the above. Instead I had loaded pronto codes I found on the internet and modified the existing device type.

But I did try what you suggested -- but with no success. I tried to map:

HDMI Button
1 1
2 2
3 3
4 4

If I go to 'layout' -- the picture looks like my remote and ...

So I bought an OARUSB03G (probably should have bought the 4 device version) for 1 purpose only -- to get it to produce discrete HDMI input codes for an LG OLED C9 TV. I'm not planning to use the remote for anything else -- I'm simply going to have my current (non JP1) remote learn via IR learning ...