Ryan Holmes
3
COW Coins
Forum Replies Created
-
Exactly what Chris said. It’s well worth it to tap into the CUDA architecture (only available on Nvidia GPU’s). It’s really how PPro was made to run. You won’t regret it. Looks like you can pick one up on Amazon for about $713.
Ryan Holmes
http://www.ryanholmes.me
vimeo.com/ryanholmes -
If you want ProRes as an export, just select it from the choice of codecs under “Quicktime.” If you use “Match Sequence Settings” you need be positive that you set those up as ProRes.
Did you check the Quicktime file you output from PPro? What codec is it using?
I’ve setup various ProRes presets in PPro so I can just select them quickly (720p30, 1080p30, 1080p24, etc.). If you have to export a lot it’ll save you time.
Ryan Holmes
http://www.ryanholmes.me
vimeo.com/ryanholmes -
[Denis Plesca] “it’s just an MP3 straight from ZOOM H1 Recorder”
Use Quicktime Pro or Compressor to convert this to an AIFF or WAV file. FCP works well with either format.
BTW, why are you recording audio in mp3 format on a Zoom? mp3 is a heavily compressed format…not ideal for editing or sound work.
Ryan Holmes
http://www.ryanholmes.me
vimeo.com/ryanholmes -
Should be fine. FCP7 plays well with many different codecs. For sure it plays best with ProRes, but if you’re talking about transcoding 25 days worth of footage that’s a pretty good chuck of time wrapped up in transcoding. An investment I wouldn’t want to make…but that’s just me.
DNxHD should be no problem in FCP7 provided your sequence settings match your footage correctly.
Ryan Holmes
http://www.ryanholmes.me
vimeo.com/ryanholmes -
Why can’t you just edit the already transcoded DNxHD .mov files in FCP? Why transcode to ProRes?
FCP7 will handle DNxHD fine, provided you’ve downloaded and installed the codecs from Avid.
Ryan Holmes
http://www.ryanholmes.me
vimeo.com/ryanholmes -
Vimeo’s compression FAQ is a good place to start. The same applies for YouTube as for Vimeo:
https://vimeo.com/help/compressionRyan Holmes
http://www.ryanholmes.me
vimeo.com/ryanholmes -
Post in the FCPX forum. You’ll get a better response to your question. This is the FCP1-7 area.
https://forums.creativecow.net/fcpxtechnique
Ryan Holmes
http://www.ryanholmes.me
vimeo.com/ryanholmes -
Given all the steps you’ve tried my next guess is that maybe you have a bad RAM chip.
I’m assuming nothing is plugged into the computer (peripheral devices), that your drivers for the video card are correct for the OS you’re running and that you don’t have any plugins installed. If any of these are the case you may try troubleshooting those one by one to see if they resolve the issue.
Ryan Holmes
http://www.ryanholmes.me
vimeo.com/ryanholmes -
Not that I’m aware of….so there may be but I’ve never seen in it in Media Encoder. If you use Quicktime Pro to encode to h.264 you can set keyframes to “Auto” so it’ll determine where/when to best put the keyframes. I don’t see an option like in Media Encoder.
Ryan Holmes
http://www.ryanholmes.me
vimeo.com/ryanholmes -
[Dan Sakols] “Im shooting at 30fps. for encodes I force an I frame every 24 frames as a rule of thumb. does that sound about right?”
This is entirely up to you and the resulting file sizes you want. More I frames typically means a larger overall file size when finished. If you have a lot of fast motion (cars, sports, etc.) then more frequent keyframes usually helps maintain quality. However, it’s just a guy taking against a static background then you can use less. Additionally, you can use less keyframes if you use 2-pass or multi-pass encoding as the software then analyzes the footage and decides where best to place the keyframes.
For most of what I do, I typically will place a keyframe at the same rate as the frame rate. So if I’m doing 30fps I’ll do a keyframe every 30 frames. If I’m doing 24fps then a keyframe every 24 frames, etc. So I usually end up with 1 keyframe per second. And I almost always use 2-pass encoding unless it’s a time crunch or I don’t care as much about the output (i.e. it’s just a rough preview).
Ryan Holmes
http://www.ryanholmes.me
vimeo.com/ryanholmes