All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Geraldo Nascimento <geraldogabriel@gmail.com>
Cc: alsa-devel@alsa-project.org, Olivia Mackintosh <livvy@base.nu>
Subject: Re: [PATCH v2] Pioneer devices: engage implicit feedback sync for playback
Date: Mon, 19 Apr 2021 09:15:20 +0200	[thread overview]
Message-ID: <s5hlf9eg2yf.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAEsQvctoF1MeGLyUiPZpfRC50kMY+8nnQ12OphPO8NvMUFj_hQ@mail.gmail.com>

On Sun, 18 Apr 2021 16:16:56 +0200,
Geraldo Nascimento wrote:
> 
> Em Dom, 18 de abr de 2021 09:45, Olivia Mackintosh <livvy@base.nu> escreveu:
> 
>     > As a blind shot: might the stall be avoided by passing the recently
>     > introduced chip->playback_first flag?  The revised patch is below.
>    
>     This appears to fix the issue, thank you! I am curious as to why this is
>     not required for Geraldo's DDJ-SR2.
> 
> Heh, sometimes I think Takashi Iwai is psychic ;-)

Heh, it was our luck that we've worked on the similar problem very
recently.

> Just kidding, he's "just" very talented and very experienced. Anyway, the
> DDJ-SR2 is originally a Serato controller. It still requires two MIDI SysEx
> messages to unmute the RCA inputs - engaging "Serato Mode" in marketing-speak.
> 
> My point is that Pioneer may be a little more compliant / a little less
> deviant from the UAC2 standard when designing gear for use with third-party
> software.

I think many devices require the implicit feedback seem following this
pattern: for such devices, the full-duplex streams are mandatory,
i.e. both streams have to be started always.  And the implicit
feedback is triggered at the later point for a proper sync.

>     My initial thought was that certain devices that restrict capture unless
>     regular SysEx/Control URBs are sent may mean that Playback first support
>     is required (e.g. 750, 850, 450). Please correct me if this intuition is
>     incorrect.

As mentioned previously, it might be the difference of the PCM
parameters to be deployed.  I guess Geraldo didn't test speaker-test
program but maybe only the standard sound backends like JACK, etc.

In anyway, I'm going to format and submit the proper patch for
merging.


thanks,

Takashi

      reply	other threads:[~2021-04-19  7:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-05 13:49 [PATCH v2] Pioneer devices: engage implicit feedback sync for playback Geraldo
2021-04-05 14:16 ` Geraldo
2021-04-06 11:48 ` Takashi Iwai
2021-04-06 13:44   ` Geraldo
2021-04-09 11:07 ` Olivia Mackintosh
2021-04-09 17:31   ` Geraldo Nascimento
2021-04-16 16:11   ` Takashi Iwai
2021-04-17 22:26     ` Olivia Mackintosh
2021-04-18  0:48       ` Geraldo Nascimento
2021-04-18  7:43       ` Takashi Iwai
2021-04-18 12:43         ` Olivia Mackintosh
2021-04-18 14:16           ` Geraldo Nascimento
2021-04-19  7:15             ` Takashi Iwai [this message]

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=s5hlf9eg2yf.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=geraldogabriel@gmail.com \
    --cc=livvy@base.nu \
    /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.