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: Playlist Organizer (aka foo_plorg) replacement on Jscript Panel 3
Last post by Jul2323 -
I was getting the same error, but just realized the mistake I made was leaving the folder titled pl_organizer2.0.8, instead of changing it to just pl_organizer.

i install version  2.0.8 . and error :

'_pl_organizer' is undefined
File: <main>
Line: 14, Col: 1

PS: i open the main.js in JP3 .

Thanks you work ....
2
3rd Party Plugins - (fb2k) / Re: [fb2k v2] Playlist Attributes (foo_playlist_attributes)
Last post by cwb -
@fbuser

Just to let you know, that with version 1.0.4 of your component. The problem of DSP's used with specific playlists being carried over to playlists with no DSP's applied to them, now appears to be fixed.

What I put in Reply #312 above was relevant yesterday when it was posted, but this morning I tried changing from a DSP applied playlist to a non DSP playlist and the DSP manager's "Active DSPs" window remained empty. There were no DSPs being carried over from playlist to playlist.

The only thing that happened yesterday, after Reply #312 was posted, is the laptop was shutdown for a few hours.

4
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.

Concerning width and bars adaptation. We did not understand each other. I said that if I start the component as a pop-us id DUI (I always use it like that) it is OK, it shows all bars or graph or peak meter correctly. But if I then click "full screeen" it becomes incorrect and if I then click "full-screen" again to make it "normal view" again..it still stays incorrect. Only starting new song corrects it. And it always is that way. SO following your suggestion I would change the settings after every click or every drag of the mouse (I sometimes want it bigger to see some parts better but just for a while).
And most important fact is that if it goes wrong it is just all moved to the right so the lest side is veeery wide and the right side is not very thin it is just cut out of the picture so for ex. normally the peak meter goes to 0 (the scale) and after changing the sizxe manually (with mouse) or to full screen the scale ends at 18. The rest is cut out. Changing it back does not change anything. Only starting new song brings it back to normal but if then change the size it is wrong again.
Alas, I can't reproduce this. I've learned my lesson: before a new version goes out I go through a cycle of resizing / fullscreen -toggles both in DUI and CUI. Nothing like that happens here.
5
3rd Party Plugins - (fb2k) / Re: JScript Panel script discussion/help
Last post by eurekagliese -
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?

I just use this for my queue button.
Code: [Select]
	this.buttons.queue = new _button(x + (bs * 5), y, bs, bs, { char : '\ue109', colour: colours.white}, null, function () {		
var handleList = plman.GetPlaylistSelectedItems(plman.ActivePlaylist);
if (handleList && handleList.Count !== 0) {
handleList.RunContextCommand("Add to playback queue");
}
}, 'Add to playback queue');
6
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by 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)?
Native ReplayGain scanner doesn't follow any standard. It just offers an option to upsample using a resampler and settings of your choosing.

True Peak values depend entirely on the used resampling method. If you configure the built-in scanner to do the same resampling operation, the results are 100% identical.

My scanner was made to follow ITU-R BS.1770-3 recommendation. They state that for determining True Peaks a sampling rate of at least 192 kHz should be used. But higher the sampling rate the better. As I have said elsewhere, my component doesn't just resample to 192 kHz. It picks the lowest integer multiplier that reaches at least 192 kHz sampling rate. For a typical 44.1 kHz audio that means 4 x upsampling isn't enough, 5 x is needed.

Plus what exactly Clippings measured in your component mean?
Any sample value that is beyond digital fullscale.

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)?
It means same as volume adjustment. It adjusts the playback level so that each track or each album have identical loudness and listener doesn't have to touch volume settings.

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?
The 'apply gain and prevent clipping from peak value' adjusts the level but if the peak value tells things would clip, the level is lowered just enough to keep the peaks inside digital fullscale. In track mode this adjustment is done for each track, in album mode all tracks are adjusted by the same decibel amount as much as is needed to prevent the track with highest peak from clipping.

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?
It works exactly like that. If the peaks are below full scale the signal is not touched at all. If the peaks are too high, the level is adjusted. In track mode each track is adjusted separately, in album mode the entire album is adjusted by the same amount.

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 don't think you need to worry about hiss. Keeping DAC and Windows volumes at maximum will ensure highest signal to noise ratio to the amp, which is of course good. For ReplayGain to work it needs the headroom for the louder material, so it would be best if you didn't try to fight it. But using the preamp slider in foobar2000 is the correct way to increase the loudness of ReplayGained output. Increasing the preamp will of course make clipping more likely, but as long as it's lower than the negative gain values shown for your tracks/albums, it won't introduce any additional clipping.

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?
It works like volume knob but since it's done before the DAC it can prevent clipping of intersample peaks or floating point material that would clip in the DAC.

I'll attach an old test file that you can use to test and demonstrate the effect of intersample clipping in your DAC. If you play that file unaltered through your DAC at max volume you will hear distortions if the DAC clips. Lowering the volume will let you hear how it should sound without clipping. I have seen some super high end DACs sold that claim they have 3 dB headroom against intersample clipping. This goes beyond that so I don't think there is a DAC that can handle this without help from computer.
7
3rd Party Plugins - (fb2k) / Re: Peakmeter Spectrum component
Last post by wojak -
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.

Concerning width and bars adaptation. We did not understand each other. I said that if I start the component as a pop-us id DUI (I always use it like that) it is OK, it shows all bars or graph or peak meter correctly. But if I then click "full screeen" it becomes incorrect and if I then click "full-screen" again to make it "normal view" again..it still stays incorrect. Only starting new song corrects it. And it always is that way. SO following your suggestion I would change the settings after every click or every drag of the mouse (I sometimes want it bigger to see some parts better but just for a while).
And most important fact is that if it goes wrong it is just all moved to the right so the lest side is veeery wide and the right side is not very thin it is just cut out of the picture so for ex. normally the peak meter goes to 0 (the scale) and after changing the sizxe manually (with mouse) or to full screen the scale ends at 18. The rest is cut out. Changing it back does not change anything. Only starting new song brings it back to normal but if then change the size it is wrong again.
8
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.
9
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?
10
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.