Print

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

[ZRocker]

Did you by chance rename the display name for Column heading "Track #" to something else (in Options > Tree & View settings)?

If so, that's the problem...or bug...you have to use the new name in [...] for the templates to work.  This is something I noticed a while back (argh)...maybe someday Matt will realize that simply using the fixed/unchangeable 'Name' field (instead the 'Display' field) in template matching makes much more sense.

[Matt]

I'm taking damage.

However, if you rename "Custom 1" to "Composer", wouldn't you expect to type [Composer], not [Custom 1]?

[dragyn]

I thought the reason for [Artist]=[] was so you wouldn't run into this problem as [Artist] would always be Artist.

I know you're talking about the rename feature but then again, it took me a long time to figure that out too. I think something needs to be done in this area just like you did with the wizard in the search bar.

[ZRocker]

Matt - I expect to put whatever is in the 'Name' field...not what is in the 'Display' field ('Name' seems to be internal).  If I want to rename each, then I can do that...but, I don't use custom fields anyways so I can't change the 'Name' field (it's constant for me).

I would also expect the 'canned' templates that MC supports (presents the user) to ALWAYS work...since MC can't save custom templates the user defines (and show those in the drop-down history listbox).

[nila]

I agree that MJ's templates should ALWAYS work.
I did in fact change Track # to just # as the actual info displayed in this field is small where as  'track #' is way wider than the info to be displayed so # makes more sense as they match size wise.

I again though just presumed that it was to do with the internal field value name rather than the display name that MJ used.

Also - I know your working on a LOT of things, but the ability to add or remove our own name format's really could do with being included into a build sometime soon.

A graphical way of doing this as well with a list of all the fields we are aloud to choose from would again eliminate all errors like this as well as making life sooo much simpler for beginners - maybe with an 'advanced' option that allows the user to enter it manually like it's done now.