Re: setting the input of many many many midi devices

really?  i've found i have to "bump" every connection in my patches every time i restart and i use midipipe.  my solution is not to restart.  i am able to put the machine to sleep and unplug my gear, travel and then plug everything back in and wake it up.  this seems to work most of the time...  the list talk of creating some template midi code is very interesting to me...

On 11/28/05, michael markert <email@hidden > wrote:

Hi Alex,

I have the same problems, but there are two ways to make this a bit
easier:

- use the same MIDI-Hub (USB), so you just have to switch the USB-
Cable and all names stay the same

or:

- use virtual ports and a routing setup for each machine. Try "Midi
Pipe" or "Midi Patchbay". For example, you setup a virtual input port
"QC-In #1" and route your Device to QC-In #1. The QC-Patch should
always use this virtual port as input.
This way, you just have to create different "Virtual Patch Setups"
for each machine – no need to touch your QC-Compositions ever again!

Midi Pipe is very powerful but also a bit more complicated to handle
than Midi Patchbay.

Best regards,
Michael




Am 26.11.2005 um 17:52 schrieb Alexander Huber:

> hello everybody,
>
> i'm currently building a vj application that uses a lot of midi
> controllers and midi keys. i have two machines, an old slow
> powerbook and a dual g5 on which i develop the project.
>
> my problem is to keep the 'development branches' synchronized: the
> midi devices are not accessed via names (port A, IAC Bus1 etc...)
> and are 'forgotten' on the powermac when i load the composition
> previously developped on the powerbook, even when i plug in the
> same midi interface. so if i change a lot of midi stuff, i have to
> click through all the midi note/controller elements in my
> composition...
>
> the composition is tied to the hardware, even if i use the same
> hardware controller.
>
> i had one idea: keeping one composition that handles only midi in/
> output and which is machine-dependent, acting as a kind of
> 'interface' to the second composition which is machine-independent
> (and really only gets copied over to the other machine) whereas the
> 'connection' between the two comps is done via copy + paste (i open
> the second, machine-independent composition, and copy the patch
> with the controllers into it... i'm sure it would work, but then i
> had to do all the cabling stuff...)
>
> to sum it up: either i step through all midi note/controller
> elements and change the device setting, or i have this 'interface-
> acting composition' that gets pasted in the main development
> composition, which i then have to reconnect using lots of cables...
>
> how do you handle such a problem?
>
> i'm fairly new to qc (great tool!) and couldn't find any other
> solutions
>
> thank you very much for any input
>
> cheers
> alex
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list      (email@hidden )
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/email@hidden

This email sent to email@hidden