Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: "M. Armsby" <m.armsby@gmx.de>
Cc: ALSA mail List <alsa-devel@alsa-project.org>
Subject: Re: Motu 896Mk3Hybrid dump
Date: Tue, 7 Feb 2023 21:27:45 +0900	[thread overview]
Message-ID: <Y+JDwWHZAI8BRgu9@workstation> (raw)
In-Reply-To: <rbih9oyihq4crt3olr-o19zohmq8w36-ipfswlyypvjp5a8src-wcww6tahyaki-q7v6tx-j5yh81-vzf7pq-qn78wo-tww8q3-2h35ww-sk0mu3-7fsog578xr2k-jfqgg5-rvg5aw-mhtapx-pch8v9t7epgq.1675704644475@email.android.com>

Hi,

On Mon, Feb 06, 2023 at 06:30:44PM +0100, M. Armsby wrote:
> Hi there Takashi,
> 
> please send me your instructions.
> 
> I will do everything to get these MOTU devices working properly.
 
Okay. As a first step, would I ask you to build `linux-firewire-utils`?

 * https://github.com/cladisch/linux-firewire-utils

In the top level of directory, execute below commands:

$ autoreconf -i
$ ./configure
$ make

When building successfully, you can find `firewire-request` in `src`
directory. It is useful to read the status of device and required for
our investigation.

Before building, I think you need to install some package required for
the work (e.g. compiler), but I'm not Manjaro user so contact to Manjaro
user to ask it...

> The problem with device allocation is this:
> 
> Ardour and Reaper see the ALSA driver and automatically choose 1+2
> for main stereo out.
> 
> But - there is no connection.
> 
> If I choose 3+4 then Motu hardware actually gets sound output on 1+2
> 
> That means all Motu outs are shifted by 2 in the Linux protocol.
> 
> This is true for Traveler MK1 and MK3 so I assume it is an error in
> all snd_motu_spec
> 
> I made a short video demonstrating this.
> 
> https://www.transfernow.net/dl/20230206jG0fet84/OFRBRajr

Thanks for your taking and uploading the video.

The below figure illustrates your cases:

 ++======================++    +-------+    ++===============++
 ||       Traveler       ||    | frame |    ||  Application  ||
 ||                      ||    |       |    ||               ||
 || headphone output 1/2 || <- |  0/1  | <- ||  Output 1/2   ||
 || analog output 1/2    || <- |  2/3  | <- ||  Output 3/4   ||
 || analog output 3/4    || <- |  4/5  | <- ||  Output 5/6   ||
 || analog output 5/6    || <- |  6/7  | <- ||  Output 7/8   ||
 || analog output 7/8    || <- |  8/9  | <- ||  Output 9/10  ||
 || AES/EBU (XLR) 1/2    || <- | 10/11 | <- ||  Output 11/12 ||
 || S/PDIF (opt) 1/2     || <- | 12/13 | <- ||  Output 13/14 ||
 ++======================++    +-------+    ++===============++

I note that the effective source of headphone output is selectable
between the above 7 pairs. Additionally, when enabling ADAT optical
output, 8 channels are newly added to the frame thus 22 channels are
available in a view of application.

Well, inconveniently to you, the above mapping is expected. ALSA
firewire-motu driver passes no information to the application about
what the channel of frame is assigned to, due to technical reason of
ALSA interface to user space application. As a result, the application
just enumerates audio sample in its order.


Regards

Takashi Sakamoto

  reply	other threads:[~2023-02-07 12:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <clpqss6u2nl2-tqmbic2pqf4x-fl7n8ufasb45-1to1x7160p65-86skuflc32uf-b435ds-2dqjqzzi2x9r-n26ssw-jjzxq0-aeknhb-drcr4x44iip67z8kfz-gayyzivnj1e3-exbx9z-ayuv2umcdyh1.1675078615418@email.android.com>
2023-01-30 13:19 ` Firewire Phase24 Motu help Takashi Sakamoto
2023-02-05 11:54   ` Motu 896Mk3Hybrid dump Martin Armsby on GMX
2023-02-06  1:26     ` Takashi Sakamoto
2023-02-06 17:30       ` M. Armsby
2023-02-07 12:27         ` Takashi Sakamoto [this message]
     [not found]           ` <-9ql34ax08baa-u8njs4ojzl8k9qj8kusba8u-119dm2-3md8uqbmil7lckunia-ijl9m4n5xuto-76roex-ucqm5h-1c3kdf-5ahx5l1oy29o-no4drk-5wjqfzqre34j-p7he4b9rr95u-3lcrfi-9o14b8.1675872031471@email.android.com>
2023-02-09  4:32             ` Motu " Takashi Sakamoto
2023-02-09 12:19               ` M. Armsby
2023-02-10  3:01                 ` Motu " 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=Y+JDwWHZAI8BRgu9@workstation \
    --to=o-takashi@sakamocchi.jp \
    --cc=alsa-devel@alsa-project.org \
    --cc=m.armsby@gmx.de \
    /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