Petros Kolyvas
Forum Replies Created
-
Lion, CS6, lots of RAM, SSD OS driver, and it’s the little engine that could… 🙂
It’s the first workstation we’ve owned that has lasted nearly 6 years in daily active duty.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
I did forget to add that “B” suite was upgraded to CS6 and has been running great and no, the Quadro won’t work in the 1,1.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
We have been running CS5 & CS5.5 in our “B” suite on a 1,1 Mac Pro with a 5770. It doesn’t support hardware accelerated playback but it has worked.
There are hacks to get the OpenCL features/hardware acceleration unlocked, but the jury seems to be out as to whether OpenCL acceleration works better than the Software Playback Engine does.
The Quadro 4000 in our current gen Mac Pro does run circles around it, but if you’re not doing a lot of time-line color correction and effects, we’ve had no trouble with the 5770 in a 1,1.
With the speed enhancements that “native” editing offered us over the applications we were using previously the occasional “render” in that suite doesn’t slow us down.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
Same here, the Wacom and keyframes really bite under Premiere. I have to use the “precision” editing feature from the Wacom drivers and even then it isn’t consistent.
We have two workstations with Intuos tablets here, a 4 Wireless and a 5 Medium, and they behave the same.
No such issues under other applications. Let’s all flood the Adobe Bug/Feature request right now:
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
I only tried it (being the keyer) once or twice before giving up but I experienced similar issues with the secondary keyer. I do use Colorista II a lot, but not that feature because, as you noted, it’s pretty broken.
Our source material was AVCHD, I wonder if that has anything to do with it?
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
AJA has yet to release a driver for CS6 (Mercury Transmit). Based on their past performance though, we shouldn’t have to wait too long!
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
It’s a bug somewhere in the AVCCAM/FCP7 pipeline and the AF100…. it will crash at the point the files are spanned. This spanning is invisible in most cases, but it’s exactly at this point where FCP7 will crash.
We made our first move towards Premiere CS5 (before the FCPX debacle) as a result of this issue and, sadly, haven’t looked back.
The only real solution is to use something like Clipwrap and do your transcoding ourside of FCP if you want to stay with 7.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
[Jack Johnson] “- was this a matter of build plug and play or did you have to get into coding/programming something?
– who makes that rack?
– What size battery backup are you using on the rack?”a) No programming whatsoever. A few questions and some help (from members here) getting the arrays configured properly. Disks are key of course.
b) Do you mean the ISOBox Post the unit is in? It’s made by Sound Construction. https://www.custom-consoles.com/Isobox-post-production.php
c) We use a cheap(ish) RS1500 from APC for each Mac Pro workstation. We test them regularly. The one attached to the large disk array only offers about 10 minutes of runtime but it’s more than enough to initiate the save and auto-shutdown of any projects. I’m noise-crazy and we had originally had a much larger unit but due to poor firmware the fans would spin up, regardless of load, and make a crazy racket.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
There were two reasons:
1- I was already committed to the headless montherboard/expander route when I tried to use the HP SAS Expander, which didn’t work with the R680.
2- Chasis to fit it in: much easier to find an ATX-ready chassis than a DIY one ready for the Areca.
While having done this once, and enjoyed it tremendously, I’d probably buy a diskless ready-made solution using the very same Areca adapter in the future.
We have found a small benefit to our setup, we want to dual-link to the host adapter, and add more disks and a few additional simple array enclosures, in our case it’s as simple as dropping a second Intel expander in the chassis, linking it up and moving along; but I don’t think this new benefit of the motherboard-style setup outweighs the simplicity, and reliability of all-in-one Area.
All this to say, I think the direction you’re heading is a better one.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
As someone who transitioned (poorly) to AE from Shake, I think node-based compositing has a serious place in any workflow requiring compositing once you begin to grasp the power of nodes and connections as opposed to layers.
It comes down to how you like working really. Some reason there seems to be a cost-premium if you like working with Nodes.
Irrespective of the “Autodesk will, one day, stick it to you” reality – there will be a trial of smoke 2013 in early summer (actually an open beta I believe) and anyone can try it for themselves. I plan on doing so and I am hopefully it really will be the holy grail for integrating a node-based compositor and a timeline.
While Nuke remains a remarkable compositor, it’s $5k to start for a single-eye pipeline (2D) and $8K for a stereoscopic pipeline.
It doesn’t mean we should all just buy into the Smoke hype and it would be nice to see some kind of long-term committment from Autodesk, but I fear we won’t get one.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger