Mason Makram
4
COW Coins
4
Premiere Pro Coins
Forum Replies Created
-
Shoot in a flat picture style, preferably log. It looks like some blues in the shadows (and desaturated), warm in the mids, slightly warm in the highlights. Mainly the look comes from production design, though. It’s not the colors added in post; it’s what’s in frame. Look at your examples. Everyone is wearing pink, red, orange, pastel colors. The furniture, the curtains, even all of the extras on the beach. This is all done meticulously by Spike Jonze and his production designer. There’s more to making a movie look a certain way than a color grade. That’s why preset looks like Magic Bullet rarely work.
-
So, today I had some free time to finally experiment with OpenCL again. It worked flawlessly. No crashing this time. AME blasted through 1080p with no issues in the final file, and exporting 8640×1080 took about 6 minutes, similar to the export times of Premiere. Does Premiere use OpenCL?
-
I’ll take a look at the Mavericks issues. But my computer is fine. After Effects and Premiere run flawlessly. This is my point. I’m getting the files I need out of Premiere, but not from AME. ProRes is fine. I think you’re confusing the 4K limit with the limitations of FCP7.
-
No, you should select Open CL for your D700’s.
I actually turned Open CL off a long while back because every export was failing otherwise. (On standard 1080p videos, not this crazy 8640×1080 stuff.) Granted, I haven’t tried it since the CC 2014 update.
You are dealing with a weird frame size and a big one at that – it will come with some performance hits in order to do it.
Right, due to the large resolution, it wouldn’t surprise me that AME would want to take so long. However, Premiere takes 5 minutes or less to export the same files and with absolutely no sound issues.
You also didn’t mention the specs of your system which are critical to determining where the cause of the issue may lie.
My second post above. I have a maxed out Mac Pro 2013, so specs shouldn’t be an issue.
Lastly, you are outputting to a non-standard codec that was installed on the system. It’s great that AME registers it and can encode to it, but you can’t blame the performance of AME on a 3rd party codec.
Actually, my issue was with the ProRes files that I exported. Since I can’t watch HapQ files, I exported two files per video, one HapQ and one ProRes. This was so I could watch the ProRes files and get some reassurance of what I exported. My new system is that I export the videos individually in Premiere as ProRes, watch them, then throw those into Compressor to batch export to HapQ.
But the fact is, AME is unstable. Google it, and it’s all that comes up. Actually, a contractor just came on site today who was saying he has 24 videos (simple 1080p) to export from Premiere, and AME just keeps crashing. Sure, I don’t know his computer specs or if he even knows what he’s doing, but it seems like people using the Adobe suite are always struggling with it. The fact that Premiere has an easier time exporting than the application built for compressing and exporting videos is a little weird, isn’t it? I let it slide for a while because the Mac Pro is brand new and so is CC, but we’re pretty deep in the 2014 updates now.
-
Do I need CUDA enabled even if my video cards aren’t nVidia? I think I uninstalled CUDA a while back because it was messing with some plugins in AE.
Mac Pro 2013
Processor – 2.7 GHz 12-Core Intel Xeon E5
Memory – 64 GB 1867 MHz DDR3 ECC
Graphics – AMD FirePro D700 6144 MB (Dual) -
It’s been running perfectly. I play 5K footage like it’s 240p.
-
I actually figured it out. Somebody on the Apple boards suggested I pull the applications out of the “Final Cut Studio” folder that FCPX throws them into. The update didn’t know where to look for the applications. After moving them directly into the Applications folder, the update worked just fine, and Color is no longer glitching.