All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Eldad Zack <eldad@fogrefinery.com>
Cc: alsa-devel@alsa-project.org, Daniel Mack <zonque@gmail.com>
Subject: Re: How to use implicit feedback with full duplex?
Date: Wed, 06 Feb 2013 21:13:29 +0100	[thread overview]
Message-ID: <5112B969.50905@ladisch.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1302052326150.1207@xoschi>

Eldad Zack wrote:
> On Tue, 5 Feb 2013, Clemens Ladisch wrote:
>> I thought I'd try to use implicit feedback with my simple audio device:
>> [...]
>> This works fine when playing something:
> ...
>> But when I then try to record at the same time, the driver refuses to
>> configure the input endpoint (to the only format, which is already set):
>> And despite that "alreay in use" check, the input endpoint is affected
>> so much that playback breaks.
>>
>> Is full duplex supposed to work?  Does it work with other devices?
>
> This is probably a "yes, but" :)
> I use my device mostly full duplex, but with jack opening both
> playback and capture at the same time.
>
> I assume you are opening two different streams, one for playback and
> one for capture.

Jack *also* uses two different streams, but it opens them at the same
time.

> Can you try using jackd -d alsa -d hw:x with the device and see if that
> works for you?

That works.  This means that there is a race condition in the driver, or
that the different open/hw_params/prepare order trips it up.


Anyway, I feel safe now to enable implicit feedback for other devices.


Regards,
Clemens

  reply	other threads:[~2013-02-06 20:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-05 20:44 How to use implicit feedback with full duplex? Clemens Ladisch
2013-02-05 22:50 ` Eldad Zack
2013-02-06 20:13   ` Clemens Ladisch [this message]
2013-02-06 20:20     ` Daniel Mack
2013-02-07  9:03       ` Felix Homann
2013-02-07  9:52         ` Takashi Iwai
2013-02-07 20:54           ` Eldad Zack
2013-02-07 20:49         ` Eldad Zack
2013-02-07 20:39     ` Eldad Zack
2013-03-24 22:49     ` Eldad Zack
2013-03-26 20:06       ` Daniel Mack
2013-04-03 22:08         ` Eldad Zack

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=5112B969.50905@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=eldad@fogrefinery.com \
    --cc=zonque@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.