-
Why one user Switched to FCPX
-
I don’t think he was saying the feature wasn’t there in Premiere. He was saying it just didn’t work reliably. So he’d have to upload manually.
————————–
Brett Sherman
One Man Band (If it\’s video related I\’ll do it!)
I work for an institution that probably does not want to be associated with my babblings here. -
[Neil Goodman] “Were hooked up to an ISIS”
Honestly, I’d blame the ISIS more so than the Macs or Premiere. Your systems probably work well with Media Composer.
– Oliver
Oliver Peters – oliverpeters.com
-
[Steve Connor] “Yes but it’s nearly EIGHT YEARS! If they hadn’t written off the costs and covered the financing years ago then that IS nuts!”
Remember that upgraded 2010 Mac Pro towers STILL test out favorably against 2013 Mac Pros. Still the only “current” Apple Mac Pro. So just because they are 8 years old, in and of itself, doesn’t justify a change. Of course, if you made a change today to newer Apple workstations, it would be to iMac Pros. This cascades, because then you also have to change all the peripheral gear, too.
– Oliver
Oliver Peters – oliverpeters.com
-
[Steve Connor] “Have they expanded and upgraded the 2010 Mac Pros? FCPX used to run very well on my 2008 Mac Pro with Sapphire 7950 card
“I cant speak to everyone’s individual computers but this one is a 5.1 2.4 quad with 32 gigs of ram and just the ATI 5870 which is surely part of the problem.
We’re not using FCPX here although it is installed and I have seen how it runs which is about what youd expect with a 1gb GFX crd
-
[Oliver Peters] “Honestly, I’d blame the ISIS more so than the Macs or Premiere. Your systems probably work well with Media Composer.
“You are correct, Media Composer 8.6 works great on this box – no issues at all. Unfortunately Avid projects are far and few between with only a handful of clients requesting we do our projects in Media Composer. Pretty much Premiere for everything else.
You think ISIS work worse as shared storage with PPro and FCPX than it does with Avid? Id figure performance would be the same because technically its just storage?
-
[Neil Goodman] “You think ISIS work worse as shared storage with PPro and FCPX than it does with Avid? Id figure performance would be the same because technically its just storage?”
Nope. I think it’s absolutely worse with Premiere and FCPX. First of all, Avid’s current storage is Nexis, and according to Avid, they’ve worked hard to make the other NLEs equal clients. So definitely ISIS is tweaked more for Avid.
Second, you are generally dealing with Avid-optimized media, that also helps. In my experience, both Premiere and FCPX don’t perform nearly as well on shared storage than they do on local storage. Are your systems connected to ISIS as 1GigE or 10GigE? I would image that if you have 50 machines cranking with anything other than low-res proxies, your system will choke.
All 3 NLEs work best with media for which they are optimized. I’m actually pleasantly surprised that Avid, via AMA, is relatively responsive on non-Avid, NAS shared storage – often more so than FCPX and Premiere. I’ve also found lately that Premiere on shared storage is actually quite responsive with media from Canon C300 and RED cameras and not so much with ProRes.
With both FCPX and Premiere, we’ve lately taken to using their internal proxy workflow, because of shared storage performance (QNAP, 10GigE).
– Oliver
Oliver Peters – oliverpeters.com
-
[Oliver Peters] “Nope. I think it’s absolutely worse with Premiere and FCPX. First of all, Avid’s current storage is Nexis, and according to Avid, they’ve worked hard to make the other NLEs equal clients. So definitely ISIS is tweaked more for Avid.
Second, you are generally dealing with Avid-optimized media, that also helps. In my experience, both Premiere and FCPX don’t perform nearly as well on shared storage than they do on local storage. Are your systems connected to ISIS as 1GigE or 10GigE? I would image that if you have 50 machines cranking with anything other than low-res proxies, your system will choke.
“Not sure if its 1 Gig or 10 tbh – and admittedly Im not a super technical person – just show up and cut – never had to maintain a computer myself.
Its interesting that the NEXUS is that much different with NLES – I saw some people order new NEXUS gear only to have ISIS gear showup, with a NEXUS sticker slapped on? Might’ve been old stock.
What would be the best codec for our AE’s to use for Premiere Proxies? Maybe I can pass on some info.
-
[Neil Goodman] “What would be the best codec for our AE’s to use for Premiere Proxies? Maybe I can pass on some info.”
I use the internal Premiere Pro CC 2018 proxy workflow. We pick the option for 1280×720 ProResProxy.
– Oliver
Oliver Peters – oliverpeters.com
-
[Shane Ross] “So yeah, it might take a while to build up the capital to afford to do that. It’s easier when you are a sole operator, or have a handful of machines.
“Unquestionably.
But my point is if that investment yields a 10% or 15% increase in efficiency it’s one thing.
But if it boosts it by 50% that’s entirely another.
My point is that I sincerely feel that the combination of FCP X “and” new hardware has easily done that for me.
Of COURSE this presumes a lot of things and isn’t a universal perscription. Type of work, experience and/or training of staff, network infrastructure, management interest, availability of capital, etc, etc, etc will all factor in.
ALL I’m saying is that looking back for this ONE user (doing only my type of work) that combo (software, hardware AND user experience upgrades all together) is what I see as the key to what I’ve experienced.
If an editor has to face a deficit in ANY of those areas, it’s going to be more difficult for them to experience what we all desire – tools that help us thrive.
That’s why I was expressing sympathy for Neil.
Sitting down to 8 year old hardware – facing today’s production pace – sounds like a difficult place to be.
That’s all.
Creator of XinTwo – https://www.xintwo.com
The shortest path to FCP X mastery. -
[greg janza] “Again, much like the original post, your inefficiency relates back to your particular setup and not the Adobe software. Many Adobe users, including myself, have no latency issues and the software works as advertised.”
I can attest to this that its the setup.
I run a 2012 Mac Pro with Quadro FX4800/4000.
I am able to work in CC 2018 After Effects using Superluminal Stardust for long periods of time without having to reboot.
I also run FCPX 10.3.4 and PPro CC2017 with no hiccups.
This is my daily machine till I upgrade (at work).
Sure I run into issues but as long as I maintain the OS and avoid stupidity, this baby still works 🙂
Reply to this Discussion! Login or Sign Up