Twister : Next Bank

Twister : Next Bank

Hi,

I’m quite new to adjusting midi settings on midi devices.

I was wandering if you could adjust, on the Midi Fighter Twister, a knob
switch to make it switch to the next/previous bank of encoder settings
when pressed (or released) ? Maybe with a plugin ?

I find the side button a bit harder to switch fast between different banks.

Thanks,
L.

Not for the next/prev action directly but you can assign the regular banks instead

e.g.: bank 1 takes you to bank 2
bank 2 has 2 buttons that take you back to 1 or 3
etc

You can find the specific CCs you need to use in the User Guide.

Thanks !

In found this in the manual :

I.e. When changing from Bank 1 to Bank 2 the Midi Fighter Twister will send a
Ch4 CC0 Note Off followed by a Ch4 CC1 Note On.

But I can’t seem to set these in the MidiFighter Utility. On the knob, I guess I have to
set the switch action type to CC toggle. But I can’t seem to set a “on_press” or “on_release”
state..

Set it as CC Hold, you don’t need press/release states.

With hold after you release it the device will be in the new bank so if you are now on let’s say bank 2, you’ll have the bank 1 and bank 3 CCs assigned to those controls.

If I set the following on a knob :

Switch Action Type : CC Hold
Switch MIDI Channel : 4
Switch MIDI number : 1

Which, from what I can figure out from the manual, is accessing Bank 2 ..

.. and press the knob, in the Midifighter Utility the bank changes to Bank 2, but it does not happen on the
Twister itself ?! The lights do not change …

If I check the log I get the following :

Pressing the assigned knob :
Received Message: b3 01 7f
Received Message: b3 01 00

Pressing the Left Side Button 1 Function (which is assigned to go to Bank 2) :
Received Message: b3 00 00
Received Message: b3 01 7f

Pressing the “Bank 2” button in the Midifighter Utility :
Sent Message: 93 01 7f
Sent Message: 93 01 7f
Sent Message: 93 01 7f
Sent Message: 93 01 7f

Trying to wrap my head arround it … It seems that I still send the wrong message to the device, compared to when pressing the side button. But can’t seem to have many options in the Midifighter Utility to send the correct message.

Just to be sure, did you send new settings to the Midifighter after you changed Midi channel and CC number for the encoders?

When testing this, I always just changed one or two settings, and sended these to the midifighter.

The firmware is up to date (23 june 2016).

A little note also;

When pressing the knob that has assigned the midi channel and number mentioned before, the bank only changes
in the Midifighter Utiliy as mentioned. When then pressing the Bank 2 button in the Midifighter Utility, the Midifighter itself won’t update also anymore.

Below is a WeTransfer link to a quick and dirty video (30MB) where you can see what’s happening.

hi mate, did you get this going eventually? it’d be really good to be skip banks via midi…

Working

I have it working from an external source, firing custom strings for each bank. The side bank buttons and bank switching strings are my only real complaint about the Twister.

Basically each bank has its own midi string (for better or for worse) You can sniff the string for each bank with a midi monitor. Its nice that you can jump from bank 1 to 3, or 4 to 2, but more often than not I’d just prefer a next/previous option… which seems to not be possible, unless there is an undocumented string Im missing. Not sure I want to try firing strings till I get anywhere with that.

Hi everyone !
New here, just received my MFT :slight_smile:

I was wondering the same things.
My goal would be - for now - to only use bank 1 and 2 and using the lower left switch button for that.
So it would give :

  • Bank1 Lower Left Button Switch : Go to Bank 2 (CC Hold - Ch4 - CC1)
  • Bank2 Lower Left Button Switch : Go to Bank 1 (CC Hold - Ch4 - CC0)

As previously mentioned, the Midifighter utility is reflecting the bank switch but not the device…

Building a small app in Max would be easy, just to route these specifics signals, but achieving this without additionnal app would be better :wink:

Any advice is welcome

After my first test… In fact a simple Midi patchbay sending back the MFT message to itself is enough… But building a Max app for that ! ? :wink: