I was started to reply with something that was both heartfelt, educational and decided to erase it all. I recognize that you’re upset but this rant is cause for me to disengage.
Best wishes!
If there is a good reason for the implementation of this type of structure during synchronization I would like to know.
Just for learning.
Thank you.
I assume (and it’s only an assumption) that there are likely space, performance and efficiency aspects tied to why the drive is setup in that manner. They likely also have to account for all the additional variables you don’t have with standard computer folder structure, like a file being referenced in multiple different places (playlists).
it would be good to know what Rekordbox does, and if that is different to Engine, or the same. If people are going to call the Engine devs lazy and stupid, I’d like to know what the Alphatheta devs are doing with their software, given it’s the ‘industry standard’ and the only other platform that exports music for use externally, we can’t compare laptop software (despite the constant assertions by some that they are comparable) as it’s a completely different workflow.
Well, suppose the user has his audio files all over the place: a few in /User/username/Music/iTunes, a few in /beatport, a few in /Volumes/externaledrive/music. Are you going to copy all those folder paths to the target drive? No. You copy the files to a proprietary folder structure, because the user isn’t supposed to mess with the file structure in the target drive anyway (otherwise you wouldn’t be using sync). Rekordbox made the same design decision, and if I would be part of the development team, I would probably too.
remember that your usb thumbdrive is not a backup or anything similar. Its a way to get media to and from your gig without carying your laptop. For all I care you throw it away after each gig and use a new one. Some people store their main collection on it, which is fine too, as long as you keep backups to prevent loss (and something Rekordbox doesnt even support!). But it is not supposed to be a 2 way sync of your entire collection, let alone a backup…
and this system works for 99.9% of us. I don’t really get where this rant is about…
I haven’t eficiency or performance issues. But my library is small now. Maybe issues will come when It grow Up.
And I have sets with a lot of tracks in more than one only playlist so I think that’s not Will be a problem.
But yes, if the users have their music in a lot of folders, recreate that structure IS not a good idea. I have my tracks under /user/music/MUSICA/… and when I sync all folders they go to /DRIVE/MUSICA
Regarding my ideas here: Is there a way to sync meta data across devices? - #38 by DeJulius
I asked Claude Sonnet 4.6 and Cursor both if it could propose the changes for code and design to how denon prime4+ handles storing its data and I had a perfect solution within minutes of some back and forth of my demands and requirements for the data on controller and PC, with all the existing denon/enginedj options functional. Denon does not even have to alter the front-end for this to work, existing users only have to run a ‘migrate data-design to new option’ once and it would be done. So, if any of the denon dev team would like me to implement a better improved file-storage methodology for its internal storage, feel free to ask. It’s not that hard. Syncing back and forth would be way faster and more logical than it is now.
For those who, like me, were tired of manually updating their music collection in ENGINE every time – and yes, I keep a mirror of what I have on my PC in ENGINE, and every time I downloaded new music I had to open ENGINE and manually add many new tracks to each playlist mirroring my PC folders!
THAT’S OVER!!!
Because I created an app that does this automatically with a single CLICK!
I can spend a whole month downloading new music to various folders on my PC now!!
Because, when it’s necessary to synchronize with my external SSD or the internal SSD of my SC6000, with one click the app directly synchronizes all the new tracks from each folder with their respective playlists directly in the m.db of the ENGINE library!!
As soon as I open ENGINE, it already has the new music added and starts analyzing them!
This works even if I create new folders!!
I’m creating a topic to make them available to you!
Of course, this doesn’t improve synchronization, because that’s not its purpose!
The app synchronizes your music library with the ENGINE so you no longer need to do it manually!! Stay tuned!
Hello, I’m very interested in seeing the application in action, because every time I want to add a new song, the program synchronizes everything again and takes a long time to do so. 
I haven’t released it yet, but I already have versions for the latest Mac and Windows on GitHub. I’m still working on the version for Macs with Intel processors because I don’t have an Intel Mac machine to compile it, but I’m trying to compile it in a virtual machine! If you want to be the first to test it, I’ll make a post soon! Release Engine Sync - v1.0.0 · lehdeejay82/Engine-Sync · GitHub