Welcome to %s forums

BrainModular Users Forum

Login Register

Is there a wiki or tutorial on how MIDI works in Usine?

General Discussion about whatever fits..
Post Reply
User avatar
parityflux
Member
Posts: 83
Location: Tucson, AZ USA
Contact:

Unread post by parityflux » 24 Mar 2014, 19:14

I was reading the patch thread: Separate the input from two MIDI devices in one patch? while I was debugging MIDI issues in one of my workspaces, and it occurred to me that I don't have a clue how MIDI works from a device perspective or within a rack. I'm missing something, I'm just not sure what. It is very confusing and not intuitive to me. I've read the manual and skimmed over the patch guide several times, I'm wondering if there's a real solid explanation of the flow of MIDI in Usine. In all the other software I've used, I could be really specific about actual device ports, but it seems that once MIDI flux enters into a rack, there's no more port support and you have to do gymnastics to utilize the streams from more than one device (e.g. a MIDI keyboard controller + an external control surface).

This is by no means a complaint, I just want to "get it". I just love this software to death. I'm a huge fan. It is the best piece of music software I've owned since Bars&Pipes Pro on the Amiga!

-john

ceasless
Member
Posts: 330
Contact:

Unread post by ceasless » 24 Mar 2014, 19:53

You might try experimenting with MIDI buses directly in your MIDI device patches. This should keep them separated.

There is an 'Additional midi input' module, which senso says is on it's way. Not for documentation, but for 'midi 2', 'midi 3', etc. Rather than the 'midi 1' that we are stuck with no matter how many input devices we stuff in the top.

Hopefully nay or someone can confirm this.


But I'm afraid that even this new module is not going to do necessarily make the experience seamless.

I might try helping often, but I don't consider myself an expert. If anyone has a different flow for the same concept, please let me know.

(This is for audio, rather than midi, but probably still relevant unless something is changing with regard to naming.)

I was just fiddling around in the 'device patch' interface today and wishing that midi inputs would be named instead of being re-numbered in each rack.

The name of the output device is 'Stereo Out'. This is accurate in that my mixer only has two outputs. The input device for the same mixer says 'Stereo In', even though there are eight inputs. This is already confusing. I'd prefer for the audio device in Usine to be named after the audio device in real life.

If I want to use channel two on my mixer, I'd also like for the audio input to Usine to be named CH2. I'd like to be able to select this from a menu when (or after) I drop audio inputs into a patch (after the 'To Usine' module exists in the device patch of course).

Right now I have to add extra audio inputs into my patch until I get to the number that is connected (for my third channel, that's two extra audio inputs). I need to leave these audio inputs in there or else the audio input switches back to 'audio 1'.

Or I can wire 'CH3' to 'audio 1', but the device patch is global, so this actually just breaks things.

Are buses the only answer to having 'named pipes' that are consistent across a workspace? It makes some sense yet I can help but wish for a more intuitive ground level that wouldn't cost latency I might prefer to use elsewhere.

User avatar
nay-seven
Site Admin
Posts: 5684
Location: rennes France
Contact:

Unread post by nay-seven » 24 Mar 2014, 21:01

This additional midi in is a part of the additional audio in and it's present in the current version
here an example
Image

Ceasless, about Devices, have you read the new chapter in the manual v 03...?
you'll find you can create your device , save them as set to use later..?
Image

ceasless
Member
Posts: 330
Contact:

Unread post by ceasless » 24 Mar 2014, 21:27

Oops. I didn't even see that the manual was updated. Thanks nay.

User avatar
parityflux
Member
Posts: 83
Location: Tucson, AZ USA
Contact:

Unread post by parityflux » 25 Mar 2014, 20:49

Thanks for some direction. I'm going to start a new workspace and really dig in to see what's going on.

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 93 guests