-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some status packet analysis #8
Comments
Thanks so much for this report! When I have a chance I will integrate it into the document. One of my DJ colleagues just ordered a pair of these players himself, so I may be able to do a bit of investigation with them too. For example I would like to add support for color waveforms. Is there any way you could perform a traffic capture so we can see what the image format is, and what kind of request is used to obtain the color version of the waveform? And I apologize about the issue you were having with the non-hexadecimal byte offsets in the text. Here is how that came to be… In the beginning, my packet diagrams used decimal numbers in the row and column headers, so the offsets were consistently decimal in both places. That felt more natural in running prose descriptions. But once I started using dysentery to look at player state, that became confusing, so I changed the packet diagrams to use the same hex labels as dysentery. But then the text became confusing, as you noted. Even I find it a bit annoying, though I’m still fairly quick at converting from hex to decimal in my head from my long-ago days of hand-assembling 6502 machine language. Thanks for raising this, though. I will make a pass through the document and change the byte offsets to hex, and help preserve our sanity. Especially now that so many more people are looking at it! |
Thanks for improving the docs! Regarding the color waveform see #9 Another note, in the documentation it says that in order to request data we need to emulate a CDJ, and thus limiting maximum number of players to 4. While I have never seen one (who has?) a DJM-TOUR1 seem to be able to request data from 4 CDJs at one. See: https://youtu.be/UMhMdbEZv0s?t=6m42s |
In that video it says that the original Nexus players (which is what I have) can’t do that; the TOUR-1 loses most of its features when you try to use them, so that seems consistent with my experience. It may be that nxs2 players would not have this limitation with Beat Link Trigger. Perhaps someone can try requesting metadata when four of them are on the network. It would also be interesting to capture traffic between a TOUR-1 and nxs2 players. But, as you say, who has seen one? I don’t expect anyone will be shipping me such gear for analysis any time soon. 😉 |
Also, the Kuvo unit is able to get at least some sort of metadata from players even when there are four of them in use, but those are also hard to find, they will not even sell them to individuals, only to qualified clubs, so I have not yet been able to get any captures of how that works either. |
OMG, @jan2000 I had forgotten completely about this thread, because it’s been quite some time since I had time to work on dysentery, but you just solved a mystery that I have been struggling with for the past several days! I am adding the ability to take over the tempo, so that people can sync from Ableton Link (Live, Traktor, or any device or software that supports that protocol) to the CDJs. I already support the CDJs controlling the tempo of an Ableton Link session, but not the other direction. And I seemed to have everything working perfectly, but the other devices were ignoring my tempo values. And I just now reviewed your discoveries, and the answer is right there: I need to set byte Thanks so much!!! |
Hi very nice project. Also very good documentation, very interesting.
One note though, why are the byte offsets in the doc not in hexadecimals? I had a hard time comparing the doc with my findings because of this.
That said, keep up the good work!
I have have tested your software with my XDJ-1000MK2 and would like to share some findings:
The text was updated successfully, but these errors were encountered: