The instructions you read were for working with IR, not RMIR.Pulse wrote: Until recently I had always been doing an upgrade by cutting and pasting that Hex data from the output window of "Remotemaster" and using the "import raw" button in "RMIR" as I thought this was the way it was supposed to be done (I read it somewhere, cant find where now). and it always worked!
Always wondered why there were 2 pieces of software, I guess RemoteMaster slots into RMIR, but I had always regarded them as 2 seperate entities
But now I have seen the light......
OneForAll URC-7950 Comfort Line 5
Moderator: Moderators
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
The instructions you read were for working with IR, not RMIR.
Ah yes!! thank you Vicky thats right, when I first started I could never connect to my remote with RMIR only IR for some reason , then at some point switched to RMIR and continued upgrading in the same way.
RMIR allows me to upload using the URC-7950 RDF to my URC-7940 and URC-7930 giving me phantom devices, IR doesnt seem to want to.....but maybe I'm bumbling again
This may not be unusual with JP1 remotes, but for some reason (perhaps because their function is already global and takes precedence like a macro) with URC-7950 and Samsung F8000 the Tv's input commands don't work if allocated directly to (unshifted) Device Mode buttons, or even when keymoved to them as i suggested earlier...
- the updated image uses macros on the Mode buttons containing the Tv Hdmi commands on shifted phantom buttons, which does get the Tv inputs to work.
As usual, the reason for employing phantoms is just to save 'wasting' real buttons.
https://www.hifi-remote.com/forums/dload ... e_id=12156
- the updated image uses macros on the Mode buttons containing the Tv Hdmi commands on shifted phantom buttons, which does get the Tv inputs to work.
As usual, the reason for employing phantoms is just to save 'wasting' real buttons.
https://www.hifi-remote.com/forums/dload ... e_id=12156
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
Hi Chris, those are some pretty strange looking device macros. To tell you the truth I have no idea on what the remote would even do with that, without some sort of extender.
The reason I'm writing though is that I one of the things that RMIR trains you to do is not necessarily the best. That is you have all the HDMI selections in TV mode. Instead of doing it that way, think of putting the HDMI selection in its proper device mode, So instead of using 5 shifted phantoms in one mode, use 1 phantom key in 5 modes. If you get your head around that keymove feature, things will be much simpler and easier to read.
The reason I'm writing though is that I one of the things that RMIR trains you to do is not necessarily the best. That is you have all the HDMI selections in TV mode. Instead of doing it that way, think of putting the HDMI selection in its proper device mode, So instead of using 5 shifted phantoms in one mode, use 1 phantom key in 5 modes. If you get your head around that keymove feature, things will be much simpler and easier to read.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Yes I have now set up something similar with my macros on the phantoms and keymoved to the device button...works very well thanks.
I have also done this with the power button so whenever this is pressed (unshifted) it sends discrete off commands to all my devices whatever mode it is in. (whether the devices are powered on or not)
I have also done this with the power button so whenever this is pressed (unshifted) it sends discrete off commands to all my devices whatever mode it is in. (whether the devices are powered on or not)
Vicky is this what you mean? taking the power button in my case as the example in the keymoves, thanks in advanceThe reason I'm writing though is that I one of the things that RMIR trains you to do is not necessarily the best. That is you have all the HDMI selections in TV mode. Instead of doing it that way, think of putting the HDMI selection in its proper device mode, So instead of using 5 shifted phantoms in one mode, use 1 phantom key in 5 modes. If you get your head around that keymove feature, things will be much simpler and easier to read.
https://www.hifi-remote.com/forums/dload ... e_id=12160
Thanks Vicky for looking in and advice.
I think you have suggested doing a keymove for each input from a key in the Tv device to a phantom button in the relevant device, and then keymove that phantom to its device selection button?
If so, because there are few spare buttons in TV, wouldn't I have to first put each Tv input either onto a shifted key or phantom key in the TV device?
Other considerations are that the two Humaxes are left in low power standby, for occasional use, and BluRay and DMR don't have low power standby so they are on mains switches and take even longer to get going, which does not matter since they are less often used. It follows from all that, apart from Tv, it is best to sit in Tv mode while waiting to get hard drives spun up and ready to show a picture. Tv has a USB hard drive for recording programmes so we use that more than the PVRs.
The BluRay/Home theatre gets most used for its speakers when we are watching a film with accented mumbling on Tv, but the Tv has to have 'anynet+' CEC setting on to be able to switch to 'receiver' for optical input. This can only be done automatically when Tv senses the Hdmi3 device AMP is powered up, but we still want to watch Tv once it has sorted that out, and have to get round a BluRay input selection manually! It remembers the last setting but goes to 'home' at start up and needs 'input I-pod' to bump back to the last input instead of going round a loop of inputs.
I did try keymoves for Tv inputs to mode buttons but don't think that worked, hence the weird device macros, which do the job. It's work in progress so your further comments would be appreciated. I am really liking the 7950 for its simple buttons and fast action compared to rather ponderous Harmony's and lcds.
I think you have suggested doing a keymove for each input from a key in the Tv device to a phantom button in the relevant device, and then keymove that phantom to its device selection button?
If so, because there are few spare buttons in TV, wouldn't I have to first put each Tv input either onto a shifted key or phantom key in the TV device?
Other considerations are that the two Humaxes are left in low power standby, for occasional use, and BluRay and DMR don't have low power standby so they are on mains switches and take even longer to get going, which does not matter since they are less often used. It follows from all that, apart from Tv, it is best to sit in Tv mode while waiting to get hard drives spun up and ready to show a picture. Tv has a USB hard drive for recording programmes so we use that more than the PVRs.
The BluRay/Home theatre gets most used for its speakers when we are watching a film with accented mumbling on Tv, but the Tv has to have 'anynet+' CEC setting on to be able to switch to 'receiver' for optical input. This can only be done automatically when Tv senses the Hdmi3 device AMP is powered up, but we still want to watch Tv once it has sorted that out, and have to get round a BluRay input selection manually! It remembers the last setting but goes to 'home' at start up and needs 'input I-pod' to bump back to the last input instead of going round a loop of inputs.
I did try keymoves for Tv inputs to mode buttons but don't think that worked, hence the weird device macros, which do the job. It's work in progress so your further comments would be appreciated. I am really liking the 7950 for its simple buttons and fast action compared to rather ponderous Harmony's and lcds.
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
I've never seen a macro call a macro in an unextended remote. Really if the TV button is a macro and then the first step in the macro is to call the TV button again, how is that supposed to work. I popped open the urc-7950 to see how macros on device keys are supposed to be implemented, and couldn't find any hint that it is even allowed. The only thing I saw in regards to macros on the device keys, is that you can't assign a macro to a shifted device key.
On the few remotes that I have, that do allow macros in the device keys, they were only activated on a long keypress, and again, nested macros were never allowed.
Since the smart guys who put the RDF's together, allow you to put macros on the device key, it probably means that macros are allowed, but I'm not sure what scheme they are using. Is it the long keypress method that was used in some JP1.2 remotes? I really have no idea.
On the few remotes that I have, that do allow macros in the device keys, they were only activated on a long keypress, and again, nested macros were never allowed.
Since the smart guys who put the RDF's together, allow you to put macros on the device key, it probably means that macros are allowed, but I'm not sure what scheme they are using. Is it the long keypress method that was used in some JP1.2 remotes? I really have no idea.
I am suggesting that you do a keymove for each input from a FUNCTION in the TV device to a button (phantom, or shifted) on the relevant device.I think you have suggested doing a keymove for each input from a key in the Tv device to a phantom button in the relevant device, and then keymove that phantom to its device selection button?
No, there is no need to have them in the TV mode. I prefer to use a key like Shift-3 on all device modes be the appropriate input selection on the TV,If so, because there are few spare buttons in TV, wouldn't I have to first put each Tv input either onto a shifted key or phantom key in the TV device
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
I agree , this is confusing but it actually works. (in my case)Really if the TV button is a macro and then the first step in the macro is to call the TV button again, how is that supposed to work.
It's as if , when the Device button is physically pressed it calls the Macro, but when called from within a macro calls the Device mode.
hope this makes sense
Thank you - if I ever knew it I had forgotten, or overlooked the possibility of keymoving a function, and that works fine now, even on Tv mode button for its own Input, and obviates the need for the impossible macrosvickyg2003 wrote:I am suggesting that you do a keymove for each input from a FUNCTION in the TV device to a button (phantom, or shifted) on the relevant device.I think you have suggested doing a keymove for each input from a key in the Tv device to a phantom button in the relevant device, and then keymove that phantom to its device selection button?
No, there is no need to have them in the TV mode. I prefer to use a key like Shift-3 on all device modes be the appropriate input selection on the TV,If so, because there are few spare buttons in TV, wouldn't I have to first put each Tv input either onto a shifted key or phantom key in the TV device
vickyg2003 wrote:... I popped open the urc-7950 to see how macros on device keys are supposed to be implemented, and couldn't find any hint that it is even allowed. The only thing I saw in regards to macros on the device keys, is that you can't assign a macro to a shifted device key...
- Needed a method of turning on/off the two PVR devices with one button from any mode and these ones do work ok:-
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
Just to get my head around how this is being processed by the remote, when switching from TV to SAT do you need to press the SAT key once or twice to get this to work it to select the HDMI?tranx wrote:Thank you - if I ever knew it I had forgotten, or overlooked the possibility of keymoving a function, and that works fine now, even on Tv mode button for its own Input, and obviates the need for the impossible macrosvickyg2003 wrote:I am suggesting that you do a keymove for each input from a FUNCTION in the TV device to a button (phantom, or shifted) on the relevant device.I think you have suggested doing a keymove for each input from a key in the Tv device to a phantom button in the relevant device, and then keymove that phantom to its device selection button?
No, there is no need to have them in the TV mode. I prefer to use a key like Shift-3 on all device modes be the appropriate input selection on the TV,If so, because there are few spare buttons in TV, wouldn't I have to first put each Tv input either onto a shifted key or phantom key in the TV device
Re. '...do a keymove for each input from a FUNCTION in the TV device to a button (phantom, or shifted) on the relevant device'
and
'...when switching from TV to SAT do you need to press the SAT key once or twice to get this to work to select the HDMI?'
May have misunderstood and #1. was to show what (I thought) you had described, but now think you may have meant InputTv should be on SAT-shift-3, to go back to Tv mode?
(One of the PVR's (FoxSat HD) is the device 'SAT' and requires Hdmi1).
Should have made it clear that #2 was chosen as an alternative, which selects Hdmi1 with one press of the SAT button, and works in any mode.
Thought it had not worked when Hdmi1 had been keymoved to TV's-SAT button - but find it does work, in #2, when Hdmi1 is keymoved to SAT's-SAT button.
and
'...when switching from TV to SAT do you need to press the SAT key once or twice to get this to work to select the HDMI?'
May have misunderstood and #1. was to show what (I thought) you had described, but now think you may have meant InputTv should be on SAT-shift-3, to go back to Tv mode?
(One of the PVR's (FoxSat HD) is the device 'SAT' and requires Hdmi1).
Should have made it clear that #2 was chosen as an alternative, which selects Hdmi1 with one press of the SAT button, and works in any mode.
Thought it had not worked when Hdmi1 had been keymoved to TV's-SAT button - but find it does work, in #2, when Hdmi1 is keymoved to SAT's-SAT button.
In the buttons tab of the TV device are shown buttons 82, 92, 93, 94, and 95 which seem to have had the Tv's inputs Hdmi1, 2, 3, 4, and InputTv allocated to them, which must have happened automatically/behind the scenes.
The titles of the device buttons and phantom buttons have a '*' symbol attached to them and are marked in red, and FF and Rew are also in red.
What does all that signify please?
(The Tv inputs were once put on the phantom buttons 1 to 5, but those allocations have since been removed)
The titles of the device buttons and phantom buttons have a '*' symbol attached to them and are marked in red, and FF and Rew are also in red.
What does all that signify please?
(The Tv inputs were once put on the phantom buttons 1 to 5, but those allocations have since been removed)