Discoagogo
So I'd looked at Leixcon some time ago, and given it a go, as I was incoming from RB to VDJ and I had denon gear that would also run Engine.
however I'd given a few goes and various bits not working had put me off giving it a proper go.
However 4 months ago, bit the bullet and having been using for 3 months constantly.
The good.
If you're a wedding DJ and get spotify and tidal playlist, then you will like the import tool.
It's great for identifying which tracks you have and which you need to go and buy (and something native in VDJ would be awesome!)
I'm aware that VDJ has the ability to read a text file and match tunes, but I've found it problematic.
Lexicon DJ's approach is a little more refined, allowing you to select which matches you want to use - perhaps you want a couple of edits of the same song
De-duplication.
the main reason I paid for LexiconDJ if I'm honest. Whilst not perfect, it is one of the best that I've found. Showing number of plays, how many cues, whether the songs are analysed etc. Which makes picking which tracks you want to keep and which can go a breeze.
However there are a couple of gotchas. It doesn't support length of track, so will happily claim an 8 minute club version is the same as a 2 minute edit and it also doesn't support the mix tag.
So if you have 12 remixes of a song, lexicon thinks they are all the same.
The bad.
There are bugs, lots of them.
They are squashed by the developer pretty quickly. But the developers focus is on DJ-Pro, Rekordbox, Serato, Tracktor and and and...so there is a lot for them to focus on.
Core parts of VDJ are NOT Supported.
if you use the very popular My Library Plugin, it breaks lexicon. (and if you're not using the very popular My Library plugin, why not?)
It also doesn't support local folders add to favourites. These get turned into random empty playlists again and again.
In summary, I wish a lot of the functions that I'm using were part of VDJ or on the roadmap.
VDJ Supports export to rekordbox, if it supported export to Engine it would be great for lots of us DJ's who use VDJ with denon kit, as it gives us a nice easy backup.
The importers from Spotify and Tidal don't seem hard to replicate and are really cool and just add to functionality that VDJ already has.
So whilst I don't mind paying the subscription to Lexicon, I wish it supported VDJ more fully, I also wish that VDJ had some of the key functionality that Lexicon has so I didn't need to use both. But I'm also disappointed that after 4 months of use, I'm realising that for a lot of my use cases, which will be similar to other VDJ users (lot of us use local folder favourites / smart folders right?) that it's not as supported as I would like.
So as a Lexicon DJ user for 3 months, primarily focusing on the de-duplicate feature and integration with VDJ - let me know if you have any questions.
however I'd given a few goes and various bits not working had put me off giving it a proper go.
However 4 months ago, bit the bullet and having been using for 3 months constantly.
The good.
If you're a wedding DJ and get spotify and tidal playlist, then you will like the import tool.
It's great for identifying which tracks you have and which you need to go and buy (and something native in VDJ would be awesome!)
I'm aware that VDJ has the ability to read a text file and match tunes, but I've found it problematic.
Lexicon DJ's approach is a little more refined, allowing you to select which matches you want to use - perhaps you want a couple of edits of the same song
De-duplication.
the main reason I paid for LexiconDJ if I'm honest. Whilst not perfect, it is one of the best that I've found. Showing number of plays, how many cues, whether the songs are analysed etc. Which makes picking which tracks you want to keep and which can go a breeze.
However there are a couple of gotchas. It doesn't support length of track, so will happily claim an 8 minute club version is the same as a 2 minute edit and it also doesn't support the mix tag.
So if you have 12 remixes of a song, lexicon thinks they are all the same.
The bad.
There are bugs, lots of them.
They are squashed by the developer pretty quickly. But the developers focus is on DJ-Pro, Rekordbox, Serato, Tracktor and and and...so there is a lot for them to focus on.
Core parts of VDJ are NOT Supported.
if you use the very popular My Library Plugin, it breaks lexicon. (and if you're not using the very popular My Library plugin, why not?)
It also doesn't support local folders add to favourites. These get turned into random empty playlists again and again.
In summary, I wish a lot of the functions that I'm using were part of VDJ or on the roadmap.
VDJ Supports export to rekordbox, if it supported export to Engine it would be great for lots of us DJ's who use VDJ with denon kit, as it gives us a nice easy backup.
The importers from Spotify and Tidal don't seem hard to replicate and are really cool and just add to functionality that VDJ already has.
So whilst I don't mind paying the subscription to Lexicon, I wish it supported VDJ more fully, I also wish that VDJ had some of the key functionality that Lexicon has so I didn't need to use both. But I'm also disappointed that after 4 months of use, I'm realising that for a lot of my use cases, which will be similar to other VDJ users (lot of us use local folder favourites / smart folders right?) that it's not as supported as I would like.
So as a Lexicon DJ user for 3 months, primarily focusing on the de-duplicate feature and integration with VDJ - let me know if you have any questions.
Posted yesterday @ 8:26 am
DJ VinylTouch
I've used LexiconDJ since its inception and before it (Rekordcloud was the predecessor) - it will never support all features in all software, as that wouldn't make sense/it's really not the aim of the software (e.g. what would importing an Action POI mean?).
I don't think it's accurate to say that the dev is focused on the other apps - VirtualDJ support has pretty much always been there in decent form (proper support for DJay pretty much just arrived), and you'll see release notes referencing updates to the VirtualDJ importer/exporter fairly often. The dev is very receptive too - I've asked him to fix many bugs in the import/export for VirtualDJ the pre-release stages and he pretty much got to them within days or in some cases the same day, so don't be afraid to file a bug/ask questions in the discord.
However, it does support the main/common things in all software.
IMO what it shines for is cross platform transfers and some aspects of autogeneration (e.g. cuepoints and tracklists from tags, auto organixstion based on tag structure). Deduplication is something I pretty much never had to use (imo you should really be handling that on track import), but I can see how it can be useful.
Tbh though (no shade to Lexicon or other tools like it - I think they are doing a great job), once you understand the database formats/representations of things amongst all the vendors (where possible) and you look around hard enough at what is actually out there + free, you'll see with a little bit of effort, it's quite easy to replicate the majority of what those tools are doing with a proper workflow and some dev work.
I don't think it's accurate to say that the dev is focused on the other apps - VirtualDJ support has pretty much always been there in decent form (proper support for DJay pretty much just arrived), and you'll see release notes referencing updates to the VirtualDJ importer/exporter fairly often. The dev is very receptive too - I've asked him to fix many bugs in the import/export for VirtualDJ the pre-release stages and he pretty much got to them within days or in some cases the same day, so don't be afraid to file a bug/ask questions in the discord.
However, it does support the main/common things in all software.
IMO what it shines for is cross platform transfers and some aspects of autogeneration (e.g. cuepoints and tracklists from tags, auto organixstion based on tag structure). Deduplication is something I pretty much never had to use (imo you should really be handling that on track import), but I can see how it can be useful.
Tbh though (no shade to Lexicon or other tools like it - I think they are doing a great job), once you understand the database formats/representations of things amongst all the vendors (where possible) and you look around hard enough at what is actually out there + free, you'll see with a little bit of effort, it's quite easy to replicate the majority of what those tools are doing with a proper workflow and some dev work.
Posted 21 hours ago