[PlanetCCRMA] Lost in the backroads..
Jeff Farr
Jeff Farr <moogah@gmail.com>
Mon Oct 10 10:58:03 2005
------=_Part_2378_14434807.1128967046951
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Ok, things are looking much better this morning. JackRack starts and things
like the amSynth work now. Muse and Ardour startup as proper and appear to
work as proper so I've got a good selection of programs at my disposal now.
Again, thanks for all the help.
Now, However, my performance is still sub-par. For instance, using a delay
plugin in jack rack with an external synth routed through is very glitchy
and at one point even crashed. asound/cards lists that the delta is on irq1=
6
and /devices shows 16: playback 24: capture. Are these irqs?
On 10/10/05, Fernando Lopez-Lezcano <nando@ccrma.stanford.edu> wrote:
>
> On Mon, 2005-10-10 at 01:36 -0400, Jeff Farr wrote:
> > Allright, I think I've narrowed it down a bit. Some of the trouble
> > was that I hadn't "alsasound on" -ed again since the last reboot. Now
> > ardour, snd, freqTweek and hydrogen are 'working'. However, if I try
> > to start JackRack it still says it can't find the alsa sequencer and
> > "no such file or directory". Likewise if I try to alsasound start or
> > stop in /etc/rc.d/init.d bash says it doesn't recognize the command.
> > Perhaps I've missed something?
>
> What do you see when you do a:
> cat /proc/asound/cards
> cat /proc/asound/devices
> Are you sure you have the alsasound script set up to run at boot?
> Do the following:
> /sbin/chkconfig --list alsasound
> It should print something like:
> alsasound 0:off 1:off 2:on 3:on 4:on 5:on 6:off
> (note the "5:on" part, that means the service will be started when you
> go to level 5, multiuser with the X server running).
>
> If it does try starting it manually, do (as root):
> /etc/rc.d/init.d/alsasound start
> That should load the sequencer module automatically (and subsequently on
> every reboot).
>
> Regretfully all apps are different and some may require command line
> arguments to use Jack, otherwise they will not try to use it and may
> fail silently when, for example, they try to use alsa and find the
> devices in use because Jack is already running.
>
> -- Fernando
>
>
>
------=_Part_2378_14434807.1128967046951
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Ok, things are looking much better this morning. JackRack starts
and things like the amSynth work now. Muse and Ardour startup as
proper and appear to work as proper so I've got a good selection of
programs at my disposal now. Again, thanks for all the help.<br>
Now, However, my performance is still sub-par. For instance,
using a delay plugin in jack rack with an external synth routed through
is very glitchy and at one point even crashed. asound/cards lists
that the delta is on irq16 and /devices shows 16: playback 24:
capture. Are these irqs? <br><br><div><span class=3D"gmail_quot=
e">On 10/10/05, <b class=3D"gmail_sendername">Fernando Lopez-Lezcano</b> &l=
t;<a href=3D"mailto:nando@ccrma.stanford.edu">nando@ccrma.stanford.edu</a>&=
gt; wrote:</span>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Mon, 2005-10-1=
0 at 01:36 -0400, Jeff Farr wrote:<br>> Allright, I think I've narrowed =
it down a bit. Some of the trouble
<br>> was that I hadn't "alsasound on" -ed again since the las=
t reboot. Now<br>> ardour, snd, freqTweek and hydrogen are 'w=
orking'. However, if I try<br>> to start JackRack it still sa=
ys it can't find the alsa sequencer and
<br>> "no such file or directory". Likewise if I tr=
y to alsasound start or<br>> stop in /etc/rc.d/init.d bash says it doesn=
't recognize the command.<br>> Perhaps I've missed something?<br><br>Wha=
t do you see when you do a:
<br> cat /proc/asound/cards<br> cat /proc/asound/devi=
ces<br>Are you sure you have the alsasound script set up to run at boot?<br=
>Do the following:<br> /sbin/chkconfig --list alsasound<br>It sh=
ould print something like:
<br> alsasound
0:off 1:off
2:on 3:on 4:on &nb=
sp; 5:on 6:off<br>(note the "5:on" pa=
rt, that means the service will be started when you<br>go to level 5, multi=
user with the X server running).<br><br>If it does try starting it manually=
, do (as root):
<br> /etc/rc.d/init.d/alsasound start<br>That should load the se=
quencer module automatically (and subsequently on<br>every reboot).<br><br>=
Regretfully all apps are different and some may require command line<br>arg=
uments to use Jack, otherwise they will not try to use it and may
<br>fail silently when, for example, they try to use alsa and find the<br>d=
evices in use because Jack is already running.<br><br>-- Fernando<br><br><b=
r></blockquote></div><br>
------=_Part_2378_14434807.1128967046951--