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
21
Validated News / Re: FFmpeg 7.0 "Dijkstra" released 2024-04-05
Last post by mycroft -
Quote from: magicgoose on
Quote from: mycroft on
Its mostly now low-effort, by state sponsored maintenance work over auto-detected issues in source code - of questionable outcomes and benefit.
…
net results is still negative.
That's an extraordinary claim needing specific examples.
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.
22
Validated News / Re: FFmpeg 7.0 "Dijkstra" released 2024-04-05
Last post by mycroft -
Quote from: ktf on
Quote from: mycroft on
[...]
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.
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.

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.
23
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by showmeyourabx -
Thanks for the great plugin. Very handy for comparing different codecs and settings.

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.
24
3rd Party Plugins - (fb2k) / Re: foo_dsp_effect
Last post by fooball -
You're not just hearing things, real-time pitch/tempo shifting seems quite straight-forward on the surface but leaves discontinuities between frames which need to be hidden somehow, which become increasingly audible (according to the material) if you go more than a few percent.

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.
26
General - (fb2k) / Re: Quiet Foobar2000
Last post by Case -
Seems you uploaded a crash. Caused by the Multiresampler DSP accessing memory beyond its buffers. So not a foobar2000 bug.

Edit: do you happen to have the file that crashed available? And is it easy to crash foobar2000 with it? I seem to have foo_multiresampler sources stored so I could attempt fixing it. Having a crashing sample would make it faster.
28
General - (fb2k) / Re: Quiet Foobar2000
Last post by sveakul -
Quote from: Case on
Note that exclusive mode is exclusive, it allocates the output device for foobar2000 and nothing else can play audio during that time. And it will error out if you try to play material your audio device doesn't support. Using shared mode output is more user friendly.
 .....without having to resort to using exclusive mode.
Case I have nothing but respect for you but IMO you're not giving the advantages of using exclusive mode due there.  For bit-perfect purists it provides an untouched path from file to audio device, instead of allowing Windows Mixer to introduce its own sample rate manipulations and DSP-related compromises.  The user may be interested more in a pure music experience than sharing the environment with Windows system sounds, app audio alerts, special effects, etc.  And inserting the SoX in a DSP chain set to only activate the few times a sampling rate is encountered NOT supported by the device is a simple, invisible way around that limitation.  I KNOW you realize all of that, but the OP's volume issues just with Foobar (he doesn't even indicate what version he is using) are probably more a result of things like gain settings and tags and overlooked DSPs.  I had to lookup "MultiResampler" to find out where that one came from (2015-2017).

Edit:  now I'm just seeing the OP is referring to "flash game" files, his preamp doesn't work, and it's only with mono files. ::)
29
General - (fb2k) / Re: Quiet Foobar2000
Last post by Case -
You were faster with your edits than I was. The default foobar2000 output plays mono as center speaker, a common method is to play mono with full loudness using stereo speakers. For now your best option is to add "Convert mono to stereo" DSP to the DSP chain.
I hope you uploaded the crash details to crashlogger, foobar2000 shouldn't crash no matter how nonsensical files it is fed.
30
General - (fb2k) / Re: Quiet Foobar2000
Last post by Klymins -
This is only happening in mono files. Interestingly, this special MP3 file (contains both mono and stereo frames, made in notepad by combining two MP3's) caused my Foobar2000 to crash a few times. This did not happen in the past. Does anyone have any ideas about this?