Christiaan, I wanted to send this completely unprompted note to express how much Lexicon has changed my workflow as a professional DJ.
I am a paid, open-format Wedding and Event DJ, and I have been a Lexicon subscriber since the summer of 2024. Across my career, I have used Engine DJ and Rekordbox side by side and previously relied on another third-party tool that was flexible but still very manually intensive. Over the years, my music library grew into something that felt impossible to fully clean or restructure.
That changed this past month.
Using a combination of Lexicon’s unique features, including “Local Path Mappings”, “Complete Library Move” using the “Incoming” and “Watch” folders, and “Smartlists”, I introduced an entirely new operating system as I moved from Windows to macOS while also overhauling, streamlining, and reorganizing my entire library. What I had not accomplished in years, Lexicon helped me accomplish in about one month.
I scaled my library from 137,000 tracks and more than 2TB of data down to 52,829 tracks under 1TB. For the first time, it feels clean, intentional, and ready for real performance use. This was not a small feat.
Your support has been incredible. You always responded to my questions, my ideas, and my requests for enhancements, including when I asked for additional categories in the “Charts” section. Lexicon is also the only tool I know that syncs directly or selectively into Engine DJ, which is my main money-maker. I have searched everywhere, and nothing else on the market does this.
Lexicon is, and will continue to be, my forever go-to library management tool. With the potential AI enhancements you are considering and the speed at which Lexicon continues to evolve, I can only imagine the improvements still to come for DJ preparation, organization, and overall efficiency.
I also have one small enhancement idea.
Below are three features I would love to see in the future:
- A playlist track count indexing view, which shows the position of a track inside a playlist separate from the track’s metadata track number.
2.For example: instead of relying on the album’s track number, the playlist view could show something like “Position 12 of 85,” similar to the playlist index columns used in Serato, Rekordbox, and Engine DJ. This provides a true playlist order reference and makes it easier to understand where a track sits in the playlist flow.* - A playlist comparison option, either as a Smartlist condition or a standalone tool, allowing us to compare two or more playlists to see which tracks overlap or differ, along with other playlist-centric analysis tools.
- A playlist mixability insight tool, showing whether one playlist mixes well with another based on BPM, key compatibility, and user metadata. This would be an amazing addition for DJs like me who manage large collections and build many performance-specific playlists. I know Lexicon already shows which playlists a track lives in, which is incredibly helpful. Expanding this to playlist-level compatibility would take it to another level.
That is all for now. I simply wanted you to know how impactful Lexicon has been for me and my entire library ecosystem.
Thank you,
JOE