[Tangier Clarke]

By the way, my first sample of that type of test looks like this:

Computer:
Mac Pro Late 2013/ 3.5 GHz 6-Core Intel Xeon E5/ 32 GB Memory/Dual AMD FirePro D700

Source File:
Apple ProRes 422 Quicktime/11m11s/12.26 GB/1920×1080 @ 29.97 fps/Linear PCM 24-Bit 48k Hz Audio

AME CC 2014 build 8.0.1.48 Transcode
Using default Youtube 1080p HD setting and GPU Renderer
Result = H.264 .mp4 Quicktime/ took 9 minutes to encode/1.36 GB file

Compressor 4.1.3 Transcode
Dragged above AME result file to Compressor so it would assume the settings of the file as a custom preset
Result = H.264 .mp4 Quicktime/ took 7 minutes to encode/1.15 GB file

AME file has slightly more contrast
Compressor result file looks more like my original file.

Other things I am not sure about I’d like to find out:
Are either of the apps 64-bit?
Does compressor use GPU at all?

Tangier

[Tangier Clarke]

Hey folks, just a quick question or rather wanted some insight. Being that compressor can create a custom preset by dropping in a quicktime. Would it be a fair test to create transcodes first using AME, then dragging those resulting clips into compressor to create comparable settings?

There are some other distinct things go consider as well:

AME allows choosing GPU or software encoding.
Compressor you can choose the number of instances.

I am not certain I can get 1:1 parameter settings situated such as compressor’s entropy mode.

Your thoughts…

Tangier

[Tangier Clarke]

Yeah, I was curious to know how this test would fair on my Mac Pro (the new one). Before his test came out I did a very quick test of my own coincidentally between AME and Compressor , but I was using CS6. I am Compressor came out about 37% faster getting ProRes 422 to H.264 ready for vimeo.

I am going to run some tests similar to Larry on my Mac Pro to see what results I get. I favor compressor, but am very interested in AME if it’s truly and consistently this fast.

Tangier

[Tangier Clarke]

Maybe take a look at this, just released:

https://www.larryjordan.biz/video-compression-speed-test/?utm_source=Larry%27s+Newsletter+-+140818&utm_campaign=8%2F18+Newsletter&utm_medium=email

Tangier

[Tangier Clarke]

Something like the pin tool in AE
Ability to bend objects (so I don’t have to convert my logo into a font just to wrap it around something)
Something like mObject 3D capability

Make it a direct competitor to AE already rather than an compliment to it.

Tangier

[Tangier Clarke]

If you had to call it, do you think Apple would build the features from mObject into Motion 6?

Tangier

[Tangier Clarke]

That exactly what I am look for. I wish this capability was built into Motion. Here I am doing it in Blender before you sent this.

T

Tangier

[Tangier Clarke]

Yep that applies! Title generators take a while to load, among other things. It’s unnerving to say the least to spend that much on a computer and have these issues with an app optimized for it.

Don’t get me wrong, there are other apps that I use in my post workflow where I see tremendous gains using this new Mac Pro, i.e. Compressor. However some of the issues I thought would be gone after moving to this Mac Pro from my old one are still present and frankly, not that much improved for a machine that is capable of far more processing than my old one. In FCP X it seems some of the new processing heft doesn’t apply to the entire app, just some features of it. Perhaps it’s due to Mavericks, I can’t say.

It’s a little disappointing though.

Tangier

[Tangier Clarke]

Biggest bottleneck = my Mac Pro. It gets sluggish to the point of making it hard to edit.

Mac Pro/ Mavericks 10.1/ FCP X 10.1.1/ 2 x 2.26 Quad Core Xeon/ 16 GB RAM/ ATI Radeon 5770/ Blackmagic Multibridge Pro 2/ Drive bays running 7200 RPM Hitachi Drives / Always use Pro Res (optimized)

Our iMacs with less RAM but equal VRAM are much faster (i5 processors)

Tangier

[Tangier Clarke]

Was there a definitive answer on this? Is it just to buy a better machine? We have almost identical computers and my machine gets bogged down on even small projects (6-10 minutes). The iMacs with less RAM but equal VRAM in our office (i5 processors) scream with FCP X. I click wait, drag storyline clips, wait. The machine just can’t keep up.

Mac Pro/ Mavericks 10.1/ FCP X 10.1.1/ 2 x 2.26 Quad Core Xeon/ 16 GB RAM/ ATI Radeon 5770/ Blackmagic Multibridge Pro 2/ Drive bays running 7200 RPM Hitachi Drives / Always use Pro Res (optimized)

Tangier