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 Case -
Quote from: darkflame23 on
Would also be nice to have an easy way to show LUFS Integrated and Max LUFS M and Max LUFS S for each track.
Here's an unpublished True Peak Scanner version with max momentary loudness (LUFS-M) and max short-term loudness (LUFS-S) scanning support: https://foobar.hyv.fi/foo_truepeak_0.6.8.fb2k-component.
At the moment the component defaults to storing LUFS-M in a tag field "truepeak_scanner_max_lufs_m" and LUFS-S respectively in "truepeak_scanner_max_lufs_s". If there are tag fields already in use by some software I'd happily change to use the same fields.

LUFS-I is computable from the ReplayGain value, but if there's strong will for yet another option, it could be stored in a separate tag field.
2
AAC - General / Re: QAAC: discussion, questions, feature requests, etc.
Last post by phadron -
Quote from: nu774 on
You need avisynth script like this:
Code: [Select]
FL = WavSource("FL.wav")
FR = WavSource("FR.Wav")
  :
SR = WavSource("SR.Wav")
MergeChannels(FL, FR, ..., SR)

You have to give channles to MergeChannels() in correct (WAV) order, and also tell qaac channel layout with the following option.
Code: [Select]
--chanmask=0x63f

Thanks nu774 for fast reply!
Is it possible stay with separate WAVs files on input?

Something like ffmpeg:

Code: [Select]
ffmpeg -i blabla_SL.wav -i blabla2_SR.wav -i blabla3_SC.wav

I prefer separate WAVs because a single WAV should be very big.
3
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by ngs428 -
Quote from: Case on
Quote from: ngs428 on
Most values were the same, peak timestamp if different, along with track and album peak.  Is this to be expeced?
Peaks being slightly different is expected with different resamplers. Highest peak position changing entirely was unexpected, I have never noticed that happening. Would be curious to see what goes on in the track in those positions that causes such shift.

You didn't mess up anything as long as you didn't include the quotation marks when you typed the preferred resampler name in advanced preferences. As Defender said, that's step is no longer needed for True Peak Scanner component but now that you have done it, all components that ask for (random) resampler will get SoX. That's good, so all components will get a very fast and high quality option.

I sent you the file in your messages that had 2 peak timestamps.  I didn't use the quotes, so I am all good there.  Thanks for this component! 
4
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by maikmerten -
As far as I'm concerned, those builds should be plenty fine and can be called "stable".

There are further patches on the dev branch (Case's reworked progress printing, improved help messages, some safeguards against negative array indices in the encoder math), but nothing that invalidates the current builds.
6
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Defender -
Quote from: darkflame23 on
Thanks once again! Can I just add that to the current pattern, or should I delete those and replace it with this? Am guessing add it?

If you don't mix tagged stuff with untagged stuff you can add it at the end, but since you organize albums in folders always (like I do) you can just replace the whole thing.

EDIT: Which is also the reason that I don't use subfolders for multicd albums.
8
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Defender -
Quote from: darkflame23 on
When True Peak Scanner scans "...(as albums)" does it take the physical file system Folders into account, or is it only looking at the metadata/album tags? I have all my albums as separate folders, but not all of them are fully tagged. The ReplayGain Scanner has a "Scan as albums (by folders)" option which I always use when scanning a mass of albums in one go. Just wondering if this one does the same as I don't see an option for it.

In Advanced you can set album grouping pattern. In your case that would be:
$directory_path(%path%)
9
Other Lossy Codecs / Re: lossyWAV 1.4.2 Development (was 1.5.0)
Last post by Nick.C -
The bit removal process is carried out on each channel separately, using the calculated bits to remove value for each channel, and may (depending on whether too many new clips are encountered or whether any of the feedback [if selected] breaches limits) remove fewer bits than desired - shown in output as "bits lost". Noting that if --midside or --linkchannels have been selected then the bit removal process will be repeated for any channels where the actual bits removed is higher than the minimum for that codec block.

This would be further complicated if adaptive noise shaping was in use (which it is by default) as the filters are channel specific.
10
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by darkflame23 -
When True Peak Scanner scans "...(as albums)" does it take the physical file system Folders into account, or is it only looking at the metadata/album tags? I have all my albums as separate folders, but not all of them are fully tagged. The ReplayGain Scanner has a "Scan as albums (by folders)" option which I always use when scanning a mass of albums in one go. Just wondering if this one does the same as I don't see an option for it.