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!
2 Likes
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.
1 Like
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…
2 Likes
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