is there a configuration where I can extent the limit of 8 physical (USB) Midi controllers? I run into troubles, cause I have 11 devices with usb midi which should be controlled via Usine. I need the USB also as power supply for those devices, so I can't use a classical MIDI Bus. Today many devices does not have a classical MIDI/IN-out.
There is a way to use MIDI-OX and MIDI YOKE to solve this, but this is not good in Live Situation due to the reason that the order how everything ist started is critical I would prefer to configure the whole environment in Usine
I use cheap USB Midi cables with this small controllers inside to control dedicated Arduinos and other devices via MIDI. This solution works very well, I need only on cable to the devices and no extra power supply, but one device one entry in the configuration.
Do I have a chance? :-)
Hello hesspet and welcome,
i suppose this is more for the suggestions forum cause senso has to change Usine configuration here,( but it's not really a problem)
One thing you can maybe test ( if you don't need audio for all connections) : Use Usine + Easine in no audio mode and route the last midi controllers for arduino for example.?
:--) Sorry, can you please move the thread?
>>Use Usine + Easine in no audio mode and route the last midi controllers for arduino for example.?
This may be an Idea. It's in fact a similar idea like mine, to use the Midi-Ox and Midi-Yoke as a sort of a concentrator. The decoupling of the non timing critical devices, I control a lot of circuit bended toys :-), seems to be a good idea. Thanks for the hint AND the great software! I'll give it a try.
For my curiosity: This limitation is it a programmers decision or a techincal limitation? If it's programmers decision, I'll write a suggestion comment.
It's in fact a similar idea like mine, to use the Midi-Ox and Midi-Yoke as a sort of a concentrator
i was more thinking of a parallel solution, usine and easine each one controlling their own hardware..? but maybe not possible in your set.
The second solution to avoid the use of virtual midi, could be to use OSC communication between Usine and Easine ? ( i said Easine but can be of course a second instance of Usine too)
I'll ask senso for the limitation
Ah, this may also a solution, yes. In fact one usine instance works as concentrator for an other instance. I'll try this in the next weeks and post the results here. Thanks for your help, don't hurry it is not so important that it must be solved in the next minutes.
yes this looks very interessting. Maybe this solves my hussels.
Thanks a lot!
Lot of things to to in the next weeks...
Sounds good, hope not only for me, cause I've now a solution
the PizMidi idea, discussed above, solved MY problem perfect. :-)
ok, so if you find a solution we'll maybe not keep this add, cause it's reduce the button size on each track , but if it's really needed later we can add this option.
I think an internal patch that allows to get more MIDI interfaces would solve the problem without changing the design. This is the way I solved it with the PizMidi. The PizMidi works as a internal proxy and from the patch where this vst is included I send the data via a MidiMessage Channel into my "Midi Routing patch".
Maybe there ist time to review some of the PizMidi ideas and transfer some ideas into write/build some patches in Usine, to reduce the minimal VST overhead (more nice to have ....the all in one solution :-) ) I'll write a suggestion post in the next weeks in the other posting group.
Again thanks for the quick help!
Direct access to MIDI interfaces from with Usine patches would be a very welcome addition and would remove the need for the VST options, plus allow remote out from interface items to the direct port with no additional create MIDI modules which is not possible with the VST. In truth, I try my best to avoid using the Usine MIDI i/o setup because I lose my previous device configuration whenever I start Usine without the MIDI devices connected.
wrong section for this talk I guess
In truth, I try my best to avoid using the Usine MIDI i/o setup because I lose my previous device configuration whenever I start Usine without the MIDI devices connected.
+1 on this.
Look how Plogue Bidule does it. You can create objects in the grid that are specific MIDI interfaces, and if they are unavailable, they show up red, but will be normally patched in next time you restart with the interface connected.
With usine, I can even save the midi setup to a file, and if one of my usb interfaces is plugged into a different jack, usine won't load the profile correctly. It's a very crude method, and forces me to open the global page almost every time I start up.
As long ago as 2002, Logic on the PC would allow me to plug in a midi or audio interface, and recognize it without a restart. (it did some sort of soft restart.) This would also be a nice feature to have.
yes, a different method and approach has been adopted for V6 and will resolve this problem, don't worry