Print

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

[V-Man]

Hi Matt!

Thanks for the new List data type, which works a treat.

What would really help now is if the Artist field could be (optionally) made a 'List' type field, to enable multiple artists.

Also, it would really help me if for all fields one could specify what to use in Rename Files From Properties if that field is not filled in. This would be text that could include other fields.

Eg. I would configure this option for the Album Artist field to be "[ARTIST]".

Then if I rename the following tracks:

Artist: Christina Aguilera; Redman
Name: Dirrty
Album Artist: Christina Aguilera
Album: Stripped
Track: 16

Artist: Avril Lavigne
Name: Complicated
Album Artist:
Album: Let Go
Track: 3

using:

Base Dir: D:\Music
Directory: [MEDIA TYPE]\[ALBUM ARTIST]\[ALBUM]
Filename: [TRACK] - [NAME] - [ARTIST]

The filenames would become:

D:\Media\Audio\Christina Aguilera\Stripped\16 - Dirrty - Christina Aguilera; Redman.mp3

D:\Media\Audio\Avril Lavigne\Let Go\03 - Complicated - Avril Lavigne.mp3

[Phydeaux]

I second that.

Also, on a similar theme is to be able to change the groups that certain fields appear in. For example, I'd like to move "Composer" to General instead of having it in Extended.

At any rate, I'm over the moon that the List feature is there!

P.

[Phydeaux]

I've just come across this bug in the media library.



For tracks that have multiple soloists, ALL soloists appear under each group that includes at least ONE of the soloists.

Here is the offending soloist string: "Bonsignore, Anne (Soprano); van Heyzen, Shylo (Soprano); Lewis, James (Tenor); Martin, Chris (Baritone)"

The the above soloists appear under the "A-E" list, the "K-O" list and the "U-Y" list.

Also notice the space before the first item. This is because it is the last item on a list.

P.

[Phydeaux]

and there is a spelling error of my own creation:)

I've also noticed that MC has lost a good deal of my soloists and I can't say why. Quite possibly they were not saved properly in the tags because I have done a library re-import... oh well...

P.

[Phydeaux]

And another thing:

(others) has the rule: (-[Soloist]=a-z,0-9) (mediatype=[audio])
(others)/(unassigned) has the rule: ([Soloist]=[]) (mediatype=[audio])

Are these intentional?

P.

[Jaguu]

Also note that the default icon is a CD! This might be OK for music, but if you have fields like Gallery, Country, Movement referring to art (images) or Composer, Soloists, Orchestra, Conductor, the default icon is not appropriate.

There should be at least a media type dependant default icon, or even better, user selectable from a list of icons!

But OK, we will wait for 9.1! My last boss always used to say "Get it out, get it out!" It is high time to get MC9 out!

[aussie1]

WOW! Adding the list data type exceeded my expectations! I'll use this a lot. Thanks for a great addition!

[aussie1]

Question:  I created a field using the list data type and selected 'Store in File tags (when possible)'.  I entered some data an 'Applied Changes'.  However, the data is not stored in the tag.

Is this intentional? Is it possible to store the data in the tag? I would prefer this.

[aussie1]

Cancel my last question. I had deslected the option to "update tags when file info changes".  I selected that option and writing worked fine.

[V-Man]

Phydeaux

I can't check right now, but I think you can move Composer to the General category via the Tree And View Settings part of the Options dialog.

Certainly, I have added my own custom field to the General category.

[Phydeaux]

When "Composer" was not yet part of the default setup, I had my own composer field in General. However, after a while, there was a need to reimport my library. The default structure, when I did my reimporting, was to have composer as part of the extended information. When I last checked, it was impossible to change any of the attributes of the default fields.

To me that's a bit counterproductive. I can understand why one would not want to have said fields deleted (but even then...), but to change artist and genre to a delimited field and move composer to where I want it... Is that _really_ too much to ask?

I'm happy to live with it at present, but will hope for a change in the future

[Doof]

How about, as a work around, creating your own fields for Genre, Artist, etc, in the groups you want them, and (this is the part that might not work) as the data type you want and then use the Copy Fields utility to copy all the data you want over, modify the files you want, and then creates view schemes that use those fields instead of the default ones?

Would that work? I haven't tried it.

[Doof]

I just tried it. It seems to work pretty well.

[Phydeaux]

That is a fairly good idea and I'm sure that it would work. The only other problem then is that you'd be left with a whole lot of unused fields that you can't, at the very least, hide...

Hmmm... there may be issues with trying to keep both fields current, but you could establish a workflow that... well... worked.

Thanks for the suggestion! I'll try this when I get home

P.

[Doof]

You can hide Artist, Genre, and all those.

They'll still show up in the list, but they at least won't be displayed.

I changed the Display of "Artist" to "Old Artist" and changed the keywords as well.

Then I added a field named New Artist, but gave it a Display of Artist, and gave it the same keywords that Old Artist used to have.

There is the added step of having to Copy Fields for every file you add, but it does seem to work.

Of course, this would all be moot if we could just edit the default fields.

[Phydeaux]

Hmm... That is my main problem --  the properties list.

Oh, I've just noticed: the properties list shows the name and not the "Display" setting....

Hmm... I'll have to wait until someone hears my plea!!

P.