Production

Production

Release: KinemeCore, v0.1

Release Type: Production
Version: 0.1
Release Notes

Have you grown weary of seeing @cwright's incomprehensibly cool transparent editor screenshots?

Are you tired of wishing your QC Editor would get out of your way, instead of getting in your face?

If you answered yes to any of those questions, the KinemeCore Plugin might be just for you.

As Seen At NAB2008! ;)

KinemeCore Options

The KinemeCore Plugin enables several modifications to the Quartz Composer Editor UI, including private patch exposure, snap-to-grid, toolbar removal, fullscreen editors, fullscreen viewers on startup, non-floating patch creators, slim and non-existent scroll bars, transparent windows, and much much more. Everything you need to get started on QC-Development Bliss.

This public release offers numerous performance improvements over the previous betas, as well as some more polished transitions and modifications. It also removes the KinemeCore Framework dependancy, removes the Sparkle dependancy, and has less start-up overhead.

This plugin doesn't affect your compositions in any way. What it does affect is how you make them.

There are still a couple Rough Edges; some of the modifications are pretty invasive, and there's not much more that can be done, unfortunately :( But there's always more room for additional changes, so feel free to fire questions, complaints, and additional features our way, and we'll see what we can do.

We're also in need of a much cooler about-box icon; if you're talented with paintshop, feel free to submit your artwork (512x512 or larger, please). Your artwork could be featured in a future update!

[edit: oops, forgot one link last reference. Sorry about that. Now it's fixed!]

Release: Safe Video Input, v0.1

Release Type: Production
Version: 0.1
Release Notes
The Safe Video Input plugin is deprecated. Information on getting around Safe Mode restrictions

Safe Video Input is a patch that modifies the existing built-in video input patch to work in safe mode. This allows it to work in "safe-mode sandboxed" applications. [Please read the warning before using this plugin!]

There are some applications that don't load "unsafe" patches from compositions. Keynote and QuickTime are two notable ones. This plugin modifies the existing video input patche to allow it to get loaded along with the others. For safety purposes, this plugin won't function in Safari.

Warning: Circumventing the "Safe Mode" restriction introduces some privacy issues — for example, malicious compositions can attempt to record Video from your PC and transmit it to remote Viewers. As such, you should only use/install this plugin when you need this functionality.

Release: PBMesh, v0.1

Release Type: Production
Version: 0.1
Release Notes

PBMesh is a plugin that allows you to quickly warp images for different kinds of cylindrical and spherical projections.

More information on how to use this patch, as well as some sample meshes, can be found on Paul Bourke's site: http://local.wasp.uwa.edu.au/~pbourke/miscellaneous/domemirror/warppatch...

Release: Safe MIDI, v0.1

Release Type: Production
Version: 0.1
Release Notes
The Safe MIDI plugin is deprecated. Information on getting around Safe Mode restrictions

Safe Midi is a patch that modifies the existing built-in midi patches to work in safe mode. This allows them to work in "safe-mode sandboxed" applications. [Please read the warning before using this plugin!]

There are some applications that don't load "unsafe" patches from compositions. Keynote and QuickTime are two notable ones. This plugin modifies the existing midi patches to allow them to get loaded along with the others.

Warning: Circumventing the "Safe Mode" restriction introduces some privacy issues — for example, malicious compositions can attempt to record MIDI from your PC and transmit it to remote listeners. As such, you should only use/install this plugin when you need this functionality.

Release: Official API Subpatch Support, v0.2

Release Type: Production
Version: 0.2
Release Notes
The Official API Subpatch Support plugin is deprecated. Information on getting around Safe Mode restrictions

QCRehab gives some of the unofficial-API functionality back to the Official API. Features such as Safe Mode and Subpatch support are enabled, allowing more flexible plugins.

This plugin uses the Unofficial API, so it goes in ~/Library/Graphics/Quartz Composer Patches/, not ~/Library/Graphics/Quartz Composer Plug-Ins/.

This plugin was written in response to several complaints about 3rd party plugins not working in "safe" environments. When installed, this plugin will allow all official-api plugins to load in any environment -- This is Extremely Dangerous, Don't Do It Unless You Know You Need it!

For security reasons, it's Disabled in Safari (so malicious compositions cannot harm your machine via the web, even when this plugin is active). Custom plugins should still work in Keynote presentations, in Motion, in Quick Time, and in other applications that may struggle with safe-mode issues.

Note that this does not unlock "unsafe" built-in patches, such as Audio and Video Input. Only custom, Official-API Plug-In patches are unlocked.

It's also useful for plugin developers who are interested in sticking with the official API. It would also be necessary for a user of such plugins.

This plugins obsoletes the "Official API Subpatch Support Plugin" we released a few months ago. It offers identical functionality, including fixed subpatch-save support (meaning compositions with subpatches are properly restored when loaded).

To use this in your Official-API plugins, simply add a +(BOOL)allowsSubpatches method that returns YES to allow subpatches in your patch.

For developers: When making a sub-patch-aware patch, you'll need this piece of code to execute subpatches:[[self patch] executeSubpatches:(double)time arguments:(NSDictionary*)args]. This should go in your execute method only.

Have a lot of fun :)

I expect Apple to include this functionality in a future release of QC, so Please only use this if you know what you're doing. If you bundle this in with other plugins, please make the user aware of what's going on, and how they can remove it.