Ryan Holmes
3
COW Coins
Forum Replies Created
-
Second link down will solve your question.
Ryan Holmes
http://www.ryanholmes.me
vimeo.com/ryanholmes -
Tough truth: Your Mac Pro is old – that’s why it’s slow compared to PC’s.
Apple should’ve updated the Mac Pro’s a year ago (or at least this past summer). However, they let them go. As such Apple has missed a cycle of components from RAM to motherboards to CPU’s for the Mac Pro. Therefore, they are slow when compared to the PC counterpart. Depending on whom you read you will hear a) The Mac Pro is dead. Abandon ship for Windows machines. Or b) The Mac Pro will be update in 2013, cool your jets and edit some stories.
MacRumors:
https://www.macrumors.com/2012/06/11/david-pogue-new-imacs-and-mac-pros-coming-probably-in-2013/Pogue:
https://pogue.blogs.nytimes.com/2012/06/11/an-explanation-of-the-news-from-apple/All that said, you would notice a decent bump if you had an Nvidia card. The CUDA technology is worlds better than Open GL and CL on the ATI side.
Just my $.02
Ryan Holmes
http://www.ryanholmes.me
vimeo.com/ryanholmes -
I don’t see any benefit to upscaling to 1080 given what you’ve said. If it’s your demo reel then I would want it to look as good as it good, not soften it by upscaling. What do you gain in 1080?
If you’re going to put it on a Blu-ray or to the web, 720 will look crisp. Remember too, if you’re going to the web that will be another softening as a whole (720 –> 1080 –> h.264 mp4 –> YouTube/Vimeo recompress it after upload). All things being equal I’d just cut out that 1080 step.
But if it makes you feel warm and fuzzy inside then I’d go with Mike’s suggestion and soften it (upscale it) at the end – once you have a final edit.
Just my $.02
Ryan Holmes
http://www.ryanholmes.me
vimeo.com/ryanholmes -
[Beau Leland] “even with my Quadro4000 card and 32MB of ram.”
I’m assuming this is 32GB of ram, not 32MB! 😉
PPro in my experience is much faster than FCP, at virtually all formats. It uses more GPU, CPU, and ram then FCP7 ever could (by nature of being a 32 bit app).
The most natural question that arise when people post this (do a search it’s posted nearly every week):
1) what codec and format is your source material in?
2) What codec are exporting out to
3) How many layers do you have, AE links, color correction, etc.
4) What hard drive are you exporting out to (internal, external, same drive as your OS)?
5) How are the drives connected – firewire, eSata, Thunderbolt…are they setup in RAID
6) How old is your machine? What version of the OS are you running?My experience has been that CS6 will do h.264 mp4’s anywhere from 2-3X faster than FCP7/Compressor/QT Pro could do them. Exporting ProRes is only slightly faster than FCP7 (could be a limitation of the old 32bit Quicktime engine…dunno).
Ryan Holmes
http://www.ryanholmes.me
vimeo.com/ryanholmes -
You’ll need to convert them to .mov so FCP can see them. I believe MPEG Streamclip (free) can handle the job for you.
https://www.squared5.comI would convert them to a ProRes based codec. Since you’re using FCP6 I think you have access to ProRes422 (I would also recommend ProRes (LT), but I don’t think that was available until FCP7).
Ryan Holmes
http://www.ryanholmes.me
vimeo.com/ryanholmes -
Jeff is exactly right. As far as NLE’s go you pretty much have your pick nowadays – Adobe Premiere Pro, FCP7, FCPX, Avid Media Composer, Sony Vegas….you can find all these NLE’s in nearly every aspect of post-production somewhere. It’s up to you what you are comfortable with and what type of editing you do.
I would ultimately suggest moving away from FCP7 because it is no longer in development – no patches, no fixes, no support, no development. Apple has moved onto FCPX. Final Cut Studio, as we knew it up to 2011 is no longer supported by Apple. That’s not to say you can’t use it, but be aware that if you go that route your on your own. The last supported OS for FCP 7.0.3 was Mac OSX 10.6.8 (Snow Leopard).
Ryan Holmes
http://www.ryanholmes.me
vimeo.com/ryanholmes -
[Chris Pearse] “The HyperDecks are actually a little unusual in that they don’t perform the RGB to YUV conversion.”
Feature request for future product releases! 😉
[Chris Pearse] “The only thing I can think of with the recording format is that if the HyperDeck is being fed standard definition signals, it will record in uncompressed. DNxHD will of course only work with HD signals.”
For some reason, I think I overlooked this. Great point. Any chance y’all will be licensing ProRes to run on these little guys? That codec handles SD to 2K without any problems. Maybe that’s 2 feature requests for future products then – RGB to YUV conversion and ProRes recording codec.
Ryan Holmes
http://www.ryanholmes.me
vimeo.com/ryanholmes -
[Chris Pearse] “The HyperDeck Shuttle only records in a YUV colourspace, and I’m not sure it has any way it could convert RGB to YUV”
Yep, I forgot this was an issue with several BMD products. I think this should be listed on your “Tech Specs” page for the product as well. Only records signals from YUV color space; cannot record RGB HDMI inputs. Might save some folk a headache (provided they read the tech specs page).
I think I’m also running into HDMI v1.1 (IO HD) vs 1.3 (Shuttle) issues. Even when the IO HD is set to send out a YUV HDMI signal the Shuttle still can’t properly display the signal. I’m going to try out the SDI port and hope that solves the problem!
As for the recording format, if I send the Shuttle a correct signal it records in the format I’ve selected in software (MXF, mov, etc.). If the signal is at all messed up then the Shuttle apparently defaults to Uncompressed format regardless of what was said through the software to USB connection.
Thanks for the quick suggestions!
Ryan Holmes
http://www.ryanholmes.me
vimeo.com/ryanholmes -
Instead of FCP Log&Capture try using the Canon XF utility app. That will allow you to see your clips and output them as a self contained MXF file (i.e. you don’t need the XML information on the card any longer) that you can then transcode and retime to 23.98 so FCP use it.
Ryan Holmes
http://www.ryanholmes.me
vimeo.com/ryanholmes -
[Shane Ross] “Interesting…because when we bring this into Avid…consolidate and not transcode, it shows up as XDCAM 422.”
Isn’t there a plugin for Avid to bring in C300 footage? Is that interpreting it as XDCAM?
From the Canon Cinema EOS website, “The Canon EOS C300 and EOS C300 PL deliver incredibly high quality images with a full 4:2:2 XF Codec, creating digital files robust enough for major post-production.”
https://cinemaeos.usa.canon.com/products.php?type=Camera-c300Maybe Avid’s doing some voodoo magic in the background to play it back using XDCAM as the decoding engine?
Ryan Holmes
http://www.ryanholmes.me
vimeo.com/ryanholmes