View previous topic :: View next topic |
Author |
Message |
The Robman Site Owner
Joined: 01 Aug 2003 Posts: 21238 Location: Chicago, IL |
Posted: Fri Oct 23, 2015 1:17 pm Post subject: Al Richey's "no repeats" protocols.ini updates |
|
|
Hi Al,
I have tried to compile all the "no repeats" protocols that I could find, where you or others have posted the info.
The file is here:
http://www.hifi-remote.com/forums/dload.php?action=file&file_id=13629
All the protocols still used their original PID except for NEC1, so what I did was change NEC1 back to 005A and then for all of them, I added VariantName=slingbox, which will ensure that a protocol upgrade is added if this protocol is selected. The idea being that we can all add this to our copies of protocols.ini without causing any other problems.
The reason I did this is because, whenever I open an RM file that uses NEC1 (no repeats), RM complains because it doesn't have the protocol, so I wanted to add them to my copy of protocols.ini and I wanted an easy way to re-add them after an RM upgrade.
If you have any others that you'd like to add to the list, please post them.
Thanks,
Rob _________________ Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help! |
|
Back to top |
|
|
alanrichey Expert
Joined: 24 Mar 2008 Posts: 3529 Location: UK/USA |
Posted: Fri Oct 23, 2015 2:00 pm Post subject: |
|
|
Hi Rob
Sorry, my fault. That was posted quite some time before I was told they should have a different Variant Name. I have since updated my file but didn't upload it.
Have you actually updated the one in the File Section ? If so I don't want to overwrite it.
Al |
|
Back to top |
|
|
The Robman Site Owner
Joined: 01 Aug 2003 Posts: 21238 Location: Chicago, IL |
Posted: Fri Oct 23, 2015 2:14 pm Post subject: |
|
|
I didn't overlay your file, I loaded a new one. My file *just* has the changed protocols in it, nothing else. _________________ Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help! |
|
Back to top |
|
|
alanrichey Expert
Joined: 24 Mar 2008 Posts: 3529 Location: UK/USA |
Posted: Fri Oct 23, 2015 4:22 pm Post subject: |
|
|
Good. I'm off to bed now but I will come up with a proper combined file tomorrow. (Mind you, I see only 14 downloads in 3 years so it isn't that popular ) |
|
Back to top |
|
|
The Robman Site Owner
Joined: 01 Aug 2003 Posts: 21238 Location: Chicago, IL |
Posted: Fri Oct 23, 2015 4:40 pm Post subject: |
|
|
alanrichey wrote: | Good. I'm off to bed now but I will come up with a proper combined file tomorrow. (Mind you, I see only 14 downloads in 3 years so it isn't that popular ) |
Yeah, the general population doesn't need it, it's just the nerd squad like me 'n Vicky, lol _________________ Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help! |
|
Back to top |
|
|
vickyg2003 Site Admin
Joined: 20 Mar 2004 Posts: 7073 Location: Florida |
Posted: Fri Oct 23, 2015 7:03 pm Post subject: |
|
|
I really don't understand why these are not included in the official protocols ini. Approximately 150 of the upgrades in the file section use these non repeating protocols. Most of these upgrades don't have a repeating counterpart. I know that is a tiny fraction of the files that have been uploaded, but I don't think this is all nerd squad. I do wonder at the low count of downloads though. Perhaps people just buy new equipment. |
|
Back to top |
|
|
The Robman Site Owner
Joined: 01 Aug 2003 Posts: 21238 Location: Chicago, IL |
Posted: Fri Oct 23, 2015 10:00 pm Post subject: |
|
|
My vote is to add them to the master protocols.ini
I'd like to add them with slingbox as the variant name so as to force a protocol upgrade, but that would make the current upgrade files clash with them, unfortunately.
But, just FYI, when I come across an upgrade that uses a "no repeats" protocol, I always switch it back to the regular one. _________________ Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help! |
|
Back to top |
|
|
alanrichey Expert
Joined: 24 Mar 2008 Posts: 3529 Location: UK/USA |
Posted: Sat Oct 24, 2015 2:05 am Post subject: |
|
|
The other option would be for me to stop uploading any BIN files that use a non-repeat protocol and simply provide the user with a one-off and upload the normal one ? |
|
Back to top |
|
|
The Robman Site Owner
Joined: 01 Aug 2003 Posts: 21238 Location: Chicago, IL |
Posted: Sat Oct 24, 2015 9:20 am Post subject: |
|
|
No no, the bin files absolutely need the no repeat version of the code, or you wouldn't have created it, but the RM file that you load in the general section should have the repeating version because people will be using that in their remotes.
But if the no repeat protocols were included in protocols.ini, it would make them available to people who are creating their own Slingbox bin files. (If there is anybody doing that, I think you may have corned the market there, lol). _________________ Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help! |
|
Back to top |
|
|
alanrichey Expert
Joined: 24 Mar 2008 Posts: 3529 Location: UK/USA |
Posted: Sat Oct 24, 2015 11:54 am Post subject: |
|
|
The Robman wrote: | No no, the bin files absolutely need the no repeat version of the code, or you wouldn't have created | Not actually sure about that. It all depends on the sensitivity of the receiver and I don't thing that applies to all of the boxes of a certain type, just a few in each batch. I have certainly seen occasions where 40 people have downloaded a BIN file but only one person has seen the problem.
The Robman wrote: | But if the no repeat protocols were included in protocols.ini, it would make them available to people who are creating their own Slingbox bin files. (If there is anybody doing that, I think you may have corned the market there, lol). |
OK, not my call about whether they are included in the 'official' Protocol.ini, I'll leave that to you. |
|
Back to top |
|
|
alanrichey Expert
Joined: 24 Mar 2008 Posts: 3529 Location: UK/USA |
Posted: Mon Oct 26, 2015 2:09 pm Post subject: |
|
|
Rob: Updated your update
I added 3 more protocols I had, TDC, Zaptor and Kaseikyo-G. I made sure they had the right Variant Names but best you check anyway. |
|
Back to top |
|
|
The Robman Site Owner
Joined: 01 Aug 2003 Posts: 21238 Location: Chicago, IL |
Posted: Mon Oct 26, 2015 2:36 pm Post subject: |
|
|
Looks good Al. There's no need to leave non-S3C8 code in these entries, especially as that code probably hasn't been changed to be non-repeating, so I deleted the HCS08, etc code from those entries.
I also just standardized all the entries to have "(no repeats)" in the name (ie, plural with no caps). _________________ Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help! |
|
Back to top |
|
|
alanrichey Expert
Joined: 24 Mar 2008 Posts: 3529 Location: UK/USA |
Posted: Mon Oct 26, 2015 3:36 pm Post subject: |
|
|
Good, makes sense. |
|
Back to top |
|
|
mathdon Expert
Joined: 22 Jul 2008 Posts: 4523 Location: Cambridge, UK |
Posted: Sat Jan 16, 2016 10:44 am Post subject: |
|
|
The Robman wrote: | alanrichey wrote: | Good. I'm off to bed now but I will come up with a proper combined file tomorrow. (Mind you, I see only 14 downloads in 3 years so it isn't that popular ) |
Yeah, the general population doesn't need it, it's just the nerd squad like me 'n Vicky.
...
My vote is to add them to the master protocols.ini
I'd like to add them with slingbox as the variant name so as to force a protocol upgrade, but that would make the current upgrade files clash with them, unfortunately. |
I see that the posted set of protocols.ini entries for these no-repeat variants does have "slingbox" as variant name. I understand from Vicky that there has been opposition elsewhere to their inclusion in the public protocols.ini, presumably because they might cause confusion and very few users, perhaps just the three of you, actually need them. But if they are not in the public file then whenever an RM/RMIR update includes a protocols.ini update, they get overwritten and need to be added again by you three to your private version.
I have tried to meet any objections in this trial posting of build 13 of RM/RMIR. There is a new entry in the Options menus of both RM and RMIR, "Show Slingbox protocols", which is set unchecked by default. The setting is common to both RM and RMIR, so it doesn't matter which one you edit, the result applies to both. When this is unchecked then the loading of protocols.ini will ignore any entries with a variant name of "slingbox" or "Slingbox", so the general user will not see these entries. When it is checked then these variants are loaded. The setting, of course, is persistent as it is stored in the RemoteMaster.properties file. As it is read on loading, any change to this entry takes effect only when you close and re-open RM or RMIR.
I think you three will all have these entries in your protocols.ini, I hope with this variant name, so please try build 13 and post how you like this proposed solution. _________________ Graham |
|
Back to top |
|
|
The Robman Site Owner
Joined: 01 Aug 2003 Posts: 21238 Location: Chicago, IL |
Posted: Sat Jan 16, 2016 11:18 am Post subject: |
|
|
I certainly like the sound of it and will give it a try. Thanks Graham. _________________ Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help! |
|
Back to top |
|
|
|