Ryan Holmes
3
COW Coins
Forum Replies Created
-
Have you tried Queueing media from Premiere CC or Prelude CC to AME?
Since you’re on CC uninstall/reinstall shouldn’t take more than about 10-15 minutes (and that’s if you have a slow internet connection). It’s very painless.
Ryan Holmes
http://www.ryanholmes.me
@CutColorPost -
[Matt McNally] ” I have always been obsessive about getting my media nicely organised before starting a job, and I don’t resent spending that time, but maybe I’m being old fashioned.”
No, you’re not old fashioned. You’re being smart. Moving to a new NLE doesn’t mean you throw all that out. You aren’t going to start using “sloppy” practices just because you migrated NLE’s – poor naming conventions, poor folder structure, bad file management, etc.
Take those strong habits and move to any of the new systems – Avid, FCPX, Adobe, Autodesk. They all run smoother if you’ve taken the time to corral your media before going into your edit.
Just my $.02
Ryan Holmes
http://www.ryanholmes.me
@CutColorPost -
You’ll need to elaborate a bit more if anybody can help you….
What steps are you going through to add media?
Are you on Adobe CC?
Have you uninstalled/reinstalled AME?
Have you repaired disk permissions?
Have you emptied the cache for AME?Ryan Holmes
http://www.ryanholmes.me
@CutColorPost -
You should also double check that the graphics card drivers that you have are compatible with the OS that you’re running. You may need to roll back to a previous driver build in order to be compatible on your OS.
Ryan Holmes
http://www.ryanholmes.me
@CutColorPost -
[Andy Oxley] “I have done some test one-minute exports at data rates of 5000 and 3500 k bits/sec (HD 1280×720), but these have indicated that the final file size will be around 16GB and 12GB respectively,”
Andy, I think your math is a bit off. Supposing a h.264 codec, if your video is 45 minutes long and you encode at 5000Kbps (both audio and video combined total), your total file size would be just under 2GB (about 1.7GB). If you run it at 3500Kbps then you’re looking at a file size of about 1.2GB.
Use a file bandwidth to filesize calculator if you want to easily experiment with different data rates:
https://web.forret.com/tools/filesize.asp?speed=5000&unit=Kbps&dur=2700But as Andrew mentioned, if you can afford the extra time a 2-pass VBR will usually net a better overall picture and lower overall file size as it more efficiently utilizes the given data rate.
Ryan Holmes
http://www.ryanholmes.me
@CutColorPost -
[Lenny Greaster] “I’d use the Avid DNxHD 220 codec.”
Lenny’s right. DNxHD is very similar to ProRes. The DNxHD codec is similar in compression and overall file size to ProRes (HQ).
The codecs are free to download from Avid’s website.
Ryan Holmes
http://www.ryanholmes.me
@CutColorPost -
[Steve Eisen] “An eSata RAID would run much better”
An eSata RAID would provide more headroom on speed. But a Firewire 800 G-RAID setup has plenty of bandwidth to handle a single stream of ProRes (HQ). Firewire 800 is about 3.5X faster than is necessary to carry 1 stream of (HQ) – 800Mbps Firewire vs 220Mbps for (HQ). If his drive is (1) a RAID (which I’m assuming it is from his first post), and (2) less than half full then this drive should theoretically deliver 1 (HQ) stream.
But like Steve says, you could pickup an eSATA PCIe card for your Mac Pro (assuming you have open slots). You should be able to get one for under $50. It might be worth a try to see if it speeds up your workflow.
Ryan Holmes
http://www.ryanholmes.me
@CutColorPost -
The RT settings only impact your playback capabilities, not your export. When you export you’ll define what codec, quality, etc that you want.
I would try setting your RT to Unlimited (not Safe), Playback Quality to Dynamic, and Frame Rate to Full. See if your system still stutters on that. Those settings on what I’ve on most of my computers since Apple came out with RT settings (waaaaaaaay back in the day!).
Ryan Holmes
http://www.ryanholmes.me
@CutColorPost -
I believe all the NLE’s offer a 30-day trial. I’d start there to kick the tires a bit. See what you like. See what works in your particular environment and workflow.
I’m an ex-FCP’er. We moved in 2011 after Apple shipped FCPX. It wasn’t going to work in our multi-editor, XSAN environment (I think it plays better now though, but it doesn’t much matter to us…because –>). I switched my team over to Premiere and we haven’t missed much about FCP Legacy. We have no problem moving FCP7 projects into Premiere Pro (and I had about 8 years worth of projects that I needed to move), ingesting media is fast as Premiere Pro handles pretty much anything you throw at it, and the exporting in Premiere CC is far and away the best I’ve used so far in any NLE.
As far as mechanics I constantly say that Premiere CC is the Final Cut 8 we all wanted. It behaves similarly with shortcuts and track based editing, but it’s a modern NLE, built on a 64 bit architecture that completely harnesses your available GPU(s) and CPU(s). I’ve been very happy with Adobe over the last 2 years.
Check Walter Biscardi’s blog, as he wrote quite a bit about his transition and the equipment he migrated to (Adobe, some Media Composer, and iMac’s mostly, I believe).
Ryan Holmes
http://www.ryanholmes.me
@CutColorPost -
What’s your RT Playback Video Quality set to? You can set it on Dynamic and let FCP moderate it or you can drop it down yourself.
Your external drive should be sufficient for sustaining ProRes (HQ) material via Firewire 800. ProRes (HQ) is a 220Mbps codec, and Firewire 800 runs between 600Mbps-800Mbps (the former number being more closer to real world and the latter number being its spec). One thing that might cause you problems is if your hard drive is more than 50% full. If so, it can be difficult for the drive head to move around the disc fast enough to deliver 24fps, 25fps, 30fps, or 60fps (or whatever your frame rate).
https://images.apple.com/finalcutpro/docs/Apple_ProRes_White_Paper_October_2012.pdf
Ryan Holmes
http://www.ryanholmes.me
@CutColorPost