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
2
3rd Party Plugins - (fb2k) / Re: Georgia-ReBORN - A Clean foobar2000 Theme
Last post by regor -
It doesn't matter at all if it's a foobar or smp crash to apply a workaround; SMP is known to do weird things sometimes, and it can be avoided with extra JS code. I mean, if that's the real problem!

Since a foobar crash does create a report, that's the thing you should share.
3
Other Lossy Codecs / Re: lossyWAV 1.4.2 Development (was 1.5.0)
Last post by Porcus -
Quote from: Nick.C on
the calculated bits to remove are then removed from each of the stereo channels in the WAV data.
From each ...
So there is then this in-principle-possible way to save "up to half a bit" extra at likely-small fidelity penalty: If we decimate each channel down to N bits, then design the dither so that Nth bit is common to both channels - then reducing the "side" channel by one bit, except for frames where FLAC uses dual-mono encoding?
Or does it already?
5
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by jaro1 -
In case no further fixes or optimizations in the code are planned in the near future, is it possible to consider the latest binaries (GCC13 and Clang by Joshua, GCC14 by Wombat) as current stable versions, or are there still some minor changes in the pipeline? I think that in the case of Kevin's Zoomtext issue, Joshua's Clang version is usable for him at the moment.
Good or bad.. till now i can't contribute with any, widely accepted bug report.

In regard the above, an additional, but offtopic (sorry) question for Case.. how likely is it according to you, that hmp3 will appear in the Free Encoder Pack some day? I think, Peter has to confirm it at the end..?

From user's perspective, i want to once again express my gratitude to Maikmerten, Case and the guys who contributed with their builds. From my subjective perspective and not least because of the encoder's performance, thanks to you guys is hmp3 IMHO definitely an alternative to the current version of the Lame encoder. Depending on preferences and priorities, hmp3 is better than Lame for someone, worse for another..
6
foobar2000 mobile / Re: {featuring request{ db trigger for corss mixing (not fading) for android version
Last post by tasamagos -
I use this component almost constantly and am very happy with it.
One feature I would like to request, if possible, to be implemented.
My playlist includes many songs with relatively long intro fade-ins, so I want to take that into account in the mix.

Is it possible to mix so that the moment when the end of the song being played falls below a certain dB threshold and the moment when the beginning of the next song rises above a certain dB threshold are at the intersection?
Maybe it is technically difficult, but it would be a more versatile crossfade mix plugin if it were implemented!
7
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.
8
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?
9
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.
10
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)),))