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 Blew -
Quote from: Defender on
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
2
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Defender -
Quote from: wojak on
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).

Quote from: wojak on
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.

Quote from: wojak on
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.
3
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by wojak -
Quote from: Defender on

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.
4
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Defender -
Quote from: wojak on
Sorry for copy-paste of my post from DR Meter topic but it is related.

@Case, would it be possible to add all features of DR Meter (per-channel DR, RMS and peak) to True Peak Scanner? The output log placed in the folder with actual audio files (as in old component) would also be very much appreciated (I would love to see every measurement in it, including LRA, Clippings and Peakstamps).

How does this plugin behave with files containing several streams (like bluray m2ts with more than one version of the album - ex. stereo, instrumental, DTS, AC3, THD...)? Will it measure the first stream (or which one?) or is it possible to measure all streams (changing the stream with stream-selector and measure them all one by one and getting different results not owerwriting the previous ones)? And if it is possible, how to write such tags with your external tags? In case of SACD-iso we can write an xml containing two sets of tags/measurement (one for stereo and one for 5.1) (I know that those are different, not two streams but separate sets of "audio files").

I have noticed that your component measures slightly different than buil-it RG scanner concerning True Peaks and Gain.  I know that True Peaks are just (gu)esstimation of what would happen in the DAC but tried to manipulate the options in both components and never got exact the same measurements. My RG sacnner always was an 8xupsampling but I tried it with other options (SOX, SRC, 4x..) and yours with 190k and 384k. The results were always slightly different (rarely the differences were quite big, on some mp3 and the differences go both ways - sometimes yours shows less and sometimes more). Why is it so and is there a way to make them as similar as possible?

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).
5
3rd Party Plugins - (fb2k) / Re: JScript Panel
Last post by wojak -
Quote from: marc2k3 on
I can exclude certain types no problem. If you can't wait for the next component release, this file can be saved inside your component folder\samples\js overwriting the exiting file.

https://raw.githubusercontent.com/jscript-panel/component/main/samples/js/seekbar.js

This works purely on the command line - fb2k components are irrelevant so I'm excluding mkv, m2ts and iso by default. While I couldn't test m2ts, I tested blu rays ripped to mkv and that resulted in huge memory usage (I let it get to 8GB before I aborted via task manager).


I am starting to understand the very basics of those scripts (I am absolutelly very far from being a programmer) so is
this.excluded = ['mkv', 'm2ts', 'iso'];
the only thing changed or is there something else?

Would it be possible to scan such large files with ffmpeg (outside of your component and foobar) that would produce a picture that could be manually renamed and placed in your database folder or would such measurement also use all resources and crash?

And what about: Would it be possible to change the destination folder of the resulting pictures to the folders containing the actual audio files?
7
3rd Party Plugins - (fb2k) / Re: Dynamic Range plugin
Last post by Defender -
Quote from: sveakul on
Edit:  Defender yes it has option to do RP gain:

Yes. I know :-)

But it has not the option to clear RG values when you choose the truepeak remove context menu option.
Which is the only reason I still need Replaygain context menu and I want to get rid of it.

I do not use the built-in RG scanner at all anymore.
Reason is that it is either less precise (if you do not enable the the true peak scan option in replaygain settings or less efficient/slower.

If you do RG scan with with comparable precision (which actually can only be achieved with truepeak auto 8x) as the standalone truepeak scanner is a lot slower AND you still have to run a separate scan for LRA+DR and clipping positions.

If you are using truepeak scanner, it won't get any slower when you enable RG, LRA, DR or scanning for clipping positions.
I attached my test results.
8
3rd Party Plugins - (fb2k) / Re: JScript Panel
Last post by marc2k3 -
I can exclude certain types no problem. If you can't wait for the next component release, this file can be saved inside your component folder\samples\js overwriting the exiting file.

https://raw.githubusercontent.com/jscript-panel/component/main/samples/js/seekbar.js

This works purely on the command line - fb2k components are irrelevant so I'm excluding mkv, m2ts and iso by default. While I couldn't test m2ts, I tested blu rays ripped to mkv and that resulted in huge memory usage (I let it get to 8GB before I aborted via task manager).
10
3rd Party Plugins - (fb2k) / Re: JScript Panel
Last post by wojak -
@marc2k3,
I have encountered an issue when using your spectrogram seekbar with large bluray files (m2ts). It starts measuring such a file but then it probably runs out of memory and crashes my computer. The resulting file appears in the database but is faulty so the next play displays nothing and the log says that the file is there but it is faulty and does not measure again. If I delete that file it starts to measure again but crashes the laptop and so on....
Doing such measurement with Spek or Spek-X does not crash and is much faster (those also use ffmpeg but can't (as far as I know) be used to generate files that would be visible in your component).
Because I can't properly scan such a file with your component without a crash I also can't check how would it behave after changing the stream of a multi-stream file (such as bluray m2ts with multiple versions of an album). Would it write multiple pictures or the second one would overwrite the previous or changing the stream would not change the measurement at all (what would be measured - always the first stream or the one actually palying?).
Would it be possible to change the destination folder of the resulting pictures to the folders containing the actual audio files?
The component (and also Spek and Spek-X) do not measure SACD-iso at all. I can live with that but I wonder why some other components show results (abviously after making the sacd componet as DSD+PCM) - does it mean those other comonents take the input data from some later part of audio-chain so they see the "fake PCM part" of DSD signal?

I can of course let all my blurays be scanned once with crash and produce faulty files and be left with no graphs but maybe there is a way to make it work or to exclude m2ts files from scanning? (I do not use Library).