by John R Leddy » Mon Jan 13, 2014 1:13 pm
Lowlander wrote:No, MediaMonkey can only show columns it natively supports.
You could see if you can get the value into a MediaMonkey custom field so you can display it that way. I'm not familiar with MP3Tag so I only assume it could do this. (
http://www.mediamonkey.com/wiki/index.p ... erties/4.0)
Lowlander,
Thank you for the link to the Track Properties Table.
I created a
%custom1% tag within Mp3tag and this displays its value in MediaMonkey's
Custom 1 column.
There would be no problem in assigning bit depth values en masse within MediaMonkey by highlighting as many tracks as required, right-clicking on a file to choose
Properties to open the
Edit Properties for multiple files box, choosing the
Classification tab and editing the
Custom 1 textbox (renamed
Bit Depth) to whichever value was required.
However, performing this task has MediaMonkey automatically
adding tags which were not asked for or required:
ALBUM ARTIST
ALBUMARTIST
DISC
ENCODER
ENSEMBLE
Clearly a bit dysfunctional.
Two solutions readily come to mind:
1. Add a fully customisable column which allows the user to allocate his or her chosen or created tag value; or
2. Add a
%bitdepth% column to MediaMonkey.
Both of which, besides being two minute jobs in themselves, and possibly a more logical approach, have the added bonus of reducing stress on those of us suffering from Tagging OCD!
All the best,
John.
[quote="Lowlander"]No, MediaMonkey can only show columns it natively supports.
You could see if you can get the value into a MediaMonkey custom field so you can display it that way. I'm not familiar with MP3Tag so I only assume it could do this. (http://www.mediamonkey.com/wiki/index.php/WebHelp:About_Track_Properties/4.0)[/quote]
Lowlander,
Thank you for the link to the Track Properties Table.
I created a [b]%custom1%[/b] tag within Mp3tag and this displays its value in MediaMonkey's [b]Custom 1[/b] column.
There would be no problem in assigning bit depth values en masse within MediaMonkey by highlighting as many tracks as required, right-clicking on a file to choose [b]Properties[/b] to open the [b]Edit Properties for multiple files[/b] box, choosing the [b]Classification[/b] tab and editing the [b]Custom 1[/b] textbox (renamed [b]Bit Depth[/b]) to whichever value was required.
However, performing this task has MediaMonkey automatically [b]adding tags which were not asked for or required[/b]:
[b]ALBUM ARTIST
ALBUMARTIST
DISC
ENCODER
ENSEMBLE[/b]
Clearly a bit dysfunctional.
Two solutions readily come to mind:
1. Add a fully customisable column which allows the user to allocate his or her chosen or created tag value; or
2. Add a [b]%bitdepth%[/b] column to MediaMonkey.
Both of which, besides being two minute jobs in themselves, and possibly a more logical approach, have the added bonus of reducing stress on those of us suffering from Tagging OCD!
All the best,
John.