Is my use case in Mopidy possible?

General
1

After two evenings of tingling, i finally got Mopidy to start but now i have to enable to icecast (oh no, snapcast), and im still not sure if mopidy can actually do what im looking for, so i thought ill ask it first here:

I have an Onkyo amplifier which is too old for Spotify or Youtube (or https), so I thought to connect it to a (private) Mopidy- webradio stream, so we could ask my amplifier to play a stream from my webserver.
I’m now a bit dissapointed that I have to set up a casting server in between - as there will be only one client - and I have a hard time making Mopidy even play youtube or Spotify tracks, but in principle, would this work?

2

I’m not 100% on your exact proposed setup you’ve described so to clarify; your amp won’t be able to connect to a snapcast stream so I am assuming there’s some machine (your webserver?) that is physically separate from your Mopidy server machine and that webserver machine is running snapclient, and then somehow feeding audio directly to your amp? If so, yes, that will work.

Alternatively, does your amp speak RTP? It should be possible to output an RTP stream from Mopidy directly or via Pulseaudio module-rtp-send. However I don’t think I’ve never actually tried this myself… I think some fancy Onkyo amps actually use GStreamer code!

In general, the common usecase is to run Mopidy on some (cheap, low power) machine that can be directly connected to the amp. Something like a Raspberry Pi is good for this role.

I do agree it is lacking we have no robust solution to serve http audio streams from Mopidy itself. It’s been on my list of things to sort out for literally years.

3

I already have a VPS, and installed Mopidy, and so yesterday also snapserver, on it, so its one “physical” machine…
And my Onkyo amp, a TX 8050, which sits at home, only accepts http:// audio streams, its a a bit legacy, and I don’t think it accepts RTP.
But now i understand the pi in Mopidy :slight_smile:
Am I aiming too high to get it to play Spotify? I already saw that Icecast wouldnt do it by itself…

4

I already saw that Icecast wouldnt do it by itself

Are you referring to the note in the docs about the shout2send bug in certain versions of Ubuntu?

Mopidy is running on a VPS somewhere else? So you are streaming audio over the internet from some remote VPS to your amp at home? You can do this. Will it work very well with Snapcast? Unsure, normally snapcast is used for streaming withing a local network. personally I would run Mopidy on a local machine but maybe you have a good reason for this setup, not judging.

5

I refered to the note and to the Icecast Faq. And the VPS is there anyway, so no need for more powered-on computers. But you dont seem to give me much hope?

6

I see it supports vorbis audio. If you configure Mopidy to output that perhaps your network reciever can play that directly. i.e. for Mopidy server running on a machine at address 1.2.3.4

[audio]
output = vorbisenc ! oggmux ! tcpserversink port=6666 host=1.2.3.4

And then your amp streams from tcp://1.2.3.4:6666 ? VLC can play such a stream.

7

nah it stays very silent on that stream :frowning:

8

Ok solved the libenc issue on ubuntu 20.04 using GitHub - raveberry/raveberry: A multi-user music server with a focus on participation

Streaming doesn’t work (there is only silence)

This is a known issue on Ubuntu 20.04 and Debian Bullseye. To fix it, downgrade libshout3:

 cd /tmp
 # for x86_64
 wget http://mirrors.kernel.org/ubuntu/pool/main/libs/libshout/libshout3_2.4.1-2build1_amd64.deb -O libshout.deb
 # for armhf (Raspberry Pi)
 wget http://raspbian.raspberrypi.org/raspbian/pool/main/libs/libshout/libshout3_2.4.1-2_armhf.deb -O libshout.deb
 sudo dpkg -i libshout.deb
 sudo apt-mark hold libshout3
9

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.