Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Shirkey <pshirkey@boosthardware.com>
To: David Sankel <camio@yahoo.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: 1.0.0 Requirements, Integration of sound deamon (JACK)
Date: Sun, 13 Oct 2002 15:05:15 +0900	[thread overview]
Message-ID: <3DA90D1B.2030406@boosthardware.com> (raw)
In-Reply-To: 20021013025239.17302.qmail@web40603.mail.yahoo.com

David Sankel wrote:
>>Have you used JACK?
>>
>>AFAIK it definitely requires a pcm. You may have
>>used it on hardware 
>>that supports multiopen which would explain what you
>>have observed.
> 
> 
> Yes, I have used jack.  I meant that it doesn't open
> the sound device when it is not being used by a host application.
> 

I'm pretty sure it does. In order to run it needs to claim a pcm device 
(or multiple devices as specified in an .asoundrc). I just tested that 
by starting jackd and then trying to start alsaplayer on the same device 
and jackd blocks alsaplayer until it is shutdown then alsaplayer will start.




-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2002-10-13  6:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-11 13:13 1.0.0 Requirements, Integration of sound deamon (JACK) David Sankel
2002-10-11 15:03 ` Patrick Shirkey
2002-10-13  2:52   ` David Sankel
2002-10-13  6:05     ` Patrick Shirkey [this message]
2002-10-13 11:23     ` Andy Lo-A-Foe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3DA90D1B.2030406@boosthardware.com \
    --to=pshirkey@boosthardware.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=camio@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox