Arrakis90
3 years agoChannel Surfer
Issue with audio timedMetaData ID3 frame
I am switching from the old method of using a video object and am now using an audio object since timedMetaData support was added in 10.5.
I am able to get good values for TIT2 and TPE1, but our WXXX frame is being modified in a way that I cannot translate into something usable. Due to limitations in our stream hosting provider, we are using the WXXX (user URL) frame to provide a GUID ID of the current song.
Expected result: b1872a6e-3aed-4be9-b523-936cbf06873e
Actual result:
0055524C0062313837326136652D336165642D346265392D623532332D39333663626630363837336500
I can't really help because I've never used ID3 frames, but I do notice it's a sort of hex ASCII representation of your GUID starting after the 0055524C00 (which would be "URL" surrounded by nulls):
62 - b
31 - 1
38 - 8
37 - 7
etc.