Serving the cardiophile community since 2016.
You are not logged in.
Chrome v58.0.3029.110
Offline
Well that is the latest version. Chrome might not be my favorite but they're good at keeping their users updated. Who were you trying to listen to and when?
Last edited by ChiraBeats (2017-05-24 20:16:24)
Online
heartoflea and I belive it was either yesterday or the day before.
Offline
Thought it might have been. Lea triggered a glitch where it showed that she was streaming when she wasn't. The reason you couldn't hear anything was because there was nothing to hear anymore.
I could have sworn I had that fixed like 5 times now but it looks like it's time to go code-diving again. In the mean time I'll see if I can't add some sort of check to the listening page that will automatically detect this problem. Should serve as a band-aid until I can figure out where the real problem is.
Online
I am trying this (not least because my youtube channel got a "community strike" and streaming is blocked until some time in September). And as usual, I have a few feature requests
1. Some sort of title/message accompanying the stream. Setting it *before* starting the stream is enough.
2. Information about the number of listeners. And when it started.
3. Webchat local to the stream, a la youtube live chat.
4. Low level info about the streaming endpoint. Web codec sucks (apparently) wrt the compression quality. I would use ffmpeg but I need to know what to stream and where. Is it simply an mp3 stream over tcp? Icecast format?
5. While I was typing this, streaming spontaneously stopped! So it becomes a bug report too
Thanks!
Online
1. I think that'd be possible. Icecast already supports slipping in media/title information. Only fiddly bit would be fishing it back out when listening to streams. But yeah, should be possible.
2. Already added but it's super sketchy right now. Something's in the works that should clear that up real soon.
3. That'd be nice. Could be pretty easily fit in with some of the bigger/longer-term projects I have on the to-do list, too.
4. Instructions are at the bottom of the streaming page. tl;dr is 128kbps, 44100KHz, mp3 sent to http://heart2h.com:8000. Username and mount point are your case-sensitive username, password is your password.
5. I'll look into it and see what I can see!
Online
If you only allow to set the title before starting the stream, it can be independent of the stream itself. Normal post/async request, and then include as a part of the listener's page.
4: sorry! I always stop reading half way
Online
Turns out, I did read the page about streaming but technical data there is incomplete. In case anybody needs this, here is some command line that seems to work pretty well for me on Ubuntu:
#!/bin/sh
ffmpeg -f pulse -i default \
-acodec libmp3lame -ab 64k -ac 1 \
-content_type audio/mpeg -f mp3 \
icecast://<userid>:<password>@heart2h.com:8000/<userid>
Change `-ac` to 2 for stereo, `-ab` is the stream bitrate.
Online
[ Generated in 0.014 seconds, 14 queries executed - Memory usage: 668.51 KiB (Peak: 704.2 KiB) ]
I could have sworn I left something here.