Currently use QC to make custom layers for Bonix TV - a vision mixing kind of application for OS X with a kind of QC stack of layers, each layer being a composition with published ports and some protocols for data types. Also generate sports graphics and twitter feeds and so on for video score boards at large sporting venues.
Spent a few years learning Quartz Composer as my way back into coding from a decade away doing design related work. Film, graphics, studied Architecture for a few years and got involved in publishing then film. Now moving into front side web development. Hope to get into app dev with Vuo and rapid app prototyping.
I found that my use of the Measure Time node wasn't orthodox, I was pausing it once the timer went past the maximum value I was testing for and it had some strange side effects in terms of reseting and starting it. I removed the pause and it started working as desired.
I'd like to be able to show/hide the console window so I can use it as a debugging window but also disable it at times (it slows comp down amongst other things, and yes I realise I could make a switch to disable the data flow to it to speed things up).
If putting an enable switch on the Console Window node is easier than dealing with full render windows, perhaps it could be first cab off the rank for a quick fix?
Yes, having the Motion template will potentially fill gaps where the Vuo UI is limited to simple value inputs restricted to known datatypes. Can't wait to check this out, I use Premier Pro and AE but will have to learn FCP and Motion to play with this I expect.