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


Thank you for suggesting external tag, it works great.
5
3rd Party Plugins - (fb2k) / Re: Dynamic Range plugin
Last post by wojak -
@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 (and True Peak Scanner) 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").
6
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by JoshuaChang -
Quote from: jaro1 on
Quote from: Wombat on
No fast-math, no AVX and there were no changes to the code since last clang version from @JoshuaChang afaik.

I was just unsure, which Clang version did Joshua used for his binary and if there would be a noticeable difference at all, if it was older..
Anyway, thanks for your reply!  

My lastest dev clang build was using clang 18.1.4; gcc build was using gcc 13.2, no additional compile flag.
All other clang builds have mentioned version on their name.
8
3rd Party Plugins - (fb2k) / Re: Dynamic Range plugin
Last post by sveakul -
Quote from: NetRanger on
Thnx Case :)
Agreed!  But to my taste the multichannel and RMS thing gets a bit cluttered.  The new foo_true_peak  results that now include DR, give me everything  I could ask for in one 3-value result:  Track peak, LRA, and now DR, optionally expandable to include album results.  Just a heads-up so fans of foo_dr_meter don't neglect to check that one too.

Edit:  Defender yes it has option to do RP gain:

9
3rd Party Plugins - (fb2k) / Re: Dynamic Range plugin
Last post by Defender -
Quote from: dalover on
Thanks Case

It would be nice if you could consider a silent mode. I have assigned the function to a keyboard key and don't need the result dialog. A progress bar would then be sufficient.

I second that.

I'd also like that the remove function removes everything you selected truepeak scanner to scan initially. You now remove DR information (which most likely was scanned with the old component), so why not RG info if Truepeak has been selected to overwrite this info upon scanning
Or make it a setting in preferences/advanced/truepeak that the remove function also removes RG (if upon scanning TP also does RG)
It's a bit silly to clutter my context menu with RG only for the removal part.