Hm, I know that Boroda74 hasn't been around for a wee while (hope all is OK!).
But maybe else has encountered this:
For 3+ years I've had a (for me complicated) regex script Boroda helped me with.
Now, after upgrading to Musicbee 3.5 an issue that occassionally occured (i.e. in dozens to 100s of uses per month, it occurred once every 3-6 months but always had me stumped, and always was on a very few files - with no pattern I have noticed...), and this has now become a constant after updating.
So what the 'script' is meant to do:
- it's based on one of the default combine scripts
- it's meant to take the rating (star) value [with half-stars] as numerical [not the actual numerical rating value - which it always just worked, regardless of the format - since id3 & vorbis have different absolute rating values, I assumed this was some magic musicbee api bit inbetween that was converting this correctly...]
- then, take a numeric value from a second [custom] field (call 'Energy' that could have values from 0 -10)
- then combine the 2 with a ' - ' inbetween and write them to 2 other fields (so '10 - 5' would be the resulting tag value for a 5 star rated track, with an Energy value of 10...)
What it now does:
- the energy value gets always written correctly still
As for the weird bits:
- the star value now gets written as:
- sometimes the numerical value (only on flac files, I have not seen this happen on id3 tags, so a vorbis rating of 60 for a 3 star track, 20 for a 1 star track, etc pp)
- sometimes the rating value gets written as 1 (regardless of the actual rating / star value)
- on top, IF the rating value gets written as 1, the [custom text 1] ' - ' always gets written twice [minus a ' '...], resulting in '10 - - 1' [instead of '10 - 5']
So, in the above example track [with 10 & 5 respectively] I may end up with '10 - - 1' or, ' 10 - 100'
I'm a tad lost there.
If anyone spots anything off here - and feels like helping - I would love to fix this up again....
I'll add a screenshot of both ASR Windows as well:
--------------------------------------------
--------------------------------------------
Also - could it be that with MB 3.5 there's something that changed, and therefore ASR Scripts would need to be adjusted ?
Did anyone encounter issues with old ASR presets after switching to 3.5 ?
