Clear all


2 Posts
2 Users
Active Member
Joined: 2 years ago
Posts: 5
Topic starter  


First of all congratulations for this very promising new version 1.8!

I would like to tell you about the problems I am having with MidiBox. Many posts talk about this subject and many have helped me to solve different problems. There are still a few left in my opinion.

To begin with, what is the button above the latch button really for (completely to the left of the layer line). Normally it is used to disable all midi inputs. Which is true...except in some cases...
Let's take an example :

I load the "BPM DRUM Airwave Trance Kit" patch for example. I select the trigger note (C1). I select the type of Midi source in Midi In mono latch and I click on the latch button. I press C1, cool the loop starts. Oh damn it launches on pitch C1. I enter MidiBox and change the Note -> Coarse option. I press C1 again, the loop launches on the root note (C3 in the example) and stays latched. Now I would like to play with all the rest of the keyboard .... oh damn, the midi loop starts again from the beginning each time a note is pressed! Not cool... so I decide to deactivate (!) the layer by selecting the famous button at the top of the latch button (which deactivates the layer)... I finally press a note to play and...? and much the same, the midi loop starts again from the beginning....
The problem is the same when changing the midi channel. How come when my keyboard is set to channel 1 continues to play the layer that I just set to channel 2 or None?? (Namely, this only happens when the loop is playing).

It would really be necessary that, in the case of a BPM DRUM type patch, all of this should be predefined. Unify is positioned on the Live! And that's what differentiates it from a DAW. And that's why people bought it. The Live! (and yes there are still musicians who use a keyboard rather than buttons to make music...).

Reading through the forum threads I saw how to do it. Okay you need:

Select the trigger key of the layer, exclude this note from all the other layers (we will have understood why) and ESPECIALLY do not forget to modify the trigger note ALSO in the transport bar!! The whole trick is there! With this setting everything works great! But........

A BPM DRUM MidiBox layer set to the C6 key (with all the settings I just mentioned)
Another BPM BASS style bass layer set on the C1 key in order to differentiate the triggering of the Drum loop (C6) and that of the bass (C1).... In this case, what should be set in the keys of release of the transport bar? C1 or C6?

As I was saying, Unify stands out from DAWs for its ease of doing Live, I find it absolutely brilliant to be able to stack different patches so easily! it's really super ! But what a pity for the BPM parts! It wouldn't take much for everything to be perfect!
Imagine, BPM DRUM on C1, BPM BASS on D1, BPM PLUCK on E1 etc that we could start and stop independently! Leaving all the remaining space on the keyboard for playing. Everything could be done automatically when loading a new patch via an additional option in the right click menu, just choose the note...)

In addition, thanks to this new possibility, the random selection via the dice could no longer choose a patch among all the others whatever the category (not very useful in the end) but could choose a BPM DRUM for the drums, a BPM BASS for the bass , a BPM PLUCK (etc..) for random accompaniment! This would generate a unique companion set with each die roll!

There it is ! Thank you for your response and review.

Illustrious Member Admin
Joined: 4 years ago
Posts: 4367


Clicking the green "MIDI light" at the left end of each MIDI/INST layer disables incoming MIDI to that layer; it does not disable the layer itself.

Depending on how MIDIBox has been set up, it may play whenever Unify's transport runs. This could explain why it sometimes plays even though you have changed the MIDI channel filter for the layer it is on.

You claim "Unify is positioned on the Live! And that's what differentiates it from a DAW. And that's why people bought it." That may be true in your case, but to be honest, we don't know how Unify's user base divides among live players, DAW users, etc. We intend to conduct surveys to find out.

Finally, you seem to be saying "Unify has such potential, but it needs to do X, and Y, and Z, and..." In today's livestream I showed the 69 pages of such suggestions which we have received since Unify launched two years ago, and how many have already been addressed. Please be patient; we will get there eventually. It is not lack of ideas that holds Unify back; there are many more prosaic factors at work.