21
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.
22
General - (fb2k) / Re: Why can jump volume? To me jumping and in my yard(. My foobar2000 1.6.18.
Last post by Swi -23
3rd Party Plugins - (fb2k) / Re: foo_dsp_effect
Last post by cwb -There won't be anything adjustable in the various algorithms.
I had used the old standalone SoundTouch component in earlier foobar2000 versions and the sound quality was actually great (subjective, I know). That component started causing problems as fb2k went higher in version number. So I stopped using it.
And I had read this short thread before: Soundtouch plugin effect the Audio Quality?
I didn't want to come off as complaining, but I brought up the issue of the reverb (or raspiness), I hear, because the sound quality change, between the standalone component and the present day SoundTouch, is so drastic. I was hopeful that perhaps something might could be done about it.
Version 0.47 of DSP Effect and the other available algorithm are functioning quite well for me. So I'll be happy and leave it at that.
24
Validated News / Re: FFmpeg 7.0 "Dijkstra" released 2024-04-05
Last post by Porcus -Extra wheels available.
25
General - (fb2k) / Re: Quiet Foobar2000
Last post by Case -Could you check if https://foobar.hyv.fi/foo_dsp_multiresampler.fb2k-component remains crashless in your hands?
Other changes are added dark mode and 64-bit foobar2000 support.
26
Validated News / Re: FFmpeg 7.0 "Dijkstra" released 2024-04-05
Last post by mycroft -Its mostly now low-effort, by state sponsored maintenance work over auto-detected issues in source code - of questionable outcomes and benefit.That's an extraordinary claim needing specific examples.
…
net results is still negative.
Are you trying to say that it's better to leave the auto-detected issues unsolved? Even those potentially exploitable? Which is what fuzzing/static analysis tools are mostly trying to find.
Trying and actually fixing are different sets.
Net results is negative because today trends only goes down for the project.
Once upon in time FFmpeg had Gold Era in development, that time is long gone and forgotten.
27
Validated News / Re: FFmpeg 7.0 "Dijkstra" released 2024-04-05
Last post by mycroft -[...]And yet, of the 1775 patches that went into ffmpeg, you used 1376 in librempeg, if my counts are correct. That doesn't seem like "mostly fixes of questionable outcomes and benefits" nor "some cool and nice stuff but net result negative" to me.
Its mostly now low-effort, by state sponsored maintenance work over auto-detected issues in source code - of questionable outcomes and benefit.
[...]
There is some cool and nice stuff, like cleanups and refactoring but net results is still negative.
Such reasoning is flawed. There is no correlation between number of new commits since some fixed period and quality of project itself.
Extreme reductions lead to lies.
28
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by showmeyourabx -What’s the point of repeating units of measurement in each cell of the table? It would be more convenient to have purely numeric values without text units for copying into a table, so as not to have to parse the brackets/dBTP/LU every time.
Regarding measuring dynamics. If the plugin can measure momentary- and short-term unfiltered true peaks and K-weighted LUFS-M and LUFS-S, you can take the next step and calculate average PMR and PSR values, which would be much more informative than PLR.
29
3rd Party Plugins - (fb2k) / Re: foo_dsp_effect
Last post by fooball -There won't be anything adjustable in the various algorithms. Just choose the implementation which sounds best in your application. If a particular algorithm always sounded best, there wouldn't be a choice!
I'm blown away by the tempo/pitch shift implementation in Virtual DJ – but I doubt that would work well on my hardware.
30