It seems that IRScrutinizer's Render tab gives slightly different results depending on the presence of a padding zero.
If a parameter value on the Render pane starts with a leading 0, it is interpreted as an octal number.
How do I rectify which is "most" correct?
The best, "most correct" format is the one with parameters, D and F. One reason is that the RC5 format toggles, so there is not one but two rendered form of a signal given by D and F. (For T=0 and T=1 respectively.)
It seems Charlie used the "0x1" version, which yields different Pronto HEX than the "0x01" notation for all values below 0x10.
Sorry, I cannot make sense of that statement.
