Sign In:     

Forum: Wishes and new features

Topic: Direct database export to Engine DJ
This appears to be impossible to achieve without using 3rd party software (Lexicon) - and every time I add new tracks to my VDJ database, I have to export the database to Lexicon again, and it really does not like my filters/folders/playlists - but seems very hit and miss on what it decides to copy across and what it decides is no longer valid.

But is the problem with VDJ or Lexicon? Who knows... but if we had the option to export directly from VDJ to Engine DJ that would cut out one possible error point.
 
Posted 14 hours ago
I just maintain VDJ and Engine databases separately, however it would be better to have a one click solution.

I've worked out a way to transfer VDJ playlists to Engine using iTunes but again it's quite convaluted.
 
Elite-Entertainment.uk wrote :
if we had the option to export directly from VDJ to Engine DJ


Is that a fair request, really? What other DJ software can export in the competitor's DB formats?

All the DJ programs are designed the same way, to import (once) from whatever you used previously in to their system and then stay with their program.

I was going to say the same thing as Keith - are you really adding so many tracks each time that it's impractical to update VDJ and Engine separately?
 
Elite-Entertainment.uk wrote :
But is the problem with VDJ or Lexicon? Who knows...

Why would the problem be with VirtualDJ ?

VirtualDJ has it's own logic and it's own database and playlist formats. These formats allow the software (VirtualDJ) to operate without any issue.
On top of that, those formats are not proprietary and/or encrypted.
They are XML files that you can open and read their contents with any text editor (even notepad)

Therefore, why would VirtualDJ be on the blame here ?
It's Lexicon that offers you a service: To read VirtualDJ data and convert them to Engine.
Since "reading" the data can be done even without having a clue of programming, the issue must be on how to convert that data to something that Engine understands.
And that's not a responsibility of VirtualDJ.

BTW: Even if reading VirtualDJ data was not "easy", it would still be Lexicon's issue, not VirtualDJ's..
It's Lexicon that claims it can read and convert the data. So if it couldn't, that would be on them. VirtualDJ has no obligation to consider how a third party would read it's own data..

PS: It's not about Lexicon either..
It's about the logic..
Same rule applies with recent changes regarding Fluid BPM and Soundswitch.
It's Soundswitch that needs to update how they read VirtualDJ database and get BPM info out of it.
Not the other way around. Nor should VirtualDJ ask any third party apps if it's ok to update/change the format of it's own database in order to work better.
PPS: VirtualDJ has happily kept it's own file formats "open" so that anyone can read them. And it happily provides any info any third party programmers asks for regarding those formats!