Gigs, Tips & tricks

gnomalab's picture

I would like to use my QTZ patches on my Gigs without external programs like a Modul8 or VDMX are remaining flexibility and quality.

Discuss different strategies for working in live: Make a megapatch with a lot of presest, keyboard mappings, Midi asigments etc.

the pros and cons involved. Thank you. Sorry for my poor english :-(

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

cwright's picture
quick and dirty

for some of our informal gigs, we've just used QC with the viewer maximized on an external monitor -- this allows us to modify the composition on the fly during the show (which can sometimes be deadly -- see the particle tools patch crashing bugs ;)

I've also got a simple full-screen skeleton app -- no inputs or outputs, just what QC provides. Not as flexible as VDMX et. al, but works in a pinch.

For an embedded installation that needed external control stuff, I made a thin app, and then a gigantic composition to handle all the state transition stuff.

gtoledo3's picture
Didn't somebody mod the

Didn't somebody mod the Performer code so that it can also do full screen? Something like what you are mentioning, plus a little mixer like is in Performer would be cool. Or is that basically what Quartonian is/was (I have it, but I have only looked at it once or twice and it seems like it didn't like Leopard...)...?

kristopf's picture
I'm currently doing an interactive installation (mostly) in QC

...I'm going to do a big write up on this when I'm done, but pretty much what I've decided to do is run QC with the viewer maximized. (and a ton of custom supporting code written in other languages talking to QC over OSC)

I've got one big macropatch doing all the OSC communication with the other computers. That connects to a JavaScript patch that forwards values to and enables/disables several other macropatches containing the various program modes. I also have been using a lot of spooky send/receive.

I've found it's easiest when you're making giant QTZs to develop each macropatch separately in it's own file, and then copypaste into your monolithic qtz when you know everything works.

Keeping each screen to about 10-20 patches does wonders for readability (and makes code reuse easier), but is often not practical.