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.
Topic: Foobar as a renderer playback unsupported format or corrupted file. (Read 407 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Foobar as a renderer playback unsupported format or corrupted file.

Hi,

I'm working on a UPnP plugin for Musicbee that can send streams to Foobar. I'm aware this could be a problem with foobar's UPnP plugin which hasn't been updated in a long time but I'm not getting any errors in it's log so I'm left with the playback error to troubleshoot.

Native - the stream is created using the BASS library (un4seen) from the source file.
encoded - the stream is created and encoded to flac using the BASS library and Flac.exe. In this example all the specs are kept the same as the source. Channel count, sample rate etc....

I've got a strange issue I can't figure out.
A native 5.1 flac stream works fine in foobar with the upnp plugin.
A native 2.0 flac works fine.
An encoded 5.1 flac produces the playback error.
An encoded 2.0 flac plays fine.

The same streams all work fine when streaming to BubbleUPnP, native or encoded.

I've sent a crash report, I was just hoping someone could identify why the encoded 5.1 flac is producing a playback error.

Thanks.

edit: just to clarify. I can get the exact same 5.1 stream which fails and set the output channels to 2.0 and it will play.