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
1
General Audio / Re: Can higher bitrates sometimes sound worse than lower ones
Last post by fred-hy -
The sample Brand linked is interesting, though the claim that higher the bitrate the worse it sounds isn't entirely correct.
At certain bitrates Opus refrains from trying to encode the noise between ~12 kHz and ~15 kHz, but once bitrate increases above those thresholds it stupidly encodes parts of that frequency range. For example 128 kbps is worse than 150 kbps, and while 256 kbps sounds worse than 150 kbps, 320 kbps is once again better than 150 kbps.
It's not doing a worse job because bitrate increases, it just doesn't seem to understand what it's encoding and sprinkles the extra bits randomly leading to awful artifacting.

Do you have a source for this?
2
3rd Party Plugins - (fb2k) / Re: Columns UI
Last post by musicmusic -
The dark mode rendering of menus is handled entirely by Windows (and so Columns UI has no control over it, I'm afraid). When it comes to old Win32 functionality, in general, Microsoft only bothered with adding dark mode support to things that they wanted to use. Given the rarity of multi-column menus, I'm not surprised that they do not support dark mode. I recall that another dark mode bug was also reported with menus, IIRC it was with the scroll buttons for a long menu.
5
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).
9
3rd Party Plugins - (fb2k) / Re: Biography Discussion
Last post by regor -
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.