1
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.
2
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by Defender -I'm foremost interested in being able to discard the old Peakmeter Spectrum. For that I prefer this tool to mimic behavior of the old plugin. Old plugin shows 3dB less than this one (even with the +3dB disabled). So please implement it the same way or just make an extra tickbox in the configuration to do enable -3dB in order to mimic the old tool.
The old plugin has tooltips that show Peak MAX and RMS max. Can you enable those as well?
Maybe an idea to (optionally) also show LRA (or LUFS/PLR) whatever in the same tooltip. That way the user interface does not get cluttered.
Last point ... until now every version creates a hard crash to the desktop without logging when I accidentally Toggle full screen mode.
I don't care much if this will be solved, but please make it configurable not to show the Toggle Fullscreen on rightmouseclick.
3
MP3 / Re: Low bitrate MP3 (+ unsupported bitrates)
Last post by Klymins -4
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by Kraeved -If you want me to test something, let me know, I'd be happy to try and troubleshoot for you!@KevinB52379 A few hours ago, I sent you a private message with the Helix build to test. Do you have any feedback?
5
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.
6
Ogg Vorbis - Tech / Re: Vorbis 1.3.7 aoTuV and Lancer patches
Last post by john33 -7
MP3 / Re: Low bitrate MP3 (+ unsupported bitrates)
Last post by fooball -@Kraeved How can i run GXLame or Helix? Double clicking did not do anything and i don't know how to specify filenames etc.Run them in a command terminal at a command prompt, not from a GUI.
8
MP3 / Re: Low bitrate MP3 (+ unsupported bitrates)
Last post by Kraeved -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.
9
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.
10
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by wojak -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.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)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
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.