
My Tags not writing to comments here as well
Rekordbox 6.0.0
MacOS 10.15.4
External SSD Library 4TB
I have checked and unchecked the settings.
My custom tags were migrated from Rekordbox 5
Thanks.
Just updated to RB6, I will be going back to RB5 for the following reasons,
Waveforms are jittery and slow.
Audio when scratching now sounds very digital and can clearly hear the algorithm artifacts
CPU usage is spiking all over the place.
MY tags are not writing to the comments section even though this option is ticked under the browse section of settings
This feels like a rushed product. And as for the subscription plans, I understand this is the future of software technology, but we as djs already pay £1000's for equipment and music, I certainly will not be paying for any plan.
Iniciar sesión para dejar un comentario.
My Tags not writing to comments here as well
Rekordbox 6.0.0
MacOS 10.15.4
External SSD Library 4TB
I have checked and unchecked the settings.
My custom tags were migrated from Rekordbox 5
Thanks.
Same issue here with 'My Tag' not writing to comments. Track Filter appears to still work ok for tags.
Some addititional info on steps to reproduce this issue:
As soon as you remove any single tag from the track or add new one, all the tags in comments are removed. You can't add any tag to comments again.
Here is some kind of a workaround on this:
If you untick "Add My Tag to the Comments" in preferences, then tick it again, all tags appear in tracks' comments.
Sounds like one of the best features RB has got borked. MyTag also has issues with the intelligent playlist.
Same here.
The option in the preferences / Advanced / Browse / My Tag / Add "My Tag" to the "Comments" is working, BUT once you choose a track and you decide to edit a Tag, let's say an additional Tag like "Vocal", it disappears again in the comments. It was perfectly working in Version 5.
I'm running Windows 10 Pro, Version 1909 and Recordbox Version 6.0.0 x64
I would recommend fixing this asap because this is one of the killer features!
Dear guys,
We've fixed this issue on ver601 beta as below.
Thanks,
Dear Kanta
This fixed the issue for me! Good job guys!
Thanks!