Pretty amazing to be honest.
Lots of thoughts going around in my head, but I guess the main questions relate to how this would affect Lexicon exports for Djay Pro and Traktor.
At the moment I know Lexicon doesn’t import Djay Pro beatgrids, but that’s somewhat down to the limitation on the metadata that Djay shares in it’s API on this feature?
It would be great to explore if this data is being shared now that the info can be fed from Djay to CDJs, Rekordbox and also once it’s launched, Traktor.
It won’t change anything for Lexicon. I already planned to add support for Pioneer USBs soon, perhaps I can get some official help from AlphaTheta for that instead of just reverse engineering it, that would be nice.
Phil Morse is spot on. While it’s a step in the right direction, it’s really a rebranding and expansion of the Rekordbox Device Library Plus.
If it’s unencrypted and open source, then I see Lexicon DJ benefiting from the extra interoperability tools.
They claim more DJ apps are getting on it soon (probably when Serato 4.0 comes out) so I hope that means they are actively getting more programs on it that are interested, like Lexicon.
First I was very happy to read this. But it doesn’t look like they’re taking this seriously. There’s no specification available. Denon isn’t even in the boat, even though they already make an effort to make their hardware compatible with RB.
Not with his take on Djay Pro tho. Stem separation and the effects are pretty nice but the UI rather sucks, especially with 4 decks 
I also doubt it that compatibility certification would get us anywhere.
Oh and Djay Pro support for OneLibrary is a joke. It blindly overwrites the beatgrid and BPM as soon as the track is loaded. Same thing already happened when the library has been imported with LXC.
Yes, @t_a , you’re right. I’m seeing complaints on the djay Pro forum and on Phil’s post comments that grids and cues are off.
I guess time will tell if this is just a ploy by AlphaTheta. There’s certainly a lot of reasons to be suspicious.