[PlanetCCRMA] Alsa-Jack config on Fedora 4

[Fernando Lopez-Lezcano]

On Sat, 2005-10-01 at 10:48 -0700, Bob Bailey wrote:
> Name        : alsa-tools                   Relocations: (not
> relocatable)
> Version     : 1.0.10                            Vendor: Planet CCRMA
> Release     : 0.1.rc1.rhfc4.ccrma           Build Date: Mon 29 Aug
> 2005 09:23:44 PM PDT
> Install Date: Wed 31 Aug 2005 07:54:01 PM PDT      Build Host:
> build.ccrma.stanford.edu
> Group       : System/Tools                  Source RPM:
> alsa-tools-1.0.10-0.1.rc1.rhfc4.ccrma.src.rpm

You have a version I put up briefly in the web before I found out that
envy24control was broken in 1.0.10rc1... You could downgrade to 1.0.9
which is fine (with regards to envy24control). 

> Yes, in qjackctl:
> 
> using 'jackd'
> driver 'alsa' of course
> realtime perameter checked
> 
> here is the output:
> 
> 10:45:01.004 Startup script...
> 10:45:01.005 artsshell -q terminate
> sound server terminated
> 10:45:01.541 Startup script terminated successfully.
> 10:45:01.565 JACK is starting...
> 10:45:01.568 /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p1024 -n2 -i2
> -o2
> 10:45:01.599 JACK was started with PID=12811 (0x320b).
> 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 ..
> apparent rate = 44100
> creating alsa driver ... hw:0|hw:0|1024|2|44100|2|2|nomon|swmeter|-|
> 32bit
> control device hw:0
> the playback device "hw:0" is already in use. Please stop the
> application using it and run JACK again

Something else is using the soundcard. Check that you don't have the kde
or gnome sound servers enabled. You may also have previous instances of
jack that did not exit properly and are still "using" the soundcard. 

-- Fernando

> cannot load driver module alsa
> 10:45:03.864 Could not connect to JACK server as client.
> 10:45:03.933 JACK was stopped successfully.
> could not attach as JACK client (server has exited)
> 
> I'm about to reboot with the new modprobe.conf you gave me and see if
> that changes anything.  To me, it doesn't seem related.
> 
> bb
> 
> Fernando Lopez-Lezcano wrote: 
> > On Fri, 2005-09-30 at 22:51 -0700, Bob Bailey wrote:
> >   
> > > 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
> > >     
> > 
> >   
> > > 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
> > >     
> > 
> > What version of alsa-tools do you have installed?
> >   rpm -q -i alsa-tools
> >   
> > > started jackd and got this.... looks like it is up.  Is there a reason
> > > it wouldn't start with qjackctl? 
> > >     
> > 
> > Check what options you have in qjackctl (in "Setup"), check that you are
> > starting it with "jackd" and not "jackstart".
> > 
> > -- Fernando
> >   
> > > [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
> > >