Skip to main content


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
Support - (fb2k) / Re: Some line break symbols are ignored in Properties dialog
Last post by Bogozo -
So it seems that text in tag was originally created on Mac OS or Unix OS. It also can be fixed directly in fb2k using "Format from other fields" $replace(%unsyncedlyrics%,$char(10),$char(13)$char(10))

But, according to Wikipedia, Unicode standard defines that LF ($char(10)) should be recognized as line terminator, just like CR+LF ($char(13)$char(10)) -
General Audio / Re: Clipping, headroom, headphones, amps and audio files/philes
Last post by Dracaena -
The 2015 is all in red to warn us to stay away, danger!  What does that mean to me as a listener?  The wave forms aren't clipped and the mountains and valleys look similar so why would that indicate that the 2015 sounds worse than the Japanese version?
In order for it to not clip, they used compression and limiting, which distort the waveform. It is perhaps less noticeable to many people because it doesn't sound anything like the crackling caused by digital clipping, but it's still audible. In effect the 2015 version is just the original with added distortion.

If I record a flute playing a single note without increasing the gain in the mixing deck during the note, wouldn't the dynamic range be very low even if the recording was clear and detailed ("audiophile quality")?  So what exactly does a dr measurment have to do with quality?  As long as the waveforms don't clip, why should the dr make a difference during playback, and effect my buying decisions?
In a sane world you are right it would have little to do with quality. It is mainly relevant within the context of the loudness war, without which that website you reference wouldn't exist. It is mainly just an easy way to spot over-compressed (aka brickwalled) releases like your "I Am The Night".

Similarly, I'm looking at purchasing DCA Stealth headphones. It  has a sensitivity of 86 dB, which means they are more challenging to get volume out of.  However, I don't listen that loud so even if I have to turn one amp to 9 and one to 3, there shouldn't be any difference in bass or "slam" between two amps if they can both listened to at the same volume, right? Similarly to the audio files, where there should be no difference in the sound at differing mastering levels provided that the wave forms are not clipping, right?
Assuming both were taken from the same source, and all else being equal (not remixed or heavily eq'd etc), the 2015 may have noticeably weaker drums and/or bass, harsh sounding mids and muddier overall mix that is harder to tell instruments apart. None of that is guaranteed but in my experience those are the most obvious results of these highly compressed masters.

Included in that screenshot is Ashes of Ares "I am the night".  It's not clipped either, but the wav looks flatter, and to me the kick drums sound dead.  What's going on there in that [too many examples in my collection of this] release?
Yes drums, especially kick drum and snare are often the first victims of the compression, this takes a bit of explanation. Attached is a spectrum plot of Ramble On from my copy of Led Zeppelin II. You can see a distinct slope, the bass frequencies have much more energy than the treble. You will find this slope in pretty much all popular music, although perhaps not always as extreme as this.

So what happens when you come along with a compressor/limiter that is designed and configured to attenuate the loudest parts of the audio stream, and apply it to the whole mix? The kick drum and bass guitar act like triggers, the compressor engages more on each kick drum hit. So those particular moments will have reduced volume (so it doesn't clip) and more introduced distortion than the rest of the track.
3rd Party Plugins - (fb2k) / Re: Library Tree Discussion
Last post by WilB -

0 sets Show Html Dialog as unsupported. It doesn't attempt to load options to avoid errors on systems like Wine that don't support it. You need it on 1 as clearly it's supported on your system.

Most users shouldn't have to be concerned about the feature check. It should happen without any user interaction and be correctly set in the background. Only in occasional cases when the feature checker detects Show Html Dialog as unsupported will a popup appear which gives the opportunity to confirm & exclude a false negative etc.

The autocheck runs on first use when the panel property value is set to 2. It's a one time check and will then be set to 1 or 0. If it's 0 (unsupported), then you'll get the one time confirm as above.  Setting the panel property to 2 will redo the autocheck.
General - (fb2k) / CUESheet Creator Component
Last post by NetRanger -

I know there is an old 'foo_cuesheet_creator' component floating around out there that doesn't work especially well with foobar2000 from what i've read, so now im wondering if there is another CUESheet Creator component available or?