It’s been a while since I have run into a problem I couldn’t fart around and solve myself…Thanks for this outstanding bit of kit.
With that said, as I work to clean up my library, I did some tag work, coupled with some smartlists, that I ultimately exported to VDJ with field mappings writing from the custom tag to the comment field.
Problem: In the SmarCrate folder, the rule is simple…Genre Contains #Untz. In Lexicon, the smartlist displays 22 tracks, and each of them have the custom tag Untz, and the tag #Untz written to the comment field. But I go to VDJ after a full sync, the Untz smartlist is there, and the rule is correct, yet there is only 1 track in the list. I did a manual search in VDJ for a few of the other 21 tracks that show up in Lexicon, and they aren’t even in the VDJ library.
Did I do something wrong here? This is really wierd.
I think I know why, and found a workaround…but maybe there’s an easier way.
I ended up having to make another folder in Lexicon, and putting all the files there to serve as a de facto ALL MUSIC folder. Once I synced that folder, I had to select all the songs in it and click Add To Search db in VDJ.
Doing it this way, I suspect I will have to recreate that step every time I add and edit the Lexicon library and sync to VDJ. Is there a more efficient way?
Did the field mapped values show up in VDJ? If the smart crate is correct and VDJ knows the values on the tracks, I would assume the smart crate shows them
Yes, everything shows up properly in the tracks. I have narrowed it down to the tracks somehow not being added to the VDJ Search dB. That was the theory that led me to create that ALL MUSIC folder, drop everything in the Lexicon library in there manually, sync it, then select all the songs in that folder in VDJ and manually add to the Search dB. Once I did that, all the expected songs showed up in the smart crate. Before I manually added the tunes to the dB, they were showing in the folder, but not in the smart crate in VDJ. It wasn’t until the manual add that everything began to work as expected.
Leads me to believe its not the mapping itself.
Yeah the search DB is a bit strange, I’m not sure how it works exactly. Usually there are no issues like this so strange that in this case VDJ decided not to update the search DB (or so it seems)
I can’t recall ever having this problem either. BUUUUUUT, I did just realize something. I have upgraded to the VDJ 2026 Beta. This may be a new default behavior (shrug). I have been racking my brain trying to figure out what I did differently than the past, and it JUST hit me.