@jcornwall wrote:
Edit: OK, here’s the problem. I think Rhythmbox developers were a bit lazy and didn’t bother to request ‘/content-codes’ for the correct dictionary. Instead, all of the content codes are hard-coded which means they cannot parse any code newer than the ones they have (because they don’t know it’s size).
I can also make a “don’t claim to be aeSP” config value as well, for compatibility until the patch makes it to release.
As a generic thing, one can always “parse over” atoms that aren’t recognized, just by getting the size and skipping over it.
That might be the cleaner patch.
— Ron