Jamie Franklin
Forum Replies Created
-
[James Culbertson] “when someone says it is a terrible editor my guess is that they have not really used it.”
I think your guess is wrong. I was careful to say, as this is always the response, from people that I have spoken with and have given it a whirl…as I have. I bought it on the first day, I have updated it and played with it since, and as an editor, I find it a creative lost cause. I like my track based timeline without mag chrome. I find 7 a unlimited canvas of choices, function and ease. The mag timeline is infuriating to work with as an editor.
-
If any of us need to make a move now on hardware, if we decided on Apple, I don’t know about any of you, but I’d feel like a battered housewife…
-
You can cut a lot of formats on fcx. No one has ever said or claimed you can’t. But when you have tv series switch from fcp7 to a more expensive avid share, or a network, even features, it says more than the stand alone editor choosing or requested to cut something on X who wouldn’t be getting the memo in a shared or facility environment…
My pov, it’s a terrible terrible editor. And most editors I speak with certainly wouldn’t use x for anything.
In 2 years now, I haven’t spoken with anyone, who has had any interest in using fcx to cut after giving it a whirl. Heads shake. It’s mind numbing how squandered this release was. I guess we’re all nuts…
-
[Steve Connor] “but the fact major broadcast facilities, broadcasters as well as big budget features aren’t using FCPX at the moment is often touted as a ‘failure””
I have to agree with those saying it. Maybe not from where they view things. While I was quite vocal during the release on the consequences to my own experience moving forward with the mag timeline of creative lost causes, seeing the consequences in the professional environment, and as Shane pointed out, the collective relief by Avid users, really was a big deal when many were saying it wouldn’t be. My point of view, all that upward momentum was squandered. But I haven’t moved on myself. I still enjoy using Legacy for what it’s worth. And that I wouldn’t have predicted 2 years ago…leaving a sour taste by my initial reaction.
-
[Steve Connor] ” Correct and important to bear in mind when measuring the “success”of FCPX”
Cept for the “tons of indies and documentaries and some TV” which by every measure, is a success, and should reflect on the current “success” of FCX
-
Before you begin, in the Color tab, you can right click on the timeline and select “Use Local Grades”, this will unlink from the source. If you have already applied a grade to your source I would save a still of it first as it will remove anything you applied so far. Hope that helps
-
During the demo I asked more about the Linux box than Smoke. Smoke doesn’t have Prores support without a Flame license nor RR on the Linux box…
If Smoke on a Mac can that’s interesting. Although still frustrating as real time deliverables are bottlenecked anyways. And with HDR in the pipe, you have to get away from R3D to time with real time playback…
-
But it does come with a FCP shortcut layout 😛
-
[Sandeep Sajeev] ”
Oh and unlike the Flame box (mentioned by James) it deals very well with ProRes – infact you can set your Intermediates to various flavours of ProRes if you don’t need to work in DPX…”Steve Jobs is still angry about something even after life….It’s mind boggling we have to spend another 30-40K for that feature…
The 3D tracker is in the Flame package unfortunately…
-
I had a private demo from Autodesk last week. Linux box with Flame Premium. Looks very promising. Some walls have come down, a new batch system I think is called CFX and it is a little more intuitive. Although that isn’t saying much. It’s still not for the uninitiated, but it is better. You need a screaming fast machine, 32 cores, to run even 1/4 res HDR R3D. Although working in 5k isn’t my bag. I’m going to put the mac version through it’s paces over the holidays on the trial. I only have a 12 core mac with 2 Q4000’s and a red rocket (which isn’t yet supported) so my expectations aren’t high on much real time material, but as an editor, it still is lacking ProRes support without the Flame package and I think that is frustrating as 30-40% of our workflow incorporates ProRes in either deliverables or handoffs from clients…
Back to the Linux box, I found it surprising Lustre didn’t receive much love and still needs to be loaded separately from Flame/Smoke. I think it’s days might be numbered…?