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
Support - (fb2k) / Re: 1.6.7 beta 8 => Exclusive=> Unrecoverable playback error: Unsupported format ! !
Last post by Fabcore -
Me, I prefer an error message.  Then I have the option to add the DSP resampler plugin I choose, setup as I choose, to resample the rates not supported by my own device.
This.
If the bit perfect is the objetive, then do not add anything to the path, but, when the sr diferences comes, there is always a dedicated Resampler on the DSP, and when the sr source is the same as the sr hardware, theres not loss in the path in that case.
2
Support - (fb2k) / Re: 1.6.7 beta 8 => Exclusive=> Unrecoverable playback error: Unsupported format ! !
Last post by sveakul -
With the old WASAPI exclusive mode component, the expected behavior was that exclusive mode would output whatever format it is fed, and it would force the output device into that format, only returning an error if that format isn't supported by the output device. For instance, when you play a 44.1kHz file the output device uses that format, then if the next song is 96kHz it is switched to that format.

Is this no longer the case with the built-in exlcusive mode?

I usually use a resampler anyway, but I did enjoy having a mode that would just output the file as is and force the output device to adjust for each track.
I think Peter intends the built-in exclusive to function as you describe, which after all is what the definition of wasapi exclusive is, but from his last post it sounded like he was considering the possibility of adding functionality that in case of the sample rate not being device supported would automatically resample to a supported rate, instead of returning an error message.  As a matter of fact, this is indeed what BASS library-based players do that incorporate bass.dll/basswasapi.dll for exclusive mode--fallback to a supported rate if the actual is rejected by the device.

Me, I prefer an error message.  Then I have the option to add the DSP resampler plugin I choose, setup as I choose, to resample the rates not supported by my own device.

5
Support - (fb2k) / Re: 1.6.7 beta 8 => Exclusive=> Unrecoverable playback error: Unsupported format ! !
Last post by Cannonaire -
Note that exclusive output - like all output plugins of the sort - doesn't perform any resampling of its own; if your device isn't agreeing with the sample rate of your audio files, errors happen. This is currently the intended behavior.

I'll think of some solution for this for post-1.6.7, perhaps negotiate some optimal rate to resample to.
With the old WASAPI exclusive mode component, the expected behavior was that exclusive mode would output whatever format it is fed, and it would force the output device into that format, only returning an error if that format isn't supported by the output device. For instance, when you play a 44.1kHz file the output device uses that format, then if the next song is 96kHz it is switched to that format.

Is this no longer the case with the built-in exlcusive mode?

I usually use a resampler anyway, but I did enjoy having a mode that would just output the file as is and force the output device to adjust for each track.
6
Support - (fb2k) / Re: 1.6.7 beta 8 => Exclusive=> Unrecoverable playback error: Unsupported format ! !
Last post by A_Man_Eating_Duck -
Many Thanks Peter.

foobar2000 1.6.7 beta 12

RAL-DSDHA5, DENON DA-310USB
No Problem. It will be played good
----------
FOSTEX HP-A4, FOSTEX HP-A4BL
The noise is still terrible.
Thanks for confirming.
As for FOSTEX, looks like I'll have to resurrect the advanced preferences option, to set the hardware buffer to 50ms (per BeepExclusive results).

I have a Fostex HP-A8C and when I use exclusive mode with B12 the audio is playing very slowed down. I have tested 44.1/16 and 96/24 and they both behave the same with the music slowed down. I have tested with smooth seeking enabled and disabled without any change.
7
3rd Party Plugins - (fb2k) / Re: Georgia-ReBORN - A Clean foobar2000 Theme
Last post by dwmartin0906 -
That did it.  Thank you very much.  I do have another question.  I have poor eye sight so I am trying to increase the tooltip font size, particularly in the timeline.  I increased font_size_px in foo_spider_monky_panel.js and g_tooltip.SetFont scaleForDisplay in georgia-main.  It works the first time, but then reverts to the smaller size.  Any ideas?
8
3rd Party Plugins - (fb2k) / Re: Columns UI
Last post by josemescud -
I use Columns UI and I have the following problem:
As seen in the image when painting the date to the right of the% Album% they are painted ...

The grouping contains the following script:

$puts(calbum,$rgb(200,200,200))
$puts(cdate,$rgb(180,180,180))
$get(calbum)$upper($get(%album%))
$rgb(60,60,60)
'  '$repeat('—',85)
$tab(-1)$get(cdate)%date%' '

9
Support - (fb2k) / Re: 1.6.7 beta 8 => Exclusive=> Unrecoverable playback error: Unsupported format ! !
Last post by eagleray -
Note that exclusive output - like all output plugins of the sort - doesn't perform any resampling of its own; if your device isn't agreeing with the sample rate of your audio files, errors happen. This is currently the intended behavior.

I'll think of some solution for this for post-1.6.7, perhaps negotiate some optimal rate to resample to.
Thanks Peter for your work on getting this right but I would encourage you NOT to engage some auto-resampling routine to Wasapi exclusive.  As you described,  passing the file rate straight through to the device is intended behavior.  Users with devices that are not compatible with the native sample rates of their files already have several options to handle this via Foobar DSP resampling plugins.  IMO, why add an extra layer of handling to something that is proving tricky enough as-is to fix.

I agree. Beta 12 making music here. Apparently the default buffer size in exclusive is small enough for Xmos 208 USB devices. It took me a long time to figure out the 25 ms default in the component was just a bit too large.
10
3rd Party Plugins - (fb2k) / Re: ESLyric - an alternative lyric show component
Last post by medp7060 -
I wonder if ESLyric can save the lyrics donwloaded from KGmusic in .krc format instead of the advanced/enhanced .lrc format. This is because this .lrc format contains timestamps that will be displayed by other players which use normal .lrc. I know ESLrics decodes .krc lyrics through "krc_parser.js". Anyone knows where the un-decoded .krc is stored?
SimplePortal 1.0.0 RC1 © 2008-2021