True... it sounds like it was a simple un-studied solution. It is
important to mention that all crashes where submitted to Apple via
crash report and to Kineme via Kinemecore's crash dialog with
comments, name and e-mail address, describing the crash. All as you
just suggested as MOST important in the Kineme forum.
far from being a developer I can't suggest the problem was caused by
one or the other preferences file. Empiric observation led me to
delete Kinemecore's preferences first. As the problem continued and QC
still crashed I decided to delete QC preferences also. Now I can even
use the kinemecore plugin v 0.4 with all options on and off and can't
make QC crash again! Note these preference files where the only thing
I didn't change in the whole process. All other plug-ins and patches
were updated and replaced by their most recent versions available at
Kineme.
Other problems seem to be solved since the prefs were deleted.....
such as the Serial number for Kineme 3D not sticking.
And here the gathering of events with the long version of logic and
method:
Installing Snow leopard led me to the new QC4. The installation
succeeds. All my plug-ins came from Kineme plus Vade's movie player.
First time I open QC4 I notice a black patched screen looking a bit
weird to be the welcome screen of QC4. Scanning the net I find out
Kineme's GL tools have an update for 10.6. So, GL tools 1.3 solved the
issue. This makes me think other plugins need to be updated. Shortly
after there are several updates at Kineme. Also Kinemecore has a new
version.
New versions installed so I decided to open one of my own
compositions. This produces a long list of:
> (null)
<QCNodeManager | namespace = "com.apple.QuartzComposer" | 353 nodes>:
Patch with name "/xxxxxxxxxxxxx" is missing, (wrong architecture,
etc..etc..)
where xxxxxxxxx is the name of some patches and plugins such as vade's
movieplayer, used often in my compositions.
So, I think.... all custom patches and plugins may need to be updated.
I take them all out of the patches folder and start using only those
with new versions or tested Betas.
Fortunately there are updates and betas for the plug-ins I used. One
by one, drop them in the patches folder and start QC again. This seems
to me like the thing to do.
Here I note QC4 is working fine only when I open a composition by
double clicking it. If i start QC4 from the dock i get a "back trace"
message. Take all plugins out again and start QC4 only from the dock
with one plug in at a time. All works fine except with Kinemecore. But
Christopher Wright has a working version at Kineme. So how come it
doesn't work in my system? Kinemecore v0.4 in my patches folder
produces a back trace error and some console messages sent in previous
messages to the list.
May be old caches stored somewhere in my system keep traces of the old
patches. So i decide to remove the developers folder as described in
the Xcode installation manual. Reinstalled Xcode started QC4 and again
the crash. Also canceling the template chooser dialog will cause a
crash. There are no custom plugins in the patches folder!!!!
Then I found out that someone at kineme's forums had similar problems
with Kinemecore. Dust's solution against the "back trace" problem was
to delete both QC and Kinemecore's preferences.
I decide to delete Kinemecore's preferences first. In kineme's forum
it is mentioned there were problems after selecting the slim title bar
option in kinemecore's preferences.
http://kineme.net/Release/Production/KinemeCoreSuggestions#comment-10044
However, QC still crashes. ONLY thing to do is to delete QC preferences.
Deleted and problem solved.
Juan Ayala-Cortés
On 02 Oct 2009, at 20:53, George Toledo wrote:
It sounds like removing the old version of Kinemecore resolved the
backtrace (this makes sense). Trashing the preferences likely didn't
have anything to do with it.
In doing things like this, it's much more constructive to change
elements one at a time, and take note as to the exact change that
resolves an issue (and then make sure to let the Developers know). It
can be counter-productive to infer cause and effect from methodology
with obvious flaws in logic (in this case, making two changes, instead
of each separately).
At the same time, I understand that in a working environment, one
sometimes needs to get something going quickly, and broad strokes are
more expeditious. However, this gives next to no constructive
information.
What was it that resolved the backtraces? Removing the old Kcore, or
deleting the plist? I have a pretty good idea myself, from my own
testing on a couple of systems (it's the old Leopard kinemecore
operating in SL, more likely than not), but it would be nice if there
was a level of methodology here that actually isolated what the exact
step is that resolves the issue on your particular system.
I say this with the best intention and humor; this is just a
suggestion to do with as you will! Without that kind of approach, it
can be a really flummoxing situation for Developers to try to solve
problems.
-George Toledo
On Fri, Oct 2, 2009 at 2:31 PM, Juan Ayala <[email protected]> wrote:
Solved. From the forum at Kineme, Dust mentioned deleting preferences
solved some "back trace" problems. Since I don't really need
Kinemecore installed at the moment, I deleted both QC and Kinemecore
preferences. This returned QC4 to a normal behavior.
Juan
On 02 Oct 2009, at 18:30, Juan Ayala wrote:
Hello Christopher,
Starting from the dock works now without any plugins. Everything works
fine opening examples and own compositions. However.... I decided to
repeat the action by clicking cancel in the template chooser (instead
of opening one template) and the crash happened again. Not a big deal
for now so I'm planning to simply go back to QC3. Looks like there are
many possible bugs or inconsistencies around related to plugins.
(By the way... Another problem... QC doesn't ask to save files when I
close the editor or the viewer. Only when I quit QC the "save" dialog
appears.)
If I decide to reinstall Xcode, is there an extra procedure to remove
all Xcode tools, preferences, folders etc? I have used this command
line today a couple of times:
sudo /Developer/Library/uninstall-devtools --mode=xcodedir
Then deleted folders manually. Reinstalled Xcode and the problem
remains. I have also removed the patches folder in my user folder. (~/
library/graphics/... )
Just incase .... attached the crash report i'm getting.
Thanks for your quick response!
Regards,
Juan
<crash report.rtf>
On 02 Oct 2009, at 13:55, Christopher Wright wrote:
Using Snow leopard, QC4. Just cant get QC working if I cancel the
template chooser. It crashes. (see image) My solution so far is to set
the QC preferences to "do nothing" (instead of template chooser) AND
starting QC by double-clicking one existing composition. This solution
also helped me to start QC with Kinemecore. otherwise this is what I
get if I start QC from the dock.
Do you have any 3rd party plugins installed? try removing them and
see if the problem persists.
Older versions of KinemeCore (prior to the 0.4 release) caused that
problem for me on startup, so that might be the cause.
Otherwise, I couldn't duplicate it on 10.6.1.
--
[ christopher wright ]
[email protected]
http://kineme.net/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list (Quartzcomposer-
[email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/juanpa%40wp.pl
This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list (Quartzcomposer-
[email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/gtoledo3%40gmail.com
This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to [email protected]
