Eric Jurgenson
Forum Replies Created
-
Yes, try to keep the bin structure as simple as possible. These are things I used to do in CS3 to avoid memory issues with large projects. I can’t say I’ve had any memory issues with CS4 on 64-bit Vista & 8 GB Ram, but I haven’t done any super large projects in CS4 yet either. I did recently complete an edit with 8 1-hour HDV tapes in CS4 without any issues, but I cut my clips from the original source tapes (captured in full) by marking ins and outs in the source monitor and dragging to the timeline, as opposed to dragging to the bin (making a subclip) and then to the timeline. The idea is to avoid accumulating hundreds (thousands) of clips in the bin, thus keeping the project file (and the memory footprint) smaller.
-
It would be good if you were on 64-bit Vista with 8 GB of RAM. But otherwise I would try to minimize the number of (sub)clips in the bins by cutting out clips (from the source tapes) on the timeline rather than creating subclips in the source viewer. This will keep the project complexity (and size) to a minimum. Also, close timelines and bins when not in use. This will help prevent low memory issues.
-
Probably bad settings. Try QT H.264. Set data rate to 400 for 360×240 or 1200 for 720×480. Check the “deinterlace” checkbox on the media export window output monitor. Adjust the aspect ratio settings to fit playback in the output screen as desired (full screen or letterbox). If the aspect is wrong in QT player (it will be), you have to fork over $30. for QT Pro. Then in QT player menu “Window->Movie properties->Presentation” check the “conform apeture to: (clean apeture)” box, and then save.
-
I believe the Z7U files should be M2T, not MXF.
-
The original project may have been done on a system with a capture card specific codec. I’d just rerender.
-
I haven’t tried it with JVC cameras, but you should be alright. You may lose some multi-track realtime capability, and you may even have to render single tracks(I doubt it), but at least it should play.
-
I believe it is more a disk speed factor. Depending on transitions, audio, etc., you might be able to get 100Mb/s playback from a single SATA drive. For higher performance, multiple track playback, etc., you would want a stripe set or an array (or use a lower the data rate).
-
No XML project export from Premiere unless it is coming with the 4.1 update, which is due later this month. You can export AAF, which could then be imported into FCP with Automatic Duck.
-
Matrox MPEG2 I-Frame (NTSC 720×486). Crank the quality slider up to whatever your disk system can handle.
-
Thanks, David. Good point. But I know Premiere won’t handle HDV Quicktimes. How about XDCAM QTs?
I’m thinking I may be able to link the FCP Quicktimes to the MXF and HDV originals by selecting the offline QT clip on the timeline, loading the original file in the source viewer, and selecting the “relink-Match Frame” right-click function on the selected clip (presuming the timecode matches).