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
1
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Defender -
With s/h you mean samples per hour? Point is that I also wanted to normalize result so that the samplerate is out of the way.
I meant just correcting the unit. If an info panel somewhere says there is "1 s" of clipping it would be interpreted as absolute value for the track (or album) in question. Saying that there is 1 second of clipping per hour would be correct way to inform about the situation. The meaning of 's' in my example remained the same: seconds.

Aaah, that's exactly what I'm doing. I display CH 3.905s. Clipping per hour is 3.905 seconds. Screenspace is valuable though in a horizontal grid. Although this value is not correct since a single sample as you explained can produce as many clipping samples as there are channels.
2
3rd Party Plugins - (fb2k) / Re: JScript Panel script discussion/help
Last post by Defender -
Hi,

I created some keyboard shortcuts 1) Randomize current selection 2) Queue (selected) files 3) Kill the queue. Works fine.

However I would this functionality in buttons.

The randomize button I created works fine with fb.RunMainMenuCommand('Edit/Selection/Sort/Randomize');

The queue button does not work. There is no main menu command to queue so I tried fb.RunContextCommand('Add to playback queue'); but this only adds a track within the selected tracks to the queue if it is playing.

How can I change this code so that all files in the selection are added to the queue?
3
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Case -
With s/h you mean samples per hour? Point is that I also wanted to normalize result so that the samplerate is out of the way.
I meant just correcting the unit. If an info panel somewhere says there is "1 s" of clipping it would be interpreted as absolute value for the track (or album) in question. Saying that there is 1 second of clipping per hour would be correct way to inform about the situation. The meaning of 's' in my example remained the same: seconds.
4
3rd Party Plugins - (fb2k) / Re: Peakmeter Spectrum component
Last post by Defender -
EDIT: My verticals do not use axes and channel legends.
The channels names and axes can be disabled or individually styled.
My horizontals only have channel legend on the left side and the dB axe in between the stereo channels. In multichannel mode I use the axe as a divider between L+R and the rest of the channels. And I do not use colors other than a gradient of blue (and red above 0dB). But your impression comes pretty close.
As usual the configuration GUI is the most work. How do you specify to have an axis as a divider between channels? What happens if multiple channels are available and selected for display as f.e. with a 7.1 track?

I assumed you received the original code for Peakmeter Spectrum. This stuff you can specify in their configuration screens. Therefore I sent the two config files as a sample.
I specified the axe between channels when stereo and under L+R in case of multichannel. I want a divider there anyway. You can see in my earlier screenshots and also in the video.
I also don't like slack on top or bottom (especially when a tool is non-transparent). And to see what channel it is both on the left and right is imo unnecessary.
5
Wiki Discussion / Re: Document hmp3 (Helix MP3 encoder) in the Knowledgebase Wiki?
Last post by maikmerten -
Actually, -U2 is useless for any modern 64-bit compile. The 64-bit compiles are preferable in terms of speed anyways.

I didn't increase the version number in the LAME tags as the changes to the encoder were on the input side (more robust and versatile .wav input), not the output side (still same algorithm with same quality). If one got to correctly feed input into the older versions (old-style 16-bit .wav without trailing data), one would usually still get indistinguishable output.
7
3rd Party Plugins - (fb2k) / Re: Peakmeter Spectrum component
Last post by pqyt -
I tried newest beta yesterday. As usual as a pop-up in DUI. Whenchanging view from normal to full-screen, the spectrum or a spectrograph or peak-meter widnows are changed in a wrong way. Just like they have been moved to the right - the left side of the window becomes blank, the begining of the bars or graph is about 1/3 to the right and the right end becomes cutt-of. So the bars/graphs do not fit the window. It only goes back to normal when manually restarting the audio file.
The algorithm has changed (again): the width of the bars adapt to the available space but will only use a whole number of pixels. To fill the available space, specify more bars or resize the window.
As for peak meter - it would be nice to be able to configure it - the bottom end ( let's say down to 120dB) and the upper end (being able to put more digits there). What I mean is now we have -12, -6 and 0. I think that it is not so informative to see if the peak is between -6 and 0 (beacuse it usually is) but it would be very useful to see if it is -5, -4, -3, -2, -1, 0 or 1. Or even more density in the area of -3/-2 to 0. Just as a feature.
Again, how would that translate to a configuration GUI? The min, max and amplitude step size can already by specified but the step is used for the whole range.
8
3rd Party Plugins - (fb2k) / Re: Peakmeter Spectrum component
Last post by pqyt -
EDIT: My verticals do not use axes and channel legends.
The channels names and axes can be disabled or individually styled.
My horizontals only have channel legend on the left side and the dB axe in between the stereo channels. In multichannel mode I use the axe as a divider between L+R and the rest of the channels. And I do not use colors other than a gradient of blue (and red above 0dB). But your impression comes pretty close.
As usual the configuration GUI is the most work. How do you specify to have an axis as a divider between channels? What happens if multiple channels are available and selected for display as f.e. with a 7.1 track?
9
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by wojak -
Hi @Case,

could you please explain why does your component measure a little differnt than the built in RG? The results differ by about 0,1/0,2.
Is there a different standard or by design those calculations are not precise (guesstimation)?

Plus what exactly Clippings measured in your component mean? Are they embedded clippings in the signal (they are there because they were introduced during the recording/mixing/mastering), which would probably mean we can not do anything with them without altering the material? Or are they hypothetical clips that might occur in the DAC? Or something different?
Then how does RG applying work. If we measure RG, Clips, True Peaks and use Album mode we can then use 4 options:
- none - obvious
- apply gain
- apply gain and prevent clipping from peak value
- prevent clipping from peak value
What does apply gain really mean - does it just turns the volume up or down (usually waaay down)? If we use prevent from clipping does it change the volume but to a degree not to produce clippings so for example it would turn the volume up by 3 but then it would clipp so it turns up by ex. 2 not to clip? Or does it turn up by 3 and compress the peaks?
Does the "prevent clipping" option (without applying gain) mean that if there are 0 clippings on the album it would do nothing but if there were clippings it would turn the volume of the album as much as needed to avoid clipping? In album mode would it do exactly the same amount in every track?

Putting classical music aside and speaking about por/rock/jazz... music. All the records (even those from original '80 CDs) are too loud (judged by RG) (even SADE or Dire Straits records or other "audiophile recordings") so the RG never (or very rarely) would make the albums louder and almost always would make it quieter. Seemingly too quiet so one would have to turn the volume knob on the amp which could hypothetically produce a hiss. So now what would be the best way to make it louder. I use USB-ASIO DAC with foobar and DAC volume at max level so I change the volume with a manual knob othe amplifier. Would it be better to use foobars built-in Preamp (the one below RG section in the preferences) or might that produce Clips?
I never used RG but when first used your component (a few days ago) to find clips I started to think how to get rid of them and for now I use the "prevent clippings" option but as you see from this post I do not fully (or at all:))) understand what exactly do all those options do.
So to sum it up - is applying RG an equivalent of just turning the volume knob on amp up/down or does it do something else? Is "prevent clipping" option just a one-direction option of RG (it would do nothing when no clippings or turn down if clipping). If it turns down - how - first look at "album peak" and turn the whole album as needed or differently?
What is the best way to control the volume nowadays (with 64bit foobar, 32bit DAC and analogue amp)?
Please excuse my ignorance and so many questions but they relate to one topic (I think).
10
3rd Party Plugins - (fb2k) / Re: Peakmeter Spectrum component
Last post by Defender -
@pqyt

Here you can see how I have peak display in Channel Spectrum, vertical PeakLED and horizontal PeakLED.
I have 3 different configs for vertical (2ch, 6ch and 8ch) and also 3 for horizontal.

I attached the config files for vertical and horizontal stereo.

And now comes the real pain in the butt, the original Peakmeter Spectrum is not aware of windows scaling, So I have 6 configs per windows scaling (125%, 150%, 175%, 200%, 225%, 250%, 300% and 350%). So in total 48 presets.

So yes, it would be quite helpful if you can pull this one off.