sonos port not working as upnp renderer from foobar2000

HI @Corry P 

Diagnostics ID whilst unsuccessfully using foobar2000 1576535344

Hi @groove_regulator 

Thanks for performing those tests and providing the diagnostics - I’ve had a look and I think I see what the problem is.

So, when the request is sent via BubbleUPnP, I can see the Port accept the prompt to start playing and it does so. With the foobar2000 attempt, however, the Port is immediately crashing and restarting it’s main software - it can recover from this in a mere second or two, but it obviously doesn’t play the requested media (you might even see the Port go offline for a moment in the Sonos app).

Due to another recent thread here on the community which strikes me as similar, in a way, I suspect a possible reason for this happening might be if the file foobar2000 is trying to play is extremely short - as in, a second or two long. Could you please confirm if this is the case or not? Thanks.

This is of course not expected or wanted behaviour, but if I can verify that the length of the track is the issue, I can at least say we’ve seen this behaviour before and are investigating.

I suspect that the person on this thread was also using UPnP to initiate playback, but the tiny audio file crashed my Amp via Music Library playback, so I don’t think the issue was do to the UPnP method.

Edit: from your first post, it doesn’t actually look like it being a short file is the answer, but I’ll wait for you to confirm.

Hi @Corry P thanks for getting back to me, I can confirm that I’ve tried numerous tracks of varying lengths and bitrates, all exhibit the same behaviour. Your feedback makes sense in that “something” happens at the Port end when trying to start the stream from Foobar, albeit it ends with a crash ( that probably explains why the DAC gives the “click.” )

Looking forward to a resolution, let me know if there’s anything else I can do to help.

Tony

Hi @groove_regulator 

Ah yes - the “click”. I asked, and Port has no mechanical parts, so the click must be coming from your amplifier - which is totally normal behaviour (especially since the Port is rebooting) and not a concern in any way.

Given that the issue is not related to the length of the file, however, and that UPnP playback is possible but not supported, I’m afraid the best advice I can give you at the moment is to not use foobar200 and use BubbleUPnP instead, if possible.

We did tighten some security recently, so it could be that BubbleUPnP is adhering to the increased security requirements more than foobar2000 is, but please be aware that this is just a guess and should not be taken as definite.

I hope you find a workaround that suits your usage needs.

thanks @Corry P I appreciate the feedback however it is disappointing that this doesn’t work. What I find confusing is that it happily works with the Roam. Would it be worth me doing a test where I stream to the Roam from Foobar2000 and send you the Diagnostics Id?

I have to admit I’m getting fairly disappointed with my S2 system, I’ve had it less than a year (i think) and it’s given me a number of significant issues ( this one here being the most critical → 

 ). I’d started using foobar2000 more often as a result of the S2 NAS Music Library issue, and now foobar2000 as you’ve seen is broken too.

The S1 platform just works better, I don’t recall any significant issue with S1 in the decade I’ve had it.

Hi @groove_regulator 

My colleague is currently looking into this issue, as although UPnP is unsupported, our products shouldn’t be crashing, so yes please - a diagnsotic of Roam playing successfully will be helpful as all data points will be useful, I think.

The Music Library indexing problem only seems to exist for some NAS drives, though I certainly appreciate how annoying all this must be for you. One option would be to have your library stored on a computer instead, though if you don’t already have a computer powered on 24/7 I can see why this wouldn’t be ideal. I personally have my S2 system linking to a Raspberry Pi with a Samba share and experience no issues, though I admit I don’t need to connect a S1 system to it too (though I do have an Android SMB app that needs SMBv1).

My colleague is currently trying to reproduce your issue with a macOS version of foobar2000 without success (as in, it works). Could you please provide us with the software version of foobar2000 that you’re running and, if possible, a sample file (via Dropbox or Google Drive or similar) of what you’re trying to play? He’s about to start trying on Windows now. Thanks.

Hi @groove_regulator 

In addition, it looks like a plugin is needed to get foobar2000 playing over UPnP - could you please provide details of which plugin you used? Thanks.

This does of course beg the question of whether or not you still encounter the issue if you use a different plugin?

HI @Corry P as always I appreciate your continued support, so Diagnostics ID with foobar2000 successfully sending the stream to the Roam → 1701381231

Foobar version v1.6.11

Foobar has the default foo_out_upnp component installed v1.3.2

I wouldn’t get too hung up on the file I’m trying to stream, I’ve not managed to get it to “break” using the Roam no matter what I send (I had it streaming to the Roam from foobar2000 for about 5 hours on the weekend with no issues).

Let me know if I can do anything else.

Tony

HI @Corry P just updated foobar2000 to v1.6.16 along with upnp component to 1.4

Unfortunately the issue persists

Hi @groove_regulator 

Thanks for all those details - I’ve passed them to a colleague, and I will get back to you once he’s done some testing.