Would it be possible to make the component scan and produce a tag file for Bluray files? I know that those m2ts files are untaggable but it has been made possible with SACD-iso files by producing xml files that contain tags and are stored in the same folder as corresponding audio file.

Quote from: wojak on 2024-05-13 10:03:45

Would it be possible to make the component scan and produce a tag file for Bluray files? I know that those m2ts files are untaggable but it has been made possible with SACD-iso files by producing xml files that contain tags and are stored in the same folder as corresponding audio file.

foo_external_tags also by Case?

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

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.

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.

Quote from: Defender on Today at 11:29

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

@Case, would it be possible to add all features of DR Meter (per-channel DR, RMS and peak) to True Peak Scanner?

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...)?

I have noticed that your component measures slightly different than buil-it RG scanner concerning True Peaks and Gain.  [...] Why is it so and is there a way to make them as similar as possible?

There is something off when scanning containers.

[...]Abort button only works at end of the scan. Foobar [...] Cancel works.

Any ideas?

Quote from: Defender on Today at 12:37

There is something off when scanning containers.

[...]Abort button only works at end of the scan. Foobar [...] Cancel works.

Any ideas?

I don't know why speed differences are so big but abort button not working is a result of input not handling it and my component not having safety checks against it. I'll add once I'm home.