Brad Bussé
Forum Replies Created
-
Thanks for all of the replies. Although I’d love to utilize something more modern and robust than HFS+, I’m sticking with that for the time being.
My workflow is primarily ProResHQ 1080 60p with ProRes4444 for alpha. I’ve actually worked off of one of the 4 drive GTech units in RAID-5 connected via e-SATA. At the time I was mainly ProResHQ 1080 24p and it worked okay, but certainly it wouldn’t hurt to have something better than e-SATA. I don’t have to have tons more space than the 6 TB available after formatting – I suppose that could be one year out from now, so perhaps this ultimately will be a stop gap measure, but I just want to make sure that I’m not stuck with an interface that will be too limiting. For this reason and to keep costs down, I was looking at starting with a G-Tech unit utilizing mini-SAS. That way I’m not worried about bumping up against the limitations of eSATA now, and I have the option of trying to add it as a TB-PCIe expansion to a new Mac Pro down the line without being forced to upgrade the array right off the bat to a larger TB native array.
Regarding USB3, is anyone using this for connecting an external RAID array for video work? Did they address the latency issues with USB in the upgrade to USB3? That might be an option since the new Mac Pro will have USB3 conections and they can easily and cheaply be added to the current Mac Pros via a PCIe card.
-
Ah, no I downloaded but didn’t install because the naming of the file made it seem that it was merely an older version of the drivers. I will install now. Thanks Walter.
-
I thought that USB was no good for video work due to an inherent latency. Has that changed with USB3?
-
Yes, on CS6.
-
Thanks, Alex. I’ve started transitioning my aep files over to proxy renders. I’m setting a proxy for the sequence at best settings. When that is rendered, it then adds the proxy box next to the sequence. Is there a way to setup these renders of the proxy files so that they are rendered out of Adobe Media Encoder so that I can continue working on a different after effects sequence while the proxy renders in the background?
I just switched my disk cache over to a 240 GB SSD drive.
-
Thanks, Alex. It’s still surprising that Adobe hasn’t as of yet addressed a better integrated workflow to deal with this. For me it makes Premiere a lot less attractive.
-
Another problem I’ve found with lots of heavy .aep files linked in a Premiere sequence is that when I track select, it takes several seconds of holding the mouse button down before everything selected actually moves. Surely there must be a more manageable way to work with linked .aep files in PP than this, no?
-
From Apple’s what’s new, under the headline Optimized for MacBook Pro with Retina Display:
“Smoothly edit multicam projects with up to nine streams of 1080p ProRes 422 (HQ) content or up to four streams of 1080p uncompressed 8-bit video, right from your internal flash storage.”Really? How many of you out there are planning on working with projects running 9 streams of 1080p ProRes 422 (HQ) on a half terabyte of storage shared with the boot drive?
-
Well, I forced the signal in the Nvidia Control Panel to 59.94 Hz and 1920×1080 resolution. And the weird thing is that the files read okay in Quicktime, just not Final Cut. Also, I can capture the signal fine with the BMD capture tool. Some kind of wonkiness with how Final Cut is handling the encoding or decoding of it’s own captures through the DeckLink.
-
The files that I captured in FCP actually play back okay in Quicktime Pro. Also, I tried capturing via the same hardware pipeline, also to 1080p 59.94, but this time in Blackmagic’s Media Express capture app. That captures files that playback okay when imported into FCP…. Anyone know what’s going on? Seems like there is an incompatability between metadata created by Final Cut when using Blackmagic hardware/drivers.
Chris, the motherboard is that of a Mac Pro 2.8 quad.