Return-Path: MIME-Version: 1.0 In-Reply-To: <560D1EC2.8010603@ladisch.de> References: <560D1893.6040509@ladisch.de> <560D1EC2.8010603@ladisch.de> Date: Thu, 1 Oct 2015 12:59:14 +0100 Message-ID: Subject: Re: [alsa-devel] [RFC] MIDI over Bluetooth Low Energy From: Felipe Tonello To: Clemens Ladisch Cc: alsa-devel@alsa-project.org, linux-bluetooth@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Clemens, On Thu, Oct 1, 2015 at 12:53 PM, Clemens Ladisch wrote: > Felipe Tonello wrote: >> On Thu, Oct 1, 2015 at 12:27 PM, Clemens Ladisch wrote: >>> Felipe Tonello wrote: >>>> I am planning to start the support of MIDI BLE profile[1]. >>>> >>>> I suggest two main goals: >>>> * To be transparent to applications, i.e., use rawmidi and sequencer >>>> ALSA interfaces to interact. >>>> * To support peripheral and central BLE roles. >>>> >>>> My question is: what is the best way possible of doing it? >>> >>> Just write a (user-space) sequencer client. >> >> But this will limit to seq interface only. It will not be available >> via rawmidi interface, right? > > Yes. And why would this be a problem? None besides the obvious fact that rawmidi interface will be out. > >>>> They all have the problem of context switching between bluez plugin >>>> and alsa midi driver. >>> >>> Why would context switches be a problem? >> >> It is just too much travelling around. > > It hasn't been a problem with any other MIDI application. It can be for MIDI Multidimensional Polyphonic Expression (MPE)[1] . [1] https://docs.google.com/document/d/1-26r0pVtVBrZHM6VGA05hpF-ij5xT6aaXY9BfDzyTx8/edit Felipe