I've kinda had this suggestion on my mind for a while and I'm wondering what others think.
Would it be possible for RM to allow you to save the configuration for multiple remotes into a single RM file?
Basically my situation is that I have my single Home Theater setup currently but have 3 different variations of atlas remotes, a comcast 1057 remote and a pair of 6690 hybrid Kameleons. A couple of them also have extenders available for them. As a result of this I have become a little disorganized when it comes to my device upgrades and probably have a dozen or more of each rm file hanging around on my system. This comes from trying out different configurations to see what I like on the different remotes, adding things to use for the extenders etc. Some of them have even been updated along the way with new codes like the discrete inputs found for my TV. Because of differences in the remotes the auto assign doesn't and couldn't handle all of switching back and forth between different remotes. Having all these very simular files ended up being a pain when I had to add codes like with my TV or went back to try testing the extender for the comcast remote.
The RM file seems to be a fairly simple text based format and I wouldn't think it would be too hard to repeat the same thing for multiple remotes in the same file. When selecting a new rdf it could scan the file to see if it had a config built for that remote and if so load it. If not proceed with the automatic button assignment process like currently happens.
Does this sound practical or does anyone else have any good suggestion on how to deal with having half a dozen different remotes?
RM Sugguestion
Moderator: Moderators
-
underquark
- Expert
- Posts: 874
- Joined: Mon Jun 20, 2005 4:58 am
- Location: UK
I can't see how having to seelct and remember which remote you're working on is going to be much easier if they are in a multiple file rather than in separate ones.
I have a spreadsheet with a page for each OEM remote. The page has a picture of the remote and columns with Function, OBC, EFC, Hex. The first page is an index page with hyperlinks to each remote.
I have a directory - JP1 Data - with a subdirectory for each OFA remote - 8040, 7562, 8910, 8910 extender, 8820, 8820 multiroom (ongoing project).
When I want to put a new device onto a remote I open RM and enter the appropriate settings (remote type, setup code, protocol etc.). I then save the file in the correct directory. Now I go to the functions page and delete everything and insert one new line and then move the OBC column to the left so it is next to the functions column.
I open the correct page in my spreadheet, copy the functions and OBC columns and paste them into RM. Then I autoassign and manually assign.
Keeping files separate - IMHO - allows a neater arrangement and you can see when you modified a particular file (you can even name them 8820 TV Panasonic 20080205, 8910ext TV Panasonic 20071222 etc. if it helps).
I have a spreadsheet with a page for each OEM remote. The page has a picture of the remote and columns with Function, OBC, EFC, Hex. The first page is an index page with hyperlinks to each remote.
I have a directory - JP1 Data - with a subdirectory for each OFA remote - 8040, 7562, 8910, 8910 extender, 8820, 8820 multiroom (ongoing project).
When I want to put a new device onto a remote I open RM and enter the appropriate settings (remote type, setup code, protocol etc.). I then save the file in the correct directory. Now I go to the functions page and delete everything and insert one new line and then move the OBC column to the left so it is next to the functions column.
I open the correct page in my spreadheet, copy the functions and OBC columns and paste them into RM. Then I autoassign and manually assign.
Keeping files separate - IMHO - allows a neater arrangement and you can see when you modified a particular file (you can even name them 8820 TV Panasonic 20080205, 8910ext TV Panasonic 20071222 etc. if it helps).