alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Rolf Anderegg <rolf.anderegg@weiss.ch>
Cc: Michele Perrone <michele.perrone@weiss.ch>, alsa-devel@alsa-project.org
Subject: Re: MAN301 internal routing (Re: [PATCH] ALSA: dice: add stream format parameters for Weiss devices)
Date: Thu, 29 Feb 2024 08:28:13 +0900	[thread overview]
Message-ID: <20240228232813.GA3532@workstation.local> (raw)
In-Reply-To: <7e5f5a65-89d8-48d6-b68f-b6c7059124e6@weiss.ch>

Hi Rolf and Michele,

On Wed, Feb 28, 2024 at 09:32:45AM +0100, Rolf Anderegg wrote:
> Hi again, quick followup:
> So basically it's like this:
> 
> ```
> spdif-opt-input-1/2  ---+
> spdif-coax-input-1/2 --(or)--> digital-input-1/2 -----------------> stream-output-1/2
> aesebu-xlr-input-1/2 ---+
> muted ------------------+
> 
> stream-input-1/2 --------------------------+----------------------> spdif-coax-output-1/2
>                                            +----------------------> aesebu-xlr-output-1/2
>                                            +--analog-output-1/2 --> analog-xlr-output-1/2
>                                                         +-----------> analog-coax-output-1/2
> ```
> 
> And all potential mixing (e.g. volume processing) would be done in userspace on the firewire host.
>
> On 28.02.24 09:14, Rolf Anderegg wrote:
> > On 28.02.24 00:54, Takashi Sakamoto wrote:
> > > [...]
> > > 
> > > I assume that the actual source selection of 'digital-input-1/2' is done
> > > in the router function of DICE chip as well as the selection between
> > > 'digital-input-1/2' and 'stream-input-1/2'. The mixer function of the
> > > chip is not used as I expected, thus the selection should exist as the
> > > source of audio signals for the outputs. However, in the above description,
> > > I cannot find such selection.
> > > 
> > > Or the device has a fixed route between 'stream-input-1/2' and
> > > 'analog-{xlr,coax}-output-1/2'? The user can not hear the audio signal
> > > of opt/coax/xlr digital input ports in the analog outputs?
> 
> Exactly, this is fixed as you can see in our DICE routing method.

Ah... OK, now I got it. I had assumed that the audio signal to any
digital input interface can be dynamically routed to any of the audio
output according to the preference selection, however it is not. Unlike
the equipments for the studio recording, the feature so-called as 'direct
monitoring' (without multiplexing) is not implemented in MAN301. As a
summary, the captured digital audio signal has the long trip to user's ear,
like:

```
spdif-opt-input-1/2  --+
spdif-coax-input-1/2 -(or)--> digital-input-1/2 ---------------> stream-output-1/2
aesebu-xlr-input-1/2 --+                                                  |
muted -----------------+                                                  |
                                                                          |
(Linux system)                                                            v
pcm-playback-1/2 <------ (software digital audio processing) <-- pcm-capture-1/2
       |
       v
stream-input-1/2 -------------------------+--------------------> spdif-coax-output-1/2
                                          +--------------------> aesebu-xlr-output-1/2
                                          +-analog-output-1/2 -> analog-xlr-output-1/2
                                                    +----------> analog-coax-output-1/2
```

I've already uploaded `firewire-dice-protocols` crate v0.3.0 to crates.io
with the diagram including the selection[1], but it should be fixed. I'll
do it later.


Thanks

[1] https://docs.rs/firewire-dice-protocols/latest/firewire_dice_protocols/weiss/avc/index.html

Takashi Sakamoto

      reply	other threads:[~2024-02-28 23:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28  9:16 [PATCH] ALSA: dice: add stream format parameters for Weiss devices Michele Perrone
2023-07-28 13:13 ` Takashi Sakamoto
2023-07-31  8:09   ` Michele Perrone
2023-07-31 14:06     ` Takashi Sakamoto
2023-08-08  8:34       ` Michele Perrone
2023-08-08 15:25         ` Takashi Sakamoto
2023-08-16 13:05           ` ALSA: dice: improve support " Michele Perrone
2023-08-18 13:13             ` Takashi Sakamoto
2023-08-18 13:23               ` Michele Perrone
2023-08-22 13:58             ` Takashi Sakamoto
2023-08-31 13:28               ` Takashi Sakamoto
2023-09-04 16:00                 ` Rolf Anderegg
2023-09-05  1:20                   ` Takashi Sakamoto
2023-09-05  8:57                     ` Rolf Anderegg
2023-09-05 23:54 ` INT203 and DAC1 (Re: [PATCH] ALSA: dice: add stream format parameters for Weiss devices) Takashi Sakamoto
2023-09-16  9:18   ` Michele Perrone
2023-09-17  2:55     ` Takashi Sakamoto
2023-09-18 13:19   ` MAN301 external clock issues " Michele Perrone
2023-09-19 14:09     ` Takashi Sakamoto
2024-01-21 14:07 ` MAN301 internal routing " Takashi Sakamoto
2024-01-21 14:30   ` Takashi Sakamoto
2024-02-15 12:04     ` Takashi Sakamoto
2024-02-26 16:06   ` Michele Perrone
2024-02-27 23:54     ` Takashi Sakamoto
2024-02-28  8:14       ` Rolf Anderegg
2024-02-28  8:32         ` Rolf Anderegg
2024-02-28 23:28           ` Takashi Sakamoto [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=20240228232813.GA3532@workstation.local \
    --to=o-takashi@sakamocchi.jp \
    --cc=alsa-devel@alsa-project.org \
    --cc=michele.perrone@weiss.ch \
    --cc=rolf.anderegg@weiss.ch \
    /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;
as well as URLs for NNTP newsgroup(s).