missing midi interfaces

[woodslanding]

One of the few things I really miss about bidule was the way it handled midi interfaces.

Basically, for plogue, each midi interface had its own object in the structure. Any interface could be placed anywhere in a workspace. If the interface wasn't found, it turned red, and obviously didn't function, but it was still there.

So every time I used a different keyboard, I could just create an object for it, and cable it in as well. When I switched back to the original instrument, it just worked. Every keyboard I'd ever used in a workspace would always work in future with no setting changes. Also, I didn't have to worry about which channel any of my keyboards was set to. Since they were each on a seperate input buss, I could take data from a specific keyboard, rechannelize it immediately, and route it where I wanted. I didn't even have to set up midi when I upgraded the software.

Usine's approach isn't terrible, but every time I work on my laptop away from my keyboard, I have to go back in and manually set up the midi interface settings again.

Not a big issue, but thought I'd mention it while Olivier is working on the big new version.....

-e

[bsork]

What about adding an input to "num virtual" on the Midi Input module, or another input that selects between one or all virtual inputs? Together with different setups, it should give the same functionality, if I've understood you correctly.

[woodslanding]

There is a way to get data from a midi interface that is not recognized in the setup window??? I'm confused.

The problem is that my interface gets deselected in [menu-->setup-->global setup>--midi input] if it wasn't plugged in the last time I ran usine. Don't the virtual inputs represent what's in that list??

[bsork]

Create different setups and switch between depending on what you have connected. Remember that all the virtual in- and outputs can in fact be the very same physical in- and outputs if you want. That goes for both audio and midi.

If I take my own equipment as an example, I have three external midi inputs, Axiom internal and it's midi in plug + the Pro24. Both Axiom and Pro24 also have midi outs. For sending midi to Reason I'm also running Maple Midi with four virtual inputs and four virtual outputs. When I'm using the laptop on it's own with asio4all for programming, I can use the Maple in- and outputs to create as many virtual connections as I've created in the "real" setup, and I only need one of each type. (Remember that it's easy to create midi loops with Maple and other loopback programs!). BTW, you can probably also use the internal soundcard's midi driver for this.

[woodslanding]

maple midi?? I'll check into it.

Thanks!
-eric

[gurulogic]

There are some VST solutions that allow you to directly pipe MIDI into Usine. For example the TobyBear MId2VST Plugin or jthalamus.

I need to use these because I can find no other way to manipulate controller data from external hardware before it gets assigned to a Usine control... I guess that would be a beef of mine. Once a MIDI input is selected in Usine, there is no way to redirect the midi controller data received on that input to not immediately take control before I get a chance to route it to a midi input module and manipulate it pre-miditousine module.. Unless I am missing something?

[nay-seven]

@gurulogic :

have you try to use the " send midi to Usine " module" ( in in /out ) , then use midi filter or/and canal change could do the job..?

[woodslanding]

Actually, I manipulate all my midi before it gets assigned to usine controls.

I bring in all midi on one track, and route it all around usine from there. None of the channels that contain controls have midi inputs--they get their midi from busses from the midi input track.....

works fine. But at the moment, I have to go into preferences and reset the midi source ports every time I start up.

But, responding to nay-seven--if the midi port is not correctly set in preferences, no midi will come in anywhere in usine!!

-e

[nay-seven]

@woodslanding : was answering to gurulogic , and maybe i don't understand his answer but he don't seem to refer to the same problem..?

[gurulogic]

@gurulogic :

have you try to use the " send midi to Usine " module" ( in in /out ) , then use midi filter or/and canal change could do the job..?

No, this does not seem to prevent midi from going directly from the selected input in the global setup to Usine.

For example,if I select my midi controller input in global setup, then I create a fader and midi learn it on channel 1.
Then I make a midi input in a patch and filter to just CC and transform the midi to channel 8 and connect that to a Midi to Usine module and the fader is still controlled on channel one. Then if I unlearn the fader and learn again, the fader still learns on channel one, not channel eight as I would like.

Also, I have a strange problem with two midi monitor VST's I use . If I connect them directly to a midi input module that is also connected to a Midi to Usine module and input a midi CC, they begin a really nasty feedback loop so this is either a bug with both VST's, or Usine.
Maybe somebody can check?
http://thepiz.org/pizmidi/pizmidi.zip (MidiMonitor) and http://www.rs-met.com/software/freebies ... r_v0.5.zip



>>"@woodslanding : was answering to gurulogic , and maybe i don't understand his answer but he don't seem to refer to the same problem"

Sorry, I am refering to a different problem but I was also suggesting an alternative solution to the original problem with the use of VST plugins that can be placed in your project and directly access your midi ports.

[bsork]

For example,if I select my midi controller input in global setup, then I create a fader and midi learn it on channel 1.
Then I make a midi input in a patch and filter to just CC and transform the midi to channel 8 and connect that to a Midi to Usine module and the fader is still controlled on channel one. Then if I unlearn the fader and learn again, the fader still learns on channel one, not channel eight as I would like.

This happens because Usine first receives the incoming data on channel 1, then the rechanneled data. Not as quick'n'easy, but you can change the assignments in the remote window.

Also, I have a strange problem with two midi monitor VST's I use . If I connect them directly to a midi input module that is also connected to a Midi to Usine module and input a midi CC, they begin a really nasty feedback loop so this is either a bug with both VST's, or Usine.

If I understand you correctly, you create a direct connection between a Midi input and a Midi to Usine module - that will most probably create a feedback loop, at least if you've operating with only one Midi input. I think the output from the Midi to Usine is always received mixed with whatever's coming in on Midi input 1, so for such an arrangement to work, you would have to connet the Midi to Usine to another input than 1|.

[gurulogic]

This happens because Usine first receives the incoming data on channel 1, then the rechanneled data. Not as quick'n'easy, but you can change the assignments in the remote window.

Right, but this means I cannot manipulate the incoming CC data, say for example in one preset I want my controller to be received as channel one data, in another preset I want the exact same controller data to be on channel two, or maybe I want to scale,remap or otherwise manipulate the midi CC's before they take command of a Usine interface object. I don't think this is possible if the Usine midi inputs are used? That is my argument for having direct midi inputs available in Usine as modules.
Definately a bit OT from the original post but on a similar vein, I think?

If I understand you correctly, you create a direct connection between a Midi input and a Midi to Usine module - that will most probably create a feedback loop, at least if you've operating with only one Midi input. I think the output from the Midi to Usine is always received mixed with whatever's coming in on Midi input 1, so for such an arrangement to work, you would have to connet the Midi to Usine to another input than 1|.

Ok,Ive just realized I don't even have a clue how to separate multiple midi inputs coming into Usine for use within a patch...I'll try this again when (if) I manage to figure this one out..? Otherwise I guess I'll stick to my VST solution or perhaps keep an instance of bidule VST inserted in my workspaces to do the type midi processing that I cannot seem to figure out with Usine...Oh, the learning curve!

[bsork]

If you want the the same fader or whatever in the same patch to be controlled by different channels/CCs in different presets, you can do that with patching instead of using midi learn; some filters (or use the filter option of the midi input), some math/logical etc, and you're ready to go.

About seperating the inputs, I'm sorry I've mixed the behaviour of the outputs with the behaviour of the inputs . The outputs get numbered, while the inputs don't. However, you can have different inputs turned on per track, and you can also use the unpack function coupled with "num virtual" to check the input one message per block.