Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
FNE 3.5 keeps freezing?
- Thread starter papa792
- Start date
- Sort by reaction score
Yep, that's 400. Are you capturing though a tape deck or cable from your camera? If it's the tape deck I would try to get a FireWire 800 cable or if your camera has a 800 port. What is the HD resolution (1080x1920 or 720x1280) you are capturing in and what do you have in Easy Setup? It could be that the 400 isn't fast enough so it's freezing up and "dying"
.
.Yep, that's 400. Are you capturing though a tape deck or cable from your camera? If it's the tape deck I would try to get a FireWire 800 cable or if your camera has a 800 port. What is the HD resolution (1080x1920 or 720x1280) you are capturing in and what do you have in Easy Setup? It could be that the 400 isn't fast enough so it's freezing up and "dying"
I am capturing straight from my camera. My easy setup is on HDV-Apple Intermediate Codec 1080i60. Im not sure what the HD resolution is but i believe its 1080x1920.
OK, those settings sound good. I think your problem is the slow cable. Does it display a dropping frames error message wen it stops or just what's in the screenshot?
Well right when i hit capture it will start lagging...and it would say how much % its lagging with the monitor. But i have not seen an error..it would just freeze and i would have to do a force quit. I dont see why it would be the cable because it was not like this before.
I assume you're capturing HDV ... is that correct?
If so, HDV has a slightly lower data rate than DV (due to it's very high compression) so Firewire 400 will work fine. If the camcorder you're capturing from is connected to the same Firewire bus as the drive where the data is being captured, it will only capture at FW100 (camcorders and VTRs are FW 100 devices). But both DV and HDV data rates are still well under that.
I don't work with HDV, but I believe that during the capture process, FCE/FCP converts from HDV to AIC or ProRes which means the data processing (writing to the hard drive) will lag behind the capture - I could be wrong on this, but I don't think so.
Essentially, the computer has to take in the long GOP MPEG-2 stream (HDV) from the camera and convert it to a frame based format for editing. MPEG-2 only has one full frame ("I frame" ) for every 15. The 14 'frames' that follow the I frame only contain data that has changed since the I frame**. The rest of the data that was contained in those frames gets thrown out. That's how HDV is compressed so they can get 60 minutes of HD footage on the same tape that holds 60 minutes of SD footage.
So the computer has to create 14 frames for every GOP and that gets rather processor intensive and the capture lags.
If it isn't HDV, then I'd suspect a data rate or throughput issue.
-DH
This is all very interesting, but I thought that GOPs and I-frame where only used in compressing, esp. for the web. So when capturing HDV FCP automatically converts to MPEG-2 using I-frames and GOPs? Is there a way to avoid this by using AIC or ProRes? I read the tutorial on Kenstone.net and I didn't catch anything about converting to MPEG-2.
No, no, NO. HDV IS MPEG-2. Which is why it is difficult to work with. Which is why you should capture as ProRes.
-DH
So no to I-frames and GOPs? No to converting to MPEG-2 because it IS MPEG-2? Capture with ProRes? What exactly does ProRes do? Convert the video to a different format, compress it with a codec? I get the HDV thing, finally I think.