Airtime: 2.4.1, OS: Ubuntu Server 12.04.3 LTS
While listening to a show and using drag & drop to prepare new song content for another, playout cuts out, or rather, the stream gets 'jumbled up' briefly. Playout recovers when drag & drop actions cease. So there seems to be some relation between the playout engine's encoder and the activities performed on the web server. Are there any setup recommendations for putting the web server on a separate machine? Or is this perhaps a cache phenomena?
Thomas Hackett said:Airtime: 2.4.1, OS: Ubuntu Server 12.04.3 LTS
While listening to a show and using drag & drop to prepare new song content for another, playout cuts out, or rather, the stream gets 'jumbled up' briefly. Playout recovers when drag & drop actions cease. So there seems to be some relation between the playout engine's encoder and the activities performed on the web server. Are there any setup recommendations for putting the web server on a separate machine? Or is this perhaps a cache phenomena?
Naomi said:Are you listening to the show via the "listen" button in the web UI? This is probably due to the main javascript thread just being a bit busy doing stuff in the UI, so the widget may not be buffering enough. This doesn't mean that your actual playout is cutting out though. Best way to monitor that is to listen to it via audio out or a separate browser that is idle.
Naomi
No, in fact the listen button doesn't seem to work for me at all, but that doesn't worry me. The PlayOut problems occur when you're listening to the station as a regular listener.
hoerich said:
Thomas Hackett said:Airtime: 2.4.1, OS: Ubuntu Server 12.04.3 LTS
While listening to a show and using drag & drop to prepare new song content for another, playout cuts out, or rather, the stream gets 'jumbled up' briefly. Playout recovers when drag & drop actions cease. So there seems to be some relation between the playout engine's encoder and the activities performed on the web server. Are there any setup recommendations for putting the web server on a separate machine? Or is this perhaps a cache phenomena?
I can confirm this issue for Ubuntu 12.04 x64.
Everytime the Library is "Processing..." the output drops-out for 1-2 seconds.
We are an FM-station and use ALSA-output and no icecast-output in Airtime.
I think Naomi is right with the cache.
According to the manual (bottom of this page) I installed php-apc instead of php5-xcache,
but my system tells me a dubious conflict of apc & xcache, although xcache is not installed anymore.
delusion@rastamann:~$ dpkg -s php-apc
Package: php-apc
Status: install ok installed
Priority: optional
Section: php
Installed-Size: 254
Maintainer: Pietro Monteiro <pietro@riseup.net>
Architecture: amd64
Version: 3.1.13-1~precise+1
Depends: libc6 (>= 2.14), phpapi-20100525
Suggests: php5-gd
Conflicts: php5-xcache
Conffiles:
/etc/php5/mods-available/apc.ini 6f9733de9436736fbbe6f967f9224e4f
Description: APC (Alternative PHP Cache) module for PHP 5
The Alternative PHP Cache, also known as APC, is a free, open, and robust
framework for caching and optimizing PHP intermediate code. APC is a fast
solution for caching PHP code locally, it is not distributed like MemcacheD,
but they can be used together for optimal caching.
Homepage: http://pecl.php.net/package/APC
delusion@rastamann:~$ dpkg -s php5-xcache
Package is not installed...
I try to reproduce this on my test-station and report.
Or hopefully some other user has a hint for us
Cliff Wang said:Can you share the liquidsoap logs? Just the part when that problem happens.
I cant reproduce it locally, maybe I miss some essential steps.
Cliff Wang said:Can you share the liquidsoap logs? Just the part when that problem happens.
I cant reproduce it locally, maybe I miss some essential steps.
Cliff Wang said:How about the cpu/mem usage? And are you using hardware output, too?
Cliff Wang said:Please try to restart liquidsoap
sudo service airtime-liquidsoap restartto see if you still have the problem after.
hoerich said:check http://sourcefabric.booktype.pro/airtime-24-for-broadcasters/the-airtime-log-command/
do sudo airtime-logs --tail to see all new logs
or sudo airtime-logs --dump to dump all logs in a tarball
more useful will be --tail while error occuring and paste it here.
I'm on holiday, so I don't know if I want to dig this week in issues like this.
hoerich said:check http://sourcefabric.booktype.pro/airtime-24-for-broadcasters/the-airtime-log-command/
do sudo airtime-logs --tail to see all new logs
or sudo airtime-logs --dump to dump all logs in a tarball
more useful will be --tail while error occuring and paste it here.
I'm on holiday, so I don't know if I want to dig this week in issues like this.
Cliff Wang said:Seems you're drag and drop a webstream, right?
Cliff Wang said:OK, it happens when I have webstream playing, then modify the schedule on the fly, right?
I think it's because Webstream reconnection will happen when you update Airtime Scheduler. And it will be fine if the regular tracks are playing.
Thomas Hackett said:
Cliff Wang said:OK, it happens when I have webstream playing, then modify the schedule on the fly, right?
I think it's because Webstream reconnection will happen when you update Airtime Scheduler. And it will be fine if the regular tracks are playing.
hoerich said:
Cliff Wang said:OK, it happens when I have webstream playing, then modify the schedule on the fly, right?
I think it's because Webstream reconnection will happen when you update Airtime Scheduler. And it will be fine if the regular tracks are playing.
that's right for me too.
Playout is interrupted only if a webstream is playing. not with scheduled library-tracks.
But for me this is not limited to scheduling on "Now-Playing"-page.
This also happens when working in library, when adding tracks to playlists.
thx cliff for investigating.
Voisses Tech said:That's like cutting off your nose to fit your face
Bigger buffer resulting in slower transitions and more latency ,this is quite suitable if you are just restreaming one particular webstream.
Lets do a face plastic surgery,test the those parameters in all case and see if its suitable for production application.
I will retry it now with the Input Modification I did after next week and tell you all the consequences of that
Hey guys, I've fixed this problem todaythis should fix the problems with the web interface activity.
Thomas Hackett said:
Naomi said:Hey guys, I've fixed this problem today
this should fix the problems with the web interface activity.
checking
root@ubuntu:/var/lib/airtime/tmp/python_apps/pypo (hope that's the right path, I wonder why it's in "tmp" )
Naomi said:Hey, you must modify the file that's in "bin_dir" in /etc/airtime/pypo.cfg
the default place is /usr/lib/airtime/pypo
Naomi said:Hey, you must modify the file that's in "bin_dir" in /etc/airtime/pypo.cfg
the default place is /usr/lib/airtime/pypo
Naomi said:Really? It shouldn't affect the web interface at all this change, but I'll run a check. Maybe it's just another bug...
do you get anything appearing in your javascript console?
Naomi said:Did you modify anything else when you were adding this line to the script?
Maybe see if there is some message in /var/log/airtime/zendphp.log when you are having these errors on the now playing page.
Naomi said:hmm I had no problem adding content when I was testing this, but maybe I missed something. Were you adding playlists/files/webstreams?
It looks like you're new here. If you want to get involved, click one of these buttons!