alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Michele Perrone <michele.perrone@weiss.ch>,
	Rolf Anderegg <rolf.anderegg@weiss.ch>
Cc: alsa-devel@alsa-project.org
Subject: Re: MAN301 internal routing (Re: [PATCH] ALSA: dice: add stream format parameters for Weiss devices)
Date: Sun, 21 Jan 2024 23:30:48 +0900	[thread overview]
Message-ID: <20240121143048.GA191130@workstation.local> (raw)
In-Reply-To: <20240121140748.GA189921@workstation.local>

Hi,

On Sun, Jan 21, 2024 at 11:07:48PM +0900, Takashi Sakamoto wrote:
> Then I have some questions.
> 
> 1. The signal source designated for stream-output-1/2
> I think it is any type of digital input designated by control element
> "Digital Input Capture Route", or source ID block which generates
> silence.
> 
> 2. The signal sources designated for the outputs
> According to the manual of MAN301, the sources are selectable somehow.
> There are two ways at least for pre-amp and player modes. I guess that
> any interface is defined to configure internal router for the purpose.
> 
> [1] https://github.com/alsa-project/snd-firewire-ctl-services/tree/topic/weiss-support
> [2] https://github.com/alsa-project/snd-firewire-ctl-services/blob/topic/weiss-support/protocols/dice/src/weiss/avc.rs#L12

I have an extra question.

3. store/load router configuration

In my understanding, TCAT DICE firmware stores configurations per three
rate modes. When switching between the rate modes, corresponding
configuration is loaded automatically. In the case of MAN301, the
configurations done via AV/C command is loaded in the way?


Regards

Takashi Sakamoto

  reply	other threads:[~2024-01-21 14:31 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 [this message]
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

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=20240121143048.GA191130@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).