Wierd problem - QC recognized Kineme plugins and now it doesn't

Hi, I am having a weird problem, a few days ago I installed all the Kineme plug-ins in the correct place and they showed up in QC and worked fine. Now when I start up QC they don't appear in the Patch Library like they used to, and if I open .qtz compositions that I made with them, I get this message that the compositon was not restored successfully and it says it cannot create a connection (or node of class) from the various Kineme objects. The Kineme plug-ins are still there in my Library>Graphics>Patches path, (not the user library but the main one). I never changed their location, or anything like that, they worked for a while and showed up fine but now they don't.

Does anyone know why this would happen? Any help is greatly appreciated!

By Thorrific at 2008-06-14 16:18
General

console

You could try putting them in ~/Library... (the user one), that's where we built/test ours. Maybe moving them will do something?

Alternately, can you see if there are any interesting messages in the console? If so, please paste them here so we can see what's going on.

(Thanks for getting the directory right! You should get 25 points just for doing that ;)

By cwright at 2008-06-14 16:43

hmmm

Well, I copied them there, started up QC again, and still nothing in the Patch Library. I wonder why? When I open compositions with some of the Kineme patches in them I get messages like this:

> Macro Patch
Cannot create node of class "KinemeMIDIOutputCC" and identifier "(null)"
 
> Macro Patch
Cannot create connection from ["outputResult" @ "Time_7"] to ["inputValue" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
Cannot create connection from ["outputResult" @ "Expression_1"] to ["inputController" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
Cannot create connection from ["outputSignal" @ "Time_5"] to ["inputTrig" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
State restoration failed on node "Patch_1" <QCPatch = 0x18A68A00 "(null)">
 
> Macro Patch
Cannot create node of class "KinemeMIDIOutputCC" and identifier "(null)"
 
> Macro Patch
Cannot create connection from ["outputResult" @ "Time_7"] to ["inputValue" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
Cannot create connection from ["outputResult" @ "Expression_1"] to ["inputController" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
Cannot create connection from ["outputSignal" @ "Time_5"] to ["inputTrig" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
State restoration failed on node "Patch_2" <QCPatch = 0x0030EA80 "(null)">
 
> Macro Patch
Cannot create node of class "KinemeMIDIOutputCC" and identifier "(null)"
 
> Macro Patch
Cannot create connection from ["outputResult" @ "Time_7"] to ["inputValue" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
Cannot create connection from ["outputResult" @ "Expression_1"] to ["inputController" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
Cannot create connection from ["outputSignal" @ "Time_5"] to ["inputTrig" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
State restoration failed on node "Patch_3" <QCPatch = 0x18E28FA0 "(null)">
 
> Macro Patch
Cannot create node of class "KinemeMIDIOutputCC" and identifier "(null)"
 
> Macro Patch
Cannot create connection from ["outputResult" @ "Time_7"] to ["inputValue" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
Cannot create connection from ["outputResult" @ "Expression_1"] to ["inputController" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
Cannot create connection from ["outputSignal" @ "Time_5"] to ["inputTrig" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
State restoration failed on node "Patch_4" <QCPatch = 0x18E2C770 "(null)">
 
> Macro Patch
Cannot create node of class "KinemeMIDIOutputCC" and identifier "(null)"
 
> Macro Patch
Cannot create connection from ["outputResult" @ "Time_7"] to ["inputValue" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
Cannot create connection from ["outputResult" @ "Expression_1"] to ["inputController" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
Cannot create connection from ["outputSignal" @ "Time_5"] to ["inputTrig" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
State restoration failed on node "Patch_5" <QCPatch = 0x18E2FE80 "(null)">
 
> Macro Patch
Cannot create node of class "KinemeMIDIOutputCC" and identifier "(null)"
 
> Macro Patch
Cannot create connection from ["outputResult" @ "Time_7"] to ["inputValue" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
Cannot create connection from ["outputResult" @ "Expression_1"] to ["inputController" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
Cannot create connection from ["outputSignal" @ "Time_5"] to ["inputTrig" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
State restoration failed on node "Patch_6" <QCPatch = 0x18E2C0E0 "(null)">
 
> Macro Patch
Cannot create node of class "KinemeMIDIOutputCC" and identifier "(null)"
 
> Macro Patch
Cannot create connection from ["outputResult" @ "Time_7"] to ["inputValue" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
Cannot create connection from ["outputResult" @ "Expression_1"] to ["inputController" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
Cannot create connection from ["outputSignal" @ "Time_5"] to ["inputTrig" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
State restoration failed on node "Patch_7" <QCPatch = 0x18E36D50 "(null)">
 
> Macro Patch
Cannot create node of class "KinemeMIDIOutputCC" and identifier "(null)"
 
> Macro Patch
Cannot create connection from ["outputResult" @ "Time_7"] to ["inputValue" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
Cannot create connection from ["outputResult" @ "Expression_1"] to ["inputController" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
Cannot create connection from ["outputSignal" @ "Time_5"] to ["inputTrig" @ "KinemeMIDIOutputCC_2"]
 
> Macro Patch
State restoration failed on node "Patch_8" <QCPatch = 0x18E3A460 "(null)">
 
> (null)
State restoration failed on <QCPatch = 0x18E0D4B0 "(null)">

By Thorrific at 2008-06-14 17:28

redownload

maybe try redownloading some? Look in Console.app for other messages (sometimes QC tells us why it's not loading plugins there, but not on-screen -- what you've pasted is just Exception-throwing fun, but not why it's failing)

By cwright at 2008-06-14 18:23

Particle Tools might be the problem

I was just about write here about similar problem which I think might be what´s happening with you.

After I installed the particle tools kineme plugin, it pretty much disabled all the other Kineme plugins. Only Kineme CV, Kineme GL, Kineme Particle, Kineme MIDI and the new Directory Scanner plugins work after installing the Particle Tools.

I´m using a MacBook Pro 2,5 GHz (early 2008 model), 2 GB RAM, GeForce 8600M GT 512 MB

Here is the error message QC gives me.

-[QCPatchClassDescription initWithNodeClass:]: ivar "inputObject" of class "ParticleColliderKineme3DPatch" is not a subclass of GFPort
 
0x92c7ec12: GFException
0x92c80855: GFThrowException
0x92c7edab: _ivarToPortClass
0x92bcb33d: -[GFNodeClassDescription initWithNodeClass:]
0x92bcb0f4: +[GFNode initialize]
0x92bcbaee: +[QCPatch initialize]
0x96e3ab78: _class_initialize
0x96e394f9: _class_lookupMethodAndLoadCache
0x96e49736: objc_msgSend
0x92bcd325: -[QCNodeManager loadPlugInAtPath:]
0x92bcd8bf: -[GFNodeManager(PlugIns) loadPlugInsInFolder:withExtensions:]
0x92bcd75b: -[GFNodeManager(PlugIns) loadPlugInsInLibrary:withExtensions:]
0x92bcd6d3: +[QCPatch(Registry) loadPlugInsInLibrary:]
0x92ce1bdb: _RegisterPatches
0x92bcbc7c: +[QCPatch(Registry) patchManager]
0x00004710
0x00004387
0x000041bd
0x00004046
0x00003f70
0x91f80bda: _nsnote_callback
0x91d039da: __CFXNotificationPost
0x91d03cb3: _CFXNotificationPostNotification
0x91f7dfd0: -[NSNotificationCenter postNotificationName:object:userInfo:]
0x91f87668: -[NSNotificationCenter postNotificationName:object:]
0x933a6377: -[NSApplication finishLaunching]
0x00003994
0x933a5dfd: -[NSApplication run]

By waxtastic at 2008-06-16 05:10

Forgot to mention that if I remove the Particle Tools plugin from my Patches folder, everything else works just like before.

So try if this works.

By waxtastic at 2008-06-16 05:16

Same error

I had the same error previously - it appeared after installing the particles plugin, no idea if it broke anything else, but the particle patches seemed to work fine.

Actually, I planned on reporting it, but didn't because when I went to check on the actual error log QC suddenly started working.. ish. I think it was then taking ages to start up and refusing to play any files. Not had time to check it again since, but I'll provide some more info if it's still playing up.

By psonice at 2008-06-16 07:51

yikes

That's a terrible error -- it should be smart enough to not cause that....

Anyway, here's some thoughts.

The problem is it's trying to register the kineme3d collider, which is only available to Kineme3D Alpha testers. If you're an alpha tester, and kineme3d is currently installed, and you're receiving this error, please e-mail me personally so we can figure this out.

If you're not, please remove /Library/Frameworks/KinemeCore.framework, and update your KinemeCore.plugin to the latest version (old versions of the KinemeCore plugin would regenerate KinemeCore.framework if it didn't exist). Let me know if this fixes the problem. [technically, this was a really cool idea. but in practice it was definitely one of my poorer choices as a software developer... sorry for the confusion it has caused with this, and a few other things...]

By cwright at 2008-06-16 09:33

fixed

Thanks. Removing the KinemeCore.framework fixed the problem.

By waxtastic at 2008-06-16 11:28

not working

Well, I threw away all the Kineme plugins, and then re-downloaded them, and put them in Library/Graphics/Patches ... still nothing. Is there some preference somewhere I have to throw away?

Please forgive my ignorance but how do I find "Console.app" to see the other error messages?

I didn't have any "KinemeCore.framework" on my computer, so I don't think that's the problem.

By Thorrific at 2008-06-16 15:39

spotlight

spotlight for "console" [Should be somewhere like /Applications/Utilities/Console.app I think?]

there aren't any preferences, so that shouldn't be a problem. Which plugins specifically are you using/trying to use? What's your machine's configuration? (PPC/Intel, Tiger/Leopard, etc)

If you're on Leopard, you'll want them to go in "~/Library/Graphics/Quartz Composer Patches" (not just /Patches, as your previous comment mentioned -- that may have just been for brevity though...)

By cwright at 2008-06-16 15:52

OK, I got a message from console

Here is what came up on Console when I started up QC:

2008-06-16 14:10:01.472 Quartz Composer[215] *** -[NSBundle load]: Error loading code /Library/InputManagers/Menu Extra Enabler/Menu Extra Enabler.bundle/Contents/MacOS/Menu Extra Enabler for bundle /Library/InputManagers/Menu Extra Enabler/Menu Extra Enabler.bundle, error code 2 (link edit error code 0, error number 0 ())

===================

Here's what came up when I opened the demo "Kineme Global MIDI In CC Demo.qtz":

2008-06-16 14:11:38.750 Quartz Composer[215] Exception raised during posting of notification. Ignored. exception: -[QTVideoInput initWithClass:]: ivar "outputImage" of class "QTVideoInput" is not a subclass of GFPort

By Thorrific at 2008-06-16 16:13

wrong QC

You're using Tiger QC on Leopard, or Leopard QC on Tiger, or some other strange setup where versions don't match. None of the reported errors you've pasted indicate errors with our patches, only misconfigured/mismatches versions of stuff on your computer.

The error about QCVideoInput indicates a misconfigured system as well -- that's a Apple-produced patch that's quite reliable -- it shouldn't ever fail like that on a normal working system.

[To see if you're on Tiger or Leopard, click your Apple menu, "About This Mac", and then if it's Version 10.4.xx it's Tiger, and if it's 10.5.xx it's Leopard (and if it's 10.6.xx, it's Snow Leopard, but our Leopard patches still work there...)]

By cwright at 2008-06-16 16:21

So do you think I should

Well, I am on 10.4.11

with QC 2.1.2

So do you think I should toss out the QC app and re-install it?

By Thorrific at 2008-06-16 16:25

upgrade

At present, you should toss it and re-install your developer tools from the Tiger CD.

But I highly recommend you upgrade to Leopard -- QC's much nicer there, and all our development time is spent on Leopard plugins, not Tiger ones (with a few small exceptions)

Many of our Leopard plugins can cause QCTiger to act strange (though not like this, as far as I've seen -- they should just fail without causing built-in stuff to blow up), so you should add plugins one at a time so you can find the ones that break it (the leopard-only ones)

By cwright at 2008-06-16 16:28

Thanks for the help, I will

Thanks for the help, I will try that. It's weird because they worked for a while...

By Thorrific at 2008-06-16 16:45

well, I threw out and

well, I threw out and re-installed the entire developer tools package and it still doesn't work. I guess I will have to upgrade to Leopard?

By Thorrific at 2008-06-16 17:42

Leopard is the way to go,

Leopard is the way to go, definitely. QC 3.0 is a very different beast to the version shipped with 10.4. Having said that, it still has its 'quirks'. All in all though, worth the upgrade price on its own, I'd say.

alx

Quartz Composer Blog: http://machinesdontcare.wordpress.com

Music Site: http://www.toneburst.net

By toneburst at 2008-06-17 03:22