Skip to main content
Topic: [BUG] Multiple metadata fields not working (Read 2268 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[BUG] Multiple metadata fields not working

To reproduce do the following:

1. Select an audio file in any playlist
2. In the context menu select 'Properties'
3. In the metadata tab double click in any existing tag or create a new one
4. Try to enter multiple fields separated by the ';' character
5. Save the metadata

When you invoke the multiple fields using %<field>% you don't get separated multiple fields but just one field containing everything.

[BUG] Multiple metadata fields not working

Reply #1
Does the field name occur in the list at Preferences | Advanced | Display | Properties dialog | Multivalue fields?

Only fields in this list are split into multiple values with a semicolon.

[BUG] Multiple metadata fields not working

Reply #2
that did the trick. thanks.
I have to say though that this way is not straightforward. Previous versions handled this better IMO.

[BUG] Multiple metadata fields not working

Reply #3
There is something wrong....
When I apply the multiple tags first time it does not separate the entries. I have to edit them again and reapply for them to work.
Does anyone else have this problem?

[BUG] Multiple metadata fields not working

Reply #4
Please give an example.

[BUG] Multiple metadata fields not working

Reply #5
1. Included the STYLE field in the multivalued fields in the advanced properties and saved all preferences:



2. Selected all tracks from one album and included the values separated by a semicolon ';'



3. Applyed the changes and got this:



4. Re edited the field and added a space between the semicolon and the last value:



5. Applyed the changes and now it works:


[BUG] Multiple metadata fields not working

Reply #6
sorry for bumping, but could anyone confirm if this is fixed in the new 0.9.3b3? Cannot test right now

[BUG] Multiple metadata fields not working

Reply #7
Seems to be fixed here in 0.9.3b3, I haven't tested it in 0.9.3b2 so not sure there's this problem to begin with.

 
SimplePortal 1.0.0 RC1 © 2008-2019