Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Michel Lefebvre]

I just noticed that the COMM (Tool Version) Tag inside some of my MP3s shows up as 11.0.190, even if the files were ripped over a year ago and never touched or played since...

Is that normal? I would have thought that the "File Properties" - "File Type Info" window in the AW would read the MC version number that was inserted in the tag when the MP3 was created or modified, not the current version of MC...

Other files seem to indicate the right version number.

Could this somehow be related to the import process?

Thanks!

Michel.

Media Center Registered 11.0.190 -- C:\Program Files\J River\Media Center 11\

Microsoft Windows XP 5.1 Service Pack 2 (Build 2600)
AMD Athlon 1989 MHz MMX / Memory: Total - 1048 MB, Free - 576 MB

Internet Explorer: 6.0.2900.2180 / ComCtl32.dll: 5.82 (xpsp_sp2_rtm.040803-2158) / Shlwapi.dll: 6.00.2900.2180 (xpsp_sp2_rtm.040803-2158) / Shell32.dll: 6.00.2900.2180 (xpsp_sp2_rtm.040803-2158) / wnaspi32.dll: 4.71 (0001) , ASPI for Win32 (95/NT) DLL, Copyright © 1989-2002 Adaptec, Inc. / Aspi32.sys: 4.71 (0001)

Ripping /   Drive J: MATSHITADVD-RAM LF-D521   Mode:ModeSecure  Type:Auto  Speed:Max
  Digital playback: Yes /  Use YADB: Yes /  Get cover art: Yes /  Calc replay gain: Yes /  Copy volume: 32767
  Eject after ripping: Yes /  Play sound after ripping: No 

Burning /  Drive J: MATSHITA DVD-RAM LF-D521    Addr: 1:1:0  Speed:12  MaxSpeed:12  BurnProof:Yes
  Test mode: No /  Eject after writing: Yes /  Direct decoding: No /  Write CD-Text: Yes
  Use playback settings: No /  Normalization: None

[GHammer]

I just noticed that the COMM (Tool Version) Tag inside some of my MP3s shows up as 11.0.190, even if the files were ripped over a year ago and never touched or played since...

Is that normal?

I wonder why this is needed at all. Is there some use that MC makes of the tool and version? If not, then why write it?

[Michel Lefebvre]

I wonder why this is needed at all. Is there some use that MC makes of the tool and version? If not, then why write it?

One reason I could think of: Let's say a perticular version of MC had a bug, purely as an example, in the Analyse Audio code and the BPM tag was wrong, one could search for all the files that were analysed with the buggy version and re-do the analysis with a corrected version of MC, instead of re-analysing 30,000 files.

I'm sure there would be more reasons if I put my thinking cap on, but I have a bad cold so thinking hurts right now... :-)


Michel.

[GHammer]

One reason I could think of: Let's say a perticular version of MC had a bug, purely as an example, in the Analyse Audio code and the BPM tag was wrong, one could search for all the files that were analysed with the buggy version and re-do the analysis with a corrected version of MC, instead of re-analysing 30,000 files.

Couldn't I do this by file date or import date instead?

[Michel Lefebvre]

Couldn't I do this by file date or import date instead?

You could, unless you did more tagging later on. Then the file date would change. The import date would work (except if you had to re-import the files in the past, then that would not, but that is a rare case (at least for me...).

M.

[GHammer]

You could, unless you did more tagging later on. Then the file date would change. The import date would work (except if you had to re-import the files in the past, then that would not, but that is a rare case (at least for me...).

Perhaps MC should not change file dates then. Other tools offer that option.

[Michel Lefebvre]

Perhaps MC should not change file dates then. Other tools offer that option.

Would be a good option. I probably would not use it... I use the file date to find the files that were modified since my last backup. This way, I only backup the files that actually changed.

M.

[GHammer]

Would be a good option. I probably would not use it... I use the file date to find the files that were modified since my last backup. This way, I only backup the files that actually changed.

Hmmm, what do you use to backup with?
The app I use does not care about dates/times, it simply copies changed files.

Magic I guess!

[qwert73]

Let me decide where the tags are stored in case of ID3v2

(f.e. I want to store the disc# in its own predefined frame, just imagine that case: you have stored this information in MC in the Comm-field and other applications display nothing under "disc#" because they search for the original frame).
 

[KingSparta]

be it known any 3rd party plug-in may also write to the file, this would update the tags.

I know most of my plug-ins will save info to the tags.