[LAD] Alsa and multiple bluetooth devices

Hi, I'm wondering if Alsa and bluetooth on Linux support connecting simultaneously to multiple bluetooth devices. I don't want to send the same output to the different bluetooth devices, I rather want a wireless multichannel system (but no need for sample accurate sync). Has anyone ever tried thi

Re: [LAD] How can a LV2 plugin know on what host's MIDI Channel it's on?

On Thu, 16 Oct 2014, Bill Gribble wrote: Here's a vote for anything (lv2 extension, OSC convention, or something else) that makes information about how a host is using a plugin available to the plugin. You can not in any case know that there is not a midifilter outside of the host. Any MIDI

Re: [LAD] How can a LV2 plugin know on what host's MIDI Channel it's on?

On Thu, Oct 16, 2014 at 2:21 PM, Phil CM wrote: > > On 16/10/14 19:02, Bill Gribble wrote: > >> Here's a vote for anything (lv2 extension, OSC convention, or something >> else) that makes information about how a host is using a plugin available >> to the plugin. >> >> This kind of introspection i

Re: [LAD] Fwd: Re: How can a LV2 plugin know on what host's MIDI Channel it's on?

On Thu, 16 Oct 2014, Phil CM wrote: Wow, not even the very channel it's broadcasting on in readable? Does that mean that I have to implement a MIDI channel selection in my synth? There is no way to go around this? A plugin, should take care of it's own midi channel setting/sensing in the same

Re: [LAD] suil error: Unable to open UI library

Looking good ! pX ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev

Re: [LAD] How can a LV2 plugin know on what host's MIDI Channel it's on?

On 16/10/14 19:02, Bill Gribble wrote: Here's a vote for anything (lv2 extension, OSC convention, or something else) that makes information about how a host is using a plugin available to the plugin. This kind of introspection is useless for most plugins, but those that need it can't get the

Re: [LAD] How can a LV2 plugin know on what host's MIDI Channel it's on?

Here's a vote for anything (lv2 extension, OSC convention, or something else) that makes information about how a host is using a plugin available to the plugin. This kind of introspection is useless for most plugins, but those that need it can't get the information any other way. In MFP [1

Re: [LAD] Fwd: Re: How can a LV2 plugin know on what host's MIDI Channel it's on?

On Thu, Oct 16, 2014 at 1:44 PM, Phil CM wrote: > > I think you're confused. The host doesn't put a plugin on a MIDI channel. > It delivers MIDI events to the plugin which might be on any channel. > > But in Qtractor I do have a choice of what MIDI channel (or any/omni, >> for that matter) I'm

Re: [LAD] Fwd: Re: How can a LV2 plugin know on what host's MIDI Channel it's on?

On 16/10/14 18:19, Phil CM wrote: Forwarded Message Subject: Re: [LAD] How can a LV2 plugin know on what host's MIDI Channel it's on? Date: Thu, 16 Oct 2014 13:16:38 -0400 From: Paul Davis To: Phil CM On Thu, Oct 16, 2014 at 12:59 PM, Phil CM

[LAD] Fwd: Re: How can a LV2 plugin know on what host's MIDI Channel it's on?

Forwarded Message Subject: Re: [LAD] How can a LV2 plugin know on what host's MIDI Channel it's on? Date: Thu, 16 Oct 2014 13:16:38 -0400 From: Paul Davis To: Phil CM On Thu, Oct 16, 2014 at 12:59 PM, Phil CM > wrote: On 16/10/14

Re: [LAD] How can a LV2 plugin know on what host's MIDI Channel it's on?

On Thu, Oct 16, 2014 at 11:42 AM, Phil CM wrote: > Is there a way to retrieve this info (and others, ideally) from the host, > thus removing the need for a "midi channel" control port? > I think you're confused. The host doesn't put a plugin on a MIDI channel. It delivers MIDI events to the plug

[LAD] How can a LV2 plugin know on what host's MIDI Channel it's on?

Is there a way to retrieve this info (and others, ideally) from the host, thus removing the need for a "midi channel" control port? Also, is there a way to tie the "volume" controller of the host (in Qtractor's case, the volume fader of the mixer strip) to one "volume" control port of the plug

Re: [LAD] suil error: Unable to open UI library

On 16/10/14 14:08, Cedric Roux wrote: On 10/16/2014 12:53 PM, Phil CM wrote: Oh Mon Dieu, it works. Cedric, thank you very much for your light. All those infos are exactly what I needed ; Those atrocious begginer errors were hard to spot, let alone correct, and I find it hard to thank you enoug

Re: [LAD] suil error: Unable to open UI library

On 10/16/2014 12:53 PM, Phil CM wrote: Oh Mon Dieu, it works. Cedric, thank you very much for your light. All those infos are exactly what I needed ; Those atrocious begginer errors were hard to spot, let alone correct, and I find it hard to thank you enough to have taken the time to put me back

Re: [LAD] suil error: Unable to open UI library

On 16/10/14 11:14, Cedric Roux wrote: remove "static" for declaration of instantiateSO_404, both in kis.h and kis.c. (...) Then, in mix.h you should add the 3 lines: #ifdef __cplusplus extern "C" { #endif near the top (let's say after all the #include lines) and at the very end, the 3 lines:

Re: [LAD] suil error: Unable to open UI library

On Thu, Oct 16, 2014 at 6:14 AM, Cedric Roux wrote: > Maybe those more familiar with the lv2 bloat > what do you consider "bloated" about LV2? is this in comparison to some other plugin API? or what? ___ Linux-audio-dev mailing list Linux-audio-dev@li

Re: [LAD] suil error: Unable to open UI library

On 10/15/2014 08:24 PM, Phil CM wrote: suil error: Unable to open UI library /usr/local/lib/lv2/kis.lv2/kis_gui.so (/usr/local/lib/lv2/kis.lv2/kis_gui.so: undefined symbol: _Z17instantiateSO_404PK15_LV2_DescriptordPKcPKPK12_LV2_Feature) remove "static" for declaration of instantiateSO_404, both