Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - azcore

Pages: 1
1
It's fixed. Thank you!

2
Rechecked by installing the latest release candidates from scratch just to be sure, but as their build numbers correspond to the ones I tried before (RC3 =  3.6.9198, RC2 = 3.6.9192), the result is the same - the plugin works as expected with RC2 but not with RC3.

3
After I applied the latest patch from https://getmusicbee.com/patches/ (the one from 2025-03-08, build number 3.6.9198) the Playlist History plugin stopped working for me. Pressing the buttons to go back in playlist history has no effect now.

Rolling back to a previous patch from a few days ago (build number 3.6.9192) fixes the issue.

Also reported in the plugin thread.

4
It seems that the MusicBee 3.6 RC3 has broken the plugin functionality for me.

5

- If the Classical Extras plugin fails to produce correct results at the first matching run you could post a bug report in its thread on MusicBrainz forum.
   (but do the results of any relevant tag actually change when doing a refresh, or is it just the warning that disappears? I myself have always ignored these warnings and things seem to go well regardless)
- If you are refreshing for the purpose of testing scripts, I am guessing it is not an actual problem that my scripts present different results after such a refresh.

So for now I am assuming that my scripts are working well and as intended, and there is not much I could or need to do to accommodate for the above scenarios.

For Classical Extras it's just how the plugin works, it always happens when the files are tagged the first time and it's documented like that.
And I suspect that if the issue triggers on refresh, then it can also occur when retagging already tagged files anew (to accomodate some changes from MB database or retagging them with different options). But like I said, it's not a big deal in any case and I agree that it's something not worth fixing.

6
Yes, exactly, after refreshing the results change sometimes (for some boxsets I have). That's the only issue…
I am curious:
Why would you want to use 'refresh' after these releases (also boxsets) are matched in the right panel and have the correct album genre tags already showing?

When using "Classical extras" pluging you have to refresh at least once (it produces a warning "No file with matching trackid - IF THERE SHOULD BE ONE, TRY 'REFRESH' - (unable to process any saved options, lyrics or 'keep' tags)" the first time). Also I quite often adjust my own scripts with custom renames etc. and test the changes that way.

7
Making sure I understand what you mean:
Do you mean that after a release has already been matched in the right panel, but you then use the 'refresh' function?
I think I recall having noticed that sometimes when I constructed and tested the scripts, but I don't think there is anything I can do about that.
It's how the internals of Picard and the script functions that I am using in the script happen to work.
(it was already a p.i.t.a. finally getting this to work at all)

Yes, exactly, after refreshing the results change sometimes (for some boxsets I have). That's the only issue and that's what I meant when I said that it works great with a few exceptions (meaning those boxsets). No big deal though, and it's really very useful, thank you again!

8
Thank you! It works great so far with a few exceptions.
I notice that sometimes the scripts are not idempotent (change the genre tag when running multiple times in a row) but not yet sure if it's something specific to my setup, will try to debug that.

9
This is a really great idea!
I would like to try it out, but for some reason I don't see the second script of the two mentioned.

Pages: 1