Curiosity question Graham, but why does RMIR not let you create "new" images for newer remotes like the Nevo? And why could I not open the raw download files that vbs posts
here?
If it's not feasible to have RMIR create a valid file for those remotes from scratch, would it be possible to include a basic rmir file for each of them in the distribution that we could use instead?
There are often occasions where I want to re-create what someone is describing, but I don't have their remote and RMIR won't let me create a generic file, so I am unable to.
Also, when I was looking at the functions list in the rf_good.rmir file that vbs posted, I tried to widen the hex column so that I could see all 3 bytes but it wouldn't let me.
Speaking of 3-byte protocols, it occurs to me that the EFC5 column is completely useless for executors that use more than 2 bytes, so we should probably kill it in such cases. I can see some value to keeping the regular EFC column, but there probably should be a way in protocols.ini to tell it which column it affects. For example, in my new Onkyo Combo executor, the OBC is in the 2nd byte, so you'd want any change to EFC to affect that byte. Might be good to also have the option in protocols.ini to kill the EFC column if you know in advance that it makes no sense to use it.