Welcome to %s forums

BrainModular Users Forum

Login Register

Midi learn only from rack

I need help on a Patch
Post Reply
sm_jamieson
Member
Posts: 554
Contact:

Midi learn only from rack

Unread post by sm_jamieson » 27 Apr 2026, 02:51

Hi.
I have a midi bus going to each of my racks, (the top patch in each rack has a midi from bus connected to a midi out)
so that all lower patches in the rack get the midi data for that rack.
I want to do midi learn only on the midi data in that rack, but Usine midi learn is global.
Is there any way to have rack specific midi learn ?

If not, this may be something for HH7.

Thanks,
SImon.

BM2F
New member
Posts: 8
Contact:

Unread post by BM2F » 27 Apr 2026, 12:18

Hello,

There is no MIDI Learn function specific to racks.
However, for each MIDI Learn, you can specify the device.

As for using MIDI In/Out modules, this allows you to retrieve data within patches. This enables more precise and potentially complex control than simply mapping a MIDI Learn, but it requires patching.

MIDI Learn allows for quick and flexible setup.
In some cases, it can be difficult to manage—for example, if a device keeps sending data. However, you can simply turn off the corresponding device (in Usine).


Happy patching !
Baptiste

sm_jamieson
Member
Posts: 554
Contact:

Unread post by sm_jamieson » 27 Apr 2026, 22:42

Ok thanks. I wonder if you could create a fake device to take midi from the bus. After all a device is also a patch. The point to remember is the device is not per workspace.

User avatar
oli_lab
Member
Posts: 1262
Location: Brittany, France
Contact:

Unread post by oli_lab » 28 Apr 2026, 00:26

Hi,
you can use clusters, global arrays or busses !
do the midi learns once and for all (here they are patched from CC1 to CC8
++
Olivar
see examples :
Attachments
learns to GA.wkp
(215.86 KiB) Downloaded 8 times
learns to busses.wkp
(204.45 KiB) Downloaded 6 times
learns to clusters.wkp
(252.91 KiB) Downloaded 6 times
http://oli-lab.org

Win11 Ryzen9/32GB RAM - RME MADIFACE - SSL alpha link 4-16 - OSC capable interfaces

follow OLI_LAB adventures on Mastodon
@olivar_premier@mastodon.social

sm_jamieson
Member
Posts: 554
Contact:

Unread post by sm_jamieson » 29 Apr 2026, 03:19

Thanks. I'll have a look at those.

I did some experiments with fake devices (a patch receiving from a midi bus dropped into the devices area of a rack).
If the real midi input devices are removed, you can actually midi learn from the fake devices but they have no real device behind them
and the the wkp file they are stored as
Tdevice name =
instead if something like Tdevice name=FOCUSRITE USB MIDI

If you learn from another fake device in the same way, it is also stored without a name so they are really clones of each other,
both with device name of "nothing", and both sliders move together.

But in principle if there was a way to give the fake device a fake external device name, this could be supported by Usine.
Note - the input device patch as seen in the devices section may be called "IN FOCUSRITE USB MIDI" but the real
device behind it is called "FOCUSRITE USB MIDI" - they are not the same thing.

If the midi was sent out and looped back in via a virtual midi cable, of course this would work, since then there is a real midi device.

Interesting anyway.

grego mondo
Member
Posts: 466
Location: 22110 Rostrenen
Contact:

Unread post by grego mondo » 29 Apr 2026, 10:18

Did some tests too over here :

If you create a midi in device getting a midi bus (called "virtual" for eg) the midi learn goes the same way with no name

but if you add the midi bus "virtual" to IN MIDI LAN & BRIDGE then it's learned with the name "MIDI LAN & BRIDGE"

Then if you plug a real midi device (let's say "MPK MINI") and put the "virtual" bus in it
As long as the MPK MINI is plugged to the computer all the learn using "virtual" values go through it and are learned with its name (MPK MINI)
Then if you unplugged the MPK MINI all the learns still works and you can make new learns ...
I added a pass flow between "virtual" bus and "MIDI TO USINE" in the MPK MINI input device so I can turn the "virtual" going through "MPK MINI" on and off
it means you need to have unused controllers that you'll plug once and then put back in your drawer ...
En attendant cordialement l'apocalypse ... 100% Usine !!
https://lesformesdufond.kaz.bzh/grego-mondo/
PC i7 2.6Ghz - Win11 / RME Fireface UFX
Tubas / Serpent / Music Box
Interfaces Midi / OSC / DMX

sm_jamieson
Member
Posts: 554
Contact:

Unread post by sm_jamieson » 30 Apr 2026, 10:51

Ok, so why not use a virtual midi port program (e.g. loopmidi) to create the midi input devices instead of needing real devices, i.e. unused controllers ?

grego mondo
Member
Posts: 466
Location: 22110 Rostrenen
Contact:

Unread post by grego mondo » 30 Apr 2026, 13:06

The way I do in my workspace is :
I use all midi learns to feed a big Gloabal Array
and then, in each rack, I get the Global Array value(s) wich I need to control my faders and knob
eg something like choosing in a combo box the first instrument : Tuba > all my faders are feeded from values 1 = volume, 9 (1+8) reverb, 17 (1+16) delay
choosing the second instrument : Serpent > all my faders are feeded from values 2 = volume, 10 (2+8) reverb, 18 (2+16) delay

(this way I can also feed one value in the GA from 2 separated controllers.


Here I just tried some stuffs to help find a solution to your problem :-)
En attendant cordialement l'apocalypse ... 100% Usine !!
https://lesformesdufond.kaz.bzh/grego-mondo/
PC i7 2.6Ghz - Win11 / RME Fireface UFX
Tubas / Serpent / Music Box
Interfaces Midi / OSC / DMX

sm_jamieson
Member
Posts: 554
Contact:

Unread post by sm_jamieson » 30 Apr 2026, 18:03

Yes thanks. I like the idea of midi learns into a global array, like a sort of midi patchbay.

We need a new forum section "Usine Hacking" :-)

Post Reply

Who is online

Users browsing this forum: No registered users and 15 guests