alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: AlGrenadine <a.granvaud@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: opening rawmidi on user ports
Date: Wed, 13 Mar 2019 14:48:51 +0900	[thread overview]
Message-ID: <20190313054850.GA13393@workstation> (raw)
In-Reply-To: <9c82e740-a327-3809-875c-3eb4f01945e8@gmail.com>

Hi,

On Tue, Mar 12, 2019 at 05:19:38PM +0100, AlGrenadine wrote:
> I use btmidi-server from the bluez stack, which creates user ports to send
> and receive midi via bluetooth.
> I can't manager which parameter string i must provide to snd_rawmidi_open
> function, can you help ?
> 
> (of course the user ports don't appear in amidi -l)
> I only have a client and port ids (128:0) when using aconnect -l

As long as reading code of 'btmidi-server'[1], it uses ALSA sequencer
interface. You need to use ALSA sequencer APIs instead of ALSA rawmidi
APIs. Some tools will assist your work; 'aseqdump' and 'aplaymidi' in
'alsa-utils' repository[2].

[1] https://github.com/oxesoft/bluez/blob/midi/tools/btmidi-server.c
[2] https://git.alsa-project.org/?p=alsa-utils.git

Regards

Takashi Sakamoto

  reply	other threads:[~2019-03-13  5:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12 16:19 opening rawmidi on user ports AlGrenadine
2019-03-13  5:48 ` Takashi Sakamoto [this message]
2019-03-13 13:37 ` Clemens Ladisch
     [not found]   ` <513b5f87-3bb9-8147-b249-75aa4a100341@gmail.com>
2019-03-13 17:29     ` Clemens Ladisch
     [not found]   ` <1a48e120-6971-832c-a918-3c5516d5bcab@gmail.com>
2019-03-14  8:59     ` Clemens Ladisch

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=20190313054850.GA13393@workstation \
    --to=o-takashi@sakamocchi.jp \
    --cc=a.granvaud@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    /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).