#6 Jitter 4-plane matrices

[kodamapixel]

I have been trying to get the sfFreeFrame plugins to work with Jitter, but get the error: "the selected effect is not compatible with Jitter 4-plane matrices" when any of the effects are loaded in [jit.freeframe] - not when they're run into a Jitter matrix.

PetesPlugins all seem to be working fine, so I'm wondering if these plugins are incompatible, or I'm just missing an attribute or object along the way?

[marc wren]

Hey kodamapixel,
I haven't tried these with jitter yet. Can you tell me the steps you took to try and load sfFreeFrame in jitter? Maybe I can figure out why they're not working.

Marc

[kodamapixel]

Hi Marc,

Following the instructions found in the Max Help Patcher, jit.freeframe.maxhelp I put the .bundle files in /Library/Application Support/FreeFrame (this is where Max automatically looks in OS X).

There are no errors when opening the jit.freeframe.maxhelp patch, but as soon as any of the sfFreeFrame plugins are selected (from [umenu] drop down list), I get the following error in the Max window:

jit.freeframe | the selected effect is not compatible with Jitter 4-plane char matrices
print | loadeffect sfcolorrings 0

When selecting one of the PetesPlugins effects (chromium for example), I simply get:

print | loadeffect chromium 1

Interestingly, even when there is no Jitter matrix connected, I still get this error. It's obviously the [jit.freeframe] object that is throwing up the error - not the Jitter matrix.

Cheers,
Scott.

[kodamapixel]

From what I've been reading, Jitter may only be able to run Universal Binary plugins, not Intel native. That may be where the problem lies.

[marc wren]

Thanks for the feedback and input. I'll let you know when I have an update on this.

[marc wren]

Hey Scott,
I've put up a new build of sfFreeFrame for OSX (0.5.1). This version was built as a Universal Binary and should support OSX 10.5+. Would you mind giving this a try in Jitter? I'm not sure if Jitter actually supports FreeFrame 1.5.

[kodamapixel]

Unfortunately getting the same error message. I'm not sure about FF 1.5 compatibility, but I've posted the question on the C74 forums.

From the jit.freeframe help file: "It supports both single and dual input effects, and 32-bit and 16-bit data sizes." Not sure if that helps at all, but maybe worth a try!