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 Nick.C -
Quote from: Porcus on
Complete n00b question that I didn't find much answer to. I see no -m in the signature immediately above, at least.

Reducing bit depth not by zeroing out both stereo channels, but by averaging bits - so that they are zeroed in a side/difference channel; is that -m?
Which might not be exploited in a way that gives any bang for the buck really?
The -m, --midside parameter only works with stereo content and determines bits to remove through analysis of mid and side channel data, the calculated bits to remove are then removed from each of the stereo channels in the WAV data. This means that the bits to remove value is the same for each channel (which is not the case normally) so the overall bits to remove for the processed data will likely be lower.
2
Other Lossy Codecs / Re: lossyWAV 1.4.2 Development (was 1.5.0)
Last post by Porcus -
Complete n00b question that I didn't find much answer to. I see no -m in the signature immediately above, at least.

Reducing bit depth not by zeroing out both stereo channels, but by averaging bits - so that they are zeroed in a side/difference channel; is that -m?
Which might not be exploited in a way that gives any bang for the buck really?
3
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Case -
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.
4
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Defender -
Quote from: darkflame23 on
Thanks for those!

For PLR I'm using this (also posted by someone else on here), which is just nuts:

$puts(PLR,$if(%replaygain_track_peak_db%, $puts(PLR,$sub($mul($replace(%replaygain_track_peak_db%,.,),10),$sub($mul($replace(%replaygain_track_gain%,.,),-10),18000))) $puts(PLR_TEN,$left($right($get(PLR),3),2)) $puts(PLR_ROUND,$ifgreater($get(PLR_TEN),40,$add($get(PLR),100),$get(PLR)))$iflonger($get(PLR_ROUND),4,<$left($get(PLR_ROUND),2)<.$substr($get(PLR_ROUND),3,3),$left($get(PLR_ROUND),1)<.$substr($get(PLR_ROUND),2,2)),))$get(PLR)

Yep. That's the one :-D

LUFS:
$if(%replaygain_album_peak_db%,$puts(LUFS,$add($mul($replace(%replaygain_album_gain%,.,),10),18000))$puts(LUFS_TEN,$left($right($get(LUFS),3),2))
$puts(LUFS_ROUND,$ifgreater($get(LUFS_TEN),40,$add($get(LUFS),100),$get(LUFS)))$iflonger($get(LUFS_ROUND),4,$left($get(LUFS_ROUND),2).$substr($get(LUFS_ROUND),3,4),$left($get(LUFS_ROUND),1).$substr($get(LUFS_ROUND),2,3)),))
5
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by darkflame23 -
Thanks for those!

For PLR I'm using this (also posted by someone else on here), which is just nuts:

$puts(PLR,$if(%replaygain_track_peak_db%, $puts(PLR,$sub($mul($replace(%replaygain_track_peak_db%,.,),10),$sub($mul($replace(%replaygain_track_gain%,.,),-10),18000))) $puts(PLR_TEN,$left($right($get(PLR),3),2)) $puts(PLR_ROUND,$ifgreater($get(PLR_TEN),40,$add($get(PLR),100),$get(PLR)))$iflonger($get(PLR_ROUND),4,<$left($get(PLR_ROUND),2)<.$substr($get(PLR_ROUND),3,3),$left($get(PLR_ROUND),1)<.$substr($get(PLR_ROUND),2,2)),))$get(PLR)
6
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Defender -
Quote from: darkflame23 on
What are the strings/title formatting we need to enter to get the DR and LRA values to show up in a Playlist column?

Would also be nice to have an easy way to show LUFS Integrated and Max LUFS M and Max LUFS S for each track. I use a long string now for LUFS-I, but be nice to have something that was more easily understandable.

$if(%replaygain_track_gain%,$puts(l,$sub(-1800,$replace(%replaygain_track_gain%,.,)))$div($get(l),100).$right($get(l),2) dB,)

And thanks Case for making this, it's fantastic.

LRA:
[$replace(%replaygain_track_range%, LU,)]

DR:
[%dynamic range%]

Doesn't give you colorcoding though.

Don't know about LUFS and PLR . I'm using a much more horrible oneliner than you borrowed from Regor.
I tried to make it more readable but failed miserably.
7
Polls / Re: Sound colors of codecs
Last post by C.R.Helmrich -
Quote from: btc on
Different codecs can introduce different type of coloration.

I can notice it especially on rock and metal genres.
Which codecs are these?

To all, especially the creator of this poll:

I fear people here interpret the term "coloration" quite differently.

Coloration (in both vision and acoustics, I would say) occurs when the intensity of certain frequencies in a signal is changed. The purpose of audio codecs, when used according to the developers' intentions, is not to color the sound in any way. Of course, at low bit-rates, audio codecs produce other types of compression artifacts like temporal or spectral smearing, as Sunhillow already mentioned. But at their intended operating rates, they try to represent the original signal as closely as possible, i.e., to maximize quality and fidelity. If a codec colors the sound during compression, there's no way it can achieve high quality and fidelity.

So none of the poll answers make any sense to me.

Quote
... 11025Hz low bitrate MP3's after realizing most Flash games were actually using 11025Hz low bitrate MP3's (they were sounding very good). 11025Hz low bitrate MP3's are easier to listen than the original ones for me.
So you like your audio to be downsampled, which obviously colors the sound because it removes high frequencies (and may even add aliased lower-frequency content). Or put differently, you're using the downsampling/upsampling as an audio effect.

That's perfectly fine with me, but has nothing to do with audio codecs. So sorry for the bluntness, but please don't confuse people with ToS-borderline terms like "good sound color" in the context of audio compression, giving such above-mentioned examples where MP3, a 30-year old codec, was not even operated according to the developers' intentions (32...48 kHz).

Chris
8
3rd Party Plugins - (fb2k) / Re: foo_skip: skip tracks that match a specified search query
Last post by Case -
It's not SQL syntax, it's foobar's search query syntax. Correct way to write the query you tried to use is:
Code: [Select]
"$mod(%play_count%,3)" EQUAL 0
It has been said numerous times but I'll say again: you can test your query (if it doesn't use the component's built-in features) in foobar's library search dialog. You'll instantly get feedback if the syntax is right and will get a list of tracks that match the query.
9
3rd Party Plugins - (fb2k) / Re: Dynamic Range plugin
Last post by Case -
Uploaded a new version and also published it on the official repository: https://www.foobar2000.org/components/view/foo_dr_meter.
Mainly improvements to the log writing, written average bitrate now matches foobar as it's properly weighted based on track lengths. Length info gets written even for tracks that don't report length to foobar as exact frame count is stored during scanning. And if album consists of various audio formats all the different formats will be listed at the bottom info section.
10
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by darkflame23 -
What are the strings/title formatting we need to enter to get the DR and LRA values to show up in a Playlist column?

Would also be nice to have an easy way to show LUFS Integrated and Max LUFS M and Max LUFS S for each track. I use a long string now for LUFS-I, but be nice to have something that was more easily understandable.

$if(%replaygain_track_gain%,$puts(l,$sub(-1800,$replace(%replaygain_track_gain%,.,)))$div($get(l),100).$right($get(l),2) dB,)

And thanks Case for making this, it's fantastic.