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
3
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by Case -
Quote from: Brazil2 on
So this one ? : https://hydrogenaud.io/index.php/topic,123331.msg1043493.html#msg1043493
That was a test build for trying to hunt down the problem with KevinB's system, don't use that. It links against Universal CRT so it won't work without extra support libraries on anything older than Windows 10. Same is true with Clang compiles created in MSYS environment, so everything posted in this topic.

The GCC compile included in JoshuaChang this post: https://hydrogenaud.io/index.php/topic,123331.msg1043667.html#msg1043667 is proper one.
4
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by Wombat -
Quote from: Brazil2 on
Define vintage Windows versions. The build will be used on PCs running Windows 7, 8.1 and 10 with Intel CPUs from 4th gen up to 9th gen. Mainly Windows 8.1 and 10, I must say.
The clang UCRT may run under 8.1 but not on 7.

Quote from: Brazil2 on
Quote from: Case on
After getting rid of the slow printing GCC compile seems to be faster here on Intel CPU.
So this one ? : https://hydrogenaud.io/index.php/topic,123331.msg1043493.html#msg1043493
Since on my AMD Ryzen it is the other way around you better speedtest your individual CPUs for best results.
5
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by pqyt -
Quote from: Defender on
Based on how your plugin behaves/displays I guess you are calculating barwidth (vertical peakmeter) by first determining the total gauge gap by first multiplying the (unscaled) configuration value gauge gap times the number of channels (bars) to be displayed minus 1. Then I guess you scale this total gauge gap, subtract that value from the panelwidth and divide the result by the number of channels to find barwidth per bar. By scaling a calculated unscaled total gauge gap this value will be to high (except winth 200% and 300%), and subsequently your barwidth/barheight will be lower than I intended.
When you display bars, you apply single gauge gaps between channels leading to pixels that are left over and are distributed to the left of leftmost bar and to the right of rightmost bar.
You don't have to guess. The code is out in the open... ;-) That's almost exactly how the metrics are determined.
Quote from: Defender on
Please investigate ...
Will do.
6
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by Brazil2 -
Quote from: Wombat on
If you don't use vintage windows versions the clang builds of @JoshuaChang don't use fancy CPU extensions or fast-math and are as fast as it gets for that.
Define vintage Windows versions. The build will be used on PCs running Windows 7, 8.1 and 10 with Intel CPUs from 4th gen up to 9th gen. Mainly Windows 8.1 and 10, I must say.


Quote from: Case on
After getting rid of the slow printing GCC compile seems to be faster here on Intel CPU.
So this one ? : https://hydrogenaud.io/index.php/topic,123331.msg1043493.html#msg1043493
9
General - (fb2k) / Re: Running Foobar in Linux
Last post by paregistrase -
Quote from: dpc666 on
For convenience I've compiled a list of compatibility fixes.

The wineprefix should be created with the WINEARCH=win32 environment variable, since winetricks has better support for 32 bit.

I installed the following verbs with winetricks:

Code: [Select]
lucida
gdiplus
winhttp
wininet
wsh57
mdac28
msxml6

This allows me to use foo_httpcontrol, foo_sqlite and foo_spider_monkey_panel.

foo_httpcontrol seems to require msxml6 to start a server but Internet Explorer and vcrun were unnecessary.

gdiplus and lucida were required for running @regor's Playlist Manager on foo_spider_monkey_panel.

Furthermore, I modified the following registry entries to add compatibility for foo_run:

Code: [Select]
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment]
"PATHEXT"=".com;.exe;.bat;.cmd;.vbs;.vbe;.js;.jse;.wsf;.wsh;."
"PATH"="%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\system32\wbem;%SystemRoot%\system32\WindowsPowershell\v1.0;Z:\usr\bin"

Linux commands must be prefixed with cmd /c.

My Wine version is 9.6-1. My Foobar2000 version is 2.1.4

I don't use foo_sqlite but there is no need of winhttp wininet or msxml6 to run foo_httpcontrol.

I only have wsh57, mdac28 and gdiplus and it runs just fine

 

10
Validated News / Re: freedb.dbpoweramp.com/~cddb/cddb.cgi
Last post by Porcus -
Good news. Thank you for fixing others' "mistakes".

Loose suggestions for consideration:
* EAC and dBpoweramp and more rippers could detect index points too, and upload and store full cuesheets.
* Since file lengths can get you Musicbrainz lookup, it could be possible to link up against that: <This> CDDB disc id matches <this other one> and artist and album so nearly match that it is likely due to spelling mistakes punctuation, so ... here you got a clean-up.
Also, I guess at least some of us would be happy to help populating a metadata from the rips we have already made - quite a few people have extensive collections with <DISCID> and dBp-generated tags.  Of course, a lot of people also have, ahem, let's call it identical rip logs, but even if you allow an automated mass submission if and only if there is a log file present ...?
* Please Do Not Assume That Capitalizing Every Word Is Correct. There are languages where it is outright wrong, making Discogs look ridiculous.