An[oux Herbit
I have a Win 11 PC aand a Mac Studio sharing a NAS Drive containing my music library is the VDJ XML Database compatible, or do I somehow need to create seperate databases?
Inviato 4 days ago @ 10:02 am
kradcliffe
I've always found it difficult to work between Windows and Mac because of the different file structures.
Tried several times and just gave up. Not just the database but playlists and history get messy too.
Tried several times and just gave up. Not just the database but playlists and history get messy too.
Inviato 4 days ago @ 10:34 am
An[oux Herbit
so they are different? are they named the same - i use the same Nas for Radio and gigging (Radio on the Mac) not bothered about sharing anything but the music library it would be a shame to have to use a completely different system when VDJ is more familiar and can do everything I need...
Inviato 3 days ago @ 11:20 am
DJ VinylTouch
I've quickly tried sharing an external drive between Windows and MacOS for use with VirtualDJ before and it seemed to work for basic playback of songs.
For external drives/network shares (mounted at expected locations like /Volumes on MacOS), I think VirtualDJ largely ignores drive mount locations in the database (it's the same database.xml created/used).
It's everything after the mount location in the filepath that could cause the trouble, which would matter for things like history and linked tracks. On external drives that's normally not a problem as that stays the same relative to the root of the external. However, on the internal drive, songs aren't stored at the root as that is normally reserved for privileged use by the OS, so paths would likely be different for any songs stored there (at least the starting filepath).
You'd also have to be smart with the way you replicate the VirtualDJ folder - it's probably better to start with the restore of a database backup and then maybe correct the paths of files stored on the internal (if any).
I do agree with @kradcliffe though - I didn't do any in depth use, and it's probably less headaches to stick with one OS throughout.
For external drives/network shares (mounted at expected locations like /Volumes on MacOS), I think VirtualDJ largely ignores drive mount locations in the database (it's the same database.xml created/used).
It's everything after the mount location in the filepath that could cause the trouble, which would matter for things like history and linked tracks. On external drives that's normally not a problem as that stays the same relative to the root of the external. However, on the internal drive, songs aren't stored at the root as that is normally reserved for privileged use by the OS, so paths would likely be different for any songs stored there (at least the starting filepath).
You'd also have to be smart with the way you replicate the VirtualDJ folder - it's probably better to start with the restore of a database backup and then maybe correct the paths of files stored on the internal (if any).
I do agree with @kradcliffe though - I didn't do any in depth use, and it's probably less headaches to stick with one OS throughout.
Inviato 3 days ago @ 1:08 pm
An[oux Herbit
Thank you both so much for your efforts... it's answered a few questions I guess :)
Looks like i'll have to find soimething else to use on the Mac...
Looks like i'll have to find soimething else to use on the Mac...
Inviato 3 days ago @ 1:36 pm
PhantomDeejay
The database itself is fully compatible and interchangeable between MAC OS and Windows computers.
What's different and makes things a little more complicated is the file system and how filepaths are understood between the two OS.
One of the reasons that VirtualDJ decided to move away from M3U playlists was to be able to handle filepaths inside "playlists" without having to stick to the rules of M3U format.
This makes it easier for VirtualDJ to read the same playlist on both OS.
NAS Drives are a completely different beast.
While for external drives VirtualDJ will create and maintain a separate database in a folder on the root of the drive, that's not usually the case for NAS drives.
Usually for NAS, all the info is kept inside the "master" database (the database of the bootable drive on your system)
This means that it becomes tricky to make it "portable" in the same fashion as an external drive would be (which should be pretty much plug & play at this point)
What's different and makes things a little more complicated is the file system and how filepaths are understood between the two OS.
One of the reasons that VirtualDJ decided to move away from M3U playlists was to be able to handle filepaths inside "playlists" without having to stick to the rules of M3U format.
This makes it easier for VirtualDJ to read the same playlist on both OS.
NAS Drives are a completely different beast.
While for external drives VirtualDJ will create and maintain a separate database in a folder on the root of the drive, that's not usually the case for NAS drives.
Usually for NAS, all the info is kept inside the "master" database (the database of the bootable drive on your system)
This means that it becomes tricky to make it "portable" in the same fashion as an external drive would be (which should be pretty much plug & play at this point)
Inviato 3 days ago @ 7:30 am