On Wed, Jul 10, 2013 at 11:25 PM, Tim RadioClash <<br />airtime-support@lists.sourcefabric.org> wrote:
> The fix doesn't work...in fact it seems to have killed my Airtime :-(
That comment was intended primarily for the Airtime developers . If you are not familiar with the GNU diff universal format for creating a patch, you could have added extra characters that shouldn't be there and would consequently prevent liquidsoap from starting.
The end result of the change to those lines of the ls_script.liq script should look like this:
def create_source() l = request.equeue(id="s#{!source_id}", length=0.5)
l = audio_to_stereo(id="queue_src", l) l = cue_cut(l) l = amplify(1., override="replay_gain", l)
After making the change, you then need to restart the airtime-liquidsoap service:
sudo service airtime-liquidsoap restart
This will cause a brief outage to all your output streams and disconnect any inputs so plan accordingly.
Seems that this fix is working. My liquidsoap is working fine after edit ls_script.liq, but I didn't test yet with mono files (I replaced all files to stereo ones)
I've made the change to /usr/lib/airtime/pypo/bin/liquidsoap_scripts/ls_script.liq and it seems OK this time, will try later with a mono file.
Confusing thing is I have 2 ls_script.liq's - the other is at /var/lib/airtime/tmp/python_apps/pypo/liquidsoap_scripts/ls_script.liq. A backup? I edited both last time...
Post edited by Tim RadioClash at 2013-07-18 17:08:00
Hmm - I had an odd thing, and this was the only recent backend change I've done (not even apt-get update, cos it was up-to-date)?
Just found the stream was about 5-7 minutes behind what it should be, did a reboot and it's now 'in sync' with the schedule...could this change affect that?
Airtime-check all looks OK, before and after - I have silan taking up loads of CPU (again - I thought that was fixed in this version?) but apart from that looks OK and is streaming OK.