brunchboy on main
Remove no-longer needed environ… (compare)
brunchboy on main
Force browsers to load updated … (compare)
github-actions[bot] on v7.0.1-SNAPSHOT
brunchboy on main
No longer throw exceptions when… (compare)
dependabot[bot] on npm_and_yarn
Bump minimist from 1.2.5 to 1.2… (compare)
dependabot[bot] on npm_and_yarn
Bump minimist from 1.2.5 to 1.2… (compare)
brunchboy on main
Add thread dump instructions fo… (compare)
brunchboy on main
Add Zulip chat links [skip ci] (compare)
brunchboy on v0.6.3-SNAPSHOT
brunchboy on v0.7.0-SNAPSHOT
brunchboy on v7.0.0-SNAPSHOT
brunchboy on main
Update chat links to the specif… (compare)
brunchboy on main
Update chat links to the specif… (compare)
midi-clj
can’t find a device you are asking for when you supply the name that it gave for that device!
midi-clj
functions wrong, because they behave in a way that is not idiomatic Clojure (they are pretty old, they were written when Clojure was new and best practices weren’t widely known). They treat input strings as if they were regular expressions, and so the brackets in Linux device names are making them not match. The more idiomatic (and developer-friendly) way for the functions to work would be to accept both plain strings and regular expressions as the target being searched for (regular expressions have nice, concise literal syntax in Clojure so they are easy to type), and then it could work either way. I may open a PR with midi-clj
about this, although the only backwards-compatible way to do it would be to offer a new function that works this way and deprecates the old one. (While I’m at it, I might suggest they get rid of the midi-
prefix on all their function names, that is also not idiomatic, the best practice is just to name the functions for what they do, and let people use namespace aliases to make it clear where they come from.) But that is a project for another day; for now I just need to fix the places that Beat Link Trigger is calling these functions to properly escape any regular expression special characters, and we should be able to get MIDI output selection working in Linux!
I checked some documents of Pro DJ Link that you made, to capture this communication of this controller I used WireShark, is this the best approach ? Which are the recommendations ? I would be very happy to collect all information and share here.
First think I noticed was this USBLAN that I did not heard about before, it seems that the DDJ-RZX behaves as a Network device, them I installed WireShark to inspect the communication of the controller and Macbook services and I noticed that the commuication happen in ports 50000 50001 similar what I saw in the Pro DJ Link documents found in Github.
If you give me some information I am willing to provide more data about it in the way we can analyze it.
Sérgio
@brunchboy Thanks for the input, I will check gain the packet detail information you prepared, anyway looking what I got from RZX so far it seems to be different values what means it will be a big work to analyze and have some results.
What I could recognize is that in the side of RZX they are using 6 Ports (49434, 49435, 49436, 49437, 49438 and 49439) and in the side of Rekordbox (49123, 49124, 49125, 49126, 49127, and 49128) the first RZX port communicate with the first of Rekordbox and son on.
Other thing is that the packets starts with 2 different patters:
https://drive.google.com/file/d/1KpHGKSU7a-ttrNpDyXU1_Laod1iK7voL/view?usp=sharing
https://drive.google.com/file/d/1KxhKckbVFf6cbUtflcYqJGuaARgQE-lK/view?usp=sharing
What is similar what you figured out in Pro DJ Link.
Let see what I can find :)
Sérgio
First and very simple to conclude, the first part represents the direction of communication flow:
192.168.110.1 -> 192.168.110.254: https://drive.google.com/file/d/1KpHGKSU7a-ttrNpDyXU1_Laod1iK7voL/view?usp=sharing
192.168.110.254 -> 192.168.110.1 : https://drive.google.com/file/d/1KxhKckbVFf6cbUtflcYqJGuaARgQE-lK/view?usp=sharing
The IP Address 192.168.110.254 is the USBLAN IP of RZX Controller. Now I am asking myself what hell is this IP 192.168.110.1 (can be Rekordbox or Something else).
Sérgio
Interesting @Army-dev, you are examining the memory of the running rekordbox program to do this? Does that work cross platform? How does it cope with new releases? And where is the source code? A very intriguing approach!
Development is still in progress, it basically reading out the information from the memory, it works like a "game cheat", and i think it will works on cross platforms too??? i never touchd a computer with MacOS in my life :D. I gonna make it open source. if there is a new update to rekordbox i have to find the values again i think, but i didnt tryed this yet because i have a cracked rekordbox lol. (or just dont update until i relase the config file for it) I need time/motivation to finish this project to make a stable relase :) i'll update you guys