William Carr
Forum Replies Created
-
Can be several things, but with such an enormous project to be open all at once I’d make 10 projects, one each for4 each 30min program. Also, render the titles as you go, it will probably amount to less waiting time than the beachball.
-
1) Use external drive for Capture Scratch folder
2) Transcode all media to ProRes for editing
-
Yeah that resulting file size increase sounds about right, MTS is compressed interframe, and ProRes is intraframe.
As far as other settings to reduce file size, you can use standard ProRes, not HQ, and even consider ProRes LT if the original material is well shot.
Plus if the final work is for iDVD that means you’re ending up in standard def. So transcode to 720– you don’t need to edit in 1080, that won’t make it look any better or more “HD” considering where it’s going. Work with a 720 ProRes sequence.
So… converting to ProRes standard and downscaling to 720 will make for significantly smaller files for your iDVD-destination project.
-
I have used Aunsoft’s MTS converter with good success, which has many FCP options including ProRes flavors.
-
The frame rate discrepancy can be a problem depending on your action; the iPhone shoots 29.97. There is an iPhone app called Filmic Pro that will shoot and then in-camera process its clips to 24. I’ve tested it and it works pretty well. If you’re using an older iPhone with only 720p camera then you’ll also have to bump it up to 1080 for your edit.
And of course as Shane says, transcode all to ProRes for editing on a ProRes sequence.
-
Hi Scott,
I shoot 60p all the time for slo-mo shots in 24p projects, and as long as you bring in those clips the right way to your 24p sequence they look smooth and wonderful. And of course they will run slower than if at 30.
-
For web only, pretty much anything that’s well captured at 1080 or 720 and scaled up or down will look pretty darn good. The real issue you may need to address is frame rate.
The 1080 GoPro clips at 30 which you will conform to 24 may stutter, depending on the action. If there’s a preponderance of 30fps clips you might be better off bringing all the 24 up to 30, since adding frames is usually smoother than taking them away. Yes, that would mean your 720@60 GoPro slo-mo wouldn’t be as slow, but mixing normal speed time base rates can be more of a problem for image quality if you’re concerned about motion, more than mixing HD sizes would be for “resolution”.
-
You did just what I was imagining I might need to do when I upgrade to the new MBP, switch to CS6. Thanks for the info.
-
Hi Phil, just to confirm, you are on FCP7?
-
This forum is unmatched to learn how to get a step forward, figure what steps we’re taking that might be broken, and quite frequently, what workarounds will get us where we need to go.
I hope someone answers your very specific query. In the mean time, folks have taken time to give you some very decent ideas here.
It seems you’re saying, if that original workflow recommendation is not carried through in the manner you intend, the compression quality will be unacceptable.
When you say “Every digital video I’ve ever worked with ends up looking better on the web the less compressed it is before the final for-the-web crunch (yes even on Apple devices).”, you are stating the obvious. Less compression looks better. You want the best and least compression possible, as do we all.
The fact is there are many ways to make an h264 for the web that yield excellent results. I do a lot of uploading final projects to Vimeo; their thoughtful recommendation is to make a 1280×720 h264 at about 5Mbps. Why not just try that from your ProRes using Compressor or Streamclip or AUNsoft or whatever and upload to Vimeo with privacy on and see how it looks. It will probably look great.