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: Dynamic Range plugin
Last post by Porcus -
Quote from: Case on
Quote from: Porcus on
Did a few brief tests. On a couple of tracks, yours returns a dB more than foo_dynamic_range . No problem unless it is a symptom of something, I'm just assuming it is roundoff.
I read somewhere the default component resamples everything to 44.1 kHz. My component doesn't do that as that shouldn't be necessary and the PDF paper describing the measurement doesn't speak anything about resampling. Another difference is that the old component clips at least sample peaks to 1.0. I do not clip anything as I consider that incorrect. Though if people disagree I can modify the behavior.

No disagreement over improved handling, please keep it - I only intended to raise the "are discrepancies to be expected?" question to a 1.0 version.

By the way, I tested CDDA stored losslessly, so it is not about resampling.
3
Speech Codecs / Re: Best practive to reeendoce previously 64k speech/music audiobook (Audi
Last post by Porcus -
Information about DRM cracking is against this forum's terms of service, so the information you can get would be down to those you can legally extract. What do you get from ffmpeg -i <filename>  ?

As for re-encoding the decode, you do get generation loss. B kbit/s lossy decoded and re-encoded into B kbit/s lossy is not the same as the original - not saying you will actually hear the difference - but the way to tell is by ear. Consider lossies on your mp3 player as disposable, and if they aren't good enough: throw away and re-encode.


4
3rd Party Plugins - (fb2k) / Re: foo_skip: skip tracks that match a specified search query
Last post by Sergey77 -
Quote from: Case on
The context menu feels like a wrong place for that action. Context menu is supposed to show valid actions that you can perform to any number of selected tracks regardless of current playback state. Bookmarking playback position is only related to the active playing track. The on/off toggle isn't in the context menu either.
Maybe this context menu option "Add Skip Track bookmark" would only be available when playing a track? Accordingly, the bookmark would be added only for the active playing track. If more than one track is selected, this option is not available.
6
Support - (fb2k) / Re: [BUG?] Foobar fails to function with Windows Sonic, why?
Last post by Case -
It might work better or more efficiently than other outputs on some setups. It lets OS do all the resampling and channel mixing. I also pass the original source sample rate along as much as possible so potentially for example Wine people can get as direct output to their native audio interfaces as possible. Current default WASAPI outputs will get resampled by foobar.
8
3rd Party Plugins - (fb2k) / Re: Dynamic Range plugin
Last post by Case -
Quote from: Porcus on
Did a few brief tests. On a couple of tracks, yours returns a dB more than foo_dynamic_range . No problem unless it is a symptom of something, I'm just assuming it is roundoff.
I read somewhere the default component resamples everything to 44.1 kHz. My component doesn't do that as that shouldn't be necessary and the PDF paper describing the measurement doesn't speak anything about resampling. Another difference is that the old component clips at least sample peaks to 1.0. I do not clip anything as I consider that incorrect. Though if people disagree I can modify the behavior.

There can be other weirdnesses going on too. The algorithm paper for example tells to split the audio for RMS scanning to blocks that are 3 seconds in length. Then it says that in their example 3 seconds of audio at 44.1 kHz equals 132480 samples. That's 180 samples too much. 44100 * 3 = 132300.
10
Support - (fb2k) / Re: Foobar seems to ignore LFE channel.
Last post by mzso -
Quote from: dexter86 on
I think there's something wrong LFE channel in that file. Check out my files that I use to test surround playback, they play fine in latest foobar.
I can see but can't hear the LFE with any of the your files either.

PS: I tried with xaudio2 output as well. No LFE that way either, but it is much louder on FB 2.1.5 instance I have for testing. (Sounds the same on my main instance, but that's 1.6.17)