Direction: Out
Request: 01
Data Length: 04
Data: buffer of length 4
Upon completion buffer is filled in for you as 01 81 hh 00 where hh is the length of the buffer needed to hold the Disc Header (plus protocol information)
Request: 81
Data Lenth: hh from above
Data: buffer of length hh
Upon completion the buffer holds hh bytes of data. The first 19h bytes are protocol information,
you are interested in the remaining data.
HH is the track number.
Direction: Out
Request: 01
Data Length: 04
Data: buffer of length 4
Upon completion buffer is filled in for you as 01 81 hh 00 where hh is the length of the buffer needed to hold the Track Title (plus protocol information)
Request: 81
Data Lenth: hh from above
Data: buffer of length hh
Upon completion the buffer holds hh bytes of data. The first 19h bytes are protocol information,
you are interested in the remaining data.
Where HH is the length of the Header, JJ is the length the header used to be, and (Header) is the full complete Header List
See Header for information on how the Disc Header is structured.
Where HH is the length of the Title and (Title) is the Track Title, remember that LP: is not inserted for you.
Where HH is the track number to move and JJ is the track number to make it.
TT is the track number.
Request: 01
Data Length: 04
Data: buffer of length 4
Upon completion buffer is filled in for you as 01 81 hh 00 where hh is the length of the buffer needed to hold the Disc Header (plus protocol information)
Request: 81
Data Lenth: hh from above
Data: buffer of length hh
Upon completion the buffer holds hh (seems to be 1f every time since its the same data per track) bytes of data. The last 3 bytes are Binary Coded Decimal representations of the track times.
#define BCD_TO_PROPER(x) (((((x) & 0xf0) >> 4) * 10) + ((x) & 0x0f))
This is a C macro which will return the proper decimal for use.
Request: 01
Data Length: 04
Data: buffer of length 4
Upon completion buffer is filled in for you as 01 81 hh 00 where hh is the length of the buffer needed to hold reply
Request: 81
Data Lenth: hh from above
Data: buffer of length hh
Upon completion the buffer holds hh (seems to be 1f every time since its the same data per track) bytes of data. The last byte holds a hex value representing the bitrate
Known Values
Request: 01
Data Length: 04
Data: buffer of length 4
Upon completion buffer is filled in for you as 01 81 hh 00 where hh is the length of the buffer needed to hold reply
Request: 81
Data Lenth: hh from above
Data: buffer of length hh
Upon completion the buffer holds hh (seems to be 1f every time since its the same data per track) bytes of data. The second to last byte holds a hex value representing the bitrate
Known Values
So if you had a MD with the Title GroovyMix and 2 groups Thumpen and Bumpen it could look like this:
0;GroovyMix//1-5;Thumpen//6-8;Bumpen//
Where 1-5 and 6-8 are the NON zero based track numbers that the group contains.
I ephasize non because the protocol refers to all track numbers in a zero based manner, making information tracking interesting