I've never had any success using this feature before. I wonder if anyone could point out any obvious mistake I'm making.
As I understand it Airtime is the only "user" on the system who can access the soundcard so I'm unsure how to diagnose the problem. How, for instance, do you specify what input to record from (is it the alsa default).
Playback of shows is fine and but /var/tmp/airtime/shows-recorder is empty?
- Chris
manager@studio-one:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC259 Analog [ALC259 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0 manager@studio-one:~$ man aplay manager@studio-one:~$ arecord -l
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC259 Analog [ALC259 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
The input is the alsa default on your machine, there isn't a configuration
for this within Airtime currently.
in your file /etc/airtime/recorder.cfg
there should be a line
base_recorded_files = '/var/tmp/airtime/show-recorder/'
this is where ecasound creates the file while it is recording from the
default alsa input. After recording has finished, the audio file should be
uploaded to your Airtime stor directory and it is then removed from this tmp
folder.
When the audio file is uploaded to Airtime and put into your stor directory,
any rebroadcast shows which have been associated with this recording should
automatically be populated with this newly uploaded recorded file.
> **
> I've never had any success using this feature before. I wonder if anyone
> could point out any obvious mistake I'm making.
>
> As I understand it Airtime is the only "user" on the system who can access
> the soundcard so I'm unsure how to diagnose the problem. How, for instance,
> do you specify what input to record from (is it the alsa default).
>
> Playback of shows is fine and but /var/tmp/airtime/shows-recorder is empty?
>
> - Chris
>
> manager@studio-one:~$ aplay -l
> **** List of PLAYBACK Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: ALC259 Analog [ALC259 Analog]
> Subdevices: 0/1
> Subdevice #0: subdevice #0
> manager@studio-one:~$ man aplay
> manager@studio-one:~$ arecord -l
> **** List of CAPTURE Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: ALC259 Analog [ALC259 Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
>
>
--
Naomi Aro
Junior Software Developer, Sourcefabric.
That's what I hope for too but if I click on the scheduled repeats and choose "Show Content" there is no content displayed? I cannot locate any show under the playlist builder tab (the library). Perhaps I should go back to first principles and check that I can record with Ecasound outside of Airtime.
Good idea. I made a recording test this morning (abut 90 mins ago) for 5 minutes. The output of /var/log/airtime/show-recorder/main/current is rather large....
hello, yes unfortunately I don't see anything on the log as it only has messages from the last 20min, so if you have time it might be good to schedule that 1min test show.
and trying 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.
(audioio-mp3) Attempt to write after child process has terminated.
(eca-engine) WARNING: An output object has raised an error! Possible causes: Out of disk space, permission denied, unable
... to launch external applications needed in processing, etc.
- [ Controller/Batch processing finished (-3) ] --------------------------
ecasound: Warning! Errors detected during processing.
- [ Engine exiting ] -----------------------------------------------------
(eca-control-objects) Disconnecting chainsetup: "untitled-chainsetup".
but recording as a straight WAV file presents no problems (see below) so it suggests a problem with LAME.
manager@studio-one:~$ ecasound -i alsa -o /home/manager/testaudio.wav -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) Opened output "/home/manager/testaudio.wav", mode "read/write (update)". Format: s16_le, channels 2,
... srate 44100, interleaved (locked params).
- [ Connected chainsetup: "untitled-chainsetup" ] ------------------------
- [ Controller/Starting batch processing ] -------------------------------
- [ Engine - Driver start ] ----------------------------------------------
hmm, how did you originally install Airtime? I know if you install from source it's listed as a dependency, but I don't know about any kind of packages we create, I'll have to ask about that.
Posts: 113Member, Administrator, Sourcefabric Team
Um, so that's an issue to flag for Daniel and Robin...
On Thu, Aug 4, 2011 at 4:52 PM, Chris Weaver
<airtime-support@lists.sourcefabric.org> wrote:
>
> I installed it via Synaptic sudo apt-get install airtime.