|
problem with Kineme patchesI've installed some kineme plugins and the Quartz Composer application is giving some errors and running weird after that! I attach here the finder screenshot of my plugins. This is some of the the text in console: 8/11/08 10:13:55 PM Finder[104] *** <QCNodeManager | namespace = "com.apple.QuartzComposer" | 354 nodes>: Patch with name "ParticleOperatorVectorRandomPatch" is missing 8/11/08 10:13:55 PM Finder[104] *** Message from <QCCamera = 0x19079C20 "(null)">: Cannot create node of class "ParticleOperatorVectorRandomPatch" and identifier "(null)" 8/11/08 10:13:55 PM Finder[104] *** Message from <QCCamera = 0x19079C20 "(null)">: Cannot create connection from ["outputObject" @ "ParticleParticlePatch_1"] to ["inputEmittedObject" @ "ParticleEmitterPatch_1"] 8/11/08 10:13:55 PM Finder[104] *** Message from <QCCamera = 0x19079C20 "(null)">: Cannot create connection from ["outputRenderClass" @ "ParticleRenderClassPatch_1"] to ["inputRenderClass" @ "ParticleParticlePatch_1"] 8/11/08 10:13:55 PM Finder[104] *** Message from <QCCamera = 0x19079C20 "(null)">: Cannot create connection from ["outputOperator" @ "ParticleOperatorVectorRandomPatch_2"] to ["Child Operator 1" @ "ParticleEmitterPatch_1"] 8/11/08 10:13:55 PM Finder[104] *** Message from <QCCamera = 0x19079C20 "(null)">: Cannot create connection from ["outputOperator" @ "ParticleOperatorNumberRandomPatch_1"] to ["Child Operator 2" @ "ParticleEmitterPatch_1"] 8/11/08 10:13:55 PM Finder[104] *** Message from <QCCamera = 0x19079C20 "(null)">: Cannot create connection from ["outputObject" @ "ParticleEmitterPatch_1"] to ["Object 1" @ "ParticleScenePatch_1"] 8/11/08 10:13:55 PM Finder[104] *** Message from <QCCamera = 0x19079C20 "(null)">: Cannot create connection from ["outputObject" @ "ParticleForceVortexPatch_1"] to ["Object 3" @ "ParticleScenePatch_1"] 8/11/08 10:13:55 PM Finder[104] *** Message from <QCCamera = 0x19079C20 "(null)">: Cannot create connection from ["outputScene" @ "ParticleScenePatch_1"] to ["inputScene" @ "ParticleRendererPatch_1"] 8/11/08 10:13:55 PM Finder[104] *** Message from <QCCamera = 0x19079C20 "(null)">: Cannot create connection from ["outputOperator" @ "ParticleOperatorVectorRandomPatch_1"] to ["Child Operator 3" @ "ParticleEmitterPatch_1"] 8/11/08 10:13:55 PM Finder[104] *** Message from <QCCamera = 0x19079C20 "(null)">: Cannot create connection from ["key_0020" @ "Keyboard_1"] to ["inputNy" @ "ParticleForceVortexPatch_1"] 8/11/08 10:13:55 PM Finder[104] *** Message from <QCTrackBall = 0x171A9850 "(null)">: State restoration failed on node "Camera_1" <QCCamera = 0x19079C20 "(null)"> 8/11/08 10:13:55 PM Finder[104] *** Message from <QCPatch = 0x171C1B30 "(null)">: State restoration failed on node "TrackBall_1" <QCTrackBall = 0x171A9850 "(null)"> 8/11/08 10:13:55 PM Finder[104] *** State restoration failed on <QCPatch = 0x171C1B30 "(null)"> 8/11/08 10:13:56 PM Quartz Composer[391] -[QCPatchClassDescription initWithNodeClass:]: ivar "outputImage" of class "KinemeImageWithComposition" is not a subclass of GFPort 8/11/08 10:13:56 PM Quartz Composer[391] -[QCCompositionRepository doesPatch:conformToProtocol:]: Argument "patch" cannot be null What am I doing wrong? or is this a bug? Thanks in advance, Ali Demirel www.magnetmus.net
|
I'm guessing the plugins are improperly unpacked -- notice how they're blue folders instead of the white box plugin icon? That means that Finder doesn't think they're plugin bundles, and thus they don't get loaded as such. try re-downloading them.
open the folders, and see what's inside -- that might also help see what's happening.
it happens the same thing to my plugin folder, (now its ok) but i didn't do nothing strange (relative strange) and nothing happens to qc.
the icon is blue but the extension is .plugin
maybe help you
Daniele
i tried downloading again, when i extract the zip file, i still see them as a blue folder, not as a white plugin file. however, this time, i can open compositions with those plug-ins (for example 'archimedes-in') in QC, with no error in Console, and I can see those patches listed in QC. BUT when I try to activate them in VDMX, VDMX crashes with this console messages:
8/12/08 10:37:52 PM com.apple.launchd[106] ([0x0-0x4b04b].com.vidvox.VDMXpb4[470]) Exited abnormally: Bus error
Any idea what's going on? Should I consider this as a VDMX failure now? or something fucked up in my system?
Try taking out all the plugins, and add them in one at a time, starting VDMX after each one is added. I'm guessing it's just a single plugin that doesn't play nicely with VDMX. When you find out which one it is, please let us know :)
I think it's the ParticleTools plugin: Because I added AudioVideo plugin first and it worked when I triggered your 'soundflower' composition. However, after I add ParticleTools and trigger 'archimedes-in' it crashes...
thanks for narrowing this down. Can you e-mail or attach a crash log so we can look into this?
Do any other particleTools compositions crash VDMX, or is it just that one particular composition?
others are causing crash too. below is the log for 'fire' composition. it looks like it can't find patches however i can open the 'fire' composition in QC with no errors...
the line
8/13/08 11:55:49 PM VDMX[2458] *** Patch class "ParticleRendererPatch" is not allowed in safe mode
indicates that it's not loading the patches because VDMX only allows safe-mode patches (that's a surprise to me..). since it fails to load them, I guess vdmx doesn't handle that well, and it dies. weird. And not our fault... :)thank you for helping me figure this out :) i'll write to VDMX about it...
howdy-
vdmx doesn't only play back clips in safe-mode; the warnings posted above were generated when vdmx was making thumbnails. cwright, here's what the crashed thread looks like (i'm surprised nobody's fwd'ed it to you yet):
...now, i'm no opengl guru- but it looks an awful lot like this crash is occurring because your plugin either doesn't have a valid gl context or is referring to the wrong gl context prior to making some gl calls. i did a [very] little poking around, and adding a [context makeCurrentContext] in vdmx prior to creating the QCRenderer which instantiates your plugin magically seems to make everything better.
: ray
Ahh, that crash is our problem :) Thanks for the relevant crash log, haven't had one sent our way yet.
A casual overview makes your GL context theory seem likely -- VEE's a nasty rat's nest, so it wouldn't surprise me if it's issuing some gl calls before it ought to.
I'm not sure how difficult it will be to do appropriate context swizzling, but I'm sure we can work something out on our end.
Thanks for the heads up :)
Cool that it looks like the problem will be solved :) Looking forward to it because I really want to play with those cool patches through VDMX...
We're planning to rewrite the VEE rendering pipeline soon (and maybe the rest of VEE while we're at it)..
Looking forward to cleaning things up a bit.
But conveniently, fixing this only takes like 6-8 lines of code I think (I need to test it, hopefully sometime this evening if this training ever ends......................................................), so we could have an intermediate fix in a day or two (maybe with our performance tweaks from WWDC, if they're stable...)
Fix published.
yes! it's working now :)
however, there is a similar problem with the 'Original Kineme Plugin, v0.2': whenever i put this plugin to patches folder, vdmx does not respond, no message in the console, and when i try to open a demo file like 'Kineme Document Info Demo', QC acts weird too, i only see a gray frame in the viewer and these messages in the console:
any idea?
thanks, ali
From the release page:
;)
sorry :)