alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@perex.cz>
To: alsa-devel@alsa-project.org, sbahling@suse.com,
	ffado-devel@lists.sourceforge.net
Subject: Re: [RFT] ALSA control service programs for Digidesign Digi 002/003 family and Tascam FireWire series
Date: Tue, 7 Jul 2020 15:15:53 +0200	[thread overview]
Message-ID: <a322006e-bd58-4dba-f590-855be17a2cdb@perex.cz> (raw)
In-Reply-To: <20200707125651.GA200100@workstation>

Dne 07. 07. 20 v 14:56 Takashi Sakamoto napsal(a):


> They have command line options. For all models of Digi 002/003 family, the
> executable has an option for the numerical ID of sound card.
> 
> ```
> Usage:
>    snd-firewire-digi00x-ctl-service CARD_ID
> 
>    where:
>      CARD_ID: The numerical ID of sound card.
> ```

It's better to handle both card number and the card id string. In the latter 
case, the user may create independent environment and use udev or 
modprobe.conf configurations to address the devices. The card number may 
change when the plug-and-play devices are randomly connected / disconnected.

snd_card_new() - third argument.

						Jaroslav

-- 
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.

  reply	other threads:[~2020-07-07 13:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-07 12:56 [RFT] ALSA control service programs for Digidesign Digi 002/003 family and Tascam FireWire series Takashi Sakamoto
2020-07-07 13:15 ` Jaroslav Kysela [this message]
2020-07-08 14:44   ` Takashi Sakamoto
2020-07-08 15:15     ` Jaroslav Kysela
2020-07-14 23:55 ` 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=a322006e-bd58-4dba-f590-855be17a2cdb@perex.cz \
    --to=perex@perex.cz \
    --cc=alsa-devel@alsa-project.org \
    --cc=ffado-devel@lists.sourceforge.net \
    --cc=sbahling@suse.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;
as well as URLs for NNTP newsgroup(s).