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: foo_vis_spectrum_analyzer
Last post by darkflame23 -
I seem to remember the only difference between "mathematical" and "AES" RMS is 3dB, due to whether you reference a sine wave or a square wave. At the end of the day it's not very important/easy to add or subtract 3dB in one's head. The best pro meters are set for +3/AES by default, or allow you to choose.
3
3rd Party Plugins - (fb2k) / Re: SACD .dsf file conversion plug-ins
Last post by file627 -
Hey guys ... your suggestions WORKED! I was able to convert some DSF torrents (ripped from LP). And now I have nice, manageable WAV files to listen to. I did get some errors/warnings, but I ignored them.
First I played ray DSF files. Worked. Then I used Convert for WAV conversion. Very cool! Thx!
4
Other Lossy Codecs / Re: exhale - Open Source USAC encoder
Last post by marc2k3 -
@Case , your site says compatible with fb2k 1.5+ but it fails to load on 1.6.17...

Quote
Failed to load DLL: foo_pd_aac.dll
Reason: Wrong version number; this component appears to have been built with a newer version of the foobar2000 SDK, please download latest version of foobar2000 in order to use it.
5
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by kor5n -
Which smoothing method do you use? ("Common" page). It should be set to "Average" to reduce jitter.
"Average" = 0.2. I have this setting on all modules. Increasing this parameter, of course, smooths out the RMS indicator, but reduces the jump of peaks. I consider this value is optimal.
It has nothing to do with the performance of the GPU. Direct2D uses a buffer swap chain that is usually synced to the refresh rate of the monitor. In D2D I don't know of a setting to influence that.
The following plugins are always active on my screen: Waveform Minibar (mod) 1.2.58 and Oscilloscope (Direct2D) 1.1.0. The first has an update rate of 60 frames per second, the second - 100. Closing these plugins doesn't solve the problem. Maybe they should be unloaded? (i.e. delete?)
7
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by pqyt -
There's a 1 pixel gap between the bars. You want it bigger?
Yes! I don't see him. And on the Spectrum it is clearly visible.
I cleaned up the calculations in the next version to better handle edge cases. Maybe I'll make the gap configurable.

There's an RMS window setting that goes up to 5 seconds to smooth the RMS calculation independent of the chunk size.
Unfortunately, this is not at all what I expect to see... Please see how your setting is applied in comparison with what I want to get in the end.
Perhaps I'm thinking incorrectly. Or I turn on the wrong setting.
Sorry if Google Drive links are not allowed.
Which smoothing method do you use? ("Common" page). It should be set to "Average" to reduce jitter.

Another user in the thread has no problem with it even though I did not change anything. Could it be a GPU driver setting?
I have an Intel Arc video accelerator, you can expect anything from it. All graphics applications on the system are allowed maximum performance. To be fair, on the AMD Radeon R9 390X the module behaves similarly.
It has nothing to do with the performance of the GPU. Direct2D uses a buffer swap chain that is usually synced to the refresh rate of the monitor. In D2D I don't know of a setting to influence that.
10
Opus / Re: Android music players that support Opus and R128 gain
Last post by ChristianK -
Looks like the best workaround for players without R128 gain support is to violate the spec and also add the regular replaygain 2.0 tag.
That way native R128 gain is supported (foobar2000 and some others) but also replaygain 2.0 as a fall back (all the other players).

The way I  do it is to first add replaygain 2.0 tags with rsgain (that tool is pretty complex for its task and a pain for mass tagging though, so I have to couple it with gnu parallel to get multithreading.)
Afterwards I add the R128 tag using r128gain (because rsgain cannot ignore the conflicting replaygain tag and Foobar doesn't accept the 2.0 tag, beware though since r128gain is no longer supported).

That way replaygain works for VLC and Foobar2000 on Android, and also for Strawberry on Linux (or any other gstreamer based player), and Foobar desktop.

Info on rsgain: https://github.com/complexlogic/rsgain?tab=readme-ov-file#opus-files
Quote
In my opinion, the authors of RFC 7845 totally overstepped their authority by specifying a format-specific loudness normalization method. Particularly egregious is the specification of a target loudness level. There is no one-size-fits-all solution for target loudness. The best value depends on the dynamic range of your music, which tends to vary by genre. Moreover, most people do not have a music library comprised entirely of a single audio format, so format-specific loudness normalization methods are inappropriate. Having Opus files play back 5 dB quieter than all other file types defeats the purpose of applying ReplayGain.

Quoted for truth. Having special standards for special cases that hardly anyone gets right is way worse than having an unofficial less than ideal standard that happens to just works across the board. Looks like we won't get the former anytime soon and because the special treatment is mandated the latter also no longer holds.
It is really sad that there have been discussions on mailing lists about this exact issue going back to 2012.
Apparently no one cares enough to finally get this settled out.