I took all of my clips and exported them from mpeg streamclip as one long clip ProRes 422 hq and then sunk up and recut in fcp.. Ever since comming out as one long clip it has been freezing up fcp after playing in timeline after roughly 5 seconds. After syncing in fcp I am exporting indivdual scenes to edit at a later date. After rexported from fcp as smaller clips there is still a freezing problem?
7d to ProRes freezing up FCP ?
- Thread starter NB1
- Start date
Imac 2gb ram 2.16ghz intel core
After I Mpegstream clipped the clip it was fairly huge 125gb stored on A 2tb Lacie HD connected by a firewire 4oo.
My paln was to then breakdown that large clip into smaller clips and export. After breaking the large clip into 12 clips it still skips.
After I Mpegstream clipped the clip it was fairly huge 125gb stored on A 2tb Lacie HD connected by a firewire 4oo.
My paln was to then breakdown that large clip into smaller clips and export. After breaking the large clip into 12 clips it still skips.
Restart your computer + hard drive to reset your memory cache. Also how full is your hard drive now after filling it up with 100+ gbs of footage?
Turn off all background running programs as well when you are working with FCP. Also I might suggest bumping the memory in your computer to 4gbs, it truly makes a difference.
Finally I would suggest for you to get a firewire 800 drive, 400 is actually not that fast.
Turn off all background running programs as well when you are working with FCP. Also I might suggest bumping the memory in your computer to 4gbs, it truly makes a difference.
Finally I would suggest for you to get a firewire 800 drive, 400 is actually not that fast.
Last edited:
WhiteMonkey
Well-known member
if you use the batch feature of MpegStreamclip you won't end up with one big file. You can then use the transcoded files as proxies.
WhiteMonkey
Well-known member
size shouldn't be an issue. I would guess it's the codec. Can you reinstall Quicktime?
ChuckS
Veteran
Size is definitely an issue, not so much the size of an individual file but certainly its data rate.
First off, unless your outputting this project to film you don't need ProRes HQ, ProRes LT is more than plenty for HD.
If you are outputting to film then Lacie 400 FW drives are cheap and lack adequate buffering to support the 220Mb/s data rate of ProRes HQ. Your going to need Fiber Channel drives or a fast eSata RAID to give you adequate data rates.
So if your hoping to work in HD then do what was recommended earlier, batch import with MPEGStream clips or the Canon plugin set to ProRes LT.
First off, unless your outputting this project to film you don't need ProRes HQ, ProRes LT is more than plenty for HD.
If you are outputting to film then Lacie 400 FW drives are cheap and lack adequate buffering to support the 220Mb/s data rate of ProRes HQ. Your going to need Fiber Channel drives or a fast eSata RAID to give you adequate data rates.
So if your hoping to work in HD then do what was recommended earlier, batch import with MPEGStream clips or the Canon plugin set to ProRes LT.
morgan_moore
Major Contributor
my mac can play prores (regular) but not prores HQ in FCP
i imagine it is a data rate computer muscle issue
S
i imagine it is a data rate computer muscle issue
S
One of the few advantages of using a Macbook Pro with an eSata connection is that you can work freely using Pro Res Hq.
To my knowledge you can inly get an eSata connection on a Macbook Pro ( certain models) and a Mac Pro. I think the newer iMacs can run fine with firewire 800 since they are such fast computers, but for older models you might want to stick to regular Pro Res.
To my knowledge you can inly get an eSata connection on a Macbook Pro ( certain models) and a Mac Pro. I think the newer iMacs can run fine with firewire 800 since they are such fast computers, but for older models you might want to stick to regular Pro Res.