JP1 Remotes

I've figured out the issues you found. I should have a new beta for you to try later today.

I don't really know what's going on with the 0042 protocol. Either it isn't actually present in your remote, or the variant in your remote is different and incompatible with the protocols.ini definition. I'm afraid you'll need help from the real experts on this one.

gfb107 wrote:I've figured out the issues you found. I should have a new beta for you to try later today.

I don't really know what's going on with the 0042 protocol. Either it isn't actually present in your remote, or the variant in your remote is different and incompatible with the protocols.ini definition. I'm afraid you'll need help from the real experts on this one.

Thanks!

Just FYI(for now, full report later) - I did find another problem last night. I have two devices that use the MCE protocol with VERY similar configurations. Somehow whenever I load the second one (into RM-IR), the fixed data of the first gets corrupted. Again - I will post more info tonight.

xnappo

I remember a bug like this in the very early days of RMIR. Thought this was fixed. Definitely want to fix this in the next beta.

gfb107 wrote:I remember a bug like this in the very early days of RMIR. Thought this was fixed. Definitely want to fix this in the next beta.

Hi Greg,

I've uploaded a debug zip here:
https://www.hifi-remote.com/forums/dload ... le_id=8290

I included the rmir file and rdf. 1052 and 1053 are my two MCE protocol devices. 1052 is the 'Windows Media Center v2_xnappo' upgrade and 1053 is the 'xbox_360_universal_media_remote' upgrade. If you reload either of them, you will (hopefully) see that the Fixed Data of the other changes to match.

Thanks!
xnappo

P.S. once we get through all this, I will start from scratch to make sure everything is fixed. I really appreciate your work!

I've just uploaded the Java version of v1.98beta8 that should address your issues. Working on the Windows standalone version now, but it takes a lot more work to build and a lot longer to upload.

gfb107 wrote:I've just uploaded the Java version of v1.98beta8 that should address your issues. Working on the Windows standalone version now, but it takes a lot more work to build and a lot longer to upload.

Very cool. A quick check looks good! Especially the 'two devices with the same protocol' issue!

Thanks!

I will do more detailed testing to make sure - and as I said do a start-from-scratch test this weekend.

xnappo

The Windows version of RM v1.98beta8 is now available.

Hi Greg,

Another minor problem - in the DSM definition window, the extender device selection macros do not show up. For my particular case, the temporary device selection (X_<dev>) is what I would normally use.

Thanks!
xnappo

And another small one - when switching between two .rmir files, or downloading from a remote that doesn't match the .rmir file currently loaded, the 'Devices' tab does not update (it stays with what was previously loaded).

Thanks,
xnappo

P.S. I completed the experiment with starting from scratch and can confirm all the bugs you have fixed to date for me are fixed.

gfb107 wrote:The Windows version of RM v1.98beta8 is now available.

Hi Greg I believe something got busted in beta 8 I was trying to build an upgrade this evening and the NEC1 Protocol does not work as expected.

Try this

Setup code = 2000
Protocol = NEC1
Device Number = 132
Sub Device = 121

The Fixed Data should change to 20 DE 61 but nothing changes and if you go to another tab all the data you have just entered is gone. Beta 7 worked just fine.

Thanks,
dolivas

Same thing happens with Linux java version. Luckily I didn't try and build anything with this. If you load an older upgrade, the data comes in right.

I would expect both the Windows standalone and the pure Java versions (regardless of platform) to always behave the same.

The areas where this might not be true are:

1. Minor UI layout differences
2. Remote IO

It's not just NEC1. It's all of them (At least all I tried). As long as you use an upgrade built with an earlier version and don't mess with the device params, beta 8 will work. But don't try and build an upgarde with this. It won't work unless device params or all null.

I'll just confirm that is the case for me too - changes to device number/ subdevice don't "stick" or cause fixed data to update - as though your typed changes aren't being "committed" - and they do indeed vanish if you switch tabs -or try to save the upgrade.

Could it perhaps be an unintended consequence of the recent "fix" for data not saving if you don't "move out of" a cell which alanrichey reported ?

It's an unintended consequence of the fix for the "corruption of fixed data when multiple upgrades use the same protocol" that xnappo reported.