Well, my prompts and pre-research was way more than just telling AI to “Pls make cue point webapp and make no mistakes”. I think A.I. wrote about 90% of the code so I guess it still categorizes as vibecoding.
Eg. finding out how to interpretate the cuepoint BLOB stored in the EngineDJ SQLiet database was a b*tch. 
Thanks for clarifying. 90% easily qualifies.
Also, you could have used an existing work product to learn how the cue points are stored and parse – check out libdjinterop.
One fun part for me is trying to figure out how the AlbumArt.hash blob in Schema 3.0.2 is stored & parsed.
Oh I just avoided reading the AlbumArt. I just use the relative path from the Track table and fetch the actual albumart from the actual mp3 metadata…
But I feel we’re going a bit off topic here lol.
To whom it may concern: update your devices, even those from 2017, to version 5.0.0.
You forgot “Thank you for your attention to this matter.” LOL j/k
Version 5.0 still doesn’t seem to fix the network link glitches I get where players don’t recognize some drives over the network until the player that the drive is connected to accesses the drive. Drive shows up fine on the player it’s connected, though. Ditto with the problem of no read-only mode, no prompt for the database update and therefore messing up drives by converting the database without asking, and sometimes the players just randomly decide not to finish analyzing tracks and saving that info over the network link – bye bye to being able to smart loop or beat jump out of the blue. None of it’s been fixed.
Every Engine OS firmware for the player separates past v3.4 still lacks the hybrid dual layer mode from 2017 that persisted thankfully for many years where you can see the whole waveform of the background layer de-emphasized above the current layer’s whole waveform. Now, you’re forced to either have only one layer’s information present, or both layers’ entire info present, with equal emphasis, including moving waveforms and everything else. Single layer mode when layers are active should still have the background layer’s de-emphasized whole waveform there above. If you deactivate layers, then the background layer info should disappear. Adding new views is fine, but removing the primary HUD view option that had been there since release is inexcusable.
Also not a fan of how small pitch readout is and how big BPM is now.
Radical workflow changes in the HUD UI. I keep trying to give the updates a chance, but they’re not working for me.
I think the update 5.0/5.0.1 are just the base for things to come once NI is integrated into the InMusic ecosystem a wealth of new possibilities will become apparent. It certainly bodes well for the future in my view and I do not see anything from the other-side for me to consider moving away from Denon. That being said for Denon specifically the quality of the motherboard (what ever you call it) has been an issue with the prime and sc devices (in my experience) this cannot be the case when the new range comes out as it just brings down what is otherwise a really great piece of gear.
Anything can go wrong - the printed circuit boards haven’t been a particular widespread issue on the Primes.
There are a number of users citing similar issues on Facebook whilst not an official source it suggests the issue is relatively common