Robin S. kurz
Forum Replies Created
-
The first and foremost relevant component when working in FCP X in terms of overall performance is: GPU. Then comes RAM, then comes disk, then comes CPU. So as long as you’re getting the “top” model 21″ (which already maxes out at 1GB VRAM) and not one of the others, then you’re fine. But obviously the 2-4GB GPU on the 27″ would be exponentially better.
-
You could either simply place an adjustment layer over everything (https://www.rippletraining.com/using-the-adjustment-layer-title-in-final-cut-pro-x.html) and apply the desired letterbox effect to it (https://blog.alex4d.com/2012/10/28/alex4d-letterbox-fcpx-effect/) or simply set your PROJECT to the desired resolution after which it would simply be rendered out cropped. As a last resort you could also simply render out whatever you have and crop, letterbox etc. however you like in Compressor via a custom preset.
-
[Jeremy Garchow] “but it’s worth exploring, no?”
Sure. Only if it’s on “Fill” why would you want/need to scale it? And if it’s on “None” then scaling it wouldn’t make things worse. But then I haven’t tried every possible combination and (scientifically) compared, so sure… give it a look. Who knows. 🙂
But I did in fact compare “fitting” then scaling and “none-ing” and scaling on a *video* (both “raw” and in a compound) and saw no perceivable difference. Who knows if matters are different with stills. Certainly a worthwhile possibility to exclude.
Proceed. 😉
-
[Jeremy Garchow] “When you Reveal IN Finder one one of the stills, where does it take you?”
Good point. Did you choose to make optimised or even proxy media on import??
[Jeremy Garchow] “In the inspector, what is your spatial conform set to?”
That shouldn’t affect the overall quality.
-
Any chance you could post a frame of each for comparison?
-
I take it you don’t actually have the project data from the other person? Can you say for sure that he/she didn’t in fact use some additional filters or the likes (a sharpener)? Because I can’t think of anything that would cause what you’re seeing. At least I’ve never experienced it myself, nor have I heard of it otherwise. In fact, at least in the area of H.264, my experience has been that Adobe’s encoder, if anything, is noticeably WORSE than that from Apple/FCP.
-
Bottom right.
-
[Mark Spencer] “It’s not a bug it a function of the order of operations. “
Well, yes and no. Let’s say that that’s to be expected *technically*, only *practically* it shouldn’t be happening. It should be possible to continuously rasterize in a case like that. And when I showed this to the Motion guys a while back when I came across it myself, they didn’t seem to think that it was right either and wanted to look into it.
-
No way that I know of, but maybe someone else? I’d have to fiddle, but I could image there MAY be a way with some convoluted rigging, but hard so say. Or I’ve never seen the obvious. 🙂
-
So simply re-saving the file didn’t work?
