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
23
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by pqyt -
If a test file is published as -20dbFS, shouldn't that be rendered at -20dBFS?
Depends who published it and what it's meant to show. For example the sine waves from soundonsound have peaks at -20 dBFS so showing peaks at -20 dBFS is very valid. True RMS for such sine is 3 dB lower, -23 dB, 'RMS+3' display would be -20 dB.

If you want a *dB* reading and rendering, activate the RMS+3 toggle.
When the toggle is off, you show 'RMS+3' values. When it's enabled you show RMS+3+3 dB. And adding the FS for full scale is just an accuracy increase, because dB alone doesn't tell what it is relative to. All values are of course relative to the digital full scale.
I have no new arguments and you still haven't convinced me. Maybe @misio can shed some light on the situation. He/She has been pushing me in the other direction. I don't care either way. But I can't follow 2 different expert opinions at the same time.
24
Ogg Vorbis - Tech / Re: Vorbis 1.3.7 aoTuV and Lancer patches
Last post by john33 -
Thanks, Case, you're right, of course! I'm off to Spain for 2 weeks tomorrow so my mind is elsewhere!! I don't think I will get to look at this until I return so please feel free to remind me if I should appear to have forgotten about it.
26
MP3 / Re: Low bitrate MP3 (+ unsupported bitrates)
Last post by Kraeved -
@Klymins There is no substitute for hours of practice if you are going to create a convincing reproduction of any famous painting. The same applies to audio conversion. There are many free and commercial apps (Xrecode, dBpoweramp, Foobar2000 to name a few) with tons of options. But there is not a single app with a single “Do it” button that could solve your specific task of creating a good-sounding copy with a minimum size in MP3 format. Such apps exist only for the most common tasks, for example, to convert FLAC into high quality MP3. This means that one way or another you will have to work hard, step by step figuring out the purpose of each option, gradually building a chain of commands that will lead you to the long-awaited result. At this stage, it seems you are faced with the fact that you do not know how to use command line apps (such as audio encoders GXLame and Helix) that do not have their own window. But the thing is, all audio encoders are inherently windowless, so you have to learn that first.

Eventually, you'll end up with a more or less similar chain of commands that I used here to convert bee.FLAC 96000 Hz 24 bit stereo into bee.WAV 11025 Hz 16 bit mono, and then to bee.MP3 using GXLame 5.3 with options --abr 16 -h. The 16.6 kbps result sounds clear enough and it is hardly possible to do better. As a bonus, I attach a 15.5 kbps fragment from the Gladiator soundtrack.

27
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by Case -
If tone://997 is a pure 997Hz sine wave that is used as reference point of dBFS (the zero point), then shouldn't that show up with a 0 *dBFS* reading?
In that reference, sure. In the so called RMS+3 scale.

If a test file is published as -20dbFS, shouldn't that be rendered at -20dBFS?
Depends who published it and what it's meant to show. For example the sine waves from soundonsound have peaks at -20 dBFS so showing peaks at -20 dBFS is very valid. True RMS for such sine is 3 dB lower, -23 dB, 'RMS+3' display would be -20 dB.

If you want a *dB* reading and rendering, activate the RMS+3 toggle.
When the toggle is off, you show 'RMS+3' values. When it's enabled you show RMS+3+3 dB. And adding the FS for full scale is just an accuracy increase, because dB alone doesn't tell what it is relative to. All values are of course relative to the digital full scale.
28
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by wojak -
Since we now have the ability to see "RMS" as text maybe it would be useful to also see "Peaks" as text. And to go further also "Peaks - RMS" - but what would that value be "equivalent" (sort of) of: momentary/short term DR (from the infamous plugin), momentary/short term PLR/PSR, momentary/short term LUFS, momentary/short term LRA or something else?
Isn't that already available in the modern Loudness Peakmeter plugin?

https://hydrogenaud.io/index.php/topic,123953.msg1027603.html#msg1027603
I thought that it should be easy to also display the text version of Peak inside the graph (let's say beside the text RMS values)
I'm not a fan of that because it will cause too much text to be drawn over the gauge. The current position of the text was decided by my laziness to write the code to give it it's own client area.

Yes - too much text could be "annoying/ugly" but if there was an option to not display any text or only RMS or only Peak or both that would be users decision.
30
Ogg Vorbis - Tech / Re: Vorbis 1.3.7 aoTuV and Lancer patches
Last post by Case -
Sounds like you are using an exclusive mode output in foobar2000. The output bitdepth is user configurable, yours is set to 24 bps. And the error is caused by the audio interface not supporting 11 kHz playback natively.
If you wish to keep using exclusive mode, you'll need to add a resampler DSP to the playback chain. Another solution would be to switch to non-exclusive output.