jbuski / erlandplugins

Automatically exported from code.google.com/p/erlandplugins
0 stars 0 forks source link

CustomScan/CustomTag not seperating multi values #62

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
CustomScan 2.2

SqueezeCenter Version: 7.3.1 - 24372 @ Fri Dec 19 17:56:44 PST 2008
OS: Windows Vista SP1

When using test mode of SQLPlaylist (with a select from
customscan_track_attributes as a parameter), the drop down list includes
items separated by ";". These items should have been treated as multiple
value fields by CustomScan. Looking at the Plugins page for CustomScan,
CustomTag has values in "Tags to scan" and no values in "Single value tags".

This behavior is new for this release (as in it worked for the previous
release of CustomScan).

My library consists of a mix of flac and mp3 files. You might need to test
the reproduction scenario below for ID3 and Vorbis.

My scanned fields include one field in quotes as it has a space in the tag
name. So "Tags to scan" looks like:

    field1,'field 2'

What steps will reproduce the problem?
1. Modify file with multiple values (delimed by ";") in a user defined tag
2. Add the tag to customscan as a customtag in the "Tags to scan" area
3. Use CustomeScan scan for CustomTag
4. Use SQL playlist to make a parameter that includes the tag
5. Verify that items in the dropdown are not separated into multivalues

Original issue reported on code.google.com by montiw...@gmail.com on 30 Dec 2008 at 1:02

GoogleCodeExporter commented 8 years ago
My comment about the quoted "Tags to scan" is not correct. My tags to scan line 
looks
like:

    field1,field 2

MP3 files seem to have all multivalue fields separated properly. Perhaps the 
problem
is restricted to Vorbis comments?

Original comment by montiw...@gmail.com on 30 Dec 2008 at 1:24

GoogleCodeExporter commented 8 years ago
I can't reproduce this, I tried tagging with:
metaflac --set-tag="MYFIRSTTAG=Value1;Value2" song1.flac
metaflac --set-tag="MY SECOND TAG=Value1;Value2" song2.flac

And set the "Tags to scan" to: 
MYFIRSTTAG,MY SECOND TAG

The result is that I get separate values for both MYFIRSTTAG and MY SECOND TAG 
fields
after scanning.

If you can't get it to work, I would appreciate if you could send me a file 
with the
problem together with the plugin/customscan.prefs file where the preferences 
are stored.

Original comment by erlan...@hotmail.com on 31 Dec 2008 at 7:05