I had a similar question. I hate to make the comparison to Max/MSP,
but Quartz Composer is missing two key elements that make this easy
in Max/Pd:
1) a "loadbang" object that can quickly populate objects with default
settings (though Roger's suggestion using JavaScript is, if I
understand him right, a solution)
2) most importantly, the ability to default to specific MIDI devices
by assigning port identifiers. That way, the default "port A" device
can be used for MIDI -- even if you substitute MIDI devices.
This is a MAJOR problem at the moment for Quartz Composer, because it
means manually setting MIDI I/O at the object properties level.
Related, though: could you handle MIDI I/O using a QC-based Cocoa
application?
Since so much interest in this list has been on live performance + VJ
applications, for instance, it'd be great to have a simple MIDI
source code example for assigning MIDI ports and passing data through
to the QC view.
Peter
On Nov 26, 2005, at 11:52 AM, Alexander Huber wrote:
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 (Quartzcomposer-
email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/peterkirn%
40gmail.com
