I tried iShowU instead of SnapX pro for screen capture.
I tried iShowU
I can tell after just a few recordings that iShowU is infinely superior (and
cheaper) than SnapX pro, so I would strongly recommend it for anyone doing
screen capture on a mac (as if Michael Roxanne's recommendations are not
enough :)
You can easily set it to DV and even select FCP uncompressed, as the
compression, and the clips work perfectly in final cut pro (though they have
to be rendered).
... Richard
On 8/30/07, Richard (Show) Hall [EMAIL PROTECTED] wrote:
I can't get SnapX recorded files to work in final cut pro.
When it finished rendering, or when I try and play the file on the time
line after rendering in the canvas I get general error.
I had this problem before and Michael and Ryanne sent me settings which
worked, but that was with an older version of everything and I think was
even with my old non-intel mac.
I found the following in the snapX manual (new version).
How can I import my movies into Final Cut Pro?
Currently Snapz ignores the frame rate settings in the movie
compression dialog, and uses the actual frame rate of the capture --
which may vary from frame to frame. This was how 2.0.3 worked, but
Final Cut Pro cannot load those movie files.
As a workaround, we've added an option to force Snapz to convert the
movie to the specified frame rate. Unfortunately, this can cause the
movie to appear choppy as frames are dropped or doubled up to
maintain a constant frame rate. One way that may reduce this
choppiness is to capture at a higher rate (say
30fps) and then down-sample to a 10 or 15fps output movie.
If you want to enable this option, enter the following line into a
terminal window:
defaults write com.ambrosiasw.snapz EnforceFrameRate true
You will not see the effects in the GUI, but the current build will log
the
details of the conversion.
So I opened terminal in the utilities and at after a command line I
typed the stuff beginning with defaults and ending with true.
I hit return and it went to another command line - nothing changed with
the way final cut pro responded to files.
Any ideas/thoughts much appreciated.
... Richard
--
Richard
http://richardhhall.org
Shows
http://richardshow.org
http://inspiredhealing.tv
--
Richard
http://richardhhall.org
Shows
http://richardshow.org
http://inspiredhealing.tv
[Non-text portions of this message have been removed]
