|
View your shopping cart.
Recent topics
Recent Comments |
Output Existing .QTZ Files To A Billboard in a New Composition I'm working on a Media Server idea. I would like to be able to play Quartz Composer files on a Billboard just like I do pictures or movie files. I want the .qtz files to still function like they do when running on their own. In other words if they are designed to work with keyboard or mouse input, I want that functionality to stay intact, so just outputting them as a quicktime and then re-inputting them won't work. I'm new to all this and I bet that someone else has this figured out. Is it you? Thanks... Les
More like this
|
Composition Importer, autoconfigure from required .qtz, save .qtz with importer patch at root level of file to be loaded & run. See attached example, calls upon a repository item.
This is great, but doesn't connect to a billboard. I'd like to load quartz compositions into a billboard. Thanks for the help!
Take a butcher's hook at the v002 Screen Capture patch, might do more of what you'd like.
In fact even better - look into the System Repository items and model your compositions upon how they take in data [often image data] and output image data - look at X-Ray.qtz , amongst many others similar.
Put the composition loader inside of a render in image patch, or put all of your compositions in render in image patches.
That's a good suggestion that works and you can feed the composition loader with a multiplex of compositions too.
"Hardcoding" the file paths of the compositions via a string multiplexer, or javascript will deliver best performance - Directory Scanner (Blocking), and searching for just qtz's will be more flexible.
Take any qtz that's in a render in image, publish the output, and then whatever inputs you need (some standard schema between comps). Get the comp loader, and do the "autoconfigure" deal in settings. After that, you could actually rename your qtz files to any arbitrary filename and/or put a "." in front to make them invisible, and the composition loader will still load it. In addition, you could possibly make the finished app hinge on a app support file (name a qtz something like "com.apple.blah.blah") that is really a qtz (a macro/insert splitter, or whatever and load it via the comp loader). All the renaming stuff I'm talking about is totally not needed, just a pointer.