Looper's Delight Archive Top (Search)
Date Index
Thread Index
Author Index
Looper's Delight Home
Mailing List Info
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Date Index][Thread Index][Author Index]

RE: Mobius Baffling Phase 3

I don't want to discourage anyone from getting the UnO chip, but it isn't clear to me that this is required to use Mobius under Live.

Mobius will simply ignore any event that isn't bound to something.  So the FCB could be puking out hundreds of random events along with the notes and it won't matter, as long as Mobius is not programmed to respond to those other events.  Where it will mess up is with the MIDI learn feature in the binding window.  This will track whatever the most recent MIDI event received was, so if the CC comes after the Note, then it will have the CC.  If that is what is happening you will need to do what Rainer suggests and disable MIDI lean and enter the notes manually.

Now how Live responds to these extra events is another matter.  You'll also need to make sure that Live is not programmed to respond to these CCs.  I'm pretty sure Live will just ignore MIDI events it does not recognize.  I doubt that it will fail to pass a Note Off to Mobius just because it receives a CC after the Note On.  Does anyone have proof of that?

There are only two situations where I can imagine these extra CCs causing problems.  First, Live gets confused by them and drops events that should have been sent to the track.  If the dropped event was a Note Off, then Mobius will go into long-press behavior and reset the loop
after 1/2 seconds of recording.  Second, the FCB tap tempo "feature" causes the FCB to not send Note Off.  That's more likely but I've
never witnessed it.  Can anyone say for sure that when FCB tap tempo is active that it will only send Note On events and drop Note Off events?
None of the documentation I can find state that.

I believe you said that this was working in Mobius standalone but not under Live correct?  If so I don't think the FCB is the problem.

Thanks,
Jeff

From: RP Collier [skeptikalist@gmail.com]
Sent: Saturday, April 14, 2012 12:21 PM
To: Loopers-Delight@loopers-delight.com
Subject: Re: Mobius Baffling Phase 3


On Apr 14, 2012, at 12:21 AM, Kevin Cheli-Colando wrote:

The CC value that is sent seems to change according to
the physical pedal and not the note assigned (I assigned the same note
value to two pedals and got different CCs depending on which pedal I
pressed).

Did someone say there is a chip that eliminates this problem on the FCB.



Below is stuff from the FCB yahoo list.


BobC



>>>If you’re using an NOTE only patches be aware that the FCB1010 will send out CC#0 regardless of whether you have it ticked or not. That’s the “tap tempo” function. Which if you look it up, may be where your “pitch bend” CC is coming from...If you also have MERGE enabled on the FCB1010, disable it, OR the FCB1010
will turn around and send ALL that data back to Live. From the sound of the
Mute buttons flashing, that sounds like MERGE is enabled.

If you send notes on where the time between presses is less than 1270ms, you
get a tap tempo CC message.<<<<


>>>I have had awesome success using the FCB1010 with Ableton Live. It may not be necessary, but the consensus seems to be that the UnO e-prom upgrade fixes lots of issues with the FCB1010 so I went ahead and upgraded to it. Have never had any issues so I recommend it.

I purchased the UnO e-prom chip and installed that. It can be found here:http://www.ossandust.be/index.php

I also use the Ripwerx editor to do the actual programming of the pedal - it is simpler. That tool can be found here: http://www.ripwerx.com/
<<<<


----

>>Without changing the firmware you can also specify a global channel for the NOTE and only react to that channel, or you can remap the global CC’s to send to an unused channel. Either one will work as well.
I do believe if you put a UnO chip in you can disable the Tap Tempo….<<<<