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
11
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Defender -
@Case

Scanning speed of 0.6.9 with LRA, but without LUFS-S/M, is the same as it was with 0.6.7.

I am confused as a result of the new PLR fields.
In essence PLR is nothing else than applying peak_db on LUFS-I. If I do that based on your LUFS-I value I get a value. In the PLR field you report this value negated and rounded as an integer.

If it was only negated, I could still exactly verify it with my own calculations of LUFS-I and PLR, but because of the rounding I cannot.

Why is your PLR rounded?
Why is your PLR negated?
12
Support - (fb2k) / Re: Unintended/accidental AVX requirement of 64-bit version
Last post by marc2k3 -
Quote from: Peter on
I'm afraid that, at this rate, you'll have to run old versions of various software, not just foobar2000, on machines without AVX because other apps built with new MS compiler will manifest the same problem.

If VS2019 works, I think you could use it for the current 2.2 series. In a previous comment you said this...

Quote
I'm waiting till VS2022 17.10 before attempting any "fixes" in fb2k 2.2 series, hoping for the problem to fix itself without having to revert C++20 use in new code.

but I don't think that's right. VS2019 should be fully C++ 20 compliant.

https://devblogs.microsoft.com/cppblog/msvcs-stl-completes-stdc20/
15
Lossless / Other Codecs / Re: HALAC (High Availability Lossless Audio Compression)
Last post by Porcus -
If I understood it right, LossyWAV's default block size choice of slightly below twelve milliseconds, is to allow for swift changes in the number of decimated LSBs. Bigger blocks would mean you would have to keep that constant over a longer time. 512 samples in LossyWAV and say 1024 in a compressor that employs a per-block wasted bits strategy, would restrict it to choosing the "worst of two".

When I suggested to facilitate LossyWAV, I didn't know whether it would be easy for HALAC to employ a user-selectable block size.

FLAC does a trick that for some signals improve compression by quite a lot, namely the partitioning with different Rice parameters. If a block is size K*2^N, then a partition order of N means that the residual coding parameter is changed every K samples; immediately after K samples there are four bits with a Golomb-Rice exponent. This instead of a low block size which would require frame headers.
Of course, if one did intend a lossy usage like this, one could have partitioned it with different wasted bits too. 

The partitioning is one reason why FLAC does better with block size 4096 than 4095. Sure if you don't use the same residual coding methods, YMMV - but we know certain signals where the advantage of rapidly changing a residual coding parameter can actually make FLAC outcompress any OptimFROG.
17
Lossless / Other Codecs / Re: HALAC (High Availability Lossless Audio Compression)
Last post by Hakan Abbas -
Quote from: MihaiPopa12346 on
How did you do lossyHALAC ...
I do not have full information about the LossyWAV structure and I haven't fully examined. And I didn't do anything specifically for the content. I only disabled the prediction phase required for the lossless mode. However, I did not activate it for 0.2.8.
Considering the results in the list, the HALAC offers enough compression even in this form. For better results, the data structure needs to be examined and certain adaptations are required. Of course, time is necessary for this.
18
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Defender -
Quote from: Case on
The LUFS-M and LUFS-S values were always calculated every 100 ms even when the option was disabled.
That was pretty much my first thought.

Quote from: Case on
I could make LUFS-M and LUFS-S faster by calculating them less often. But then their accuracy would be somewhat reduced. I don't know at all how often other tools update these values, to my knowledge LUFS-M and LUFS-S were originally meant for live monitoring.
Exactly. Live monitoring you can see/do with foo_loudness_peakmeter.
I'm still struggling whether I will display your Max LUFI-S/M values (without the location where they occur in the audiofile) in my playlist grid. This grid is intended to show general helpful information about the audiofile to give you a rough idea what to expect when listening to it and I don't know if Max LUFS-M/S bring something extra to the table.
Showing these (live) values would make more sense as mouseover tooltips in live tools such as the minibar mod. But I sure don't want this functionality in the minibar I'm using in my audiocontrol area. Would only be feasible in the area I designate for monitoring tools.

Quote from: Case on
I'd also like to see if I could utilize the Peter's ReplayGain scanner optimizations to speed up the libebur library, I believe there is a lot of room for improvement there.
Always good to optimize.

Thx again.
19
Support - (fb2k) / Re: Unintended/accidental AVX requirement of 64-bit version
Last post by Peter -
VS2022 17.10 installed, problem NOT fixed.

I'm afraid that, at this rate, you'll have to run old versions of various software, not just foobar2000, on machines without AVX because other apps built with new MS compiler will manifest the same problem.

On a side note, more or less same thing happened with foobar2000 v1.5.x series and SSE2 but apparently too few people care and I didn't notice until yesterday.
20
Support - (fb2k) / Opus Audio Files For Recent Game Not Opening
Last post by TerrorTempest -
Hi there. A recent game, Paper Mario TTYD Remake, has Opus files that can't be opened with foobar. By taking a look at a file in a hex editor, it appears to have an Opus header without a container. I think this was the case with Super Mario RPG when the hca files were extracted from the AWB. I've attached an example file. The game extraction contains only the opus files and no container (no AWB/ACB).