Charlie Austin
Forum Replies Created
-
[Herb Sevush] “My resentment was based on EOL’g a workflow that suited me for a workflow that didn’t without nearly enough transition time built in.”
I get this, but again… FCP 7 did not stop working, and in fact still works just fine in Yosemite. Maybe they could have more clearly communicated the timeline, but they didn’t kill the software. There are a legit workflow reasons to stick with one NLE over another. “Apple sux” isn’t a good reason though, especially at this point. But it is what it is i guess…
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Andrew Kimery] “The FCP-only friends I had were staring ‘square one’ in the face for the first time as professionals and had no idea how to react. I think them taking it personally could make it less likely for them to pick up X. Or it could just be that Avid (and to a lesser extent PPro) are much more viable alternatives in Los Angeles than X so it’s a pragmatic choice, not an emotional one.”
I think that’s true. I also think there is an element of fear, not in the “fear a new paradigm sense”, but in the square one sense you mention. FCP X is not hard to learn, but you can’t just import a project from 7 and hit the ground running. Thus the lure of Premiere for FCP 7 switchers. At least that’s what I observe here in the trenches. If you know 7, you can stumble into Pr, (lazily) use the FCP 7 KB layout, and just keep grinding away.
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Herb Sevush] “of course if you have 4 different “roles” and you highlight one of them you are still left with a timeline that is 75% unintelligible. And you have to constantly keep hitting that index feature whenever you need a refresher on what is what, audio wise. With tracks you hit nothing and have 100% intelligibility.”
Have to respectfully disagree here. FCP X audio clips are much easier to read than any NLE I’ve used just on their own. You can also change the clip names to Roles and it’s brainless to tell what’s what. I’ll give you that a 2 hour timeline, zoomed all the way out, would be easier to “read” with tracks than in X. But really, does that matter? I’m only looking at small chunks when cutting and it’s easy to se what’s what, no Role highlighting is necessary. I don’t really even use it. I do use the index to solo Roles and to to make sure I’ve properly assigned everything before exporting audio. It’s not a big deal.
[Herb Sevush] “As has been stated repeatedly, color coded roles would address this issue, but since people have been asking for it to no avail for almost 3 years I don’t see why anyone expects to see it anytime soon.”
I hope Apple will get to the timeline soon. Seems like they’re focussing on one or two panels at a time. The timeline would seem to be all thats left. We’ll see I guess…
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Herb Sevush] “[Charlie Austin] “At this point though, it seems kind of irrational to me.”
If humanity were rational would weekends only last 2 days?”
lol, true… 🙂
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Herb Sevush] “Not saying it’s smart, not saying it’s right, just saying it’s very human.”
Absolutely true. At this point though, it seems kind of irrational to me.
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Andy Neil] “it’s definitely more than a “fraction of a second” operation, even with auto-patching.”
True. I generally have a minimum of 10 stereo pairs in my cuts, often quite a bit more. You can use targeting shortcuts with tracks to an extent (better in MC than in PR or FC old), but at some point, the clicking and dragging begins. I don’t think about that in X. Ever. I do occasionally spend time shift-dragging clips to try to keep everything viewable without scrolling too much. Really easy to do with the X timeline, as you only need to think about where it’s going, not how it will fit and what you need to move to fit it. Ya know, Track Tetris. 🙂
Yes, it makes the timeline look “messy”. Doesn’t matter. To me anyway.
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Neil Goodman] “Its a fraction of a second operation thats hard wired in my brain and that hardly leads to a ton of added time.”
But you have to do it every time you cut something in! ahahahah!!!! uh, sorry. 🙂 kidding!
This really is a silly conversation huh? If you’re proficient in any NLE, you’re gonna be fast. Your preference is your preference. I actually think the people who are most resistant to FCP X are current and former FCP 7 users. It’s really odd.
[Neil Goodman] “either way, this is a really great spot, I couldnt care less what it was cut in.”
Yep, totally agree. And i want that player script thingy! I can’t wait for it to start showing up on Blu-Rays, alternate endings, scenes etc. Maybe even in theaters! What fun it would be to cut 2 alternate but matching features simultaneously! Yikes! 😉
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[James Ewart] “So we are talking split screen?”
Not at all, you really need to see this, on a desktop, not mobil. Then it’ll make sense. 🙂
https://www.youtube.com/user/HondaVideo
[James Ewart] “it’s funny isn’t it. Doesn’t take much but suddenly from nobody but me using FCPX in the UK and almost having to mutter it under one’s breath, suddenly everybody has realised that this is software that works very nicely.”
Not here in L.A., at least in the little trailer cutting world of which I’m a part. It’s kind of odd.
[James Ewart] “he more I work with complex audio with multiple “tracks” the more I enjoy having my audio ext to my video no matter where it is in the timeline. It’s so liberating.
“Yep. All NLE’s have their strengths, but there’s nothing that compares to cutting in X.Once you get used to it it’s hard to work in the rigid world of tracks. 🙂
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[James Ewart] “I must be thick. I do not understand the two timelines. What is the purpose of the timeline below? When it plays you see the upper timeline. What is the lower timeline for?
“
Have you watched the spot? Link is somewhere in this silly thread… anyway, there are 2 films,cut simultaneously that play at the same time, one day and happy, one night and dark. In the final product a viewer can then switch between the two while watching. All the shots are “matching, and the same length. If the editor disables the top bits, the bottom plays and vice versa. Read the fop.co writeup for details.
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[John Heagy] “I’m guessing your working in 23.976.”
Yep
[John Heagy] “24000/1001 is the fractional way of defining 23.976.
24000/1001=23.976
Probably Adobe’s way of defining that frame rate.”
If their app modified the file, that makes sense. But nobody is taking responsibility. 😉 It probably wouldn’t be an issue on local files, but modifying file metadata on a server from a client seems to make bad things happen.
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~