[PlanetCCRMA] Alsa-Jack config on Fedora 4

Bob Bailey bob@digisonus.com
Fri Sep 30 22:48:00 2005


This is a multi-part message in MIME format.
--------------040601060001020706010105
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Thanks Fernando.  I think I determined that I didn't need to run 
alsaconf, but only after I'd run it.  Can I then delete the alsaconf 
generated section and replace with your suggestion from below?

by the way, here is /proc/asound/cards and /proc/devices:

[root@daw bbailey]# cat /proc/asound/cards
0 [M410           ]: ICE1712 - M Audio Delta 410
                     M Audio Delta 410 at 0xd000, irq 10

[root@daw bbailey]# cat /proc/devices
Character devices:
  1 mem
  4 /dev/vc/0
  4 tty
  4 ttyS
  5 /dev/tty
  5 /dev/console
  5 /dev/ptmx
  7 vcs
 10 misc
 13 input
 14 sound
 29 fb
116 alsa
128 ptm
136 pts
180 usb
226 drm

Block devices:
  1 ramdisk
  2 fd
  3 ide0
  9 md
 22 ide1
253 device-mapper
254 mdp

looks like ALSA is there.

When I start envy24control, it starts to initiate, but quickly closes.  
hmmm.  here is the output:

[root@daw bbailey]# envy24control
using    --- input_channels: 2
         --- output_channels: 8
         --- pcm_output_channels: 8
         --- spdif in/out channels: 2
Segmentation fault

started jackd and got this.... looks like it is up.  Is there a reason 
it wouldn't start with qjackctl?

[root@daw bbailey]# jackd -R -d alsa -d hw
jackd 0.100.1
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details

JACK compiled with System V SHM support.
loading driver ..
creating alsa driver ... hw|hw|1024|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
nperiods = 2 for capture
nperiods = 2 for playback


Bob

Fernando Lopez-Lezcano wrote:

>On Fri, 2005-09-30 at 10:32 -0700, Bob Bailey wrote:
>  
>
>>I may have over estimated my abilities in venturing to Fedora4 without 
>>more documentation available.  I have had success with Fedora2, but it 
>>seems that there may have been some changes in the version 4 that are 
>>keeping me from a successful install.  I've not installed ardour or any 
>>of the other apps I will use, but am just trying to get the audio 
>>working well with xmms and perhaps realaudio streams.
>>
>>when I try to open an ogg/mp3/wav file, I get an xmms error:
>>Couldn't open audio.  Please check that your soundcard is configured 
>>properly, you have the correct output plugin selected, and that no other 
>>program is blocking the soundcard.
>>
>>I have the alsa 1.2.10  output plugin selected (libALSA.so) and 
>>modprobe.conf:
>>
>>alias eth0 e100
>>alias snd-card-0 snd-ice1712
>>alias usb-controller uhci-hcd
>># --- BEGIN: Generated by ALSACONF, do not edit. ---
>># --- ALSACONF version 1.0.9 ---
>># --- END: Generated by ALSACONF, do not edit. ---
>>    
>>
>
>You should not have neede to run alsaconf on fc4, it should have found
>your card automatically...
>
>  
>
>># -- Keep modules from being autocleaned
>>#add options -k snd-card-0
>>alias net-pf-10 off
>>alias ipv6 off
>>
>>by the way, I get errors when I uncomment these 'autoclean' options
>>    
>>
>
>Try with this for the soundcard options:
>
>alias snd-card-0 snd-ice1712
>options snd-card-0 index=0
>options snd-ice1712 index=0
>
>That should be all you need. 
>
>  
>
>>In previous installs, I had to start up jack first.  When I attemt to do 
>>this now, I get this error from qjackctl:
>>
>>creating alsa driver ... /dev/dsp|-|1024|2|44100|0|2|nomon|swmeter|-|32bit
>>ALSA lib control.c:817:(snd_ctl_open_noupdate) Invalid CTL /dev/dsp
>>control open "/dev/dsp" (No such file or directory)
>>cannot load driver module alsa
>>09:27:01.025 JACK was stopped successfully.
>>09:27:02.818 Could not connect to JACK server as client.
>>    
>>
>
>This is all very strange. 
>What do you have in:
>  cat /proc/asound/cards
>  cat /proc/asound/devices
>If you don't have anything there then alsa is not started. 
>
>If you appear to have things there try starting "envy24control" to make
>sure it can see your card. 
>
>Then start (from the command line first) jack:
>
>  jackd -R -d alsa -d hw
>
>-- Fernando
>
>
>  
>

--------------040601060001020706010105
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="-1">Thanks Fernando.&nbsp; I think I determined that I didn't
need to run alsaconf, but only after I'd run it.&nbsp; Can I then delete the
alsaconf generated section and replace with your suggestion from below?<br>
<br>
by the way, here is /proc/asound/cards and /proc/devices:<br>
<br>
</font><font size="-1">[root@daw bbailey]# cat /proc/asound/cards<br>
0 [M410&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ]: ICE1712 - M Audio Delta 410<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; M Audio Delta 410 at 0xd000, irq 10<br>
<br>
[root@daw bbailey]# cat /proc/devices<br>
Character devices:<br>
&nbsp; 1 mem<br>
&nbsp; 4 /dev/vc/0<br>
&nbsp; 4 tty<br>
&nbsp; 4 ttyS<br>
&nbsp; 5 /dev/tty<br>
&nbsp; 5 /dev/console<br>
&nbsp; 5 /dev/ptmx<br>
&nbsp; 7 vcs<br>
&nbsp;10 misc<br>
&nbsp;13 input<br>
&nbsp;14 sound<br>
&nbsp;29 fb<br>
116 alsa<br>
128 ptm<br>
136 pts<br>
180 usb<br>
226 drm<br>
<br>
Block devices:<br>
&nbsp; 1 ramdisk<br>
&nbsp; 2 fd<br>
&nbsp; 3 ide0<br>
&nbsp; 9 md<br>
&nbsp;22 ide1<br>
253 device-mapper<br>
254 mdp<br>
<br>
looks like ALSA is there.<br>
<br>
When I start envy24control, it starts to initiate, but quickly closes.&nbsp;
hmmm.&nbsp; here is the output:<br>
<br>
[root@daw bbailey]# envy24control<br>
using&nbsp;&nbsp;&nbsp; --- input_channels: 2<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --- output_channels: 8<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --- pcm_output_channels: 8<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --- spdif in/out channels: 2<br>
Segmentation fault<br>
<br>
started jackd and got this.... looks like it is up.&nbsp; Is there a reason
it wouldn't start with qjackctl? <br>
<br>
[root@daw bbailey]# jackd -R -d alsa -d hw<br>
jackd 0.100.1<br>
Copyright 2001-2005 Paul Davis and others.<br>
jackd comes with ABSOLUTELY NO WARRANTY<br>
This is free software, and you are welcome to redistribute it<br>
under certain conditions; see the file COPYING for details<br>
<br>
JACK compiled with System V SHM support.<br>
loading driver ..<br>
creating alsa driver ... hw|hw|1024|2|48000|0|0|nomon|swmeter|-|32bit<br>
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods<br>
nperiods = 2 for capture<br>
nperiods = 2 for playback<br>
<br>
<br>
Bob<br>
</font><br>
Fernando Lopez-Lezcano wrote:
<blockquote cite="mid1128131646.24979.32.camel@cmn3.stanford.edu"
 type="cite">
  <pre wrap="">On Fri, 2005-09-30 at 10:32 -0700, Bob Bailey wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">I may have over estimated my abilities in venturing to Fedora4 without 
more documentation available.  I have had success with Fedora2, but it 
seems that there may have been some changes in the version 4 that are 
keeping me from a successful install.  I've not installed ardour or any 
of the other apps I will use, but am just trying to get the audio 
working well with xmms and perhaps realaudio streams.

when I try to open an ogg/mp3/wav file, I get an xmms error:
Couldn't open audio.  Please check that your soundcard is configured 
properly, you have the correct output plugin selected, and that no other 
program is blocking the soundcard.

I have the alsa 1.2.10  output plugin selected (libALSA.so) and 
modprobe.conf:

alias eth0 e100
alias snd-card-0 snd-ice1712
alias usb-controller uhci-hcd
# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF version 1.0.9 ---
# --- END: Generated by ALSACONF, do not edit. ---
    </pre>
  </blockquote>
  <pre wrap=""><!---->
You should not have neede to run alsaconf on fc4, it should have found
your card automatically...

  </pre>
  <blockquote type="cite">
    <pre wrap=""># -- Keep modules from being autocleaned
#add options -k snd-card-0
alias net-pf-10 off
alias ipv6 off

by the way, I get errors when I uncomment these 'autoclean' options
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Try with this for the soundcard options:

alias snd-card-0 snd-ice1712
options snd-card-0 index=0
options snd-ice1712 index=0

That should be all you need. 

  </pre>
  <blockquote type="cite">
    <pre wrap="">In previous installs, I had to start up jack first.  When I attemt to do 
this now, I get this error from qjackctl:

creating alsa driver ... /dev/dsp|-|1024|2|44100|0|2|nomon|swmeter|-|32bit
ALSA lib control.c:817:(snd_ctl_open_noupdate) Invalid CTL /dev/dsp
control open "/dev/dsp" (No such file or directory)
cannot load driver module alsa
09:27:01.025 JACK was stopped successfully.
09:27:02.818 Could not connect to JACK server as client.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
This is all very strange. 
What do you have in:
  cat /proc/asound/cards
  cat /proc/asound/devices
If you don't have anything there then alsa is not started. 

If you appear to have things there try starting "envy24control" to make
sure it can see your card. 

Then start (from the command line first) jack:

  jackd -R -d alsa -d hw

-- Fernando


  </pre>
</blockquote>
</body>
</html>

--------------040601060001020706010105--