You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks for this amazing tool! It has proven to be really useful for exporting music libraries e.g. for portable use in the DJ software Mixxx, which has an importer for the iTunes XML format.
Recently, I've tried to export a large library containing some esoteric track titles and came across a small difference between the way this app encodes characters and the XML directly exported from Music.app that Mixxx had trouble parsing. Consider this admittedly unusual title (don't ask me where this came from):
The problematic characters are U+0004 and U+0005 (i.e. Unicode control characters). Music.app seems to remove them while Music Library Exporter preserves them:
Perhaps Music Library Exporter could filter out control characters too to make the file more robust against brittle parsers? (I know this is very much an edge case, but it would still be a nice quality-of-life improvement for large libraries than happen to contain strange characters).
The text was updated successfully, but these errors were encountered:
First of all, thanks for this amazing tool! It has proven to be really useful for exporting music libraries e.g. for portable use in the DJ software Mixxx, which has an importer for the iTunes XML format.
Recently, I've tried to export a large library containing some esoteric track titles and came across a small difference between the way this app encodes characters and the XML directly exported from Music.app that Mixxx had trouble parsing. Consider this admittedly unusual title (don't ask me where this came from):
The problematic characters are U+0004 and U+0005 (i.e. Unicode control characters). Music.app seems to remove them while Music Library Exporter preserves them:
Perhaps Music Library Exporter could filter out control characters too to make the file more robust against brittle parsers? (I know this is very much an edge case, but it would still be a nice quality-of-life improvement for large libraries than happen to contain strange characters).
The text was updated successfully, but these errors were encountered: