Hey buddy, kudos to you if you’re gonna provide something to the community. I probably haven’t spent as much time as you figuring out the schema, but I can code. So let me know if I can help you with anything.
I guess what you’re saying makes sense, but the schema’s good design is defeated by the fact that you can’t move your files. I mean, I guess it’s cool that you can take your external drive to another Engine DJ and have it work right away. But right now, it’s at the expense of not moving a single file, let alone the folder hierarchy, or else it won’t be able to find them.
For me, I’m normally using a couple of sc6000m decks, which are running Engine OS. So there’s not much value for me in having more than one Engine DJ. My music is in one place, which is safe, and depending on where I go, I just push my playlists with Sync Manager to my USB stick and off I go.
Denon knows relocation of files is important because eventually they sort of implemented it (I guess because of the many requests here in the forum?). And don’t get me wrong, it’s better than nothing. I guess many people keep their music in their documents folder. But others like me, don’t.
We would all be happy if you could just tell the program which folder to start looking from. Instead of going to the documents folder by force. Damn, the functionality is there, and I know where my music is. Just let me tell the program where to look for it, for crying out loud…
If this renaming of paths hadn’t worked, I would have gone with junctions or symbolic links. I didn’t try it but I have a feeling it would work. I use them all the time.
There’s another idea to try as a workaround.
Anyway, let me know if we can join forces
Alex