Highlighting Rules with 3.6.8694+

[phred]

Using 3.6.8688 which works. Later versions have the issue I'm reporting.

I have found that most of my highlighting rules are not being respected when in Track Details view. They all work fine with 3.6.8688, but are not working with 3.6.8694 and newer.

Digging a little deeper...
- I have a rule to show tracks with no lyrics. The newer 3.6 versions are showing that -all- my tracks do not have lyrics. Which is not true.
- I have a rule which shows which files have a PDF file in the directory. If I do a custom search for "Has PDF" nothing is returned so I can't tell if the highlight rule is showing or not.
- I have a rule which shows if a track/album has no volume leveling. All my tracks/albums have volume leveling, yet the highlight is showing that no tracks have it.

Let me know if you need more information.

Thanks.

EDIT for claification

[hiccup]

Using 3.6.8688

Best to update to most recent 3.6.8697 that was released today.
There is currently some stuff going on regarding MusicBee recognising if (virtual) tags are blank or not.

[phred]

Best to update to most recent 3.6.8697 that was released today.

Did that already and the issue exists. Which is why I put "3.6.8694+ " but I see how my stating the version that works at the top of my OP can be confusing.

[Steven]

this should fix the issue
https://getmusicbee.com/patches/MusicBee36_Patched.zip

[phred]

this should fix the issue

It did indeed. Thanks.

[shineangelic]

this should fix the issue
https://getmusicbee.com/patches/MusicBee36_Patched.zip

I just tried the patched 36 version, but in my case it's still present: this bug looked very similar to one I had a couple months ago, posted here

I am also using Hightlighting rules, with a couple icons to show whether the song has lyrics or some value above a threshold.
When I start MusicBee those highlighting rules are applied to ALL songs, unless I go back to settings and re-apply them. At that point (even with no actual config change) the icons are shown correctly. In my case it's there since version 3.5.8447 minimum

[sapr]

I do have the same problem too (some highlight rule suddenly apply to (almost) all tracks), since updating to 3.5.8698.

The highlight rule concerned is checking if "Sort Composer" exists. I was rigorous on making my library free of any "Sort Composer" tag, and use the internal sorting within MusicBee instead (I mean the "enable custom sorting" option). With 3.5.8447 there was no problem (no highlight shown); but with 3.5.8698 all tracks that contain Composer tag has the "Sort Composer" rule highlight applied. Just tried 3.5.8727 (newest patch as of today) and the problem persists.

[phred]

@shineangelic...
Your issue doesn't not appear to be the same as what I reported in the OP. I suggest creating a new bug report as what I reported has been fixed.

@sapr...
Your issue does indeed sound like what I reported. But the patch that Steven posted is for version 3.6 therefore the issue won't be resolved until you update to 3.6. Which is only in an early beta at this point. Many are using it, so if you wish to try it, and you're not using the Windows Store version, you can get it from here:
https://getmusicbee.com/patches/MusicBee36_Patched.zip.

I suggest you download the latest portable 3.5 version from the first forum topic placing it in a directory outside of Windows control - such as C:\MusicBee. Do a minimal configuration. Then apply the 3.6 patch directly over the portable 3.5. Once satisfied, you can apply the 3.6 patch over your current 3.5 installation and then delete the temporary portable.

[scorpion]

You're talking about a version 3.6.8694.
But the latest official version on this page for download is 3.5.8698. Am I missing something?

[phred]

You're talking about a version 3.6.8694.
But the latest official version on this page for download is 3.5.8698. Am I missing something?

But the patch that Steven posted is for version 3.6 therefore the issue won't be resolved until you update to 3.6. Which is only in an early beta at this point. Many are using it, so if you wish to try it, and you're not using the Windows Store version, you can get it from here:
https://getmusicbee.com/patches/MusicBee36_Patched.zip.

I suggest you download the latest portable 3.5 version from the first forum topic placing it in a directory outside of Windows control - such as C:\MusicBee. Do a minimal configuration. Then apply the 3.6 patch directly over the portable 3.5. Once satisfied, you can apply the 3.6 patch over your current 3.5 installation and then delete the temporary portable.

[Steven]

this should fix the issue
https://getmusicbee.com/patches/MusicBee35_Patched.zip

and if using v3.6:
https://getmusicbee.com/patches/MusicBee36_Patched.zip

unzip and replace the existing musicbee application files

[sapr]

this should fix the issue

Thx Steven, just confirmed 3.5 version do fix the problem I encountered. Will try 3.6 later today, if I didn't show up reporting again, things should be fine 👍

But the patch that Steven posted is for version 3.6...

Actually I did try 3.6 after writing the post and it's the same, so didn't bother editing the post  

[phred]

@Steven...

It seems that patch version 3.3.8730 reintroduced the issue in my start post. Reverting back to 3.6.8698 fixes the issue.

[Steven]

this should work
https://getmusicbee.com/patches/MusicBee36_Patched.zip

[phred]

this should work

Yes, it does. Thanks Steven.