From mboxrd@z Thu Jan 1 00:00:00 1970 From: Clemens Ladisch Subject: Re: [alsa-devel] [RFC] MIDI over Bluetooth Low Energy Date: Thu, 1 Oct 2015 13:53:38 +0200 Message-ID: <560D1EC2.8010603@ladisch.de> References: <560D1893.6040509@ladisch.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-bluetooth-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Felipe Tonello Cc: alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org, linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: alsa-devel@alsa-project.org 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? >>> 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. Regards, Clemens From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [alsa-devel] [RFC] MIDI over Bluetooth Low Energy To: Felipe Tonello References: <560D1893.6040509@ladisch.de> Cc: alsa-devel@alsa-project.org, linux-bluetooth@vger.kernel.org From: Clemens Ladisch Message-ID: <560D1EC2.8010603@ladisch.de> Date: Thu, 1 Oct 2015 13:53:38 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: 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? >>> 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. Regards, Clemens