Graham,
I tried Test5 (I'm glad I made a separate RDF directory for Test6!) and Test3. Neither appears to change the memory in the remote, and looking at the Raw Data tab, I see no apparent change before and after making the assignments. Of course, Test11 doesn't change anything either. I wanted to give Alpha 21e a try, but I could only open the first device. However, that's not new behavior-- until Test 3 came out, RMIR with my ARRX12G was not really functional, so I'm very happy with the Testx series.
BTW, I'm not in any hurry to get this feature working, but I did want to give prompt feedback.
RMIR Xsight Support
Moderator: Moderators
Chris, please save your non-functioning setup as a .rmir file and post it for me to look at.
Dave, that's strange because it worked at one time and I thought I had tested it recently with Test 6 or later on my XSight Lite. Thanks for the prompt feedback. I must do more thorough testing before posting the next version, but I have been wanting to get things working for Stephen and so have only been testing that I have sorted his bugs.
Dave, that's strange because it worked at one time and I thought I had tested it recently with Test 6 or later on my XSight Lite. Thanks for the prompt feedback. I must do more thorough testing before posting the next version, but I have been wanting to get things working for Stephen and so have only been testing that I have sorted his bugs.
Graham
Sorry - I uploaded it but neglected to post the link:
https://www.hifi-remote.com/forums/dload ... e_id=12514
Thanks,
Chris
https://www.hifi-remote.com/forums/dload ... e_id=12514
Thanks,
Chris
Chris, when I load your .rmir file into my XSight Touch using Test 10, the activity macro works fine. I've checked the signal with a widget and it sends what it is set up to send. I think you may be misunderstanding activity power macros. They fire when the activity is selected, not when you press the Power button. That is nothing to do with RMIR, that is how the remote is designed and it is the same when activities are set up with EZ-RC. I don't like it, but that is the way it is.
I don't know if you are still having other issues with RMIR now that you have started your setup again from scratch. If so, please post them again so that I can look into them.
BTW Why did you switch from a Color to a Touch? I thought you liked the physical buttons of the Color for soft keys rather than the on-screen ones of the Touch. I would like to know, as I was thinking of doing the opposite. I find the on-screen buttons of my Touch often to be unresponsive, needing several presses, and the battery holds its charge for only a matter of days. I am used to the batteries in my URC 7781 lasting for years.
I don't know if you are still having other issues with RMIR now that you have started your setup again from scratch. If so, please post them again so that I can look into them.
BTW Why did you switch from a Color to a Touch? I thought you liked the physical buttons of the Color for soft keys rather than the on-screen ones of the Touch. I would like to know, as I was thinking of doing the opposite. I find the on-screen buttons of my Touch often to be unresponsive, needing several presses, and the battery holds its charge for only a matter of days. I am used to the batteries in my URC 7781 lasting for years.
Graham
Hi Graham,mathdon wrote:Chris, when I load your .rmir file into my XSight Touch using Test 10, the activity macro works fine. I've checked the signal with a widget and it sends what it is set up to send. I think you may be misunderstanding activity power macros. They fire when the activity is selected, not when you press the Power button. That is nothing to do with RMIR, that is how the remote is designed and it is the same when activities are set up with EZ-RC. I don't like it, but that is the way it is.
I don't know if you are still having other issues with RMIR now that you have started your setup again from scratch. If so, please post them again so that I can look into them.
BTW Why did you switch from a Color to a Touch? I thought you liked the physical buttons of the Color for soft keys rather than the on-screen ones of the Touch. I would like to know, as I was thinking of doing the opposite. I find the on-screen buttons of my Touch often to be unresponsive, needing several presses, and the battery holds its charge for only a matter of days. I am used to the batteries in my URC 7781 lasting for years.
No - definitely not misunderstanding how the activity macros work. On my remotes when I select the activity there is no IR signal sent at all. I will try again with a 981 reset and see if that makes a difference. Is there any chance there is a difference between the AR remotes and OFA remotes? I know that I had one with an old firmware that liked RMIR even less until I upgraded it.
As to the switch from Color to Touch - I definitely wish the Touch had the hard buttons. But the form factor and weight of the Touch is just much nicer. The battery life of the Color leaves a lot to be desired too, and though the touch doesn't last all that long (I get about 10 days) I have multiples with one always on the charging base.
I agree on the touch screen though - I am going to start putting functions on the color keys and leave the touch screen for the muggles.
Chris
Graham,
I've been lurking for a while and trying the new versions. It's looking really good.
I find that in some cases when adding new devices, a setup code doesn't get assigned, and the upgrade doesn't work (doesn't send any signal). In cases where I open an existing RMDU which has a setup code, the upgrade does work. Could this missing setup code be the culprit? I'll try to get you some files and examples to reproduce the behavior.
I also wanted to ask a question about editing macros. On some of my files, I can edit macros and press ok, and the popup closes and all is well. But on others, pressing OK does nothing, and the window stays open, and the macro is not saved. What might cause this?
I have a few other bug reports I'll be posting later.
I've been lurking for a while and trying the new versions. It's looking really good.
I find that in some cases when adding new devices, a setup code doesn't get assigned, and the upgrade doesn't work (doesn't send any signal). In cases where I open an existing RMDU which has a setup code, the upgrade does work. Could this missing setup code be the culprit? I'll try to get you some files and examples to reproduce the behavior.
I also wanted to ask a question about editing macros. On some of my files, I can edit macros and press ok, and the popup closes and all is well. But on others, pressing OK does nothing, and the window stays open, and the macro is not saved. What might cause this?
I have a few other bug reports I'll be posting later.
Ah, Chris, I think I've found it. It seems that you are a victim of the same problem that Stephen had. Out of all that enormous raw data, loading your file into RMIR changes four bytes. I missed that when I first looked. I think you will find that if you load your .rmir file into your remote, the activity macro will work as intended. The saving and re-loading has removed an inconsistency in the data.
It is almost impossible to track down what caused the inconsistency. If I delete the activity macro, save the result as a .rmir file, re-load it and then re-create the macro, the bytes are as they should be. It seems as if something else you did caused the corruption, most likely causing the dreaded Null Pointer Exception
. I have identified one or two minor errors that could have been responsible, but the best I can do is post the new version and see how you get on with it. I'll do some more testing first, though, as I think I have given you a way to fix your immediate problem.
If you continue using Test 10 and get this happening again, please post the rmaster.err file. That may give me a clue as to the cause.
It is almost impossible to track down what caused the inconsistency. If I delete the activity macro, save the result as a .rmir file, re-load it and then re-create the macro, the bytes are as they should be. It seems as if something else you did caused the corruption, most likely causing the dreaded Null Pointer Exception
. I have identified one or two minor errors that could have been responsible, but the best I can do is post the new version and see how you get on with it. I'll do some more testing first, though, as I think I have given you a way to fix your immediate problem.If you continue using Test 10 and get this happening again, please post the rmaster.err file. That may give me a clue as to the cause.
Graham
Wow, some good news for oncemdavej wrote:I've been lurking for a while and trying the new versions. It's looking really good.
.How are you adding the device? If you are creating one in the Device Upgrade Editor, you need to give a setup code in the top line. It doesn't get assigned automatically. Or do you mean that you give one but it disappears when you press OK?I find that in some cases when adding new devices, a setup code doesn't get assigned
That looks like the dreaded Null Pointer Exception againOn some of my files, I can edit macros and press ok, and the popup closes and all is well. But on others, pressing OK does nothing, and the window stays open, and the macro is not saved. What might cause this?
. See if there is traceback in the rmaster.err file when it happens, and if so, post it for me to look at.Graham
I can't seem to reproduce the device setup code error at the moment. Seems like it may have occurred if I started with an existing device in EZRC which was entirely learns, not a built in code. If I then edited that device and opened an existing RMDU, the newly assigned setup code did not stick. Perhaps just a refresh issue, as described in the next paragraph.
If I add a new device on the devices tab, it appears on the general tab, but not on the devices tab. It's as if the devices tab isn't refreshed after the device is added.
As for the macro, I didn't see anything in the err file. But you can reproduce it if you assign the macro bound key to a Soft button. Any other button works.
Another thing I noticed on Favorites was Send Final Key may be incorrect in some cases. In EZRC, that option was false. But when downloading that from my remote, it got set to true with a Null key.
This is all on test 10 and an Xsight 18G.
If I add a new device on the devices tab, it appears on the general tab, but not on the devices tab. It's as if the devices tab isn't refreshed after the device is added.
As for the macro, I didn't see anything in the err file. But you can reproduce it if you assign the macro bound key to a Soft button. Any other button works.
Another thing I noticed on Favorites was Send Final Key may be incorrect in some cases. In EZRC, that option was false. But when downloading that from my remote, it got set to true with a Null key.
This is all on test 10 and an Xsight 18G.
Wrongmathdon wrote:It is almost impossible to track down what caused the inconsistency.
. I've found it. It happens when you create a new device and use it in a macro without a save/re-load or upload/download stage in between. Easy to fix now I've found it.I managed to reproduce this, too, in locating the above bug and can fix that, too. That one IS a Null Pointer Exceptionmdavej wrote:I can't seem to reproduce the device setup code error at the moment.
.Graham
Graham,
Your touch screen complaints got me thinking. I am going to order these:
http://www.amazon.com/gp/product/B001JT ... CVB9A2IXYG
Will let you know how they work.
Chris
Your touch screen complaints got me thinking. I am going to order these:
http://www.amazon.com/gp/product/B001JT ... CVB9A2IXYG
Will let you know how they work.
Chris
Graham,
Just wanted to tell you how well favorites icons are working. I added a few more the other day and it was a breeze. Just to remind people how they work, I've updated the original post with some info and links that I had posted elsewhere in the thread.
And here's a little tip for those with Sony devices. RMIR really wants to use Sony (12/15/20) combo for all, even simple devices that use only one of those three. I tried to keep mine as simple as possible and changed protocols when I didn't really need the combo, but this did not work well, as each new download would insist on the combo protocol. So if you just leave it alone, it works fine. Don't try to change protocols like I did. Same goes for other combo protocols like Denon.
Just wanted to tell you how well favorites icons are working. I added a few more the other day and it was a breeze. Just to remind people how they work, I've updated the original post with some info and links that I had posted elsewhere in the thread.
And here's a little tip for those with Sony devices. RMIR really wants to use Sony (12/15/20) combo for all, even simple devices that use only one of those three. I tried to keep mine as simple as possible and changed protocols when I didn't really need the combo, but this did not work well, as each new download would insist on the combo protocol. So if you just leave it alone, it works fine. Don't try to change protocols like I did. Same goes for other combo protocols like Denon.
Update on the Win 8 and 8.1 connection issue. Audiovox support here in the US has stated that it won't work and will never be fixed since the remote is discontinued here. If any fixes or updates for the conduit show up in Europe or elsewhere, please let us know. I have successfully downloaded the Euro version of the conduit, but it still doesn't work properly in 8.1 (I had it working in Win 8, in spite of what support said). Note that this affects both EZ-RC and RMIR. See the first post in the thread for more details.
It's not really a big deal to me since I'll probably have access to Win 7 machines for years to come, but it does make programming a bit less convenient.
It's not really a big deal to me since I'll probably have access to Win 7 machines for years to come, but it does make programming a bit less convenient.