<div dir="ltr">This is turning a bit into a hate-thread against Airtime.<div style>Personally, I am not much of a hater (although sometimes I make exceptions, depending on how my day is), but I will say that Airtime is a pain-to-maintain on your server.</div>
<div style><br></div><div style>It's pretty bloated as well; correct me if I'm wrong (this dates back to when I tried it with version 1.5 and 1.6 and 2.0 was in the works)</div><div style>- Zend PHP framework (bundledinto the app) + plenty of JavaScript thrown in<br>
</div><div style>- RabittMQ for queue-ing messages to liquidsoap</div><div style>- liquidsoap pushing to icecast</div><div style>- icecast</div><div style>- Python glue-code that had UTF-8 problems with certain non-ASCII filenames (mostly because of Python 2.6-7 which is not yet UTF-8 compliant)</div>
<div style>- monit to keep the whole thing from cracking</div><div style>- PostgreSQL, which is less friendly than</div><div style><br></div><div style>all of this to add a simple (and (back then) not very useful) frontend to make a playlist; and when you try to upgrade, a lot of the problems you've hacked into Airtime to get it working, get reset, so you have to start re-hacking it; that is, if it still works after upgrading it;</div>
<div style><div>Other problems that I've had with Airtime were:</div><div>- empty streams; just silence, because...... RabbitMQ I guess</div><div>- the UI said the radio was on-air, but everything in the back was just sitting</div>
<div style>- sync-ing into the DB always failed when I had non-ASCII filenames (bad Python scripting); I had impartial files in Airtime because of that;</div></div><div style>- if you had a podcast of 1h and 10-30 seconds, you could only set it to the 1h + 1minute, or cut it 1h sharp; kind of... well, I didn't like it, personally;</div>
<div style><br></div><div style>I think (and it's a bit evil of me to say this without having contributed to Airtime) that it should have only consisted of any of these (or similar) combinations:</div><div style>- (standard) PHP + icecast</div>
<div style>- a simple frontend in whatever(for liquidsoap) + liquidsoap + icecast</div><div style>- icecast + frontend written for icecast (i saw someone work on this, where )</div><div style>- Python (frontend + queue-ing to icecast) + icecast</div>
<div style><br></div><div style>Queue-ing is a bit redundant with IceCast, if you try to use one server as master, and others as slaves or relays.<br></div><div style>You'll still need a load balancer for this, but that's another topic.</div>
<div><br></div><div style>In the end, I found that using just liquidsoap + icecast (and shoutcast because I wanted to listing in the Shoutcast Directory) was more than sufficient for my needs.</div><div style>And after that a simple frontend with HTML5 was sufficient to be the player.</div>
<div><br></div><div style>I personally still think that if you want to do radio-streaming on the net, you have to start working from the last node that sends out every byte on the web (icecast and shoutcast in this case) and work backwards from there.</div>
<div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jun 17, 2013 at 1:14 PM, macbroadcast <span dir="ltr"><<a href="mailto:marc@let.de" target="_blank">marc@let.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Am 17.06.2013 11:12, schrieb Daniel James:<br>
> Airtime<br>
<br>
<br>
After several weeks of trying and calling my provider and talked to your<br>
support i gave up on<br>
airtime, because it does not work on a virtualized system, it seems the<br>
installtion script has<br>
dependencies.<br>
<br>
<a href="http://forum.sourcefabric.org/discussion/15323/airtime-install-on-ubuntu-error-in-installation-script" target="_blank">http://forum.sourcefabric.org/discussion/15323/airtime-install-on-ubuntu-error-in-installation-script</a><br>
<br>
<br>
_______________________________________________<br>
Icecast-dev mailing list<br>
<a href="mailto:Icecast-dev@xiph.org">Icecast-dev@xiph.org</a><br>
<a href="http://lists.xiph.org/mailman/listinfo/icecast-dev" target="_blank">http://lists.xiph.org/mailman/listinfo/icecast-dev</a><br>
</blockquote></div><br></div>