Thank you so much for this, I did exactly as you said.
There was 1
plugin in the Users/Library/Graphics/Quartz Composer patches/ that was
causing all of this.
Thanks again
Date: Mon, 27 Dec 2010 12:47:22 -0500
Subject: Re: Quartz Composer crashing after adding plugins and patches
From: gtole...@gmail.com
To: ramonara...@hotmail.com
CC: quartzcomposer-dev@lists.apple.com
On Mon, Dec 27, 2010 at 11:42 AM, Ramona Behravan <ramonara...@hotmail.com>
wrote:
Hi everyone,
I'm very new to QC. A friend of mine gave me some plugins and patches for QC. I
double clicked them and I guess they've all been installed and now QC does not
open, it crashes after second. I tried changing the bit mode from and to 32
bit, nothing happened, tried deleting the patches and plugins, again nothing
happened. also I can't find the com.apple.quartzComposer.plist, I saw in a
forum that I should move the plist but it doesn't exist.
Can you please tell me what I can do about this? Do I have to re-install QC, if
yes where do I get it from online? Otherwise how do I deal with this issue.
Many thanks
When Quartz Composer.app starts, it looks for patches, and loads them into the
app. This can be "built in" patches from the app, or patches that are present
in any of the three "Graphics" folders in OS X (the System/Library, the
/Library, and the User/Library. This allows the scope of what a plugin can
affect to be controlled. In general, it's best to place custom stuff in the
User folder, to make sure that the OS doesn't load any plugins for its own
processes.
These patches can be QCPatches, QCPlugins, or qtz's (which are a type of
QCPatch). Depending on the type, one places it in either Graphics/QCPlugins or
Graphics/QCPatches. Stock/standard api stuff always goes in Quartz Composer
Plugins folders, "skanky"/non-Apple api stuff, qtz's, and one or two plugins
that the OS installs, always go in Quartz Composer Patches folders.
If you were double-clicking on plugins to install, you must have had the
Kinemecore.plugin/QC Patch already installed. If one was to have a stock
install, place just the Kinemecore.plugin inside of
User/Library/Graphics/Quartz Composer Patches, and double click on plugins for
every other plugin/patch install, things should generally work without problems.
When QC.app opens and a plugin causes problems, one can throw that plugin
away... and if the app is still active, the problematic patch will actually
*still be loaded* in QC. Whenever you're getting rid of stuff, or doing
updates, you should manually restart QC to be double-sure. (Kinemecore
automates restarts the app on upgraded patches, so that patch will handle this
for you automatically, *if* everything was working right to start with, and if
installed already.)
There are also "Image Unit" folders that can be in the Graphics folder as well
(and can also cause QC to crash, if they are "bad").
Sorry for the novel, but I thought that needed a run through first...
So, first, I would probably try removing all three Graphics folders, placing
them on the Desktop (or some folders that clearly label where they came from),
make sure QC is off, and *then* start it up. This will make QC start with no
extra plugins/patches/image units for sure (it's also removing some stock
stuff, unfortunately).
If QC still crashes, I would do another search for that plist, and delete it
(it may not exist if QC has never started up successfully... but if it has,
even once, it is definitely in there somewhere.)
If you get QC so that it's not crashing, go ahead and add back empty folders in
all of the Graphics locales. Install kinemecore in the user locale, and then
start installing your plugins/patches one by one and testing.
If none of this works (there really shouldn't be a problem if there are no
Graphics folders being loaded, and the plist gets written from scratch) or if
you feel like the folder setups may have gotten really whacked out, and you
just want to be *really* sure, you can always reinstall all of Developer Tools,
which should set you up with a clean QC install. Then, when you add new
plugins/patches, add them one at a time, checking that each new plugin or patch
doesn't mess up QC.
Awhile back I had some plugins (or were they image units?) that were crashing
QC on start - CIGrabberDesktopInput and CIGrabberWindowInput. I would probably
make sure neither of those were installed off the top.
-GT
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/gtoledo3%40gmail.com
This email sent to gtole...@gmail.com
--
George toledogtole...@gmail.com
www.georgetoledo.com
The information contained in this E-mail and any attachments may be
confidential.
If you have received this E-mail in error, please notify us immediately by
telephone or return E-mail.You should not use or disclose the contents of this
E-mail or any of the attachments for any purpose or to any persons.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
