|
|
Problem with using Kineme GL Tools & Apple Primitives within Render in Image within Image Filter Template Basically, the composition - see attached working example - excuse current state of bloat codewise - will run AOK at all Viewer window resolutions, but when stopped at full screen and restarted, causes a an unrecoverable crash. [every time :-( ] Also, the uploaded example of this problem does have the noodle in the wrong place - although it will give a True setting flag. It was meant to be attached to the Value to start the queueing of the audio peak values, but now every time I try to attach that noodle , I crash, I also crash when trying to save the file if I've successfully joined the noodle. [immediately] 0x92438e4b: -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] 0x92415ae6: AppKitMenuEventHandler 0x9549311d: DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) 0x9549255b: SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) 0x954aeeac: SendEventToEventTarget 0x954e31c7: SendHICommandEvent(unsigned long, HICommand const*, unsigned long, unsigned long, unsigned char, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef**) 0x95509939: SendMenuCommandWithContextAndModifiers 0x955098f4: SendMenuItemSelectedEvent 0x9550980a: FinishMenuSelection(MenuData*, MenuData*, MenuResult*, MenuResult*, unsigned long, unsigned long, unsigned long, unsigned char) 0x954e6474: MenuSelectCore(MenuData*, Point, double, unsigned long, OpaqueMenuRef**, unsigned short*) 0x954e5e5f: _HandleMenuSelection2 0x954e5cd3: _HandleMenuSelection 0x9235249b: _NSHandleCarbonMenuEvent 0x922b91fa: _DPSNextEvent 0x922b85c0: -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] 0x922b15fb: -[NSApplication run] Pity it was beginning to look like a really nice idea, although I always find bringing almost any kind of audio interaction within a Render in Image placed at top level with the Image Filter template base tends to a be a little finicky. Sorry to be presenting nothing more than glowing comments on others recent uploads and my current problem whilst so many are letting their new comps and patches bask in the summer sun. I know the underlying Render in Image works well in other situations, so it shall be getting exploited elsewhere. |
Any chance you can trim this down some, so I can take a closer look at what's causing it?
Does it happen if GLTools isn't installed (i.e., with stock patches etc)?
(I was able to reproduce it, but with a wildly different backtrace -- I couldn't find any kineme stuff in the BT though, which makes it more difficult to track down)
I've "faked" image filter protocol for convenience at time, but this can squarely fit under the graphic animation protocol if desired ( I am starting to feel all sc-fi talking about protocols and such).
Anyway...
I'm NOT starting this up to reproduce the crash right now, because I have too much stuff open.
See what happens if you enforce a pixel width and height on your render in image patch.
Also, going from full to "not fullscreen" is probably restarting your patch time and screwing up that whole queue thing you have going on. Again, half talking out my butt since I haven't pressed render, yet those are two educated guesses from 10 seconds of poking around.
Simplified, yes, smaller byte size - for some unknown reason [see edit below] - not really.
Also without GL Tool dependent items - no reproduction of the problem. So actually, possibly - posting my own solution to my own problem - if only I knew just what was causing this problem. Definitely related to the Music Visualizer protocol. Been getting other crashes related to running Image Filter dependent Music Visualizers.
Indeed the example attached is actually getting closer to reproducing the sought after effect, without reproducing the problem.
When I try to remake the original from the Image Filter template it weighs in at over 300KB before any of my stuff gets slotted into place.
will give that try in the meantime this a little more like what I actually meant to do. I don't think that the graphics animation would do this but who knows? I might give it a try.
I don't find that the Image Filter template file is good to edit too much in on any Composition, RIM image input component. Best to get it adjusted and sorted externally before doing owt else, same likewise with the image filter and the scripting in either the rim, composition dropped in or the image filter layer.
Again, excuse the bloat.
edit - this works then crashes - so problem kind of reproduced. Will leave this for now as it is not getting anywhere fast. Will look at it again, but under the simpler more successful conditions as described above
Two examples that allow for the use of GL Tools line and point within an image filtered / visualizer successfully and unsuccessfully , respectively.
file audioimagefilterbug3 works AOK, whilst file audioimagefilterbug4 works AOK, but if you switch the viewer off and go to save half the Kineme Spline options disappear, see attached picture.
Probably just a bad mix of elements, but when iTunes is running, and visualizing concurrently results in a kernel failure. [bad exec]
Ok, this looks like a bug with GL Spline (I've triggered a crash with it as well) -- hopefully that's the underlying issue. Taking a look at it.
Cheers, I am busying myself right now with clearing up my plugin folder.
Time to put that Apple TV to good use and view some sci-fi methinks - this has been a real stop start day with these crashes, they have last occurred with one particular, non Image Filter dependent compostion that otherwise works AOK as a visualizer in iTunes, but refuses to be editable past any useful point in QC - just crashes as soon as any initally saved parameters are reset - colour , position - whatever !
I hope this is of some use... I just had an issue with the spline yesterday, and iterator, and it crashing QC if I would drop a spline patch on the editor while QC was running. This is in the context of a standard kind of iterator setup where you are moving an object from front to back on the z axis.
As it happens the very same composition is fully editable in QC on a PPC G5, just my Intel Mac that's giving grief.
Splines
Intel
our clues for the day :-)
G'night y'all
// edit //
try 1.1 not 1.2 GL Tools was the solution for the time being as I have lately found out.
// edit //
Ok, with my current build (only cybero and myself have it at this point), both of these work across start/stop in both windowed and fullscreen modes on Intel and PPC (via Rosetta at least).
Cybero, is that the case for you? (you indicated not in your email, but I want to exhaustively hit each composition posted on this thread).
This composition works for me with both Intel and PPC (via Rosetta) with my (and cybero's) latest build. Function across start/stop, fullscreen or windowed.
cybero, is that the case on your end?
Thanks gtoledo3 and cwright for your input.
I have no problem as it happens whilst running any of the files submitted against GLTools 1.1, it is 1.2 that provokes problems as I found out earlier today, when I replaced the newer version with the older one.
Only under 1.2 do I get any of the reproducible problems , specifically, cannot edit without a crash and also can't save such without a crash if opened and simply run.
Under 1.1 I can open at Viewer window, go full Viewer window, stop , go full screen, start full screen and so on without any problem at all.
Sigh - I was so looking forward to using that Inverse Rotation from the 1.2 build.
Pardon the extra reply, but having hauled a a couple of self made items out of /Library/Graphics/Quartz Composer Patches and placed them into ~/Library/Graphics/Quartz Composer Patches, then cleanly deinstalled the older and reinstalled the new GL Tools, logged in, logged out, I find that all the experimental items work AOK without any imperfections.
*So - just to say it loud, the 1.3 GLTools plugin patch works AOK**
All told, I'm half inclined to zero my disk and go for a fresh clean install with little or no migration, which previous migration is , I suspect, another contributory factor to the tangled installation history on such a new bit of kit.
Funny thing about Rosetta, I hardly ever see it anywhere •~
However, the beautiful composition that I wanted to upload won't fit the category it was intended for.
Methinks the ImageFilter template is just too , well Image Filtering to allow for the subsequent inclusion of any other protocol at any level.
So for the time being this will just have to be a footnote until properly worked to fit the bill it was intended for - still rough draft stage in any case on the composition. Must see if it will QC
And yet, the day laughs in my face, for the very file in edit mode post upload, has yet gain crashed in QC.
Interesting how the Spline issue is so finicky .
Time to get some cooking done.