More precisely, this means that using the "reload" tag button in RekordBox to get that written information will ERASE EVERY OTHER INFORMATION that is part of the non-savable fields in Rekordbox. In addition, I want to clarify the importance of this issue and how many people are affected on this entire planet!Įveryone on this planet who uses a combination of Rekordbox + Traktor or MIK pointing to the same database of songs, has this problem!! No joke! Everyone who uses MIK's beat intensity analysis that writes to the comments tag or any other program that writes to ID3 tags (other than key) for that matter causes issues when retrieving it in Rekordbox. Whatever methods you have inside your company to flag this one, it needs to be done ASAP or i'm leaving all your products behind! Not a joke! Write to ID3 for at least comments or key! Seriously! Let's wake up! 2016 here! This thread has been kicking for 4 years. The design concept is straight jacket thinking, it's big brother restrictions here. For example if it does it in "Remixer" re-writes, heck, i'll put it there while you guys at pioneers figure it out! But someone save us OUR precious time and let us F-Know! For real! Not only do we have a design issue here, but it seems we have a comprehension and communication issue as well.ĭon't leave us hanging man. If I have to do that, you will loose me and I'm going back to Traktor! Here's the logic: If we know that there is a field that RB will write to, then we can use that field for writing down the Key, comment, etc. I shouldn't have to mess up my database for that and waste my precious time. Please tell me why Rekordbox is even using id3v1 tags in the first place? They are ancient, and in most cases are truncated to 39 characters (not very useful for a Pulse!!! Hey buddy, can we have the list that this guy asked for 4 years ago at the beginning of the thread please ?!?! I'm talking about a list of what RB write to the tags and what it does NOT. Usually, the tags are marked inactive and left in the file.
ID3 EDITOR FAILED TO UPDATE THE VERSION 2 TAG SOFTWARE
Now, why is software supposed to ignore deprecated tags? Because it is common practice to leave the information in place to avoid dangerous rewrites of large media files. So, you'll probably tell me to delete the v1 tags, right? Well, here's where it really gets weird: I delete the tracks from the library, and then delete all id3v1 tags on the MP3s, then re-import them into the library and guess what's back? That's right, those id3v1 comments are back again. Rekordbox pulls 'BAR' into the library comment field, indicating that it pulls from that first (standard behavior is to ignore deprecated tags, BTW)
If I look at the look at the file with a utility (dbpoweramp) it shows id3v2.3 comment tag of 'FOO' and and id3v1 comment tag of 'BAR'. aif and I have no issues with tags, but i've a cluster of 200+ MP3's that import or reload tags into the comment field incorrectly every.time. Okay, here's a weird one related to tagging and v2.0.3: I hope you guys take this into consideration, as tagging, adding custom cue points and organizing music takes a lot of time and work. If this is not possible because of design, Pioneer should really consider opening up its database / API so other applications can read the database files \ tags and or convert it. Its really irritating with all the proprietary databses. Pioneer Rekordbox should always use ID3 and or other open formats at much as possible. That mean that all the hard work with tagging will be useless in Serato, Traktor or any other application that supports the open ID3 tags.
Its pretty disappointing if Rekordbox only uses its proprietary DB to tag the music files. Hello, i have just started using Rekordbox with my new CDJ 2000 and DJM 900, I have a few questions about the tagging inside rekordbox and the database its generating.Ĭan we get any confirmation on what ID3 tags Rekordbox can read and what ID3 tags Rekordbox can write back to the music files? And or if its deleting any of the original tags form the music files?