Quote

So please be more specific. Which one is being used in Tooltips?

? Can not be more specific than that.

<Picture>

Quote

No complaint. Just a headsup that your Fix is not working anymore on a fully upgraded windows. So maybe update the warning. People might get confused if the fix does not work. And yes I know I can disable it, but I don't like to disable stuff.

It's not "my fix". And it's not a feature I use. It's also not my responsibility to find how things work on Win 11 or any other OS. I just show general info gathered on the forums.

The popup clearly states "none of my scripts use it" -for this particular fature-. I added it to help people recognize why usual features are not working on SMP  (specially using Wine). Whatever users do with it, is their problem. If you don't want to disable it, so be it. If you have any info to "update it" for Win 11, great, but there is nothing more I will do.

About the scaling thing ... I was able to solve it by changing the font in globFonts just as you suggested and restarting fooBar. After that I changed it once more to the exact original values, and restarted fooBar once again. Also no issues.
So it seems as if something (Spidermonkey?) checks if globFonts is changed/touched and issues a kind of reset with the desired result.

Fonts used by scripts at multiple places on UI. File is loaded on the fly at startup, so no hard-saving on properties is involved (thus only requiring a panel reload to use the new values). The fallback font can not be changed, is forced by SMP/foobar2000.

Since your Playlist-Tools have an excellent routine to resize buttons and text, would it be an idea to include a touch of the globFonts file (or give a popup with info about globFonts)? You won't be changing any actual data so it would not hurt anything else out there.

You mention that Bio Script configuration will not work. I don't know which Bio Script you are referring to, but I use WillB's and I have no issues whatsoever with using that script or it's configuration on the system that gets the SO features warning popup. So if you are referring to WillB's script the SO features warning is in my case a false positive.

new ActiveXObject('Scripting.FileSystemObject');
new ActiveXObject('MSXML2.XMLHTTP');
new ActiveXObject('ADODB.Stream');

Another thing is that the popup is completely random. Only about 50% of the times I start fooBar on that machine I get the popup. Maybe you have an idea why it is a random thing.

Quote

About the scaling thing ... I was able to solve it by changing the font in globFonts just as you suggested and restarting fooBar. After that I changed it once more to the exact original values, and restarted fooBar once again. Also no issues.
So it seems as if something (Spidermonkey?) checks if globFonts is changed/touched and issues a kind of reset with the desired result.

Obviously that's how it works. There is no need to restart foobar, just reloading the panel works too. Any setting there will be applied at startup in all my scripts as default values. BTW all this is already written on the json file...

Code: [Select]

new ActiveXObject('Scripting.FileSystemObject');
new ActiveXObject('MSXML2.XMLHTTP');
new ActiveXObject('ADODB.Stream');

If there is a problem, one of those, in your system, in a blank panel will make it crash. And all 3 are used on Bio.

So this plugin only works if using 32-bit Foobar, and not 64 (v2), is that correct?

@regor

Case made a nice tool to scan for Truepeaks and number of clipped samples which integrates with the Replaygain context menu.

Would you consider to add this utility to be selectable in the button_automation_tags.js script?

Quote from: Defender on 2024-03-28 14:35:57

@regor

Case made a nice tool to scan for Truepeaks and number of clipped samples which integrates with the Replaygain context menu.

Would you consider to add this utility to be selectable in the button_automation_tags.js script?

That plugin also has 3 different settings for tags usage and all tags are customizable... which means I would have to add all those possibilities on the script. That's a nope. Specially since that script is just meant for my personal usage.

I may add a single option using the default custom tags and nothing more. People may edit the script to change the tags though.

Quote from: regor on 2024-04-04 10:45:38

Quote from: Defender on 2024-03-28 14:35:57

@regor

Case made a nice tool to scan for Truepeaks and number of clipped samples which integrates with the Replaygain context menu.

Would you consider to add this utility to be selectable in the button_automation_tags.js script?

That plugin also has 3 different settings for tags usage and all tags are customizable... which means I would have to add all those possibilities on the script. That's a nope. Specially since that script is just meant for my personal usage.

I may add a single option using the default custom tags and nothing more. People may edit the script to change the tags though.

Great!
Would be great just to hit one button that does all things I want to scan, instead of one button and a couple of context clicks.

If you are referring to edit either tags_automation or buttons_tags_automation, I have to admit I had a look and those two scripts are way above my level to make changes unless I get specific instructions where to make those changes.

Quote from: Defender on 2024-04-04 11:00:41

Quote from: regor on 2024-04-04 10:45:38

Quote from: Defender on 2024-03-28 14:35:57

@regor

Case made a nice tool to scan for Truepeaks and number of clipped samples which integrates with the Replaygain context menu.

Would you consider to add this utility to be selectable in the button_automation_tags.js script?

That plugin also has 3 different settings for tags usage and all tags are customizable... which means I would have to add all those possibilities on the script. That's a nope. Specially since that script is just meant for my personal usage.

I may add a single option using the default custom tags and nothing more. People may edit the script to change the tags though.

Great!
Would be great just to hit one button that does all things I want to scan, instead of one button and a couple of context clicks.

If you are referring to edit either tags_automation or buttons_tags_automation, I have to admit I had a look and those two scripts are way above my level to make changes unless I get specific instructions where to make those changes.

Not gonna happen. As I said (and the readme states), this script is for my personal usage. If people want to tweak it, great, but not gonna help with that.

EDIT: The single entry without extra things seems to work fine, will upload it later.

Should be working now. Also fixed a long time bug with Chromaprint requiring manually running next step in some cases.

I may think about adding fingerprints to a json database instead of files, considering the problems on x32 foobar v2 and tag caching.

Great. Where can I find it? Checking for updates does not find it.

Another thing is if I remember correctly that it is mentioned somewhere in your documentation that in order to get FooID running you have to put FooID.dll in the root folder of %fb2k_profile%. I had to put in user_components\foo_biometrics to get it working.

Quote

Great. Where can I find it? Checking for updates does not find it.

If there is no update, it's because there is no update. Obviously. I don't create an update for every minor thing I change.

Check the Nightly. As shown at the wiki.

Quote

Another thing is if I remember correctly that it is mentioned somewhere in your documentation that in order to get FooID running you have to put FooID.dll in the root folder of %fb2k_profile%. I had to put in user_components\foo_biometrics to get it working.

That's not what the instructions say about FooID.dll. Nothing goes to the profile root.
https://github.com/regorxxx/foobar2000-assets/tree/main/FooID

Error: Spider Monkey Panel v1.6.1-mod (ListenBrainz Tools Button: Playlist Tools: Buttons Bar v1.1.0 by regorxxx)
include failed:
themedButton is not defined

File: buttons_others_device_selector.js
Line: 30, Column: 2
Stack trace:
  @buttons_others_device_selector.js:30:2
  includeButton@buttons_toolbar.js:223:4
  reducer/</</<@helpers_xxx_prototypes.js:353:60

- Buttons: changed filename for 'buttons_others_device_selector.js' to 'buttons_device_selector.js' and 'buttons_others_main_menu.js' to 'buttons_utils_main_menu.js'. Before updating, rename all instances of these names at '[foobar2000 profile]\js_data\buttons_XXXXX.json' with the new names. 'buttons_XXXXX.json' are all json button toolbar files.

Well, actually you're a bit wrong here, haha I did read the change log at the time but I simply forgot to do those changes later when I updated, I assumed I already made those changes....I guess lately I was frustrated by so many annoyances...Foobar v2, foo_plorg, and the list is very very long...Or as you saw recently foo_skipcount....where you helped the developer with those bugs, some of them I've also noticed...When you have many components it's hard to keep track with so many changes , especially now with Foobar v2...

I solved the problem by resetting the toolbar, then I reimported the user presets for the Playlist Tools, the other buttons didn't have many settings, so nothing is lost.