That was it!!

Yes, I was exposing the Mobius VST plugins so the "sliders" were showing for
each script or parameter I wanted to map to. Then I used Abletons mapping
capability to associate an incoming FCB1010 signal to an exposed Mobius
script-slider. This works just well enough to keep trying.

Opening a new midi track dedicated to take the midi signal from the FCB1010 and
have that output to Mobius track works well, just like the standalone Mobius.



--- In zonemobius@yahoogroups.com, Jeff Larson <jeff@...> wrote:
>
>
> > The longpress does nothing, and from Ripwerx, I can see the same 4
> > lines (see "with Ableton" below).
>
> I still don't understand how Ripwerx fits into this, it's an FCB1010
> editor,
> does it also have some kind of MIDI stream monitor? How have you
> inserted
> that between Ableton and Mobius?
>
> > I feel like I'm closer, but longpress still no worky, maybe because
> the
> > mapped slider (Ableton) for the pedal now takes two pedal pushes to
> make
> > a full cycle (full cycle = goes from left to right and back to left).
> > With one quick pedal up/down, I get Record, then a short time later
> > it resets like it thinks it was a long press.
>
> Oh, are you exposing functions as plugin parameters then trying to bind
> MIDI to the plugin parameters in Ableton? There should be a way
> to make that work, but for hosts that support direct MIDI connection
> it's usually easier just to pipe MIDI into Mobius and do the MIDI/
> function
> association in Mobius rather than the host. All the bindings you made
> in standalone mode should still work. Setup a MIDI track that receives
> from the FCB device, then send the output of that track to the audio
> track containing Mobius.
>
> If you're doing *both*, routing MIDI into Mobius and trying to map
> MIDI to a plugin parameter in Ableton that would explain the double
> messages.
>
> Jeff
>