JP1 Remotes

Vicky,
If you want to download RMIR.....
http://www.hifi-remote.com/forums/dload ... le_id=8819

Really sorry if I am being repetitive, but I do suggest watching my video if you have never used it before to get started...

http://www.youtube.com/watch?v=mB6mAHqeW3I

xnappo

I must be hallucinating. I spent 48 minutes looking for it, and then came in and found a link from Dave that led me right to it, and now I came back to thank him and there is no link here!

vickyg2003 wrote:I must be hallucinating. I spent 48 minutes looking for it, and then came in and found a link from Dave that led me right to it, and now I came back to thank him and there is no link here!

Here is the latest 'preview' release:
http://www.hifi-remote.com/forums/dload ... le_id=8819

RM and RM-IR are, and always have been, the same thing, but in the new version RM-IR is the default...
xnappo

Hmm I must have been, because now dave's post is back.

Thanks xnappo, I looked at your video. It was very helpful.

I must say this needs a lot of work. I downloaded from my remote and tried to save the RMIR but the RMIR file is empty.

I now understand what is going on in RM and keymove and must say I really don't like this level of integration.

How do you share your rdmu files? Are they going to be in the RMIR files? Do I have to create the upgrade for every remote?

Then do I have to fix the upgrade for every file?

vickyg2003 wrote:
I must say this needs a lot of work. I downloaded from my remote and tried to save the RMIR but the RMIR file is empty.

This is quite possibly an RDF issue

I now understand what is going on in RM and keymove and must say I really don't like this level of integration.

Well I love this level of integration, so we need to make it work for everyone's taste. Specifics please!

How do you share your rdmu files? Are they going to be in the RMIR files? Do I have to create the upgrade for every remote?

There is no change here - sharing is not comprimised. Just click 'edit' on an upgrade then hit 'save' to make an RMDU.

xnappo

RMDU files will continue to exist, but RMIR files will replace IR files.

Even though the RMIR image is now the first thing that you see, if all you want to do is edit an RMDU file (or a KM file) you still can and the steps are exactly the same as before, in other words, File > Open > select a file. Once the RM/KM file is selected, a second UI will open which will be RM.

So what is it doing when you hit "edit" on any of the device entries?

So far none of the remotes I have tried, allow me to save an RMIR, so I'm kind of shooting in the dark here.

I know saving RMIR files works for some people, because I've opened their RMIR files.

vickyg2003 wrote:I downloaded from my remote and tried to save the RMIR but the RMIR file is empty.

I had a similar issue due to an upgrade pointing to a nonexistent protocol. IR allows this, but RMIR doesn't. Greg is working on a fix.

mdavej wrote:

vickyg2003 wrote:I downloaded from my remote and tried to save the RMIR but the RMIR file is empty.

I had a similar issue due to an upgrade pointing to a nonexistent protocol. IR allows this, but RMIR doesn't. Greg is working on a fix.

well that could very well be my problem. These are my bench remotes, where I load upgrades and OP's setups to diagnose problems.

Nope, that's not my problem, I just did a 981 and I'm still getting an empty RMIR even with no device upgrades, but JP1.2 remotes are not yet totally supported for upload, so they may not be supported for SAVE either..

So how do you keep your device upgrades centralized? Everytime you edit your RM file do you need to have two RM sessions open that look exactly alike, one that's holding what's in RMIR, and the other with your master RM file? If so, how do you keep track of whichi is which? OR do you abandon the RM master file for each piece of equipment you own?

Edit: Oh I see the difference one has a menu.

I do have some constructive things to say.

RMIR Font/Row Height: There isn't enough white space on the various rows in RMIR. RM is just a little bit bigger and a little bit whiter, and a heck of a lot easier to read. I'd like to see RMIR have that same larger font where possible.


The Upgrade EDIT screen: The location of [load][import][save][ok][cancel] buttons is bad. When they are below the tabs, they look like they don't belong to this screen. They look like they are just part of another screen below this one. If they were located above the tab control, then it would be easier to digest what is on the screen. However the bottom of the screen is consistent with the other RM and RMIR screens, so most people are probably fine with that. Its just the 3-d effect of the tabs control that makes the [load][import][save][ok][cancel] button that looks like they are not part of the same screen. Or perhaps this is just me.

gfb107 wrote:RMIR is taking over. You can get to RM by opening a .rmdu or (KM) .txt file, or by File > New > Device Upgrade

I am afraid I have to report I just cannot live with the new logic of folding RM into RMIR. I get the impression this is being forced through based on how a few people use the software tools, without realising there are other people out here who use the tools completely differently, and are thus being screwed by the changes.

I tend use the 'Recent' function of RM a lot, and that used to be easy: Click on the shortcut, select File > Recent and I was good to go. Now I have to go through the (completely unnecessary) extra steps of opening RMIR and then selecting the 'New > Device Upgrade' option to get a clean copy of RM before I can use the function (and also have an extra useless window I have to minimise to keep out of the way).

And the final straw this morning was when I exited out of RM and it asked me if I wanted to save the Upgrade. I realised I had made an error and hit the Cancel button and it just dumped RM completely, putting me back into RMIR and I lost everything.

So unless I can have a shortcut to get a standalone copy of RM running I am afraid I have to revert back to V1.99 and just hope that it remains supported.

Sorry

Al

Are the protocols being hidden too, or is that just an error? 99% of what I do with IR involves variations of Protocol 01FF. I've added several devices that use custom protocols, but the protocol tab is blank, and there is no information telling me that I have a conflict in protocols. There is no way to tell which version of 01FF is being used.

Finding out which of the 8 upgrades in IR is using 01FF is important to me, if this is hidden, its going to be a lot more work to use RMIR than it is to use IR.

vickyg2003 wrote:Are the protocols being hidden too, or is that just an error? 99% of what I do with IR involves variations of Protocol 01FF. I've added several devices that use custom protocols, but the protocol tab is blank, and there is no information telling me that I have a conflict in protocols. There is no way to tell which version of 01FF is being used.

Finding out which of the 8 upgrades in IR is using 01FF is important to me, if this is hidden, its going to be a lot more work to use RMIR than it is to use IR.

The protocol viewer/disassembler just is not implemented yet in the 'IR' side. Of course you can go into each upgrade and look, but I agree that is not I nice way to find it.

A reminder to everyone that this is a preview release. The idea is to find areas that need improvement before even a beta release. Ideally thinking outside of the box rather than knee-jerk 'put it back the way it was/copy IR'. Though that may be the right thing to do, please also think about other options.

xnappo

vickyg2003 wrote:JP1.2 remotes are not yet totally supported for upload

Where do you get that from? If you are using the latest preview version, all remotes except JP1.1 should be fully supported. Even the WinUSB driver for the Delcom chip is supported. However, RMIR is fussier about needing the RDF to be correct than is IR.exe. This is not the fault of RMIR, it arises because RMIR is inherently more powerful than IR.exe, even if much of that power remains to be developed.

I am aware of certain RDFs in the latest release that have line break problems. There needs to be a blank line separating the RDF sections, and no blank lines within a section. I have found, in random testing, some RDFs in which two sections are not separated in this way. I was going to post that in the appropriate forum but haven't yet got round to it. That is one thing worth checking.