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
Other Lossy Codecs / Re: lossyWAV 1.4.2 Development (was 1.5.0)
Last post by Porcus -
N00b question (again!)
1.4.3c  and flac.exe 1.4.3, is the latter supposed to return
WARNING: RIFF chunk size of file file.lossy.wav does not agree with filesize
file.lossy.wav: ERROR reading foreign metadata: invalid WAVE file: unexpected EOF (010)

?


(By the way, I forgot to mention WavPack's has a --merge-blocks - for those who will test a codec that already has a hybrid lossless solution.)

3
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by ngs428 -
This component reports several values.  I am trying to understand what they all mean and how I can use them. I am familiar with RG and DR values, rest is new and trying to learn.  Searching has been hit and miss.  I tried to explain some of what I a using for definitions below.  Ultimately I want to understand how I can apply the values and what are "good" vs "bad" values.  Assistance would be appreciated.  Thanks! 

  • Track and Album Peak- This is the common RG value. Can be used to prevent gain adjustments from inducing clipping in the playback device
  • Track and Album Gain - This is the common RG value in dB.  ReplayGain-capable audio players use the replay gain metadata to automatically attenuate or amplify the signal on a per-track or per-album basis such that tracks or albums play at a similar loudness level
  • Track and Album LRA - Loudness Range in Loudness Units (LU).  Measures the variation of loudness across a song or album.  LRA values can show whether a song has a continuously constant loudness (low LRA values) or a high variation between low and high level components (high LRA values)
  • Track and Album Max LUFS-M - Momentary (0.4 seconds?) measurement, as opposed to "I" which is the whole song
  • Track and Album Max LUFS-S - Short Term (3 seconds?) measurement, as opposed to "I" which is the whole song
  • Track and Album LUFS-I - Similar to RG.  Measures the entire song.  How can I apply this value to normalize song's loudness levels?  When I use Case's ReplayGain DSP, does it use this value?  I can pick a loudness target of -14 LUFS, -18 LUFS, etc, but that is just the target.  What value is is using to match the target?  Is it still using the track and album gain or is it actually using the LUFS-I value, or does it matter?
  • Track and Album DR - The distance in dB between the softest sound and the loudest sound.
  • Track and Album Clipped Samples - Any sample value that is beyond digital fullscale.  One clipping sample means that only one channel clipped. If same spot clipped on all channels of a 384 channel recording, it would be shown as 384 clipped samples.
  • Peak Timestamp - Time in track which contains the highest peak value.
4
Other Lossy Codecs / Re: lossyWAV 1.4.2 Development (was 1.5.0)
Last post by Nick.C -
I have never considered the idea of compressing according to the content by giving the right to play with block sizes.
Of course, for LossyWav, this may be necessary by nature.
To achieve the best reduction, i.e. where bits to remove changes within a larger block size, it is indeed necessary.
The only problem for me right now is the processing speed of LossyWav.
While it is readily acknowledged that lossyWAV is not particularly fast, it is what it is - and as each file need only be processed once, it's not the worst downside, IMO.
6
3rd Party Plugins - (fb2k) / Re: Dynamic Range plugin
Last post by omasciarotte -
Yup, the MkII version is at 2.2.3. DROffline MkII is a much more modern and complete product relative to the OG DROffline. When we built DROffline, we wanted to replicate the TT ancestor as closely as possible while making it 64 bit, 384k-capable, et cetera. The MkII version has all the modern stuff added, and the future MkIII will have a bunch of new functionality.
7
Lossless / Other Codecs / Re: libttaR (TTA rewrite part 2)
Last post by rdtsh -
Using (old version) ffmpeg of cli tool for performance comparison is flawed and extremely biased.
The tta codec version should be the same between the version I used and the current version, or at least the differences are negligible. You are always welcome to post your own benchmarks.

Also current ffmpeg cli tool have bad performance with smaller packets due to clumsy MT work of ex-developer.
ok

Also just to run generic build of ffmpeg for the first time takes extra time
That cannot be more than a millisecond.

Also this repo does not have any SIMD x86 assembly and the only way performance can go up if compiler is modern clang.
If anything, that is a virtue.
FYI, most of the performance increases came from optimizing the rice coder, which is completely unSIMDable
9
Scientific Discussion / Re: Are complex-input FFTs really useful for audio analysis?
Last post by TF3RDL -
For the last sentence can you cite relevant non-pseudo scientific papers?
I'll answer this for later (probably if there are either reliable source about this as in my last sentence being cited over or a satisfactory answer that isn't about performance improvements on this miscellaneous reference desk on Wikipedia) as there aren't many non-pseudescientific papers that details the usefulness of complex-valued FFT as in I/Q signals but on audio analysis or even processing stereo audio

BTW, what I call this method a "joint stereo FFT"
10
3rd Party Plugins - (fb2k) / Re: help setting up Georgia-ReBORN please
Last post by TT -
So did you read the text I have sent you as private message and did you read the text from this reply here?
https://hydrogenaud.io/index.php/topic,125957.msg1044764.html#msg1044764

Have you watched the attached video from the replay?
It shows you exactly how to move the mouse to the playlist top bar which will display the playlist manager text,
further more it will also show you how to deactivate the auto-hide feature.

-TT