BrainModular

Hi all.

I was used to see that Sysex connector on "Midi In" modules and not understanding the use of it.
But it does not exists anymore and now I can see there an "Unpack" switch!
I did not find any explanation about it in the doc...
I'm sure it's very useful, I would like to understand! I've tried ON and OFF, without noticing an explicit difference...
Can someone explain it to me?

Thanks!

I forgot to explain the "unpack" parameter in the midi in module...
The Unpack option transforms a polyphonic signal to a monophonic one.
For example, if two midi note arrive at the same time, Usine delays the second note a little to always create monophonic signal.
With this new midi flow, you can apply any math transformations you want because it's almost like a normal data flow.

Ok! I understand!
I'll try to make good use of that.

Thanks.

Nice idea, Olivier. I thought it had something to do with sysex, like unpacking all the code between the sysex start and end messages. Like Vincent, I'll have it in the back of my head to see whether a good idea comes along that makes use of it.

Vincent wrote:Ok! I understand!

Hem... well... In fact, I don't.
Does it mean that when switching unpack on, we don't have midi arrays anymore (except for note# and note velocity)? No need to make loops in scripts? should I rewrite them to increase there speed?

Olivier,

Will it be possible to delete all my "looping scripts" when using the unpack feature of the MIDI In?

not really, if it works well with your script keep them!
The unpack option can produce a kind of very short arpeggio effect, if you play a big chord.