Looper's Delight Archive Top (Search)
Date Index
Thread Index
Author Index
Looper's Delight Home
Mailing List Info

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Date Index][Thread Index][Author Index]

Re: Mobius controlling Bidule via MIDI

Il martedì 2 giugno 2015, Per Boysen <perboysen@gmail.com> ha scritto:
Very interesting! Thank you for reporting back! Got some questions to
be answered before I understand it:

1. So Seb suggested that script for Mobius? ("MidiOut noteon 3 64 127)

That  script is reported in the manual as an example. You can send any desired midi command (I'm using CC right now)
2. "Using the VST", guessing you are using the Mobius VST? Hosted in
Bidule standalone? Right?
Right ! 

3. And you had to open the Mobius preferences and there select one of
the Bidule MIDI ports?
Yes, in the plugin midi OUT section I selected BIDULE 1 (virtual midi port)

Then I dragged the BIDULE 1 MIDI IN object into the layout

4. And finally open up that port in your Bidule layout to receive the
MIDI note and cable it somewhere...

No need to cable (I just do ìt for midi monitoring) 

It all makes sense and is very interesting because by assigning MIDI
notes to be sent into Bidule on the same foot switches you are using
for other looping commands you can add up a lot of fun stuff to happen

What I'm doing is to trigger a single script that:
- load a Mobius project of a specific piece
- set the midi config for that piece
- set a mixer preset  (fades and pan) in Bidule.
I can see many options: with  "wait" and the appropriate quantization  you can tell Mobius to change pre or post loop FXs, midi controlled instruments, volume of your electronic instrument ....and so on,  exactly at the end of the specified cycle.

Great that we still have Bidule that works so well with 32 bit plugins
on a modern 64 bit OS. Over here I'm learning Bitwig now and the cool
thing with that DAW is that it is performance oriented and supports
both 64 bit and 32 bit plugins on a 64 bit system. And plugins are
being run inside "sand boxes", meaning that if one plugin crashes it
doesn't crash the host. You just have to reload that plugin instance
and keep on. Downside with Bitwig is that it doesn't follow a MIDI
Clock tempo sync signal, so I can not run the Mobius VST as the tempo
sync master - being forced to run Mobius following the host's tempo
instead. Thus losing out on "flashy looping kick-offs" (that you can
do with Mobius as the master) but gaining on the Unified Modulation
System of Bitwig. Almost anything can be set to modulate anything, and
this includes both software instruments, note MIDI effects and audio
effects (like Mobius). So, for an example, you can have an audio
signal's amplitude set to modulate several software parameters in any
kind of scaling. It's like a dream finally coming true.

Sounds interesting ! Have fun.

Greetings from Sweden

Per Boysen

On Tue, Jun 2, 2015 at 12:04 AM, Fabio_A <eterogenus@gmail.com> wrote:
> Just for the record: Seb @ Plogue solved it !
> In case anyone else is interested, here his post:
> I just created a simple script containing only:
> MidiOut noteon 3 64 127
> add it to the list of script, add a new keyboard shortcut linked to that
> script.
> Using the VST, no MIDI signal was coming out of the plugin, I had to select
> one of the Bidule virtual MIDI port in the plugin output section of
> the MIDI Devices dialog and once that was done (and the corresponding Bidule
> virtual input port was in the layout), I was able
> to see the Note On message while pressing the key with the
> focused/foreground Mobius window.
> -f
> Il lunedì 1 giugno 2015, andy butler <akbutler@tiscali.co.uk> ha scritto:
>>> !name miditest
>>> message test
>>> end <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>>> ends script?
>>> MidiOut control 15 78 40
>>> next
>>> I can see the message on Mobius layout, but no midi is sent out.
>> otoh we don't know if Mobius is sending to its host
>> andy