>I'm just used to the way it works on the Rio remote

But.. but.. that's exactly the same way the translations do it!
(or at least that is how the code is supposed to be doing it).

Perhaps here it's just a matter of the particular player function responding differently? Try programming an alternative longpress to do exactly what an existing Rio longpress does.. same behaviour?

If the translator were to NOT hang onto the release code until the user lets go, then how the heck could anyone map buttons to do "fast forward" or "fast reverse" ??

Regardless, I'll add something to change the behaviour for some situations.
Perhaps a .I modifier on the macro definition might do it?

Cheers