GadgetMan
Having tried CDJ Export, it has made me realise there is far more to exporting than just CDJ’s
There should be support as many platforms as possible: Rekordbox/CDJ, Engine, and so on.
But it’s should a must that VDJ is supported as well as the other target platform(s).
By supporting VDJ, as well as the target platform(s), the DJ will have the most versatile external drive.
If possible, support multiple platforms in a single export.
It shouldn’t be just export, why not a full and maintained sync whenever the drive is connected where it makes sense to.
Remember what folders and playlists are exported so they can be kept in sync with the host VDJ.
Treat VDJ as a true export target, so that a DJ can prep his night and walk into a venue where VDJ is already in use.
If, like CDJ/Rekordbox, the files need to be stored in a certain format/path, make sure the VDJ database on the export drive keeps all the cue points, etc. but uses the revised filename.
If not, mirror the location of the file, with the same filename as the host.
Add the ability to export:
All of the above would be stored under the root VirtualDJ folder on the target drive, along with sync settings for when reconnected to the host VDJ.
The VDJ database on the external drive could contain a reference to the original file name/path as an extra attribute in the <song /> element. Eg. <original FilePath=”” />. This would make the conversion of virtual folders, history and playlists easy to keep in sync.
If the drive was inserted into a machine where VDJ was running, the DJ should have the option to “take control” of VDJ using the contents of the export drive.
When required, control would be handed back to the defaults.
On reconnecting to the host VDJ, any history captured (from any platform) should find its way back to the host History folder with the filenames replaced to match the originals.
Cheers,
Roy
There should be support as many platforms as possible: Rekordbox/CDJ, Engine, and so on.
But it’s should a must that VDJ is supported as well as the other target platform(s).
By supporting VDJ, as well as the target platform(s), the DJ will have the most versatile external drive.
If possible, support multiple platforms in a single export.
It shouldn’t be just export, why not a full and maintained sync whenever the drive is connected where it makes sense to.
Remember what folders and playlists are exported so they can be kept in sync with the host VDJ.
Treat VDJ as a true export target, so that a DJ can prep his night and walk into a venue where VDJ is already in use.
If, like CDJ/Rekordbox, the files need to be stored in a certain format/path, make sure the VDJ database on the export drive keeps all the cue points, etc. but uses the revised filename.
If not, mirror the location of the file, with the same filename as the host.
Add the ability to export:
- Playlists
- History
- Virtual Folders
- Filter Folders
- Quick Filters
- Mappers
- Pads
- Samples
- Skins
All of the above would be stored under the root VirtualDJ folder on the target drive, along with sync settings for when reconnected to the host VDJ.
The VDJ database on the external drive could contain a reference to the original file name/path as an extra attribute in the <song /> element. Eg. <original FilePath=”” />. This would make the conversion of virtual folders, history and playlists easy to keep in sync.
If the drive was inserted into a machine where VDJ was running, the DJ should have the option to “take control” of VDJ using the contents of the export drive.
- The DJ’s own personalised mappers would now take control
- Playlists and History would replace the hosts
- The same for skin, samples and pads
- Any songs played would get written to the export drive History folder
When required, control would be handed back to the defaults.
On reconnecting to the host VDJ, any history captured (from any platform) should find its way back to the host History folder with the filenames replaced to match the originals.
Cheers,
Roy
Posted Sat 05 Feb 22 @ 9:09 pm