Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Recent Posts
2
3rd Party Plugins - (fb2k) / Re: Wrapped-SMP
Last post by regor -
Anyone using this with newest foobar v2.25+, please update to nightly version to not have problems. Anyone else may ignore it.

https://github.com/regorxxx/Wrapped-SMP (at bottom)

Newest foobar version is using different file protocols for portable installations + relative paths (library) which breaks some components and scripts (in particular this one).
6
3rd Party Plugins - (fb2k) / Re: Biography Discussion
Last post by regor -
Quote from: Defender on
Marc for which I cannot find any documentation (does it run both under 32bit and 64bit?
All SMP mods only run on 32 bits. Newest SMP mod only runs on foobar v2+. Old mod runs on anything (but it will be slower on foobar v2+ than the newest mode.)

Quote
Is a wrapper available to run older JS3 code?)
No. It's SMP in all regards + some fixes and improvements.

Quote
You worked with all of these versions. What would be the recommended SMP plugin to only run (multiple) single SMP instances with only one WillB script in it in your opinion (in my case 3x BIO/REV, 3x Lib Tree and 1x Find&Play; and of course I also run your Playlist Tools)?
In fact the "best" thing is to have multiple JS components xd I mean... every JS component has a 3GB Ram limit, thanks to mozilla engine limits. If you have SMP and JSplitter, then you can add panels to both of them, and SMP panels would have 3 GB and JSplitter's panels would have another 3GB. Both would run on different engine threads (which may also affect if the panel is blocked when other panels are interrupting the engine).

At least in x64 would work that way. In x32 you would still benefit for having things running in different threads, but obviously there is still a 4GB ram limit.

Also note that whenever the JS engine reaches the ram limit, it crashes all panels from the component. I have run into that many times while testing or using fingerprint tools. If you run panels on different components then you could avoid that.

Ideally, if there is a SMP x64 version at some point.. I would run some panels on SMP and others on JSplitter if I'm running a complex skin or heavy scripts with huge libraries. You may also add JSP3 too to the mix. As long as you find scripts which work on a component and fulfill your usage, use them. Trying to port everything to a single component is in fact worse than mixing them.
8
Other Lossy Codecs / Re: SBR usage of xHE-AAC at 72kbps, 80kbps, and 96kbps
Last post by Klymins -
Thanks. But I'm experimenting with xHE-AAC just because I'm curious, I'm not planning to use it. More than one devices that I use accept only MP3 and WMA as lossy codecs anyway, and I even use the same MP3 files on computers and computer-like devices (e.g. a smartphone) because it is easier for me though this may change. (I prefer MP3 because I don't feel that WMA is really estabilished.)
9
3rd Party Plugins - (fb2k) / Re: Biography Discussion
Last post by Defender -
@regor

I am quite confused and have a simple question that many of us simple users have, I think.

There are now a couple of solutions to run SMP scripts. The original SMP or the mod version on this (32bit only), JSplitter 3.6.1.1x which runs on 32bit and 64bit and has splitter functionality and the new version by Marc for which I cannot find any documentation (does it run both under 32bit and 64bit? Is a wrapper available to run older JS3 code?). All in all quite confusing to choose among those.

You worked with all of these versions. What would be the recommended SMP plugin to only run (multiple) single SMP instances with only one WillB script in it in your opinion (in my case 3x BIO/REV, 3x Lib Tree and 1x Find&Play; and of course I also run your Playlist Tools)?

NB. Whatever solution you hopefully may recommend, I will still have to keep JSplitter since that is the only splitter that protects again crashing to the desktop going fullscreen with a long-time beta visual plugin. For this visual plugin I only need the splitter functionality and not the SMP part of JSplitter.
10
3rd Party Plugins - (fb2k) / Re: Biography Discussion
Last post by regor -
Quote from: sveakul on
Quote from: regor on
As you may expect... your report is vague at minimum. If you expect more updates or help, provide more details.

There have been zero changes related to the usage you described and again zero changes on mod 2 (except the auto-cycling bugfix, also present on original bio).  If there is something wrong, it was also on previous updates.
Correlation does not imply causation

Your skin and particular usage is also clearly beyond the scope of most packages. And different foobar versions also behave differently, have been multiple reports about streaming TF being broken on latest updates for example.
I think Defender's intent here was not to create a bug report about earlier versions, but to indicate how fast and error-free your new mod2 version has proved even with his complex usage.
No worries, I didn't see it as a "negative comment" at all. Just saying there are so many variables on that skin that it's impossible to know what's going on without a detailed report xd

Also since I didn't code Bio and Library, it really takes me a lot of time to fix even small things. Not saying the scripts are particularly complex, sure mine are more... but it's not the same to fix someone's else code than mine. So having as many clues as possible helps me.

Also check defender's instructions. That's the thing you should do, using the package manager and just import new version. Otherwise people may try to do what you did while foobar is running and bad things may happen ;)