i don't know if this is a routine or procedure, but i would like to ask
ferenc, akos, sebastian and tomas to think about the steps the intallation
needs to go through when using the install CD. and michael, i would like to
ask you how i can set the soundcards in the install process so that i have
the shitty one for preview and the high quality one for transmission...
primarily the following two scenarios for the install procedure:
---------------------------
use scenario A:
2 machines for livesupport. one the datastorage / remote admin and one for
the live mode in the studio.
what do i do?
a) install the datastorage with the install CD. set the network
configuration have an IP address. all is fine.
b) install the studio live machine with the install CD. so NOW the install
process needs to ask me: where is the datastorage? what's the IP? what else
does it need to ask? how to connect to postgresql?
---------------------------
use scenario B:
1 mighty machine with the one in all.
does the install now only need one IP address???
---------------------------
and michael, this one is for you:
during the installation process, how can i determine the use of which
soundcard? the maximum number will be three in one machine (not recommended
but possible in use scenario B).
1. live for transmission
2. preview for DJ
3. scheduler for transmission
content and media development http://mi.cz
----------------------------------------------------------------- http://www.campware.org -- http://crash.mi.cz -- http://suemi.de
"5. HOW TOs
X ?
?
X X
X X." (John Pye)
-----------------------------------------------------------------
------------------------------------------
Posted to Phorum via PhorumMail
> the steps the intallation
> needs to go through when using the install CD.
>
I would not only refer to these questions as specific for the install
CD. This also needs to be clarified for other or manual installations
and possible (re)configurations on changing system/settings.
as I don't see it anywhere I would define some feature requests here:
- documentation of livesupport (re)configuration
- approbriate interface to configuration on userlevel (a settings-dialog
included with the GUI for example ..)
> and michael, this one is for you:
>
> during the installation process, how can i determine the use of which
> soundcard? the maximum number will be three in one machine (not recommended
> but possible in use scenario B).
>
> 1. live for transmission
> 2. preview for DJ
> 3. scheduler for transmission
>
I would need further clarifications here as well...
- where are above settings actually configured?
- how should this be intended to be configured?
all I know so far is:
> 1) products/gLiveSupport/etc/gLiveSupport.xml.template or
> gLiveSupport.xml.
>
>
>
>
> audioDevice = "/dev/dsp"
> />
>
>
>
>
>
>
> audioDevice = "/dev/dsp1"
> />
>
> 2) or put an alias for dsp in conf.modules or modprobe
>
> alias /dev/dsp dmasound_pmac
> alias /dev/dsp2 dmasound_pmac
>
so we choose dsp device(s) ... and: are we fine?
what's outputPlayer and cuePlayer matching the scenario above?
m,-
------------------------------------------
Posted to Phorum via PhorumMail
At 15:18 12.05.2005, you wrote:
>I would need further clarifications here as well...
>
>- where are above settings actually configured?
>- how should this be intended to be configured
and you are the one to ask the right questions. so don't stop here
the scenario i see is:
robert in belgrade has a machine with three soundcards. he slots in the CD
and starts the install process. at some point he needs to decide which
sound card does what.
how does he decide that and
what does that mean for the intallation procedure?
content and media development http://mi.cz
----------------------------------------------------------------- http://www.campware.org -- http://crash.mi.cz -- http://suemi.de
"5. HOW TOs
X ?
?
X X
X X." (John Pye)
-----------------------------------------------------------------
------------------------------------------
Posted to Phorum via PhorumMail
>>1) products/gLiveSupport/etc/gLiveSupport.xml.template or
>>gLiveSupport.xml.
>>
>>
>>
>>
>> audioDevice = "/dev/dsp"
>> />
>>
>>
>>
>>
>>
>>
>> audioDevice = "/dev/dsp1"
>> />
>>
>
> so we choose dsp device(s) ... and: are we fine?
> what's outputPlayer and cuePlayer matching the scenario above?
The outputPlayer is the sound card for Live Mode broadcast output;
cuePlayer is for the preview sound card. There is an tag
in the scheduler.xml config file, which also takes an audioDevice =
"..." attribute, for the Scheduler broadcast output. Yes, we will
eventually need some script and/or gui to edit these config files.
Ferenc
------------------------------------------
Posted to Phorum via PhorumMail
>
> the scenario i see is:
>
> robert in belgrade has a machine with three soundcards. he slots in the CD
> and starts the install process. at some point he needs to decide which
> sound card does what.
>
> how does he decide that and
I don't know how this guy robert comes to his decision
joking ...
before questioning the how I'd like to know what he needs to decide:
a) he installs a studio. what sound-routing has to be decided and made?
b) he installs a station. what sound-routing has to be decided and made?
m,-
------------------------------------------
Posted to Phorum via PhorumMail
> > so we choose dsp device(s) ... and: are we fine?
> > what's outputPlayer and cuePlayer matching the scenario above?
>
> The outputPlayer is the sound card for Live Mode broadcast output;
> cuePlayer is for the preview sound card. There is an tag
> in the scheduler.xml config file, which also takes an audioDevice =
> "..." attribute, for the Scheduler broadcast output.
so asking "dump" questions on dev and reading config files slowly start
to clear things up..
so we have:
"station" part
- with the scheduler broadcasting a signal via device defined in
scheduler.xml (which is per default: not set?)
"studio" part
- with a live mode broadcast (btw: can you define the term for me?) via
device defined in gLiveSupport.xml by outputPlayer
- with a preview signal on device defined in gLiveSupport.xml by
cuePlayer
(which per default are set to /dev/dsp)
right?
> Yes, we will
> eventually need some script and/or gui to edit these config files.
>
I think so...
What about including the possibility of setting the sound devices in
postInstall-scripts for now? (maybe better: stripped down versions of
them down for plain config file (re)generation) ... so also install
procedure(s) could call them therefor ...
m,-
------------------------------------------
Posted to Phorum via PhorumMail
michael aschauer wrote:
> "station" part
> - with the scheduler broadcasting a signal via device defined in
> scheduler.xml (which is per default: not set?)
yes; not set means use the system default
> "studio" part
> - with a live mode broadcast (btw: can you define the term for me?) via
> device defined in gLiveSupport.xml by outputPlayer
the scheduler program has an audio output (== scheduler audio), and the
gLiveSupport program has an audio output (== live mode output == live
mode broadcast); these will both go into an analog mixer (together with
a microphone input, probably) and from there to air
plus the gLiveSupport program has a second audio output (== live mode
cue == live mode preview), which goes to the DJ's headphones, and does
not normally go on air
> - with a preview signal on device defined in gLiveSupport.xml by
> cuePlayer
> (which per default are set to /dev/dsp)
>
> right?
yes
> What about including the possibility of setting the sound devices in
> postInstall-scripts for now? (maybe better: stripped down versions of
> them down for plain config file (re)generation) ... so also install
> procedure(s) could call them therefor ...
Yes, we need to be able to set it from the install script, at least.
Any volunteers willing to write (or find) a simple php script which
modifies a single tag in an xml file?
Ferenc
------------------------------------------
Posted to Phorum via PhorumMail
> Yes, we need to be able to set it from the install script, at least.
> Any volunteers willing to write (or find) a simple php script which
> modifies a single tag in an xml file?
.. what would you think about this?
open issue(s):
where to place the audioDevice for scheduler?
using config file '/opt/livesupport/etc/scheduler.xml'
error parsing configuration file
Validity error:
No declaration for attribute audioDevice of element helixPlayer
michael aschauer wrote:
> .. what would you think about this?
Looks nice to me, but ask Akos, too.
> open issue(s):
> where to place the audioDevice for scheduler?
>
>
> using config file '/opt/livesupport/etc/scheduler.xml'
> error parsing configuration file
> Validity error:
> No declaration for attribute audioDevice of element helixPlayer
>
The DTDs for the optional arguments were missing. Fixed now.
Ferenc
------------------------------------------
Posted to Phorum via PhorumMail
> >>
> >>
> >>
> >> audioDevice = "/dev/dsp1"
> >> />
> >>
> >
> > so we choose dsp device(s) ... and: are we fine?
> > what's outputPlayer and cuePlayer matching the scenario above?
>
> The outputPlayer is the sound card for Live Mode broadcast output;
> cuePlayer is for the preview sound card. There is an tag
> in the scheduler.xml config file, which also takes an audioDevice =
> "..." attribute, for the Scheduler broadcast output.
so what are valid audioDevices for this tag and helixPlayer?
just "/dev/dsp?" ?
is there a way to choose card/device in ALSA style also (hw:0,1 ...)?
btw: anyone knows a simple way (that can be automated) how to look up
wich dsp belongs to which (channels of) soundcard?
m.
------------------------------------------
Posted to Phorum via PhorumMail
michael aschauer wrote:
> so what are valid audioDevices for this tag and helixPlayer?
> just "/dev/dsp?" ?
The only ones I positively know to work are /dev/dsp and /dev/dsp1. If
we are not at-least-one-side-of-at-least-one-cow types of people, we may
safely assume /dev/dsp2, /dev/dsp3 etc work, too.
> is there a way to choose card/device in ALSA style also (hw:0,1 ...)?