RemoteMaster v1.83 is now available!

mdavej · Post by **mdavej** » Thu Mar 06, 2008 10:15 am

Capn,

One in particular that needs improving is the Pause protocol. I just tried to use it and couldn't quite figure it out without looking at the KM notes, which are more complete. However, the bit at the end of the notes about the keymoves sheet of course doesn't apply to RM. Those types of KM specific references are something to watch out for.

Thanks in advance for your efforts on this.

mr_d_p_gumby · Post by **mr_d_p_gumby** » Fri Mar 07, 2008 12:55 pm

mdavej wrote:One in particular that needs improving is the Pause protocol.

Capn, be careful with the Pause protocol help. KM calculates different delay times on the Protocol Help sheet depending on which processor is used by the currently selected remote. AFAIK, RM does not have a way to do this with protocol comments, so you may have to show all the variations.

Capn Trips · Post by **Capn Trips** » Fri Mar 07, 2008 1:02 pm

Ahhhh! Important safety tip! (Don't cross the streams.)

Thanks, Mike.

Capn Trips · Post by **Capn Trips** » Fri Mar 07, 2008 1:13 pm

Actually, upon detailed review of KM, there are only 2 different factors for converting "desired delay time" to OBC, 16 and 10.33. And the 10.33 is the exception - only applying to S3C8 processors while the 16 applies to all others - so it's an easy edit.

mr_d_p_gumby · Post by **mr_d_p_gumby** » Fri Mar 07, 2008 1:19 pm

Capn Trips wrote:Actually, upon detailed review of KM, there are only 2 different factors for converting "desired delay time" to OBC, 16 and 10.33. And the 10.33 is the exception - only applying to S3C8 processors while the 16 applies to all others - so it's an easy edit.

That's mostly because when I wrote the Pause protocols for the other processors, I tried to match the timing of the older S3C8 remotes. The S3C8+ CPUs execute the same code as the S3C8, but do it faster, which results in shorter time delays.

Capn Trips · Post by **Capn Trips** » Mon Mar 10, 2008 2:08 pm

OK, then,

I've uploaded a proposed update to protocol.ini. I have made no SUBSTANTIVE changes, except for writing/upgrading/re-writing several of the [Notes=] entries for selected protocols.

I do NOT claim to have fixed every possible error in the various [Notes=] entries, but have made an honest attempt to:
(1) Provide sufficient descriptions for those Protocols that have multiple executors to assist a user in selecting the best one of several alternatives;
(2) Explain (for the non-obvious executors - usually the various Combos) how to construct an upgrade using the selected Protocol Executor.

Specifically, I have modified the [Notes=] entries for:
Denon Combo (official);
HK Combo;
JVC and JVC Combo;
Kaseikyo;
the NEC family;
the Panasonic family;
Pause;
the Pioneer family;
RC5; RC5x, RC6 and related Combos;
the various Sharps; and
the Sony Family (excepting the Egg executor)

I hope this proves helpful.

kupakai · Post by **kupakai** » Tue Mar 11, 2008 2:35 pm

I realize this will be more under substantive change, but maybe it can noted in the HK Combo notes that NEC 2DEV or 4DEV with 128.112 and 130.114 can be used instead, especially since there is no HK Combo executor for HCS08, and you will get an error if you change to a JP1.2 remote.

Capn Trips · Post by **Capn Trips** » Tue Mar 11, 2008 2:48 pm

I can incorporate that into the notes.

Capn Trips · Post by **Capn Trips** » Tue Mar 11, 2008 3:05 pm