LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

Reply
 
Search this Thread
Old 09-30-2006, 12:00 AM   #1
Barnix
LQ Newbie
 
Registered: Sep 2006
Location: Canada
Distribution: Mandrake + My own LFS crop
Posts: 5

Rep: Reputation: 0
Help: Mystified with ALSA+Jack..(almost there)..


I made it quite far already but I'm confused
about what remains to be done.

I've already build a fine LFS 6.2.
My hardware is SB Live 24bit, and my Kernel
is cmpiled fine for it. I also have an
onboard ICH5 Intel sound device. All detected.

I've compiled JACK and installed.
I've compiled ALSA libs tools and plugins.

/dev/snd has the entries:
controlC0 and C1
midiC1D0
pcmC0D0c
pcmC0D0p
pcmC0D1c
pcmC0D1p
.
.
.
seq
timer

When I type:.. I get:
#aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0:ICH5 [Intel ICH5], device 0: Intel ..blablabla.
Subdevice: 1/1
Subdevice #0: subdevice #0
card :ICH5 [Intel ICH5], device 4: Intel ICH -IEC958 [Intel ....]
Subdevice: 1/1
Subdevice #0: subdevice #0
card 1:CA0106 [CA0106],device 0: ca0106 [CA0106]
Subdevice: 1/1
Subdevice #0: subdevice #0
card 1:CA0106 [CA0106],device 1: ca0106 [CA0106]
Subdevice: 1/1
Subdevice #0: subdevice #0
card 1:CA0106 [CA0106],device 2: ca0106 [CA0106]
Subdevice: 1/1
Subdevice #0: subdevice #0
card 1:CA0106 [CA0106],device 3: ca0106 [CA0106]
Subdevice: 1/1
Subdevice #0: subdevice #0
----
I'm interested in using the CA0106, which is
the SB Live 24bits.

I also have:
/proc/asound/CA0106/
/proc/asound/ICH5/
/proc/asound/card0/
/proc/asound/card1/
/proc/asound/oss/
/proc/asound/seq/
/proc/asound/cards
/proc/asound/devices
/proc/asound/pcm
/proc/asound/timers
/proc/asound/version

MY PANIC is that I don't know how to setup
ALSA to use JACK; Or is it JACK using ALSA ??
I'm confused. Am I right to think I have to
start some sort of JACK deamon first,
(jackd -v -d alsa (card???) -r44100 ?????
and
then give ALSA some kind of 'pcm' config file.
Is it the other way around ?
I'm really confused.
--
P.S.
I'll be happy when I can successfully run the
JACK example-clients like:
jackrec*
(I presume this allows me to record a timed WAV file)
And yes, the asound library is there ready..
I'm just quite lost with the setup.

Thanks in advance.

Last edited by Barnix; 09-30-2006 at 12:10 AM.
 
Old 09-30-2006, 12:40 AM   #2
Barnix
LQ Newbie
 
Registered: Sep 2006
Location: Canada
Distribution: Mandrake + My own LFS crop
Posts: 5

Original Poster
Rep: Reputation: 0
FOLLOW-UP:

Without doing anything to my configuration.
Remember this is no Mandrake or Suze, it`s a plain
vanilla Linux From Scratch (LFS) to which I am
growing sound support. My purpose is not tu run
under Xwindows, so I'm not installing the more advanced
tools often used to ease the pain..

So, I just tried to start 'jackd' from the prompt:

#jackd -v -d alsa ca0106 -r44100 2>/mnt/floppy/test

Then I CTRL-C to stop it and see.. Here is test file:
(I think it`s promising)

getting driver descriptor from /usr/lib/jack/jack_alsa.so
getting driver descriptor from /usr/lib/jack/jack_dummy.so
getting driver descriptor from /usr/lib/jack/jack_oss.so
JACK compiled with System V SHM support.
server `default' registered
registered builtin port type 32 bit float mono audio
loading driver ..
new client: alsa_pcm, id = 1 type 1 @ 0x80578d0 fd = -1
apparent rate = 44100
configuring for 44100Hz, period = 1024 frames, buffer = 2 periods
Note: audio device hw:0 doesn't support a 32bit sample format so JACK will try a 24bit format instead
Note: audio device hw:0 doesn't support a 24bit sample format so JACK will try a 16bit format instead
nperiods = 2 for capture
nperiods = 2 for playback
new buffer size 1024
registered port alsa_pcm:capture_1, offset = 4096
registered port alsa_pcm:capture_2, offset = 8192
registered port alsa_pcmlayback_1, offset = 0
registered port alsa_pcmlayback_2, offset = 0
registered port alsa_pcmlayback_3, offset = 0
registered port alsa_pcmlayback_4, offset = 0
registered port alsa_pcmlayback_5, offset = 0
registered port alsa_pcmlayback_6, offset = 0
++ jack_rechain_graph():
client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
2064 waiting for signals
load = 0.0070 max usecs: 3.000, spare = 21330.000
load = 0.0105 max usecs: 3.000, spare = 21330.000
load = 0.0123 max usecs: 3.000, spare = 21330.000
jack main caught signal 2
starting server engine shutdown
stopping driver
unloading driver
freeing shared port segments
stopping server thread
last xrun delay: 0.000 usecs
max delay reported by backend: 0.000 usecs
freeing engine shared memory
max usecs: 3.000, engine deleted
no message buffer overruns
cleaning up shared memory
cleaning up files
unregistering server `default'
-------

Okay,, So the line above:
"jack main caught signal 2"
Probably came when I've hit CTRL-C to stop this fg task.

Now I guess I have to fiddle with a proper alsa ~/.asoundrc
????
Thanks in advance for any tips.
 
Old 06-01-2007, 11:27 AM   #3
Tom Jennings
LQ Newbie
 
Registered: Aug 2002
Posts: 5

Rep: Reputation: 0
alsa and jack

I am hardly an expert on sound, but I did just get jackd working, and can tell you a few thins hoepfulyl helpful.

ALSA drives the sound hardware; you can think of Jack as a higher-level service, that provides sound connectivity services to sound applications (patching app A to app B, etc) and uses ALSA to output (and input) sound.

When Jack is used, sound apps (xmms, whatever) no longer talk to ALSA; they talk to Jack. Jack adds a layer of sound-service abstraction above ALSA.

If all you want to do is have single apps output sound (xmms, mplayer, etc) skip installing Jack -- not only is it not necessary it's a major PITA to get running, but worth it if you intend to make music, DJ, etc. It requires the use of a low-latency kernel. Skip Jack unless you intend to do high-end audio stuff like mixing or live performance.

When Jack is running sound apps can no longer talk to ALSA; Jack owns it.

You must first get alsa to work.
 
Old 06-02-2007, 06:07 AM   #4
loopie
LQ Newbie
 
Registered: Jun 2007
Posts: 5

Rep: Reputation: 0
good U done well
 
  


Reply

Tags
jack, jackd


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
jack and alsa problem zepphead5 Linux - Software 2 04-07-2006 11:39 AM
JACK, Ardour ALSA - Mandrake 10.1 trey85stang Linux - Software 2 05-22-2005 08:30 AM
jack, alsa and Terratec DMX 6fire s_siouris Linux - Software 3 04-11-2005 09:33 PM
alsa/jack/ardour foo_bar_foo Linux - Software 1 10-20-2004 04:43 AM
JACK doesn't detect ALSA disciple061 Linux - Software 0 07-31-2003 07:52 PM


All times are GMT -5. The time now is 10:38 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration