From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: "mj@mj" <mj@michaeljosephs.com>
Cc: paul@neyrinck.com, alsa-devel@alsa-project.org
Subject: Re: Firewire Audio Interface
Date: Thu, 23 Feb 2023 11:38:58 +0900 [thread overview]
Message-ID: <Y/bRwirgNNPPCpop@workstation> (raw)
In-Reply-To: <CB595AFA-C37B-44AE-BF7F-9F58A3AEF106@michaeljosephs.com>
Hi,
(C.C.ed to alsa-devel)
On Wed, Feb 22, 2023 at 11:51:23AM -0500, mj@mj wrote:
> Hey man thanks so much for the reply!
>
> Why TC put the phantom switch in the software instead of on the
> hardware unit I can’t figure out!
>
> I think I’m just going to use it a 2-in 2-out interface without
> the phantom.
>
> A friend of mine looked at the circuit board and told me it
> would be too difficult to put a switch for the phantom power in it.
>
> Thanks again for the reply!
If it is Desktop Konnekt 6, node offset 0x'ffff'e0a0'103c has the 32 bit
value to express the state of phantom powering. If it is 0, disabled, else
enabled. Quadlet write asynchronous transaction can change the state, but
I have never used MacOs to operate any node in IEEE 1394 bus.
I know some developer and user for the craft driver; e.g.
* Re: [alsa-devel] Tascam Coding Inquiry
* https://lore.kernel.org/alsa-devel/20200108095430.GA16741@workstation/
I think it your help to contact to them. Especially Paul Neyrinck[1] seems
to complete his work for the craft driver of Digidesign Digi 002/003
family in MacOS. They are different hardware from yours, while he will
help you to execute the simple read/write transaction to a certain
offset of it.
[1] https://neyrinck.com/
Regards
Takashi Sakamoto
prev parent reply other threads:[~2023-02-23 2:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2E89E35E-85D0-45D1-8727-BB013FA78DAA@michaeljosephs.com>
2023-02-22 10:21 ` Firewire Audio Interface Takashi Sakamoto
[not found] ` <CB595AFA-C37B-44AE-BF7F-9F58A3AEF106@michaeljosephs.com>
2023-02-23 2:38 ` 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=Y/bRwirgNNPPCpop@workstation \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=mj@michaeljosephs.com \
--cc=paul@neyrinck.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox