|
|
Kineme Core v0.5 auto recovery has put me into an infinite loop Does KinemeCore have a safe-boot-mode where I can disable the autoload of an offeding .qtz comp causing GPU overload 'crash'? I set the Rii patch to its max dimension (4096x1671 for me) to output a still using the imagewriter patch tb compiled from apple dev examples. It has made QC so slow to respond it is effectively 'mangled' beyond user-interaction (if not technically crashing). Force Quitting QC and reopening is making KinemeCore reload the composition and go into death-mode again. I've tried renaming the autosave file which doesn't help. Removing GLTools in Patches Folder saved the day as it broke the render chain in the comp and I could edit the resolution of the RII patch. It took me a while to twig — I was typing this post saying there are no plugins left to disable… then realised patches so wasted lots of time. Be good if KinemeCore could go into a don't-load-autosave–mode with option-key boot or something. I guess editting the Plist was next but I wasn't sure where KinemeCore was getting the comp file from. And where is KinemeCore itself installed to, I could find it either to uninstall it (temporarily of course ;) )? Also, any hints for getting greater mileage out of RII patch, anybody?
|
Thought...
Does this really have anything to do with k-core?
Can't you just disable the Viewer from starting automatically when you open a composition? I bet if that wasn't happening, nothing would evaluate, and the image writer would never start to begin with.
I have k-core installed, and when QC opens, I get nothing but a title bar, no compositions open, no Viewers to make a wonky thing start evaluating and crash, etc. That is all part of the generic prefs. When k-core saves a composition that crashed... it doesn't reopen when I open QC either. That's not a k-core pref either, just standard.
I may be overlooking some weird bug or something, but I would definitely recommend to never have the Viewer start by default, whether or not you use any plugins.
You could always find wherever the file is located at by doing a search in Finder for your qtz files, by searching something like "qtz crash" or "qtz pid". It's usually on my desktop or wherever the file was located to begin with... I think the desktop, but I always do my work on my desktop, so I'm not 100% sure.
If you rename the file with a different file extension, like "au" or something, QC app won't open it.
I can't believe I just saved over my comp and NONE of the patches were inside the RII patch when I reinstall GLTools. Usually I keep versions of files on a big project but in this case nothing spare.
I have a 4K version of my file saved over the good one with 2 days of Javascript coding lost, save for a screen shot I have with 25% of the code shown. And no, I don't have time-machine!! I am reminded of our ultimate impermanence, once again. Time to buy a FW drive.
Yes good points gt. Do nothing at start up was set, so don't know why it is opening files unless KinemeCore is telling it too. View window was selected at start up so switched that off, good advice.
It was not the crash file QC was opening, well the name hadn't changed in the editor window title bar anyhow. I'm confused as to what makes QC open a file automatically if you have Force Quit out. Sometimes KinemeCore will save a crash file, sometimes not, but always QC seems to try reopening the file I was working, which is perhaps part of the autosave functionality??
Another part of my problem was I actually need to get this file open because it was the only version with all my JS code updates. Tonnes of time went into it and my project deadline is like, tomorrow! so not much time to re-write code. Presuming I can!
Is there a way to get into files contents and JS code via PList editting, I'm pretty new to that kind of lowish-level thing.
Thanks for the tips though, george.
Sorry to hear it. Sometimes things like that just happen, even though you're good with data hygiene. All programs should have incremental save and autosave built in.
For future reference, yes, you can get your javascript out of .qtz files. I just checked with TextWrangler, and any script is just stored as a string inside the XML in there.
renaming to .au will get it out of QC, which is nice (you can then change QC prefs, etc).
You can also open the composition in Property List Editor, and find the JS code that way. It'll take some searching though.
Another alternative to is get an app called 0xED -- that's a hex editor. You can load the .au in there, and poke around till you find your source (other hex editors, like hexfiend, work as well).
kinemecore does absolutely nothing with document opening. If you remove kcore, does the problem still persist. if not, there's a severe bug that we overlooked somehow, but I have a feeling it's QC trying to be polite, and not any plugins.
Isn't there an open source versioning technology that can be used on OS X? Suppose time machine is that but don't really want to be versioning all my files just documents can it do that?
Cool, thanks.I think you are right about QC doing the auto-opening. I don't have the file to check anymore (boo hoo) I saved over it with an almost entirely empty RII macro when I disabled GLTools to get into it (duh that was stupid). The nest of macros had a GL-scale patch near the top.
For future reference: I wasn't sure which file QC was auto-opening because when I change the autosave filename (but not the filetype: .qtz) it still auto-opened it. Next time I'll try .au until I find the file.
I think I was overcooking this design. Took this as an opportunity to finish the job in Ai and stop complicating it with QC madness that my machine can't process. All this came about because I was working down near 1 fps to render a maximum size still image.
I recoded all the JS and it wont run. I'm sure the code is clean. I've tested every function and routine independently in isolated comps. JS patch absolutely drives me mad when it does that. I consider it a Major bug.