fun fact: the playback BPM is not actually 174.00 as shown in the UI! the track sync feature causes the real BPM to cycle between ~174.04bpm and ~173.98bpm, presumably because it works based on time quantisation via rekordbox's internal framing system (iirc 150 ticks per second).
next job is to have it pull the content ID for the active track, so if you have access to the sqlcipher database (assuming you didn't upgrade to the new db format - still work to be done there!) you can pull all the track info without me needing to muck about with updating pointers and offsets for each release (although I do have a plan to automate that to some degree!)
my favourite thing about this kind of fuckery is that it is 100% my wheelhouse, so I can give the dickheads over at pioneer some serious headaches if they want to try to run anti-consumer interference and block interop.
I spent the last couple of years writing a paper on novel anti-VM tricks, none of which are currently documented. if they want to shit on my fun, they're going to have a horrible time.
(note: if you missed the context, pioneer pull this shit constantly, encrypting the database used to store track info [broken], trying to change the keys [broken again], changing the db format [WIP on that], and actively paying attention to 3rd party interop devs posts to patch stuff so their tricks don't work. this isn't even a piracy thing - I literally paid for their controller - they're just assholes hoping to tie you into their ecosystem for future rent-seeking opportunities)
I'm stuck with them until I can spare the cash to buy a new controller that'll do serato as well as rekordbox (not cheap) but at this point I'm more driven by spite than anything else.
Add comment