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
31
3rd Party Plugins - (fb2k) / Re: JScript Panel script discussion/help
Last post by marc2k3 -
I've added full $rgb support to the following samples, They can be tested by pasting the contents of these links in a panel.

Track Info + Seekbar + Buttons + Volume
https://raw.githubusercontent.com/jscript-panel/component/main/samples/Track%20Info%20%2B%20Seekbar%20%2B%20Buttons%20%2B%20Volume.txt

Track Info + Seekbar + Buttons
https://raw.githubusercontent.com/jscript-panel/component/main/samples/Track%20Info%20%2B%20Seekbar%20%2B%20Buttons.txt

Track Info + Spectrogram Seekbar + Buttons
https://raw.githubusercontent.com/jscript-panel/component/main/samples/Track%20Info%20%2B%20Spectrogram%20Seekbar%20%2B%20Buttons.txt
32
General Audio / Re: Downsample 300 gigs of audio
Last post by Porcus -
If you are going for a "lossy codec that works in floating-point" (so that the format itself won't do any clipping), I guess the best is likely to just keep the old true peak RG tags? There will be some more overshoot, but those are lossy artefacts anyway.

For the kind of conversion you started this thread about, where the target format is integer PCM, then you just reduce volume in advance to protect against clipping. Just for the sake of a simple numerical example: say you target 18 bits. Scale everything by 0.5, and you have the same resolution in 19 bits, so decimate to 19 instead.
While a "19-bit" WAV file won't be smaller than a 24-bit WAV file, FLAC (and WavPack and TAK) will handle it so you don't need to worry that 19 is a non-standard number.

SoX can warn you about clipping, but I don't know if there is any easy way to script it in a way so you don't have to manually review.


Anyway ... I would still keep the collection as is.
Or WavPack -c it, keep the correction files on the Big Bad Spinning Drive and the .wv files on your everyday portable or whatever.
33
Other Lossy Codecs / Re: EnCodec: High Fidelity Neural Audio Compression
Last post by Spyrοs -
Since it's from the same company, I figured I should post it here, instead of making a new thread:

MLow: Meta’s low bitrate audio codec

Quote
The MLow codec

We broke ground with our development of a new codec in late 2021. After nearly two years of active development and testing, we are proud to announce Meta Low Bitrate audio codec, aka MLow, which achieves two-times-better quality than Opus (POLQA MOS 1.89 vs 3.9 @ 6kbps WB). Even more importantly, we are able to achieve this great quality while keeping MLow’s computational complexity 10 percent lower than that of Opus.

Figure 2 below shows a MOS (Mean Opinion Score) plot on a 1-5 scale and compares the POLQA scores between Opus and MLow at various bitrates. As the chart makes evident, MLow has a huge advantage over Opus at the lowest bitrates, where it saturates quality faster than Opus.

X

Hacker News discussion
34
General Audio / Re: Downsample 300 gigs of audio
Last post by Squeller -
But is totally certain? When I started to think about resampling my useless 192.000 Hz, someone here warns me about the fact that a risk of clipping exists. I didn’t thought about that. So a tiny problem exists with resampling and is well known. Fortunately, it’s easy to fix (by reducing the volume).

In a lossy conversion scenario (so this is a bit Offtopic. Say, to encoding to AAC @44.1 or 48 khz) what would be the technically best way to treat clipping? With the help of the TruePeak-Scanner, I noticed tracks that already have clipping present in their flac instance. Say, 150 clipped samples a track. Post-conversion there may be 200.

How to react with the converter? a) There's the "Amplify" dsp which could just do some 0.x db decrease of volume - but IMO this is not optimal, because it would to that on every track.
b) "Replaygain alternative" DSP with "Only prevent clipping" - "Max peak 0dbtp" (did not remove clipping), so "Max peak -1dbtp" (already a lot)?

And if DSP: before or after SoX? EDIT: I think post-Resample with "0 dbtp, compress peaks" is a good way.

Thx
40
General - (fb2k) / Re: ReFacets
Last post by Savior32 -
Anyone know if there is a work around to hide the search menu settings on ReFacets? (Toggling Library/Filters buttons on/off)