HTTP streaming

[kraigo]

High on my remaining wish list for things I would like my Raspberry Pi with Rune to do is stream the output via HTTP. This handy page shows me what to do to mpd.conf: https://wiki.archlinux.org/index.php/Mu ... and_Tricks.

>>
audio_output {
type "httpd"
name "My HTTP Stream"
encoder "vorbis" # optional, vorbis or lame
port "8000"
# quality "5.0" # do not define if bitrate is defined
bitrate "128" # do not define if quality is defined
format "44100:16:1"
}
<<

I've changed the format to "44100:16:2" for stereo. I'm not sure if any encoders are included in Rune. Vorbis is reputed to be the most universally supported but to be high CPU usage. When I use "top" it appears that my CPU usage is pretty low so perhaps the Pi can handle it.

Has anyone used HTTP streaming with Rune?

What encoders are included in Rune?

KO

P.S. at least one person in the world is doing HTTP streaming with MPD on a Raspberry Pi: http://www.raspberrypi.org/forums/viewt ... 0&p=350142. Given that my CPU usage with Rune and a HiFiBerry is quite low, I'm curious if this will work. I'll be trying it in the morning. I'm too tired to trouble shoot tonight.

[kraigo]

Probably just better to look into Airplay instead, huh? It just seemed like a lot of overhead if HTTP streaming were built in, but

1) I'm not sure if Rune will play to two outputs at once (HiFiBerry and HTTP).

2) The re-sampling/re-encoding would degrade the signal. I'm not sure whether Airplay forces that or not, but HTTP certainly would. Most of my library is encoded in variable bitrate, so the encoder would/will have its work cut out for it.

3) Airplay is an official feature of Rune and I'm not subverting, fun as that may be.

I'm interested in hearing about anyone's experiences with this.

KO