Print

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

[plopje]

Hi everyone.

I think MC is a real gem, but apperantly, it has flaws...

I recently noticed a strange behaviour of MC when ripping and updating filenames from filetags.
After ripping (all tracks were recognised) the files were not named after the song but their paths and names were exactly like this:

[artist]\[album]\[track #] - [name](1).mp3
[artist]\[album]\[track #] - [name](2).mp3
etc.

However, all the right tags (like album, artist and song) were in the files.

So I tried to change filenames by using "Rename files from properties" from the Library Tools. It didn't work. MC just tried to overwrite my files with files with identical names.

Looking for a solution I remembered that I changed the way the fieldnames had to display. I made a number of dutch translations (Tools --> Options --> Library Fields --> Edit).

Now I discovered that when fieldnames are changed that way , MC uses the displayed text of a rule and not the rule itself for (re)naming a file. As a workaround, I changed the text of a rule to match my translation. Then it worked again as expected.

However, IMHO, this is not the way it should work, because when I try to select a field in MC, only built-in field names are displayed and not the changed (translated) ones.

Any chance there will be a solution?

[Doof]

What exact naming criteria are you using?

To get the results you want, you should be using:

[ARTIST]\[ALBUM]\[TRACK #] - [NAME]

I'm pretty sure they need to be in all caps.

[Matt]

In the next build:

Changed: Building filenames from info now supports both field names and field display names. (in case of user editing)

(note: rules aren't case sensitive)

[Marko]

What exact naming criteria are you using?

To get the results you want, you should be using:

[ARTIST]\[ALBUM]\[TRACK #] - [NAME]

I'm pretty sure they need to be in all caps.

Yup. But if say, you change the Track # column header to just show #, then [TRACK #] in the mask will not use the field. The mask must be changed to

• .
  
  plopje,
  If you use a common filenaming formula, it *should* be saved in the presets flyout after you've used the string once.

[plopje]

Yes Marko, that's correct. Is is saved as a Preset. That is a help when I am using my workaround, but it is not exactly what I mean. When I want to build a new rule (with different fields)  I still can't see them in the pick-list.

But.... Matt is telling me that it will be changed in the next build. That's great!  Can't wait to pick it up.

Thanx