Skip to main content
Recent Posts
General - (fb2k) / Re: If you're sick of unnecessary forced updates...
Last post by Peter -
Several times now I've been in the middle of doing other things and I attempt to pause or switch tracks (through the executable /pause switch (bound to a hotkey (linux...))) and instead I get the update warning, which means I have to drop everything I'm doing to deal with foobar2000 stuff.

Maybe it's better to disable update check if foobar2000 instance just sends a message to the main foobar2000?
Valid point, I'll get that changed ASAP, it must indeed be annoying as hell. Thanks for pointing it out.
Support - (fb2k) / Re: Pioneer u-05 DSD issue
Last post by Case -
Architecture in foobar2000 hasn't changed. DSD is a hack and all attempts to play it in foobar2000 other than converting it to sane PCM are hacks. Everything in foobar2000 only deals with PCM samples and trying to pass DSD through the pipeline requires bypassing the player entirely. Custom input, bypassing DSPs, custom output. That's not what foobar2000 is about.
Support - (fb2k) / Re: Question mark for duration on alot of AAC files
Last post by Case -
You need to reload info for files after you switch to FFmpeg decoder. It will otherwise show cached info from the time length wasn't known. Also you don't need to have both upper case and lower case aac in the extension list. The match isn't case sensitive.
Support - (fb2k) / Re: Pioneer u-05 DSD issue
Last post by dejanm -
It seems that Pioneer U-05 driver requires older F2K plug-ins, where the definition of ASIO support could be explicitely established. With the new versions of F2K that is not possible any more and the whole architecture seems to be different now.

Is it possible that the new version of F2K implements better support for DSD reproduction ?
Opus / Opus frequency notching at 15.5 kHz
Last post by GeezerHz -
Using Opus 1.2.1 and 1.3beta I notice that there is a notch between about 15.5 kHz and about 16.5 kHz that is attenuated by up to -3.8dB from the original source. This effect remains until using a bitrate >= 144 kbps. I can't say it's audible to me, but my hearing sucks above 16 kHz. It seems like cutting the volume of 15.5 kHz frequencies in half would be fairly audible to sensitive ears.

This graph was made from Adobe Audition CS6 frequency analysis of the track "Flora's Secret" by Enya. The orange line is the average volume level at each frequency of the source WAV and the blue line is a 96 kbps Opus decoded by opusdec 1.2.1. See the notch at 15.5 kHz. You can also see frequencies above 17 kHz appear boosted over the original. It's as if the line of the original between 15.5 kHz and 19.5 kHz was tilted to the left.

Is this effect by design, or at least a known and accepted side effect of "folding" bands?
General - (fb2k) / Re: If you're sick of unnecessary forced updates...
Last post by kode54 -
They already explained it. They're using a component that someone forcibly designated for 1.4 or newer. I know two other developers who release components with such settings. One of them does it for unknown reasons, and the other, @mudlord , has released a single component update that requires new SDK features to properly reconfigure DSPs from Default UI element inserts in real time.

I also made some changes to some of my inputs, to support the new priority control, and thus also removed previous code which would detect redundant inputs of the same format and disable certain inputs automatically if multiple components were installed. Now, if you lack the 1.4 update, the redundant components will just fight each other depending on the randomized order on program startup.
3rd Party Plugins - (fb2k) / Re: foo_volsync 0.11
Last post by kode54 -
What is the purpose of low latency, "bit perfect" output if you're going to ask the sound hardware to munge the bits anyway by lowering the volume? May as well use DirectSound, in that case.
SimplePortal 1.0.0 RC1 © 2008-2018