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.
Topic: foo_loudness_peakmeter (Read 35143 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: foo_loudness_peakmeter

Reply #100 –
Quote from: Just_Addict on
Turns out it's only showing ~somewhat exact values if you've got no DSP active at all.
Any DSP that does something to the audio will skew the values one way or the other.
Obviously true as all foobar2000 visualizations (not just this component) gathers audio data after all of DSP effects you put onto the playback chain so if you want "exact" values, just remove all DSP effects from the playback chain

Re: foo_loudness_peakmeter

Reply #101 –
Quote from: Crossover on
I need the component to monitor my self-mixed songs.
What do you mean by "self-mixed" songs?

As I haven't even produced a single music in my entire life obviously, yet I have realtime audio analysis tools developed to my needs to monitor songs produced by someone else (obviously, you can't rely on graphs to gauge sound quality per ToS #8, but it is still a good way to spot fake FLACs or any other lossless/uncompressed audio files sourced from lossy sources with spectrum analyzers and spectrograms) as well as my sound design content I've produced with Audacity (which most of them are mashup of other sources)
 

Re: foo_loudness_peakmeter

Reply #103 –
Quote from: boxerfan88 on
Hi there,

I'd like to let the developer know that foo_loudness_peakmeter has a slow memory leak issue.
Ref: https://hydrogenaud.io/index.php/topic,126259.new.html
That could be a problem on 32-bit versions since in this version, it obviously has 4GB hard limit for the RAM usage

BTW, to not clutter this thread like I did on a forum thread for foo_enhanced_spectrum_analyzer component, I had to create a separate thread if I continue posting almost endless FRs

Re: foo_loudness_peakmeter

Reply #104 –
Quote from: TF3RDL on
When not using "single spectrum" mode, I noticed that the top graph didn't react to right channel (when using the Stereo Balance effect that comes with Utility DSP Array component) but the bottom graph reacts to both channels as opposed to only reacting to right channel but not left channel

Also, the line (which is the momentary LUFS display over time) reacts to both channels on two graphs as opposed to have LUFS lines react to each channel on each graph (which is a FR to add an option to make LUFS line graph react differently to different channels on each graph as opposed to all channels when not using "single spectrum" mode)
Also, this nitpick (or a small bug in this @Crossover component) also applies to single spectrum mode albeit in a different way; the dark part is decreasing on each channel number iteration on this 18ch test tone like this:
X

BTW for those who wondering about this nitpick, here's what this test tone file would look like with "single spectrum" mode disabled:
X
And I think it is correct to have the bottom part of dual graph (in the case of stereo) only reacting to a right channel as opposed to both channels and in the case of multichannel sources like 5.1 and 7.1 surround sound as well as quadraphonic music, 2.1 and 3.0 stereo and 17.1 surround (which maxes out WAVEFORMATEXTENSIBLE channel mask), I think the number of graphs should change accordingly to number of channels of currently-playing audio (though it might change especially with channel upmixing/downmixing DSPs) rather than being limited to mono and stereo