Support |
Please let me see if I am understanding you correctly: You're saying you wrote a Mobius script for creating MIDI events and send them out? Or was that a different kind of script you were writing? (Bidule Groups are quite script-like) As the criminals say: Do Not Trust The Manual! :-) L∞P Police may be watching... Bidule is not like "a normal host", more like a routing laboratory. The best thing with Bidule is that it is totally configurable so I sugest that you set the Mobius plugin to not use any MIDI ports at all and then you do all virtual cable work in Bidule. That way you'll be getting a good view over what you are doing since it is totally visible on the screen. Open MIDI Devices (both IN and Out) in Bidule and drag cables to and from them whenever you need any specific routing. Greetings from Sweden Per Boysen www.perboysen.com http://www.youtube.com/perboysen On Sun, May 31, 2015 at 11:27 PM, Fabio_A <eterogenus@gmail.com> wrote: > Any experience in this topic ? > I use Bidule to set the tempo for Mobius plugin to follow. > I wrote a script that should send CC to control a parameter of a Bidule's > module, but nothing happens and the Midi monitor doesn't show any midi > command. > The manual says that Mobius plugin doesn't need to configure a midi > output > port, since all Midi work is made through the host. > In the midi output device window I have many ports: my main audio > interface, > Softstep ports (since it's bi-directional) and 2 Bidule virtual midi > ports. > I'm a bit confused, any help would be appreciated > > -f > >