we made some progress with our daemons for Radio Orange. The one daemon
listens on a sound card over alsalib and if no sound is available, it
talks to a perl daemon which switches a Matrix Switch and talks via
XML-RPC to the Campcaster scheduler (and restores the Switch if sound is
available again).
I have two questions:
1.) Scheduler/gstreamer reactivity
I noticed, that when I schedule a playlist for now() it will be played
by the scheduler immediately, but I do not hear any sound. If increment
now() by 15 seconds, I hear the sound. Anything below 10 seconds will
for sure not work in terms of hearing any sound. Is this delay
normal/planned?
2.) Removing currently playing playlists
Is it possible to stop and remove a running playlist? I have used
stopCurrentlyPlaying and it actually stops sound output. By using
removeFromSchedule the scheduler says it can't remove it because it is
playing. Is there a XML-RPC method for stopping and removing a currently
playing playlist? Or is this simply not possible by design?
Mic
PS: Thanks for this amazing software, the new release and the great
support on IRC.
--
strg.at design development server http://strg.atoffice@strg.at
liniengasse 20/12, 1060 wien
tel +43 1 526 56 29 fax +43 1 526 56 49
Michael Dosser wrote:
> I have two questions:
>
> 1.) Scheduler/gstreamer reactivity
> I noticed, that when I schedule a playlist for now() it will be played
> by the scheduler immediately, but I do not hear any sound. If increment
> now() by 15 seconds, I hear the sound. Anything below 10 seconds will
> for sure not work in terms of hearing any sound. Is this delay
> normal/planned?
Hi Michael -
Yes, this is a known bug. It only happens with playlists - they take
about 10 seconds to load per hour of songs. The scheduler and the GUI
interface deal with this by pre-loading the playlists 10 seconds before
they start playing. We hope to speed this up in the 1.2 release.
> 2.) Removing currently playing playlists
> Is it possible to stop and remove a running playlist? I have used
> stopCurrentlyPlaying and it actually stops sound output. By using
> removeFromSchedule the scheduler says it can't remove it because it is
> playing. Is there a XML-RPC method for stopping and removing a currently
> playing playlist? Or is this simply not possible by design?
> Michael Dosser wrote:
> > 2.) Removing currently playing playlists
> > Is it possible to stop and remove a running playlist? I have used
> > stopCurrentlyPlaying and it actually stops sound output. By using
> > removeFromSchedule the scheduler says it can't remove it because it is
> > playing. Is there a XML-RPC method for stopping and removing a currently
> > playing playlist? Or is this simply not possible by design?
Paul Baranowski schrieb:
> Yes, this is a known bug. It only happens with playlists - they take
> about 10 seconds to load per hour of songs. The scheduler and the GUI
> interface deal with this by pre-loading the playlists 10 seconds before
> they start playing. We hope to speed this up in the 1.2 release.
The timeframe of 10 seconds should be ok. If this will be less in the
next release the better
>> 2.) Removing currently playing playlists
>> Is it possible to stop and remove a running playlist? I have used
>> stopCurrentlyPlaying and it actually stops sound output. By using
>> removeFromSchedule the scheduler says it can't remove it because it is
>> playing. Is there a XML-RPC method for stopping and removing a currently
>> playing playlist? Or is this simply not possible by design?
This is very important for the implementation at Radio Orange. The
running playlist should be stopable and removeable in order to upload a
new playlist which matches the current studio audio output.
Can anybody help me with this?
Mic
--
strg.at design development server http://strg.atoffice@strg.at
liniengasse 20/12, 1060 wien
tel +43 1 526 56 29 fax +43 1 526 56 49
Michael Dosser wrote:
> This is very important for the implementation at Radio Orange. The
> running playlist should be stopable and removeable in order to upload a
> new playlist which matches the current studio audio output.
>
> Can anybody help me with this?
We're going to implement this for our next release, due out at the
beginning of January. If you would like to help us out, let us know and
also stop by in the IRC channel: irc.freenode.net/#campcaster