Spooky Patch Use and Consideration

scalf's picture


I've been using spooky extensively in a visual mixing program I've been making for Quartz. I want to reduce cabling and awkward patching by sending remote values to other location with porting values up and down, etc...

I was wondering if there were any special considerations like don't use over 512 of them, or make sure to toggle this off when sending this value, etc? I'll be sending video, color, float, string, all of em.

From what I gather, have the "auto-clean" feature enabled, and the spooky patch may really be just a pointer so it may in fact be a very lightweight option. This seems to be a good way to maker modules of patches that can be moved to different places and not need to be reconnected.

Thanks for any advice

Bezier Iterate (Composition by gtoledo3)

Author: gtoledo3
License: MIT
Date: 2012.05.20
Compatibility: 10.6
Required plugins:

This composition uses Kineme2D's Bezier Path With Curve and the Grid With Bezier Path. It iterates the Bezier Path With Curve in a way that allows you to subdivide a grid by multiple beziers, and warp along the path.

(This seems to expose a slight counter-intuitive or wrong aspect of Grid With Bezier Path - as the grid is composed of more beziers, UV's shift some. In practice, this isn't a big deal, because the texture scale can be adjusted with Image Texturing Properties.)

This will need Kineme2D and Data Tools. Syphon Server is incidental, but that will be needed to for the composition to fully restore.

Tested in 10.6.

Obsolete Plugin Cleanup

It would be excellent if there was a little utility app, independent of kinemecore probably (but this wouldn't be bad with kinemecore too), that would go and "cleanup" old plugins like structure tools, directory scanner blocking, spooky, gl tools during the alpha port function era, etc., that have been made obsolete by new plugins/have been lumped in with new plugins. Like, how Kinemecore checks for duplicate versions/older versions of a given plugin, or locations being in the wrong place.

I realize that something like that would have to have a static list of some outdated plugins inside the app and patches that replace them, that would be maintained, and that this could get into a pain. Maybe this would be best as an opensource thing where people could update that list themselves.

The purpose of it's being it's own utility app, script, or whatever, is so that someone wouldn't have to start up QC to do a "plugin management".

The "problem" scenario, is that, if you're loading an app that uses patches like Structure Maker or Directory Scanner Blocking that have been gobbled up by other patches over the years (DataTools, FileTools), and the user has them double installed - like, they have Structure Maker AND DataTools installed, not only does QC have problems on start, but it's pretty darn hard to figure out a way to keep your own app from crashing on start, or not initializing, because of the duplicates.

Maybe there's some eloquent way to handle this in the internals of an app, but I sure haven't found it - and I doubt there is in the case of duplicate plugins, when loading them from user, library, or system locations. I don't necessarily want to stop external loading of QCPatches altogether, but I guess that would be the alternative, to making it so the user doesn't have to jump through as many hoops. It just keeps them from using QCPatches installed on their system though (like QB does currently), which is sometimes not an advantage.

about : about artificial life

cybero's picture

Couldn't add a comment to the artificial life post you made,zanroversi, so wrote this post.

I find that hexagon and jeu de la vie don't work much at all whilst opinion and vie_K work just fine.

Grid Warp - looking for a better solution

.lov.'s picture

Hi Guys,

i need a bit help. I'm working on a grid-warp patch, using latest GL Tools and Spooky patches - and the Interaction. Basically, the composition working, but if i changing the current "work point" too fast that will screw up all the things - check the attached file, please.

ps.: It's not too bad in Quartz Composer, but if i want to using this comp outside of QC, the issue will be bigger - tested with a single QCView, QuartzBuilder, CoGe, so looks like its not my fault (maybe i found a bug?).

I had the same issue with Quad Warp (http://coge.lovqc.hu/coge/forum/viewtopic.php?f=17&t=175), but with that composition i found a working solution which works outside of QC.