[Andi Winter]

is it the spinning wheel of death or just quitting with no error code?

[Andi Winter]

look in the media pool, do you have proper reel-names?

are the reel-names the ones from the xml?

if not, change the reel name setting (eg to embedded in source clip)

[Andi Winter]

then try node sizing! you can grab a still
and append the node to varilous clips
at once.
or do it the dirty way:
make two black windows to fo the “cropping”….

[Andi Winter]

why dont you just grab a still of the cropped clip, turn the cropping off in the edit page and apply the changes
where they should have been applied in the first place, in the input-sizing of the clip. if you wanna have the all
your clips cropped the same way, do it in the track tab and you’re done!

[Andi Winter]

copying each node seperately should work…

[Andi Winter]

if you wanna use noise reduction, go for more
ram! as the announced v11 will have better caching
as well this seems to be more future-proof!

[Andi Winter]

get an additional gtx gpu, i think the quadro
could be your bottleneck.

[Andi Winter]

interesting! yes, hitting rewind/play very fast
sometimes can cause this on my machine as
well! and i have a cooper eclipse, so it’s not
the element…

[Andi Winter]

another thing, i am wondering if i am the only one:
during grading in split-screen-mode or sometimes by simply viewing
and hopping from clip to clip resolve just quits without an error-code.

anyone else?

OSX 10.8.5
double titan

[Andi Winter]

go to the tracking tab, switch to stabilize and track forward. go on the context menu
and copy track data. switch to your clip where you wanna have the data, paste track data,
change parameters and hit stabilize.