Hoping I can get some of the Sourcefabric folks on here.
We run an WGOT-LP 94.7FM in Gainesville, FL and have been using campcaster 1.2 since we started broadcasting back in Jan '08. Campcaster has served us well but we need to upgrade to Airtime as CC is showing its age. Once we have Airtime 1.6 running on a new system we're prepping, we're going to switch it out with the current broadcast computer.
We have a unique setup in that we don't yet have a proper studio so everything is done remotely (which is why campcaster has been ideal for us). All our DJs record their shows and then we use dropbox to synchronize uploads; the schedulers (we have 2-4 of them) have access to campcaster and they then set up the schedule according to our programming.
I have a few questions:
1. Getting audio out of the soundcard.
Audio is working fine with other apps but I can't seem to be getting audio out of Airtime. According to
Is this really the only way to handle it? We normally don't have a user logged into the PC as it is sitting in a shack at the tower with the rest of the broadcast equipment.
Regardless, even if I try to run that command, I get 404 error from the server. Looking at the /var/log/icecast2/error.log, I see that it's actively checking for listeners:
[2011-02-20 13:58:17] INFO connection/_handle_source_request Source logging in at mountpoint "/airtime.mp3"
[2011-02-20 13:58:17] INFO source/get_next_buffer End of Stream /airtime.mp3
[2011-02-20 13:58:17] INFO source/source_main listener count on /airtime.mp3 now 0
[2011-02-20 13:58:17] INFO source/source_shutdown Source "/airtime.mp3" exiting
However, when I try to connect, it throws:
[2011-02-20 17:54:50] INFO fserve/fserve_client_create checking for file /airtime.mp3 (/usr/share/icecast2/web/airtime.mp3)
[2011-02-20 17:54:50] WARN fserve/fserve_client_create req for file "/usr/share/icecast2/web/airtime.mp3" No such file or directory
I'm pretty sure I followed all the steps and also rebooted the system but this was a system on which I'd been trying to get Campcaster 1.4 running so perhaps something in the install didn't get correctly set. Any input would be greatly appreciated.
2. This is not so important for us as we use dropbox along with the import script to handle uploads however, I can't seem to upload files over the web interface. The apache2 error logs report the following continuously as the web interface tries to redo the upload over and over again:
[Sun Feb 20 15:22:15 2011] [error] [client 10.0.1.5] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 86499732 bytes) in Unknown on line 0, referer: http://tower2.local/Plupload/plupload
[Sun Feb 20 15:22:16 2011] [notice] child pid 24053 exit signal Segmentation fault (11)
BTW, the size limits in php.ini are set to 150MB and the file I'm trying to upload is 82MB.
3. Can't right-click from Safari (at least on Mac).
I can't seem to right-click to add content to a show and I know at least 1 of our schedulers will be using a Mac. This seems to be working from Firefox so it won't be a problem to get them switched however, just thought you should know in case other people bring it up.
Thank you for any feedback on this. We really appreciate all the hard work.
The default setting is that Airtime outputs to an Icecast server on the
same machine (localhost). For an FM station where the Airtime machine is
at the tower, I guess you want to output direct to a soundcard, and then
on to your stereo encoder etc. Liquidsoap has an option output.alsa that
should do what you need; this will be documented shortly.
> [2011-02-20 17:54:50] WARN fserve/fserve_client_create req for file
> "/usr/share/icecast2/web/airtime.mp3" No such file or directory
> [Sun Feb 20 15:22:15 2011] [error] [client 10.0.1.5] PHP Fatal error:
> Allowed memory size of 134217728 bytes exhausted (tried to allocate
> 86499732 bytes) in Unknown on line 0, referer:
> http://tower2.local/Plupload/plupload
> [Sun Feb 20 15:22:16 2011] [notice] child pid 24053 exit signal
> Segmentation fault (11)
>
> BTW, the size limits in php.ini are set to 150MB and the file I'm trying
> to upload is 82MB.
134217728 bytes is 128MB rather than 150MB, so perhaps your intended PHP
settings aren't being applied. Even so, this should work - are you
uploading multiple files at once perhaps?
> I can't seem to right-click to add content to a show and I know at least
> 1 of our schedulers will be using a Mac.
Does the Mac have a two-button mouse, or are you doing a click and hold,
to emulate a right button?
On Feb 21, 2011, at 12:04 PM, Daniel James wrote:
> The default setting is that Airtime outputs to an Icecast server on the
> same machine (localhost). For an FM station where the Airtime machine is
> at the tower, I guess you want to output direct to a soundcard, and then
> on to your stereo encoder etc. Liquidsoap has an option output.alsa that
> should do what you need; this will be documented shortly.
I just saw some other comments about problems on 32-bit systems; could this be related to that?
> 134217728 bytes is 128MB rather than 150MB, so perhaps your intended PHP
> settings aren't being applied. Even so, this should work - are you
> uploading multiple files at once perhaps?
I originally had it to 100MB as per the wiki (and our original campcaster install). I've tried uploading files from ~28MB to ~80MB and they all have the same problem. I've restarted the apache server several times for various other reasons (removing the default site-enabled, etc.) and have also rebooted the computer a couple of times since. Is there any other reason you could think the apache2/php.ini settings would not be getting applie?
> Does the Mac have a two-button mouse, or are you doing a click and hold,
> to emulate a right button?
I'm trying with control-click. It works fine on Firefox and also worked fine on campcaster with both firefox and safari, if that helps.
> > [Sun Feb 20 15:22:15 2011] [error] [client 10.0.1.5] PHP Fatal error:
> > Allowed memory size of 134217728 bytes exhausted (tried to allocate
> > 86499732 bytes) in Unknown on line 0, referer:
> > http://tower2.local/Plupload/plupload
> > [Sun Feb 20 15:22:16 2011] [notice] child pid 24053 exit signal
> > Segmentation fault (11)
> >
> > BTW, the size limits in php.ini are set to 150MB and the file I'm trying
> > to upload is 82MB.
Hi Daniel,
I stand corrected: I thought I'd seen the 27MB file fail but it didn't. At least not today when I retried it:
So now I'm thinking this has to do more with the memory_limit php value which, what do you know, it's set to... 128M.
Ugh. So, what's odd is that the current broadcast computer has this value set to 8M (!!) so obviously we didn't mess with that before. Any reason why you think this is suddenly a problem?
I'll play with increasing this value a bit more to support our 1-hour programs.
> [Sun Feb 20 15:22:15 2011] [error] [client 10.0.1.5] PHP Fatal error:
> Allowed memory size of 134217728 bytes exhausted (tried to allocate
> 86499732 bytes) in Unknown on line 0, referer:
> http://tower2.local/Plupload/plupload
So if I actually took the time to read the above error log this actually doesn't seem to make sense. It's reporting the correct amount of memory given to php as 128M but it's stating that it's not able to allocate the amount equivalent to the file size (82.5MB).
As if that wasn't enough excitement, the problem is on line 0 of Unknown. Will the universe swallow itself next? One can only hope not.
I tried up to 200M so I'll try this next. However, just saw another post stating the minimum system requirements as 512MB ram. Should this be higher then?
Our system currently has 512MB but I'm planning on upgrading that once we've confirmed everything is working well with the hardware.
I was getting an error when trying to run the command with the sine() argument. I saw somewhere that there was a problem with liquidsoap on 32-bit systems and that we should compile it from source. I also noticed there was a 1.6.1 release.
Thus, I uninstalled 1.6.0, installed 1.6.1 and then grabbed liquidsoap from svn as instructed on another thread. For some reason, my users were no longer on the audio group so I readded them and now I get the sine wave.
I then scheduled a show and I'm able to listen to it via mplayer / vlc but I was expecting it to be sending it directly to the soundcard since alsa support was built in. I need to run so I can't look but I imagine there's discussion on how to do this in one of the threads but, if not, could you point me to it? I'll take a look tomorrow otherwise.
One other thing: how should I manage updates with a separate build of liquidsoap? And should I switch to git for updating airtime?
I'm going to be setting this up as a month-trial for our schedulers to get familiar with it. Plus I need to configure auto-import of files from dropbox, etc.
I've got both local audio from the soundcard and the icecast stream working. A few observations:
I. I tried following the instructions to run the server on a different port (1000) but could never get audio so I must be missing something. I modified:
I re-installed airtime, restarted the PC.. nothing. We're assigned port 1000 externally so we don't really have the option to run on 80.
II. Moving location of the storage archive.
I would prefer to keep the file stor on /opt but it's currently set up to stay in my home directory. I looked at application/configs/conf.php and see this:
'baseFilesDir' => __DIR__."/../../files",
but the problem is none of the subsequent variables use this directive but rather continue using "../../files" for the path:
Could you modify this to allow relocation? I realize I could just extract the airtime files to /opt but I'd rather start keeping files separate when it comes to runtime-files vs. install packages. Plus there's also file ownership, etc.
III. How do you envision upgrades being handled?
Running airtime-uninstall.php is not optimal as the database gets wiped out every time.
IV. Twitter integration?
The install scripts seem to be broken now. Any plans to get that back in?
I'll be traveling most of next week but will have remote access to the computer to test things. Plus, I'm now ready to provide access to the schedulers so they can start playing with it.
Thank you for everything. We're really looking forward to the switch.