Am I correct in thinking MMC only reads ID3V1 tags?
ID3v2 Tags?
Collapse
X
-
Re: ID3v2 Tags?
Now I've done some more checking I do believe that's what's happening - MMC is only reading the ID3V1 tag.
I've just updated all my tags to MusicBrainz format (which took a hell of a lot longer than I anticipated) and, afterwards, told MMC to refresh its database details from the ID3 tag for all tracks.
As an example, let's look at the album called One Woman: The Ultimate Collection. The title is stored correctly in the ID3V2 tag but is shortened in the ID3V1 tag to One Woman: The Ultimate Collec. What is now stored in MMC is the shortened version. This is obviously just an example and there are hundreds of others :(
Maybe I've missed a setting somewhere which, when I change it and re-do the refresh from ID tag, will correct the database? (he asked not very hopefully).Comment
-
Re: ID3v2 Tags?
MMC is based on dBpoweramps codecs so they read (in this order)
APE2
ID3v2
ID3v1
Make sure you have the latest Music Converter Installed.Comment
-
Re: ID3v2 Tags?
This is my DMC configuration options. I think these are the latest versions aren't they?
Sounds like this might be fixable if we can figure out what's wrong
Kevin
Version Information
dBpowerAMP Music Converter: Release 11.5
Power Pack & Mp3 License: [ Registered: Yes ]
dBpowerAMP Audio Player: Release 3 Beta 6
dBpowerAMP CD Writer: Not Installed 'easy way to burn audio cds'
Sveta Portable Audio: Not Installed 'enhance your portable player'
Contact Information
Web Site: http://www.dbpoweramp.com
Support: http://www.dbpoweramp.com/support.htm
Support Forum: http://forum.dbpoweramp.com
Codec Central: http://www.dbpoweramp.com/codec-central.htm
Add extra [en/de]coding abilities such as m4a, wma, etc.
Smart Install Codecs
Windows Media Audio: .wma
Musepack: .mpc
Mp4 (AAC): .mp4
Flac: .flac
Monkeys Audio: .ape
OptimFROG: .ofr
Shorten: .shn
WavPack: .wv
Advanced Audio Compression: .aac
===Shell Integration===
Convert To (right click): On
Edit Tag (right click): On
Popup information Tips: On
Explorer ID Tag Property Page: On
Explorer Columns: On
===Codecs===
Installed Compression Codecs (Write)
Mp3 (Lame): Lame Version 3.96.1 [ .mp3 ]
Test Conversion (No Write)
Wave: [ .wav ]
Installed Input Codecs (Read)
Auxiliary Input Decoder: .aux
CD Input Decoder: .cda
Midi Input Decoder: .mid; .midi
Mp3 Input Decoder: .mp3; .mp2; .mpga; .mpa; .mpx; .mpg; .mp1
Ogg Vorbis Input Decoder: .ogg
Wave Input Decoder: .wav
===Options===
dBpowerAMP Reference Options
Pro. Frequency Conversion: On (slower but high quality)
Mp3 Input Decoder
CRC Errors: Ignore
Decode To: 16 bit (dithered)
Wave Compression Codec
More than 16 bit or 2 Channels: Write WaveFormatEx Header
===ID Tag Options===
Mp3
Tag Creation: ID3v2
Write ID3v1 Version: v1.1
ID3v1 UTF8 Read: Yes
ID3v1 UTF8 Write: No
Write ID3v2 Unicode: Yes
Write ID3v2 Version: v2.3Comment
-
Comment
-
Re: ID3v2 Tags?
I have a feeling that ID tags may not be changed for audio file types for which you don't have the encoding codec, does that make sense?
No idea what this may or may not have to do with the problem at hand.
On a different note:
I just noticed this : a midi decoder codec? That's misleading, isn't it Spoon? Yes, midi can be played by dAP, but decoding midi is not the same notion as it is for other audio types. Conversion is not possible yet, only recording through dMC Auxiliary Input as it is palyed the soundcard.Comment
-
Re: ID3v2 Tags?
Originally posted by SpoonHold the mouse over a file, is the ID3v2 tag read?
[Later] So I uninstalled dMC and dAP, rebooted, then reinstalled them but it made no difference - the v1.1 tag is still the one Explorer displays.
MP3TagStudio, Tag&Rename and TagScanner can all see an ID3V2.3 tag.
MMC reports 1.1:
Length (m:ss) : 3:22
Size : 6084KB
Original Size : 34946KB
Compression Ratio : 5 to 1 (17 %)
Preferrence : 4
Year : 1970
Times Played : 0
Date Added : 03 January 2006
Volume Boost : Auto [Yet to set]
Variable Bitrate (Kbps) : 245
Frequency : 44100
Channels : 2 [Stereo]
Level : MPEG 1 Layer III
Encoded By : LAME3.96r Preset Extreme
ID Tag : ID3v1.1
Title : Ain't No Mountain High Enough
Artist : Diana Ross
Album : One Woman: The Ultimate Collec
Year : 1970
Genre : Soul
Track : 6Comment
-
Re: ID3v2 Tags?
[Later still] I think it may be the MusicBrainz (MBz) data in the tag (defined here) that may be confusing MMC. I have a few tracks that I didn't add MBz data to and they show in Explorer as having v2.3 and v1.1 tags. Everything that I've tested that has the MBz data in the tags shows v1.1 only.
Is there somewhere I can put a 'problem' file for you to see?Comment
-
Comment
-
Re: ID3v2 Tags?
Thanks Spoon but after spending a lot of time with this I now know what the issue is - the tags in question are ID3V2.4 tags and dAP supports up to v2.3. I haven't found any other tagger that will support 2.4 either.
I then told the MusicBrainz (MBz) tagger to save the data in 2.3 utf16 format and tested those with dAP, MP3 TagStudio, Tag&Rename, TagScanner, Dr.Tag, Jaikov and Magic-tagger (the last two are supposedly MBz-aware).
Out of that long list only dAP and MP3TS would correctly display accented characters and edit the tags without corrupting the MBz data - nice work Spoon .
The only problem I have now is it doesn't appear to be easy to change the v2.4 tags (the MBz tagger default) that are currently in over 10k files to 2.3 :(.Comment
-
Re: ID3v2 Tags?
Any non-standard tags will not be preserved by dMC, regardless. Things like artwork, lyrics, etc, will get lost in any conversion, no matter which ID tagging convention is used.Comment
Comment