Chris Frantz
Forum Replies Created
-
Was that fix open in timeline and delete the channels you aren’t using? Because that’s not a fix, that’s a deal breaker when it’s not necessary in other NLEs.
-
On the topic of transparent PNGs, last I tried I couldn’t manage to get a proper transparent PNG out of FCPX, has this been fixed?
-
Troubleshooting options is one. Last time I had an issue with CC 2014, Adobe’s only solution was to upgrade to Yosemite as that would fix the GPU problem. We were locked to Mavericks due to XSAN incompatibility which made that not an option, and our fancy Mac Pro unable to render jobs out of Premiere without GPU errors. In a SaaS model, developers tend to focus on the latest versions of everything so backwards support may become less of an issue for them. On that note though, Apple doesn’t even attempt it as they won’t even allow anything prior to Yosemite run 10.2. I guess there’s a reason some shops still run FC7 and an ancient version of OSX, the bugs you know are better than the ones you don’t.
-
[Herb Sevush] “As for “my Beta is better than your Beta” – I don’t know anyone who uses Beta software to pay the rent, and that’s why it’s called “Beta.””
Windows 10 is still a garbage fire in terms of broken UI elements and system demolishing bugs. It’s a massive update and is about to come out. El Capitan is incremental and introduces performance updates mostly. Eventually people will have to upgrade, and it certainly helps to read the tea leaves ahead of time.
-
I guess what I’m looking for ultimately is a way of setting Roles/Subroles in the finder. It would be the equivalent of patching tracks at the finder level, as we send everything out and it all passes through Producer’s Best Friend. The pain point is Roles not flowing downward, meaning that if you use a clip in the timeline without setting the role in the browser you then have to set the role in the timeline because if you set it in the browser it will not pass down to the clip in use. If you remember to set roles every single time you import anything maybe it wouldn’t be so bad, but we remember about 70% of the time which means hunting and pecking down the timeline before exporting XMLs. Setting those roles before import would alleviate those issues.
I haven’t really heard anyone else complaining about it so maybe this is an issue unique to our workflow.
-
If it’s not a numbers game then why respond? For the record, Yosemite works great and El Capitan public beta is ages ahead of Windows 10. Life is a compromise and maybe there’s a fix coming in a few weeks for general bugginess? Those aren’t resounding points about anything, much less a render score. If you’d like to see additional tests done, then you should do them and add them to the spreadsheet, otherwise you’re introducing points without any data to back them up.
-
Awesome 🙂 The only thing missing is setting video roles.
-
[Herb Sevush] “So if your NLE is constrained to OSX, and if you you use a laptop to edit with, then FCPX is superior to Ppro when exporting – is that the deal? Fantastic, now let me get back to using PPro on my old Mac Pro, and if i want to decrease my export times I’ll buy a faster GPU, and if I want to increase my Ppro efficiency further, I’ll buy a PC workstation.
“Did you check out the spreadsheet he posted? On workstations (Mac Pro & iMacs) FCPX came out ahead on all but one render. And you can go ahead and install Windows w/ Premiere and immediately start making compromises. Make sure you’re running CC 2014 because 2015 is too buggy for production work. Also, Windows 7 because 8 is dead, but also Windows 10 is about to come out with an aggressive update schedule so you may want to do that but not for active production work. That sounds like fun. In the meantime, I guess we’ll all just be rendering faster in on our software optimized for our hardware by the same manufacturer. Is that the deal?
-
So a few things. I’m pretty sure there are installed users with FCPX then there were with 7. The timeline works for plenty of people, including myself and several of our in house staff. Also, to negate the real cost-saving features associated with one part of the app with your feelings about the workflow decisions Apple has made doesn’t really equal out. They’re all great apps and all very capable. The best editors I’ve seen also have the simplest and cleanest looking timelines.
-
Affinity Photo is really good. I think once Photos integrates it via app extensions you’ll be able to use Photos as a catalogue and Affinity Photo for more extended works. Affinity has just absolutely lightning fast software, and despite still paying for CC, I’m using their apps more and more. I’m a bit biased though because I can’t find my cancel subscription button. Terrible business practice.