
Originally Posted by
NReek wrote:
When speaking about file formats, there are many possible combinations available.
Practically speaking, there are certain random "poltergeists" when using mp3 and dealing with ID3 tags.
I'm talking about ID3 that are not handled correctly by some applications, it can be traktor or it can be itunes or any other tools, but sometimes ID3 are not written, sometimes they are lost, randomly in appearance. This makes difficult for you to reproduce the issue, maybe this issue has passed unnoticed but more likely you are aware of this.
As Traktor relies now on tags to store the valued information regarding cue points, stripes, transients, beatgrids, etc., and from our point of view we would like to avoid making this job repeatedly, i'd like to ask you:
Have you made analysis, tests in this area? As a result of your tests, which version of ID3 would you officially recomend as the most compatible or the less "buggy" to work together with Traktor, keeping in mind to keep safe the data we store in our files?
Are there any known issues with MP4 files we should be aware of? Is there any reason why the m4a files are not showing their bitrate? (it appears to be 0kbps)
Metadata has become a very complex area because there are many different entities that store track information - the standard ID3 tags themselves and proprietary tags written by iTunes or Traktor, the iTunes Library or the Traktor Collection. So it can be confusing to work out which of these entities “override” the other.
For this reason we have decided to give the highest priority to the standard ID3 tags when available, because they are the most common denominator among all tagging applications. For information going beyond the standard, we rely on extended tags written by Traktor Pro into the files.
We decided for the latest ID3 version 2.4 for Traktor Pro so this should ideally be used.
Regarding MP4 files, the bit rate is not stored in a tag, it is retrieved by the decoder. The MP4 decoder in Traktor Pro has a bug where the bit rate is not calculated correctly. Because this decoder is licensed from a third party, we can't make any promises about when this bug will be fixed.
Bookmarks