Note to self: configure spare PC with enough memory, install and configure foobar2000 and Bubble UPnP, attach it to the local network, and start testing...
Using foobar2000 as renderer on the remote PC seems to play more reliable now, so the amount of memory does seem to make a difference.
But I still get the same error messages popping up somewhere at the end of every playing track though.
Something like "Decoding failure at 5:46.093 (Socket not open)"
The numbers are the playing time, the socket (port number) it says is closed, I am pretty sure is open. (it's the same port that is set and used for playing the audio)
So that's a bit weird.
Anyway, play will continue, and for the brief time I have been testing it on this new setup, I haven't noticed any skipping to a new song in the middle of a current song playing, so that's some improvement for sure.
Next, in trying if I could get rid of these error messages (and perhaps also solve the problems I have with trying to have MusicBee playing to my Squeezeboxes) I am trying to use BubbleUPnP as some 'mediator':
I installed it on the remote PC in my local network that has foobar2000 installed as a UPnP renderer.
For as far as I am able to tell, the installation seemed to have gone well.
I can reach it's configuration web-page using my main PC. (which has MusicBee installed)
I don't see anything out-of-order there.
But, whatever I try, in MusicBee's Preferences > Player > Output, there is no entry available that refers to BubbleUPnP.
And I am guessing it should?
Either some general 'BubbleUPnP player', or a specific 'Open home player' I have configured in BubbleUPnP should probably show?
It's all still a bit confusing to me.
Looking at my Windows network, I do see some entries for BubbleUPnP, but they are under 'Other Devices', and not under 'Media Devices'.
Could that be (part of) the problem?