Re: [LAD] automation on Linux (modular approach)

Ah. I knew I shouldn't have asked that question. Louigi, I will send you some details offlist it goes like this: Now a fairly long time ago, fortunately, bristol did some stuff with NRP that was basically broken, I put the code behind a run time option defaulting to off. I think I found the issues when I started driving it with an Oxygen8 and got some of these issues but then it was also sending me something other than CC for some controls. The symptoms were either no tracking or totally arbitrary, nervous, random movement of some mapped GUI devices. Those were the nicer symptoms. I won't go into the others. startBristol -juno -activesense 0 -mididbg -mididbg2 -console This will give midi msg debuging if you want to link messages to controller movements, etc. Louigi, I will send you some details offlist. Nick. "we have to make sure the old choice [Windows] doesn't disappear”. Jim Wong, president of IT products, Acer Date: Wed, 24 Mar 2010 14:01:12 +0300 From: louigi.verona(a)gmail.com To: paul(a)linuxaudiosystems.com CC: linux-audio-dev(a)lists.linuxaudio.org Subject: Re: [LAD] automation on Linux (modular approach) I have had this with Qtractor and Bristol. I will test again, if you say that there should be no problem. I am using M-Audio midi keyboards, they seem to be standard stuff. I will test again, it was a long time ago. On Wed, Mar 24, 2010 at 1:57 PM, Paul Davis <paul(a)linuxaudiosystems.com> wrote: On Wed, Mar 24, 2010 at 6:45 AM, Louigi Verona <louigi.verona(a)gmail.com> wrote: i have no idea. you'd better name some "linux midi applications" that do this. MIDI-handling apps have ZERO idea what kind of physical controller is responsible for causing messages to be sent. _________________________________________________________________ Hotmail: Trusted email with powerful SPAM protection. https://signup.live.com/signup.aspx?id=60969