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
3rd Party Plugins - (fb2k) / Re: ReplayGain DSP - Alternative ReplayGain implementation by Case
Last post by Case -
Quote from: Squeller on
a) If it is set to "Rescan everything", it will be enforced to know gain/peak levels?
In theory. It will try to scan the track gain and peak levels. But remember that the scanner will abort the job if it takes too long. The scanner will only be allowed to run while the output buffer still contains audio data so that playback remains gapless. If that time isn't enough to scan the entire track, then the new checkbox will essentially treat the track as if its RG gain value is 0.0 and peak info is missing, if the RG scanner returned above 0.0 gain.
Note that easy way to give more time for the scanner is to increase foobar2000 output buffer size.

Quote from: Squeller on
b) If set to "Prevent clipping only" the checkbox has no effect?
That's correct.

Quote from: Squeller on
c) With positive gain you mean "volume increase", correct? Because first I read it like "Allow end result to be +0.5db"/i.e. "Allow clipping".
Actually at the moment the new checkbox can still allow volume increase in certain situations. Namely if the target loudness is higher than the ReplayGain reference level and the gain value is zero or less negative than the volume boost. For example if estimated gain is -1.0 dB and you have selected Spotify playback level of -14 LUFS. That means the playback level is reduced by 1 dB but boosted by 4 dB, so +3 dB increase.
I will need to change that to prevent volume increase instead of just positive RG result. But that will have to wait until tomorrow, too many quick fixes already released today. Let's see if there are more things that need adjusting.
3
3rd Party Plugins - (fb2k) / Re: ReplayGain DSP - Alternative ReplayGain implementation by Case
Last post by Squeller -
Quote from: Case on
New version out with an option to prevent loudness increase for tracks with missing or guessed peak.
But do I understand correctly:

a) If it is set to "Rescan everything", it will be enforced to know gain/peak levels?
b) If set to "Prevent clipping only" the checkbox has no effect?
c) With positive gain you mean "volume increase", correct? Because first I read it like "Allow end result to be +0.5db"/i.e. "Allow clipping".

I may be confused about terminology.
5
Polls / Re: 2024 Lossy format poll
Last post by Squeller -
Mostly LC AAC (always created by qaac/Apple), sometimes mp3 - because of cars. It's not even because they don't understand AAC (one car of mother-in-law is just stupid and needs m4a renamed to mp4), but e.g. they don't display embedded art from aac files, whereas mp3 works. Car audio - a sad story, often just an afterthought and a mystery. E.g. embedded album art exceeding 800px doesn't display in my car. It takes time to find that out. OK, that's offtopic.
7
3rd Party Plugins - (fb2k) / Re: foo_dsp_lowpass (discussion)
Last post by Squeller -
Quote from: Case on
I had missed the request to increase the lowpass limit. I uploaded a modification where the limit is now raised to 96 kHz.
The new version can be found at https://foobar.hyv.fi/?view=foo_dsp_lowpass.
That's awesome. It works. Could you also extend the width? If it makes sense. On a 96k file, I maxed it out to 20% with a cutoff point at 25k. You see in the screenshot, it is still rather a narrow transition.

X
8
3rd Party Plugins - (fb2k) / Re: NEW ESLyric v0.5 - an alternative lyric show component
Last post by michi777 -
Quote from: always.beta on
Quote from: michi777 on
  View/ESLyric//Open containing folder
1. I remember that there would always be a few temporary displays, but it didn't have any effect, it was just temporary.
2. What lyrics source, what song, I'll try
3. The command has changed, and you have modified it according to the new one.
2.Every lyrics same.
  (kugou.js) [id:～], [language:～] is saved.
  (ex. Bon Jovi - Livin' On A Prayer)

  (and Japanese lyrics [kana:～] is saved )
9
Polls / Re: 2024 Lossy format poll
Last post by yourlord -
I use opus when I'm converting my flacs for use on my phone. I only use aac when I rip backups of my movies as that's just the default audio codec for mp4 files. These days I don't really use lossy compression for anything else.
10
3rd Party Plugins - (fb2k) / Re: Should some foobar2000 components be using AVX2 instruction set?
Last post by TF3RDL -
Quote from: Case on
I'm a bit wary of using these in an audio player at all. For example Haswell limited the maximum speeds of all cores if any core was using AVX2. And even with newer CPUs these instructions cause throttling and limit the executing core's frequency. Personally I rather have efficient audio player and enjoy uncapped CPU power for other tasks as the player is running on the background.
Of course, this is where I might see using AVX2 as a crutch for a spectrum analyzer component (just because I saw performance drop on anything beyond 1/24th octave bands and more than 4th order filters on my own project, as well as 1/12th octave bands with RMS spectrum shown) for foobar2000 audio player (especially foo_enhanced_spectrum_analyzer and its high CPU usage "problem") and obviously can cause compatibility issues with low-end CPUs that lack support for AVX2 instructions (especially when fallback to older SIMD instructions like SSE4.2 isn't present or incorrectly implemented), unless you have a good reason to use these