These are chat archives for brunchboy/afterglow

20th
May 2017
James Elliott
@brunchboy
May 20 2017 18:47
Nice indeed, thanks again! I have dysentery properly parsing and constructing all of the type-tagged fields (kibbles) and messages that make up transactions now, and got the track metadata download working from start to finish that way last night. I discovered a new itemTypeLabel value that you may want to add as well: 0x2e means the message contains information about when a track was added to the collection (it seems to propagate from iTunes on my system). The last message before the menu footer in a track data response has an item type with this value, and its label 1 string contains a date in the form yyyy-mm-dd.
James Elliott
@brunchboy
May 20 2017 19:56
I’ve also discovered that a message type of 0x1004 gives you the track list (sorted by title), whose menu items are of type 0x704. And message type 0x1002 gives you the artist list (sorted by name); those menu items are of type 0x07 which we already knew meant artist.
James Elliott
@brunchboy
May 20 2017 23:29
All right, @awwright, I seem able to retrieve waveform data, but I don’t know how to display it. Unlike the album art, it is not in a standard image file format. You mention that it is one byte per pixel, but what order are the pixels in? And what do the bytes mean? How do they map to a color? It doesn’t seem like there is enough data there, I am only getting back 900 bytes… Also, more worryingly, once I request waveform data, my next request, whatever it is, gets back a message with type 0x0100, and no arguments, and then the socket closes. Wait, I just checked, and that 0x0100 message is coming right after the 0x4402 message with the 900 bytes of waveform summary even if I don’t send any more messages. So clearly I must be doing something wrong. I guess it is time to bust out my spanned switch and do some more network captures, unless you have a better idea?