Airtime 1.9 RC2 released today.
-
Hi everyone,
Airtime 1.9 RC2 is out. Our amazing dev team tell me this is now production ready. There are no known bugs in this release and we'd love you to test it fully.
To test an online demo, visit http://airtime-dev.sourcefabric.org/login (username: admin | password: admin)
What's really important is that the install/upgrade process is tested. If you're feeling brave, head over to the wiki and follow the guides there in order to manually install or to test the upgrade process.
Thanks to everyone who tested and gave us feedback on previous versions. Hopefully you'll be pleased with the improvements that have gone into this almost, almost final version!
For any feedback or issues, please make a post in this forum, or over at our bug tracker (just select Create Issue in the top right and then Airtime).
What's new?
New file storage system and human-readable file structure. The directory structure and file names on disk are now human-readable. This means you can easily find files using your file browser on your server.
Magic file synchronization. Edits to your files are automatically noticed by Airtime. If you edit any files on disk, such as trimming the length of a track, Airtime will automatically notice this and adjust the playlist lengths and shows for that audio file.
Auto-import and multiple-directory support. You can set any number of directories to be watched by Airtime. Any new files you add to watched directories will be automatically imported into Airtime, and any deleted files will be automatically removed. The "airtime-import" command line tool can now set watched directories and change the storage directory.
Graceful recovery from reboot. If the playout engine starts up and detects that a show should be playing at the current time, it will skip to the right point in the track and start playing. Previously, Airtime would not play anything until the next show started. This also fixes a problem where the metadata on the stream was lost when a file had cue-in/out values set. Thanks to the Liquidsoap developers for implementing the ability to do all of this!
Output to Shoutcast. Now both Shoutcast and Icecast are supported.
A new "Program Manager" role. A program manager can create shows but can't change the preferences or modify users.
No more rebooting after install! Airtime now uses standard SystemV initd scripts instead of non-standard daemontools. This also makes for a much faster install.
Frontend widgets are much easier to use. Their theme can now also be modified with CSS.
Improved installation Only one command to install on Ubuntu!
Improvements
Cumulative time shown on playlists. The Playlist Builder now shows the total time since the beginning of the playlist for each song.
"End Time" instead of "Duration". In the Add/Edit Show dialog, we replaced the "Duration" field with "End Time". Users reported that this was a much more intuitive way to schedule the show. Duration is still shown as a read-only field.
Feedback & promotion system. Airtime now includes a way to send feedback and promote your site on the Sourcefabric web page. This will greatly enhance our ability to understand who is using the software, which in turn will allow us to make appropriate features and receive grant funding.
Other nice things
- The show recorder can now instantly cancel a show thanks to the use of RabbitMQ.
- Only admins have the ability to delete files now.
- The playout engine now runs with a higher priority. This should help prevent any problems with audio skipping.
- Airtime has been contained. It is now easier to run other apps on the same system with Airtime because it no longer messes with the system-wide Python or PHP configurations. The python libraries needed for Airtime are now contained in a local Python virtualenv, and the PHP config variables are set in the Apache virtualhost and .htaccess files.
Bug fixes
- Fixed bug where you couldn't import a file with a name longer than 255 characters.
- Fixed bug where searching an audio archive of 15K+ files was slow.
- Fixed bug where upgrading from more than one version back(e.g. 1.8.0 -> 1.9.0) did not work.
- Fixed bug where the wrong file length was reported for very large CBR mp3 files (thanks to mutagen developers for the patch!) -
24 Comments sorted by
-
After I clear my browser's cache and go back to the UI, it is still 1.8.2 and shows this error along the top Notice: Undefined index: base_files_dir in /var/lib/airtime/application/configs/conf.php on line 69 Notice: Undefined index: base_files_dir in /var/lib/airtime/application/configs/conf.php on line 71. What am I doing wrong?
-
Did you change the default php files directory? It almost seems like maybe the new php files are not overwriting your current ones that apache is loading for you. How did you install?
-
Sorry if this is the wrong spot for this. I just upgraded and I noticed that the config line for base_file_dir is missing from the airtime.conf file.
I want to put my media on an external drive. How can I specify where the files should be uploaded to?
** Update **
I figured out where the Configure preferences were in the new interface to Manage Media Folders. But no matter what I change these to (even the Desktop), uploaded files don't appear to actually get uploaded into AIRTIME or the file system itself. Thoughts? -
hey Garrett, were you changing the stor folder location or adding a new watched folder? Maybe you can post your logs from
/var/log/airtime/media-monitor
-
On Mon, Aug 1, 2011 at 6:01 PM, Garrett Kelly <
airtime-dev@lists.sourcefabric.org> wrote:
> **
> Sorry if this is the wrong spot for this. I just upgraded and I noticed
> that the config line for base_file_dir is missing from the airtime.conf
> file.
>
You upgraded to 1.9, correct? If so, the base_file_dir has been removed
from the config file, that info is now stored in the database. You can use
the command-line tool "airtime-import" to change the location of your
storage directory, or you can do it in the web interface (Configure->manage
media folders).
- Paul
-
No sooner had I sorted Record and Rebroadcast function in 1.8.2, prompted by Adams email I'd thought I'd upgrade to 1.9 RC3. Unfortunately, following the instructions here:
I've ended up with same issue as "Wireless Radio Union College" at the top of this post.
I've tried the following:
airtime-import --storage-dir-get
None
manager@studio-one:~/airtime-1.9.0-RC3/utils$ sudo airtime-import --storage-dir-set /media/DATA/Airtime_Library/
Are you sure you want to change the storage direcory? (y/N)y
Unable to connect to the Airtime server.
-
Ok, I think this might have something to do with upgrading from a packaged version using source.
I don't have a folder /var/lib/airtime on my computer.
can you tell me what value you have set in /etc/airtime/airtime.conf, do you have
airtime_dir = /var/www/airtime ?
what is your apache config pointing at?
/etc/apache2/sites-enabled/airtimefilenamehere
Maybe /var/lib/airtime instead of /var/www/airtime? I'm not sure if these are matching up between the two installation types.
-
Hi Naomi,
On this system /etc/airtime/airtime.conf
airtime_dir = /var/www/airtime
and in the /etc/apache2/sites-enabled/ directory there is airtime and
airtime-vhost
manager@studio-one:~$ cat /etc/apache2/sites-enabled/airtime
<VirtualHost *:80>
ServerAdmin foo@bar.org
DocumentRoot /var/www/airtime/public
php_admin_value upload_tmp_dir /tmp
<Directory /var/www/airtime/public>
DirectoryIndex index.php
AllowOverride all
Order allow,deny
Allow from all
</Directory>
</VirtualHost>
manager@studio-one:~$ cat /etc/apache2/sites-enabled/airtime-vhost
<VirtualHost *:80>
ServerName localhost
#ServerAlias www.example.com
ServerAdmin chris@resonancefm.com
DocumentRoot /var/lib/airtime/public
DirectoryIndex index.php
SetEnv APPLICATION_ENV "development"
<Directory /var/lib/airtime/public>
Options -Indexes FollowSymLinks MultiViews
AllowOverride All
Order allow,deny
Allow from all
</Directory>
</VirtualHost>
- Chris
On 5 August 2011 10:34, Naomi <airtime-dev@lists.sourcefabric.org> wrote:
> **
> Ok, I think this might have something to do with upgrading from a
> packaged version using source.
>
> I don't have a folder /var/lib/airtime on my computer.
>
> can you tell me what value you have set in /etc/airtime/airtime.conf, do
> you have
> airtime_dir = /var/www/airtime ?
>
> what is your apache config pointing at?
> /etc/apache2/sites-enabled/airtimefilenamehere
>
> Maybe /var/lib/airtime instead of /var/www/airtime? I'm not sure if these
> are matching up between the two installation types.
>
>
>
--
--
As a consequence of our engagement with a large scale, off-site,
broadcasting project throughout June and July, I will not be able to attend
to day-to-day matters relating to programming/broadcasting. Focus will
solely be on work produced specifically for this unique event. "Normal"
service will be resumed from August onwards.
Chris Weaver
Production Manager
Resonance104.4FM
resonancefm.com
+44 (0)207 407 1210
-
ok I think it's something different with this setup.
Do you have any content in /var/lib/airtime? I think it might work if you remove it and replace it with the content from /var/www/airtime (if there is any content there, which I think it should contain the source for 1.9.0)
either that or you can modify airtime-vhost (if there is content in /var/www/airtime) change these lines to be:
DocumentRoot /var/lib/airtime/public
DocumentRoot /var/www/airtime/public
<Directory /var/lib/airtime/public>
<Directory /var/www/airtime/public>
then delete the file /etc/apache2/sites-enabled/airtime
and do
sudo service apache2 restart -
Great! Logins in and all. Will check the scheduling and all. Shall I copy
this exchange into the forum.
- Chris
On 5 August 2011 10:59, Naomi <airtime-dev@lists.sourcefabric.org> wrote:
> **
> ok I think it's something different with this setup.
>
> Do you have any content in /var/lib/airtime? I think it might work if you
> remove it and replace it with the content from /var/www/airtime (if there is
> any content there, which I think it should contain the source for 1.9.0)
>
> either that or you can modify airtime-vhost (if there is content in
> /var/www/airtime) change these lines to be:
>
>
> DocumentRoot /var/lib/airtime/public
> DocumentRoot /var/www/airtime/public
>
> <Directory /var/lib/airtime/public>
> <Directory /var/www/airtime/public>
>
> then delete the file /etc/apache2/sites-enabled/airtime
>
> and do
>
> sudo service apache2 restart
>
--
--
As a consequence of our engagement with a large scale, off-site,
broadcasting project throughout June and July, I will not be able to attend
to day-to-day matters relating to programming/broadcasting. Focus will
solely be on work produced specifically for this unique event. "Normal"
service will be resumed from August onwards.
Chris Weaver
Production Manager
Resonance104.4FM
resonancefm.com
+44 (0)207 407 1210
-
It's automatically in the forum! no worries.
Can I just ask one more question, when you did the upgrade from 1.8.2 do you remember if you ran the upgrade script in the folder
install_minimal or install_full? -
I used the minimal install out lined in the upgrade instructions here:
http://wiki.sourcefabric.org/display/CC/Upgrading+to+Airtime +1.9.0
- Chris
On 5 August 2011 11:20, Naomi <airtime-dev@lists.sourcefabric.org> wrote:
> **
> It's automatically in the forum! no worries.
>
> Can I just ask one more question, when you did the upgrade from 1.8.2 do
> you remember if you ran the upgrade script in the folder
>
> install_minimal or install_full?
>
--
--
As a consequence of our engagement with a large scale, off-site,
broadcasting project throughout June and July, I will not be able to attend
to day-to-day matters relating to programming/broadcasting. Focus will
solely be on work produced specifically for this unique event. "Normal"
service will be resumed from August onwards.
Chris Weaver
Production Manager
Resonance104.4FM
resonancefm.com
+44 (0)207 407 1210
-
There is one strange issue though. The time is wrong on Airtime. My
/etc/php5/apache2/php.ini has date.timezone set as "Europe/London" but
Airtime is using EDT (6Am currently)
Restarting the computer and clearing the browser cache haven't updated it.
- Chris
On 5 August 2011 11:28, Chris Weaver <chris@resonancefm.com> wrote:
> I used the minimal install out lined in the upgrade instructions here:
> http://wiki.sourcefabric.org/display/CC/Upgrading+to+Airtime +1.9.0
>
> - Chris
>
>
>
>
> On 5 August 2011 11:20, Naomi <airtime-dev@lists.sourcefabric.org> wrote:
>
>> **
>> It's automatically in the forum! no worries.
>>
>> Can I just ask one more question, when you did the upgrade from 1.8.2 do
>> you remember if you ran the upgrade script in the folder
>>
>> install_minimal or install_full?
>>
>
>
>
> --
> --
>
> As a consequence of our engagement with a large scale, off-site,
> broadcasting project throughout June and July, I will not be able to attend
> to day-to-day matters relating to programming/broadcasting. Focus will
> solely be on work produced specifically for this unique event. "Normal"
> service will be resumed from August onwards.
>
>
>
>
> Chris Weaver
> Production Manager
> Resonance104.4FM
> resonancefm.com
> +44 (0)207 407 1210
>
--
--
As a consequence of our engagement with a large scale, off-site,
broadcasting project throughout June and July, I will not be able to attend
to day-to-day matters relating to programming/broadcasting. Focus will
solely be on work produced specifically for this unique event. "Normal"
service will be resumed from August onwards.
Chris Weaver
Production Manager
Resonance104.4FM
resonancefm.com
+44 (0)207 407 1210
-
oh sorry I forgot to mention that, in 1.9.0 it doesn't use the timezone set in php.ini.
I'm not sure if you're using /var/www/airtime or /var/lib/airtime but in the one you are using look in your public folder. There is a .htaccess file and you will have to put your timezone into that file. -
Got it. Set to Toronto time!
On 5 August 2011 12:01, Naomi <airtime-dev@lists.sourcefabric.org> wrote:
> **
> oh sorry I forgot to mention that, in 1.9.0 it doesn't use the timezone
> set in php.ini.
>
> I'm not sure if you're using /var/www/airtime or /var/lib/airtime but in
> the one you are using look in your public folder. There is a .htaccess file
> and you will have to put your timezone into that file.
>
--
--
As a consequence of our engagement with a large scale, off-site,
broadcasting project throughout June and July, I will not be able to attend
to day-to-day matters relating to programming/broadcasting. Focus will
solely be on work produced specifically for this unique event. "Normal"
service will be resumed from August onwards.
Chris Weaver
Production Manager
Resonance104.4FM
resonancefm.com
+44 (0)207 407 1210
-
Oh dear I hate to sound like a stuck record but now the "Record and
Rebroadcast" feature is not recording again!
- Chris
On 5 August 2011 12:16, Chris Weaver <chris@resonancefm.com> wrote:
> Got it. Set to Toronto time!
>
> On 5 August 2011 12:01, Naomi <airtime-dev@lists.sourcefabric.org> wrote:
>
>> **
>> oh sorry I forgot to mention that, in 1.9.0 it doesn't use the timezone
>> set in php.ini.
>>
>> I'm not sure if you're using /var/www/airtime or /var/lib/airtime but in
>> the one you are using look in your public folder. There is a .htaccess file
>> and you will have to put your timezone into that file.
>>
>
>
>
> --
> --
>
> As a consequence of our engagement with a large scale, off-site,
> broadcasting project throughout June and July, I will not be able to attend
> to day-to-day matters relating to programming/broadcasting. Focus will
> solely be on work produced specifically for this unique event. "Normal"
> service will be resumed from August onwards.
>
>
>
>
> Chris Weaver
> Production Manager
> Resonance104.4FM
> resonancefm.com
> +44 (0)207 407 1210
>
--
--
As a consequence of our engagement with a large scale, off-site,
broadcasting project throughout June and July, I will not be able to attend
to day-to-day matters relating to programming/broadcasting. Focus will
solely be on work produced specifically for this unique event. "Normal"
service will be resumed from August onwards.
Chris Weaver
Production Manager
Resonance104.4FM
resonancefm.com
+44 (0)207 407 1210
-
ok please post the logs from
/var/log/airtime/show-recorder
py-interpreter.log show-recorder.log -
Looks normal enough:
manager@studio-one:~$ cat /var/log/airtime/show-recorder/py-interpreter.log
************************************************************ **************
* ecasound v2.7.0 (C) 1997-2009 Kai Vehmanen and others
************************************************************ **************
(eca-chainsetup-parser) Set processing time to 300.00.
(eca-chainsetup) Chainsetup "untitled-chainsetup"
(eca-chainsetup) NOTE: Real-time configuration, but insufficient privileges
... to utilize real-time scheduling (SCHED_FIFO). With small buffersizes,
... this may cause audible glitches during processing.
(eca-chainsetup) "rt" buffering mode selected.
(audioio_alsa) Warning! Period-size differs from current client buffersize.
(eca-chainsetup) Opened input "alsa", mode "read". Format: s16_le, channels
... 2, srate 44100, interleaved.
(eca-chainsetup) NOTE: using existing audio parameters -f:s16_be,2,44100
... for object '/var/tmp/airtime/show-recorder/2011-08-05-12:25:00.mp3
... (tried to open with -f:s16_le,2,44100).
(eca-chainsetup) Opened output
... "/var/tmp/airtime/show-recorder/2011-08-05-12:25:00.mp3", mode "write".
... Format: s16_be, channels 2, srate 44100, interleaved (locked params).
- [ Connected chainsetup: "untitled-chainsetup" ] ------------------------
- [ Controller/Starting batch processing ] -------------------------------
- [ Engine - Driver start ] ----------------------------------------------
(audioio-mp3) Starting to encode
... /var/tmp/airtime/show-recorder/2011-08-05-12:25:00.mp3 with lame.
- [ Engine - Processing finished ] ---------------------------------------
- [ Controller/Batch processing finished (0) ] ---------------------------
- [ Engine exiting ] -----------------------------------------------------
On 5 August 2011 16:31, Naomi <airtime-dev@lists.sourcefabric.org> wrote:
> **
> ok please post the logs from
>
> /var/log/airtime/show-recorder
>
> py-interpreter.log show-recorder.log
>
--
--
As a consequence of our engagement with a large scale, off-site,
broadcasting project throughout June and July, I will not be able to attend
to day-to-day matters relating to programming/broadcasting. Focus will
solely be on work produced specifically for this unique event. "Normal"
service will be resumed from August onwards.
Chris Weaver
Production Manager
Resonance104.4FM
resonancefm.com
+44 (0)207 407 1210
-
can you also post the log show-recorder.log ?
-
Here is the log for a recent recording. Nothing particularly seems to be
amiss except the files are empty. I've checked the Alasmixer setting and
tried recording via ecasound on the command line. Everything gives me an
empty file?
Hmmmm
- Chris
ecasound -i alsa -o /home/manager/testaudio.mp3 -t:60.0
************************************************************ **************
* ecasound v2.7.0 (C) 1997-2009 Kai Vehmanen and others
************************************************************ **************
(eca-chainsetup-parser) Set processing time to 60.00.
(eca-chainsetup) Chainsetup "untitled-chainsetup"
*(eca-chainsetup) NOTE: Real-time configuration, but insufficient privileges
to utilize real-time scheduling (SCHED_FIFO).
... With small buffersizes, this may cause audible glitches during
processing.*
(eca-chainsetup) "rt" buffering mode selected.
(audioio_alsa) Warning! Period-size differs from current client buffersize.
(eca-chainsetup) Opened input "alsa", mode "read". Format: s16_le, channels
2, srate 44100, interleaved.
(eca-chainsetup) NOTE: using existing audio parameters -f:s16_be,2,44100 for
object '/home/manager/testaudio.mp3 (tried
... to open with -f:s16_le,2,44100).
(eca-chainsetup) Opened output "/home/manager/testaudio.mp3", mode "write".
Format: s16_be, channels 2, srate 44100,
... interleaved (locked params).
- [ Connected chainsetup: "untitled-chainsetup" ] ------------------------
- [ Controller/Starting batch processing ] -------------------------------
- [ Engine - Driver start ] ----------------------------------------------
(audioio-mp3) Starting to encode /home/manager/testaudio.mp3 with lame.
- [ Engine - Processing finished ] ---------------------------------------
- [ Controller/Batch processing finished (0) ] ---------------------------
- [ Engine exiting ] -----------------------------------------------------
(eca-control-objects) Disconnecting chainsetup: "untitled-chainsetup".
cat /var/log/airtime/show-recorder/show-recorder.log
2011-08-08 10:44:41,427 INFO - [recorder.py : __init__() : line 174] -
RecorderFetch: init complete
2011-08-08 10:44:41,589 INFO - [recorder.py : run() : line 272] - Started...
2011-08-08 10:44:41,590 INFO - [recorder.py : init_rabbit_mq() : line 177] -
Initializing RabbitMQ stuff
2011-08-08 10:44:39,108 ERROR - [recorder.py : init_rabbit_mq() : line 187]
- [Errno 111] Connection refused
2011-08-08 10:44:39,108 ERROR - [recorder.py : run() : line 274] - Error
connecting to RabbitMQ Server. Trying again in few seconds
2011-08-08 10:44:44,113 INFO - [recorder.py : init_rabbit_mq() : line 177] -
Initializing RabbitMQ stuff
2011-08-08 10:44:44,115 DEBUG - [connection.py : _start() : line 648] -
Start from server, version: 8.0, properties: {u'platform': 'Erlang/OTP',
u'product': 'RabbitMQ', u'version': '1.8.0', u'copyright': 'Copyright (C)
2007-2010 LShift Ltd., Cohesive Financial Technologies LLC., and Rabbit
Technologies Ltd.', u'information': 'Licensed under the MPL. See
http://www.rabbitmq.com/'}, mechanisms: ['PLAIN', 'AMQPLAIN'], locales:
['en_US']
2011-08-08 10:44:44,151 DEBUG - [connection.py : _open_ok() : line 494] -
Open OK! known_hosts [studio-one:5672]
2011-08-08 10:44:44,151 DEBUG - [channel.py : __init__() : line 70] - using
channel_id: 1
2011-08-08 10:44:44,151 DEBUG - [channel.py : _open_ok() : line 484] -
Channel open
2011-08-08 10:44:44,153 DEBUG - [api_client.py : get_shows_to_record() :
line 320] -
http://localhost:80/api/recorded-shows/format/json/api_key/% %api_key%%
2011-08-08 10:44:46,162 INFO - [api_client.py : get_shows_to_record() : line
325] - shows {u'is_recording': False, u'shows': []}
2011-08-08 10:44:46,163 INFO - [recorder.py : parse_shows() : line 209] -
Parsing show schedules...
2011-08-08 10:44:46,163 INFO - [recorder.py : parse_shows() : line 222] - {}
2011-08-08 10:44:46,163 INFO - [recorder.py : run() : line 284] - Bootstrap
complete: got initial copy of the schedule
2011-08-08 10:44:46,163 INFO - [recorder.py : run() : line 290] - Loop #1
2011-08-08 11:20:24,010 INFO - [recorder.py : handle_message() : line 195] -
Received command from RabbitMQ:
{"event_type":"update_schedule","shows":[{"starts":"2011-08-08
11:30:00","ends":"2011-08-08
11:31:00","record":"1","rebroadcast":"0","soundcloud_id ":null,"instance_id":"20","show_id":"13","name":"Recording
Test 5","description":"","color":"","background_color":" "}]}
2011-08-08 11:20:24,011 INFO - [recorder.py : handle_message() : line 198] -
Handling command: update_schedule
2011-08-08 11:20:24,011 INFO - [recorder.py : parse_shows() : line 209] -
Parsing show schedules...
2011-08-08 11:20:24,011 DEBUG - [recorder.py : get_time_till_next_show() :
line 235] - Next show 2011-08-08 11:30:00
2011-08-08 11:20:24,011 DEBUG - [recorder.py : get_time_till_next_show() :
line 236] - Now 2011-08-08 11:20:24.011465
2011-08-08 11:20:24,011 INFO - [recorder.py : parse_shows() : line 222] -
{u'2011-08-08 11:30:00': [datetime.timedelta(0, 60), u'20', u'Recording Test
5']}
2011-08-08 11:20:24,011 INFO - [recorder.py : run() : line 290] - Loop #2
2011-08-08 11:29:54,112 INFO - [recorder.py : run() : line 295] - timed out
2011-08-08 11:29:54,112 DEBUG - [recorder.py : get_time_till_next_show() :
line 235] - Next show 2011-08-08 11:30:00
2011-08-08 11:29:54,112 DEBUG - [recorder.py : get_time_till_next_show() :
line 236] - Now 2011-08-08 11:29:54.112558
2011-08-08 11:29:54,113 DEBUG - [recorder.py : start_record() : line 246] -
sleeping 5 seconds until show
2011-08-08 11:29:59,120 INFO - [recorder.py : record_show() : line 81] -
starting record
2011-08-08 11:29:59,120 INFO - [recorder.py : record_show() : line 82] -
command ecasound -f:16,2,44100 -i alsa -o
/var/tmp/airtime/show-recorder/2011-08-08-11:30:00.mp3,25600 0 -t:60.0
2011-08-08 11:29:59,121 INFO - [recorder.py : run() : line 290] - Loop #3
2011-08-08 11:30:59,680 INFO - [recorder.py : record_show() : line 90] -
finishing record, return code 0
2011-08-08 11:30:59,681 INFO - [recorder.py : run() : line 153] - Preparing
to upload /var/tmp/airtime/show-recorder/2011-08-08-11:30:00.mp3
2011-08-08 11:30:59,681 INFO - [recorder.py : set_metadata_and_save() : line
131] - time: 11-30-00
2011-08-08 11:30:59,756 DEBUG - [api_client.py : upload_recorded_show() :
line 342] -
http://localhost:80/api/upload-file/format/json/api_key/%%ap i_key%%
2011-08-08 11:30:59,756 DEBUG - [api_client.py : upload_recorded_show() :
line 344] -
http://localhost:80/api/upload-file/format/json/api_key/K4YH RWHSE1EHY7ASWC3Y
2011-08-08 11:30:59,756 DEBUG - [api_client.py : upload_recorded_show() :
line 347] - Upload attempt: 1
2011-08-08 11:31:00,017 INFO - [api_client.py : upload_recorded_show() :
line 353] - uploaded show result []
2011-08-08 11:31:02,923 INFO - [recorder.py : handle_message() : line 195] -
Received command from RabbitMQ: {"event_type":"update_schedule","shows":[]}
2011-08-08 11:31:02,924 INFO - [recorder.py : handle_message() : line 198] -
Handling command: update_schedule
2011-08-08 11:31:02,924 INFO - [recorder.py : parse_shows() : line 209] -
Parsing show schedules...
2011-08-08 11:31:02,924 INFO - [recorder.py : parse_shows() : line 222] - {}
2011-08-08 11:31:02,924 INFO - [recorder.py : run() : line 290] - Loop #4
On 5 August 2011 18:00, Naomi <airtime-dev@lists.sourcefabric.org> wrote:
> **
> can you also post the log show-recorder.log ?
>
--
--
As a consequence of our engagement with a large scale, off-site,
broadcasting project throughout June and July, I will not be able to attend
to day-to-day matters relating to programming/broadcasting. Focus will
solely be on work produced specifically for this unique event. "Normal"
service will be resumed from August onwards.
Chris Weaver
Production Manager
Resonance104.4FM
resonancefm.com
+44 (0)207 407 1210
-
Ok, I'm not really sure of the state of setup anymore since the upgrade was done on a packaged install.
Do you have pulseaudio installed?
if you do su pypo (password pypo) and then type "groups" what groups is user pypo in? -
So just to confirm. Upgrades should only be done via Synaptic if you
installed via Synaptic? I could just reformat the machine, install 1.8.2 and
then wait for the upgrade via Synaptic. Perhaps that is best?
No pulseaudio anymore
Groups
pypo : pypo audio www-data
- Chris
On 8 August 2011 12:25, Naomi <airtime-dev@lists.sourcefabric.org> wrote:
> **
> Ok, I'm not really sure of the state of setup anymore since the upgrade
> was done on a packaged install.
>
> Do you have pulseaudio installed?
>
> if you do su pypo (password pypo) and then type "groups" what groups is
> user pypo in?
>
--
--
As a consequence of our engagement with a large scale, off-site,
broadcasting project throughout June and July, I will not be able to attend
to day-to-day matters relating to programming/broadcasting. Focus will
solely be on work produced specifically for this unique event. "Normal"
service will be resumed from August onwards.
Chris Weaver
Production Manager
Resonance104.4FM
resonancefm.com
+44 (0)207 407 1210
-
Yes, if you install via synaptic you should only upgrade there or else there can be conflicts etc, when synaptic thinks Airtime has an update, but you've already got it, or you could lose dependencies if you uninstall the synaptic one and keep the upgrade from source.
If you install 1.9 from a fresh install is there any difference? You don't have to try this, but I would suggest waiting for the synaptic package for 1.9 -
Hmmm Perhaps I'll just go back to the 1.8.2 for the time being.
Thanks for all your help.
- Chris
On 8 August 2011 12:53, Naomi <airtime-dev@lists.sourcefabric.org> wrote:
> **
> Yes, if you install via synaptic you should only upgrade there or else
> there can be conflicts etc, when synaptic thinks Airtime has an update, but
> you've already got it, or you could lose dependencies if you uninstall the
> synaptic one and keep the upgrade from source.
>
> If you install 1.9 from a fresh install is there any difference? You don't
> have to try this, but I would suggest waiting for the synaptic package for
> 1.9
>
--
--
As a consequence of our engagement with a large scale, off-site,
broadcasting project throughout June and July, I will not be able to attend
to day-to-day matters relating to programming/broadcasting. Focus will
solely be on work produced specifically for this unique event. "Normal"
service will be resumed from August onwards.
Chris Weaver
Production Manager
Resonance104.4FM
resonancefm.com
+44 (0)207 407 1210
Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Categories
- All Discussions8,397
- Sourcefabric
- ↳ Announcements25
- Newscoop
- ↳ Newscoop Support2,189
- ↳ Newscoop Development722
- ↳ Newscoop Security13
- ↳ Newscoop Documentation17
- ↳ Newscoop Themes69
- Airtime
- ↳ Airtime Support3,139
- ↳ Airtime Development1,286
- ↳ Airtime Français146
- ↳ Airtime Documentation14
- ↳ Airtime Hacks102
- ↳ Promote your station!37
- ↳ Airtime Security11
- Booktype
- ↳ Booktype Support277
- ↳ Booktype Development55
- ↳ Booktype Documentation7
- Superdesk
- ↳ Superdesk Development264
- ↳ Web Publisher21
Poll
No poll attached to this discussion.Top Posters
-
Albert FR
1978
-
Martin Konecny
1860
-
Andrey Podshivalov
1526
-
Voisses Tech
1423
-
John Chewter
899
-
Daniel James
844
-
Roger Wilco
784
-
hoerich
627
-
Paul Baranowski
389
-
Cliff Wang
339