[Mark]

I have rerendered. I now see that even with realtime no render if I drop the keyframe opacity one notch it with glitch between the
key frame jumping about 15 frames. It might be related to some older captures. For now I am throwing in some work arounds
to get some files for the client. I’ve just cut the clip at the key frame and slip it forward. Strange but works. I might just have
to recapture the guilty clips but wouldn’t you know it my deck is out on rental right now. ha! upgrading in a middle of a project
what was I thinking!

Thanks for you help.

[Mark]

I’m working with uncompressed 8 bit pipe pro capture from betacam. This project has been updated many times and
footage has gone from drive to drive and recaptured and lost and relinked and soforth so it’s not a clean recently captured
ducks all in a row project if you know what I mean. I have found a few work arounds for some of the glitches. might be related
to some older captures working with new ones. Or sources that are used but not linked in the project. I knew I should have waited
before installing this update to see what bugs show up. What was I thinking installing updates just before outputing. Doh!

Thanks for all the help. I guess I’ll fix it with work arounds for now.

Mark

[Mark]

Thanks for the feed back Dan. I have been wanting to here about someones system similar to mine working fine just so
I could have piece of mind plugging forward to a bug free capture and edit day. I’m in the middle of a waterfall landscaping
“how to” project with 10 hrs of raw and approaching a 2 hr dvd so I am going to wait till this raps up before I try any new
configs. As you suggested to Jared I have turned off the “abort on dropped frames during capture” so that it will batch without stopping. I haven’t
noticed a real dropped frame yet on any captures but figure I’ll just go and recapture if I see an issue. Though I would
not recomend turning off the “abort on dropped frames on capture” permanently since dropped frames are not always
easly spotted. It just would be nice to know it’s all there without having to find the glitch later and digging up the tape again.
I’m looking forward to FCP 5.0.. Regards, Mark

I fixed the compressor issue from an earlier Cow link.
The Cow is quickly becoming like my cell phone… what on earth did I do before it!

[Mark]

Not that this is of any help but I have a similar problem with an internal 4 drive(maxtor 300g 16mb cache) software raid, seritek 1v4 card,
a uvw 1800 beta deck and a aurora pipe studio capture card. No time code break errors but I get a random dropped frame error
usually at the very start of the capture. I’ll press try again a couple of times and then it suddenly will deside to capture, even a
long piece, then a short 2 sec capture comes up next and it errors dropped frames again. I have to baby sit the process and keep
hitting return on error. Batch capture use to be a coffee break for me! Now its the biggest hassle.
I’m Running G5 2.3, 2g mem. FCP 4.5 quicktime 7.0.3 and all updated aurora.

Did you do a computer to computer upgrade? I upgraded from a G4 moving all my programs and files from there to the G5. I was under the
impression this is as good as a clean install but not sure now.

When I try to compress a FCP file using compressor it gives an “unable to connect to background process” error.

[Mark]

The system software is still on the 250g drive that came with the G5
For those that may wonder how I have an internal raid + the system disk
I have setup a mount on the base of the G5 behind the two big fans for
extra hard drives similar to the Swiftdata 200 but I used standard drive
mounts modified by a dremel tool to make them attach to the base plate
which is attached to the G5 base.
Thank you for the possible culprit Charlie, Have you heard of a 2 drive array
working fine for betacam uncompressed capture?