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?
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.
@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.
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.
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