-
Bug
-
Resolution: Fixed
-
Normal
-
None
-
2.6.3
-
None
-
Win 7
Using AcousticBrainz Tags plugin (2.1), scripts which use at least one of its tags don't work as expected.
For example, an script with
$noop(ISMIR2004 Rhythm Classification Dataset "Ballroom dataset")
$unset(ab:hi:ismir04_rhythm:chachacha)
$unset(ab:hi:ismir04_rhythm:jive)
$unset(ab:hi:ismir04_rhythm:quickstep)
$unset(ab:hi:ismir04_rhythm:rumba-american)
$unset(ab:hi:ismir04_rhythm:rumba-international)
$unset(ab:hi:ismir04_rhythm:rumba-misc)
$unset(ab:hi:ismir04_rhythm:samba)
$unset(ab:hi:ismir04_rhythm:tango)
$unset(ab:hi:ismir04_rhythm:viennesewaltz)
$unset(ab:hi:ismir04_rhythm:waltz)
Should delete those tags when High level tags are enabled (and obviously the script too).
Contrary to what I would expect, it never gets applied (it's like those tags doesn't exist yet when the script runs after loading the release). Manually re-applying the script does work (see gif 2).
Similarly, using the high level tags to set some values results in the same errors. None can be used! (see gif 2)
$noop(Timbre tags: timbre -label-)
$set(timbre,$if($gte($substr(%ab:hi:timbre:bright%,2,3),5),Bright,Dark))
Tried another script to merge last fm moods with the "moods" tags by the plugin, and it doesn't work. Again.. because the moods tags provided by the plugin seems to be applied after the scripts run, therefore the merging is overwritten with whatever the plugin outputs.
$copymerge(mood,moodnew) $delete(moodnew)
As can be seen at the gifs, the scripts work fine once the release is fully loaded and using then manually (see gif 2). But they are broken when applied automatically (see gif 1).
- is a dependency of
-
PICARD-2141 AcousticBrainz Mood-Genre conflicts with MusicBrainz genre
- Review Submitted