James Culbertson
Forum Replies Created
-
[Shawn Miller] “[James Culbertson] “Premiere and FCP7 feel more engineer-driven now than they used to in comparison; I think students prove this point too.”
How so? Premiere Pro seems to have incorporated more user feedback into it’s design and functionality than ever before… certainly more so than in the pre CS days.”
More than feel or using of the interface than the features themselves.
-
[David Lawrence] “I don’t mean to suggest that creating a new timeline model that addresses clip collisions is a bad thing. Just the opposite, I think it’s a brilliant idea in theory. But I think Apple blew an opportunity to do a better job by not talking to and understanding their users. The magnetic timeline solves problems, but it also creates new ones. The UI design seems very engineer-driven rather than user driven to me. My point being, data models don’t usually make for the best user experience design.”
David, Why do you assume that they created the magnetic timeline just for clip collisions or to solve a problem? Did someone at Apple say that?
I see the magnetic timeline as one of a number of features in FCPX that allow me to edit faster, more efficiently, and more creatively. Rather than solve problems (which it may also do), the magnetic timeline reveals new creative pathways; it opens up the editing space and makes it more freeform. It gets the UI out of the way so that we can just edit, which, for me at least, is the ultimate in user experience design. Premiere and FCP7 feel more engineer-driven now than they used to in comparison; I think students prove this point too.
-
[Mark Suszko] “Really, as far as bikes and timelines, wouldn’t the more apt FCPX analogy be a unicycle, or Penny-Farthing? :-)”
AVID is more like a Penny-Farthing at this point.
BMX may be a better metaphor for how malleable FCPX is. Or perhaps a hybrid BMX/Road bike.
-
[Andrew Kimery] “Step 1. Watch this 8 minute video about learning how to ride bike where the handlebar movement has been reversed (left turns you right, right turns you left).”
When I discovered FCP legacy, AVID MC started to feel a bit like a backwards bicycle. Now, FCP 7 and Premiere feel a bit like backwards bicycles compared to FCPX.
But FCPX clicked immediately with me, and I can go back and edit on FCP7 without a beat. So, while some may feel this is an applicable metaphor, by no means is it applicable in any systematic way. It certainly makes no sense to me. All NLEs are just bicycles to me; FCPX feels like a racing bike, and the rest feel like good solid touring bikes.
-
[Scott Witthaus] “Actually, I use Premiere for some clients and it doesn’t suck all that bad. Plus it’s slower, so on the by-the-hour jobs it can be more lucrative.”
Scott, are you ready yet to talk about your experience of Premiere relative to FCPX?
I keep meaning to make time to get back up to speed on Premiere, but the corporate work I am doing currently specifies FCPX and I have not had time.
-
[Dean Neal] “Surely its time to simply just call it – Apple FCPX?”
The title of this forum isn’t relevant anymore. But a more accurate name would be “which NLE do you prefer,” which isn’t as controversial or dramatic as the current name. And the folks at creative cow know that in order to keep folks coming back here they need to create some drama even if it is fictional at this point. No different than any film or TV show; a more accurate analogy in this case would be a reality TV show.
I do find some of the more informed discussion of NLEs interesting which is why I keep coming back here. I just try to ignore the more ignorant opinions about FCPX, and the incorrect title.
-
[Aindreas Gallagher] “he is actually the first person to ever slap the spacebar for a marker”
What was the exact date?
-
Don’t know about a moment, but it sounds like it is time gentlemen please.
-
One thing I just noticed which may or may not be related. I was having a slow After Effects render, and just quit Firefox which immediately sped up the rendering by probably 5x or more. I’m assuming it is the old Flash memory leak (or whatever causes Flash to hog up resources) that I had forgotten about. Next time FCPX is sluggish I will have to make sure Firefox is not contributing…
-
[tony west] “To me, one of the main problems seems to be that after one of those updates, X started to render in the background on it’s own. Even when you have that unchecked in preferences.”
I’ve noticed this, but it doesn’t appear to have anything to do with rendering video previews for me. As far as I can tell it is rendering audio waveforms. Once those are built the sluggishness goes away. Unless I open up the audio inspector and then the audio waveforms can slow things down some of the time until I close the audio inspector again. These are only problems for me with longer source files (like an hour or longer).