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.)
Is a wrapper available to run older JS3 code?)No. It's SMP in all regards + some fixes and improvements.
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).
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 xdAs you may expect... your report is vague at minimum. If you expect more updates or help, provide more details.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.
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.
Sorry , I'm a bit late.Thanks for the update!Helping myself
Can anyone point me to/describe how I would update from 1.4.2 mod 1 to 1.4.2 mod 2 without losing my current settings?
I am running JSplitter 3.6.1.14 with Foobar v2.24.5, 64-bit. Biography is the only SMP package I have installed.
I appreciate any help you can give.:
1. Environment: Foobar v2.45.5 64-bit Portable; JSplitter 3.6.1.14; Biography-v1.4.2.mod.1 installed.
2. Locate the folder (foobar2000-x64_v2)\profile\foo_uie_jsplitter\packages\{BA9557CE-7B4B-4E0E-9373-99F511E81252}
3. Extract the contents of Biography-v1.4.2.mod.2.zip into it, allowing it to overwrite all.
That's it. I didn't notice any reversals of previous settings. New version number will appear at the top of the Options panel:
Thanks for the update!Helping myself
Can anyone point me to/describe how I would update from 1.4.2 mod 1 to 1.4.2 mod 2 without losing my current settings?
I am running JSplitter 3.6.1.14 with Foobar v2.24.5, 64-bit. Biography is the only SMP package I have installed.
I appreciate any help you can give.
:
As you may expect... your report is vague at minimum. If you expect more updates or help, provide more details.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.
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.