Thanks @jvallius – I can confirm this issue is resolved for our next release. Here are your files in Build 30 (which you’re currently running):
And here’s the current code which will go live with our 1.1 release:
I think this is related to some recently-resolved issues with our ALAC decoder – look for this to resolve itself in your collection once 1.1 is released.
Sorry for the trouble and thanks for your patience!