Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: ralfbeck1@gmx.de
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] rawmidi.c Set a name for a newly allocated rawmidi substream
Date: Thu, 08 May 2014 22:08:27 +0200	[thread overview]
Message-ID: <536BE43B.90603@ladisch.de> (raw)
In-Reply-To: <536B1F1B.5070205@gmx.de>

Ralf Beck wrote:
> Am 07.05.2014 19:39, schrieb Clemens Ladisch:
>> Ralf Beck wrote:
>>> Rationale: Bitwig Studio (and possibly other rawmidi clients) enumerate the Midi I/Os by substream names. With the current rawmidi implementation, the name is an empty string and only the USB mididriver changes it to a meaningful value after allocation.
>>
>> Many RawMIDI devices have only one substream, or multiple substreams that are merged into one port. For these, separate substream names do not make sense.
>
> Any having no substream name at all makes more sense?

The device itself already has a name.

Apparently, Bitwig has not been tested with any driver except snd-usb-audio.

>>> This patch sets a default substream name of the form "somename x-y-z"
>>
>> The ID string is not meant to be a name.
>
> Would it be acceptable, if i remove the ID string and only return x-y-z ?

No; you should use the device name or something like that.

But the substream name buffer is rather short; a better idea would be to
fix all rawmidi drivers to set the substream name(s) to the appropriate
value.

> Other than the alsa developers i would call creating rawmidi substreams, but not
> assigning a name to them a bug.

For most drivers, substreams do not have a logical identity separate
from the device.


Regards,
Clemens

      reply	other threads:[~2014-05-08 20:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07 17:24 [PATCH] rawmidi.c Set a name for a newly allocated rawmidi substream Ralf Beck
2014-05-07 17:39 ` Clemens Ladisch
2014-05-08  6:07   ` Ralf Beck
2014-05-08 20:08     ` Clemens Ladisch [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=536BE43B.90603@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=ralfbeck1@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