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
22
3rd Party Plugins - (fb2k) / Re: JScript Panel
Last post by marc2k3 -
The presence of that array is obviously not enough. The file extension has to be checked against it. Full changes here...

https://github.com/jscript-panel/component/commit/f3132412ea73ee3786f92114e6c64e1f0b6a8e8e

The cache location really needs to be the same folder for all files otherwise it will break the menu options for clearing the cache. And the filenames are not meant for easy reading by people - they current use the fb2k $crc32 function to generate a numeric hash as part of the image filename. I really don't see the value of them outside the scope of this script.
24
Audio Hardware / Re: Continuously monitor Power Amp Input or Output to see if it is maxing out
Last post by rbl -
There is a circuit called a peak detector, which at its simplest is a diode and a capacitor.  The capacitor charges-up to the peak voltage and the diode prevents it from discharging.    You can measure the DC voltage and calculate peak power.   Or, once you know the approximate maximum voltage you can get, you can just monitor and mentally compare with the maximum.

That's ingenious! TBH my knowledge of electronics is pretty limited. I guess the diode just has to have a maximum voltage greater than the amp (so 100V/1A would easily cover it). But what sort of capacitor? Also given the peak may only last a millisecond or so, will the capacitor actually charge in that time? And won't the capacitor drain pretty quickly anyway (even if the parallel resistor is removed) - ideally I need it to last for minutes rather than seconds as I don't want to have to keep an eye on it all the way through a movie.

To be honest I had hope for a more off the shelf solution, one that more continuously monitors things so I get more than one data point. But I may well give the above a go!
26
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Defender -
@Case

There is something off when scanning containers.

For reference: Truepeak scans 30x 96/24 files with a speed of 664x. Foobar RGx8 does 255x.

SACD-ISO with 2&6ch content: Truepeak Scanner extremely slow (speed 46x) and the Abort button does not work until you reach the end of the scan.
Foobar's built-in RGx8 scan is also similarly very slow (speed 42x) but it does respond to it's Cancel button.

DVDA-ISO with MLP 96/24 2&6ch content: Truepeak Scanner is slow (speed 371x). Abort button only works at end of the scan. Foobar RGx8 Scanner is slow (speed 579x) but Cancel works.

MKV with DTS-HD 48/24 content: Truepeak Scanner is slow (speed 333x). Abort button does work. Foobar RGx8 is slow (speed 214x) and Cancel works.

Any ideas?




27
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Defender -
That said, yes, I agree there needs to be a convenient export function whether it is a plain textfile like it used to be with DR or an automatic screendump (png/jpg) of the result screen which is also a custom in (bootleg) releasegroups. I prefer the latter.
Why would you prefer a screendump over text?
My preference is a CSV for those of us who like spreadsheets :D
I don't give a damn about logfiles or screendumps as long as I can check (my) rips are accurate.
Would be nice if download content is already properly tagged with relevant info like catalognumber and including this stuff :-)
28
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Blew -
That said, yes, I agree there needs to be a convenient export function whether it is a plain textfile like it used to be with DR or an automatic screendump (png/jpg) of the result screen which is also a custom in (bootleg) releasegroups. I prefer the latter.
Why would you prefer a screendump over text?
My preference is a CSV for those of us who like spreadsheets :D
29
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Defender -
I am not sure if upsampling is the only difference, because taking 48kHz file and scanning it with RG with 8x (giving 384k) and scanning it with TP scanner set to 384k gives different Gain and TPeaks (which then give different PLR and LUFS).
I did not tinker with TP minimum scanning sample rate so 48kHz sources are upsampled to 192k when scanning. (And 44kHz to a bit higher I guess).

The only issue with it is that I already have scanned tens of thousands files with RG and started to scan other files with TP scanner and use "prevent clipping" option (without applying gain) so the effect will be different. Moreover I have different releases  of the same albums and check if they are sonically the same (comparing TP, DR, LRA, LUFS, PLR) so having different results on different releases makes it impossible. I have to rescan all the files once again.
Same here. So when I want to compare specific releases of the same album I just rescan those fully to get apples and apples. Scanning is rather quick. Then I listen to them with DSP Retain playtime enabled to switch seamlessly.

If you want to compare different albums/artists it really does not matter that much imo with what version those albums were scanned since scanning results don't differ that much.

I did not say that the text results should look exactly the same as in old comonent. I just suggested that it would be convinient to be able to automatically export the results to the file (not having to clik "copy" than creating plain file and pasting the results - the old component just had an option to do this (or don't)). and if we get that option it would be nice to have everything included.
I do agree and already thought about the dr_log file earlier. Then again I'm not a fan of overloading a developer with nice to have (or even silly) requests before the tool itself is bugfree, which is happening unfortunately with some other promising components.

That said, yes, I agree there needs to be a convenient export function whether it is a plain textfile like it used to be with DR or an automatic screendump (png/jpg) of the result screen which is also a custom in (bootleg) releasegroups. I prefer the latter.
30
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by wojak -

Of course results are different. With RG you can only use a fixed truepeak method. In other words it does not base the amount of upsampling on the content.
The truepeakscanner upsamples based on the content (up to a minimum of 192k if I remember correctly).
So the used upsampling methods differ, therefore also the results.

I don't exactly understand why this tool should give the exact information as the original DR component which is ancient.
Why not use the exact info from the scan resultscreen? Everything including LRA is there.

Only thing that could be better is to remove all Album stuff from the tracklines and show this info (preferably on top) as a separate line.
And it would be nice if tracknumbers&length would be included in the grid (eg total tracks/ total time for the album line).

I am not sure if upsampling is the only difference, because taking 48kHz file and scanning it with RG with 8x (giving 384k) and scanning it with TP scanner set to 384k gives different Gain and TPeaks (which then give different PLR and LUFS). The only issue with it is that I already have scanned tens of thousands files with RG and started to scan other files with TP scanner and use "prevent clipping" option (without applying gain) so the effect will be different. Moreover I have different releases  of the same albums and check if they are sonically the same (comparing TP, DR, LRA, LUFS, PLR) so having different results on different releases makes it impossible. I have to rescan all the files once again.

I did not say that the text results should look exactly the same as in old comonent. I just suggested that it would be convinient to be able to automatically export the results to the file (not having to clik "copy" than creating plain file and pasting the results - the old component just had an option to do this (or don't)). and if we get that option it would be nice to have everything included.