INTERACT FORUM
More => Old Versions => JRiver Media Center 19 for Windows => Topic started by: Brovig on December 17, 2013, 04:12:38 pm
-
I'll ask this again as I got no joy last time:
I converted a bunch of songs from the source ALAC to MP3 (VBR high) and I notice that while the Album Artist tag in the original is <A.N. Other>, in the MP3 file it shows up in all cases as <A.N. Other; A.N. Other>.
In other words it gets duplicated with a semicolon separator.
What can I do to avoid that?
I'm using MC19.0.67 under Win7-64.
-
Can you make a sample ALAC available so someone can duplicate the problem?
-
Can you make a sample ALAC available so someone can duplicate the problem?
Sure. How should I submit it to you? I could use Dropbox.
-
Sure. How should I submit it to you? I could use Dropbox.
Please email a link to yaobing (at) jriver [dot] com.
Thanks.
-
Email and Dropbox notification has been sent. Thank you!
-
Thanks for the samples.
I will take a closer look tomorrow. Right now I do not see anything wrong with the mp3 files you provided. MC shows Album Artist as "The Beatles" in the Action Window. I also examined them using MediaInfo and the tags look normal in that too. I will try a conversion and also check what is in the tag fields in debugger tomorrow.
-
I use the tag editor built into DBpoweramp as my de facto editor and that's where I see the duplicate. Perhaps it doesn't show up in other players or editors?
Later:
I have viewed the MP3 files in another tag editor (MP3Tag) and it shows two identical Album Artist entries rather than duplicate values for one field entry as DBpoweramp does.
-
We write Album Artist tag in two places for maximum compatibility - TPE2 and TXXX Album Artist.
I do not know how dBpoweramp deals with these tags, but I guess it reads both and show both. I believe they should just use one value.
So there is really no issue here.
-
Ok. My fear was that the double entry would cause problems when imported into other applications, such as iTunes. But rather than duplicate entry in one field, as dBPa implies, it's more a case of the Field itself being duplicated which I suspect will not cause a problem.
Thank you kindly for looking into this.