Forum Replies Created

Page 65 of 282
  • Chris Harlan

    April 23, 2013 at 5:25 am in reply to: Avid Won’t Transcode Atomos Samurai Footage

    I’m curious. Did you ever get to the bottom of this?

  • Chris Harlan

    April 23, 2013 at 5:23 am in reply to: Is AVID worth the swap?

    [Ben Taylor] “I have been editing on both Adobe Premiere Pro and Final Cut X for quite some time now. However, I am considering swapping from these programs to AVID.

    Hey, Ben–out of curiosity, why are YOU considering this? I think we can all answer you better if we know why you may want to change. Also, what kind of work do you want to do? What kind of projects?

    I’ll say this much; its a venerable NLE and I quite enjoy using it. It is quite different from X. It’s a little closer to version 6 of Premiere, but still very much its own system. The learning curve is a little steeper, though nothing that can’t be managed with tutorials. To my mind, some of its elements are a little archaic, and some elements, like its full suite of trimming tools, can’t yet be beat by any other NLE.

    As you see, I personally like it quite a bit, but there are plenty of good reasons why it might not be the best choice for someone as well.

    So, why are you interested in it? And why do you want to move away from the other two?

  • Chris Harlan

    April 23, 2013 at 4:21 am in reply to: lively discussion at John Nack’s blog.

    [Oliver Peters] “At some point you DO have to call a project “DONE” or you’ll work for free forever. “

    Amen.

  • Chris Harlan

    April 22, 2013 at 8:13 am in reply to: **Danger Will Robinson** **Danger Will Robinson**

    [David Lawrence] “No. It’s not the price. I want to give Adobe my money.

    I do get where you are coming from, and feel some of it to, though I did go for the cloud deal the other day. I would PREFER to own it, though I’ll go along for now because it is offering some add-ons that I like.

    This is the issue for me: Right now I like where Adobe is going, and I want to go along. But what happens if Adobe decides to go somewhere I don’t want to go? If I’ve bought upgrades through CS8, but don’t like CS 9, and I own CS 8, well, I can just stop. No need to upgrade, no need to follow along. I can just keep working with what I have. If I’m Clouding it, however, that option isn’t as easy. Yes, I can not hit the update button, but I’d then be paying in perpetuity for something that was frozen in time.

    To take it a little further, let’s say its not about the software. Let’s say its about the company. I like Adobe quite a bit right now, and I have no reason to think I won’t in the future, as well, but the cloud-only scenario marries me to them in a way I’m not completely comfortable with. If it turns out that they have been enslaving Time Lords, clubbing with baby seals (I don’t think Adobe would ever actually club baby seals), or are bought out by either Massive Dynamics or the Vogons, I want the opportunity to walk away without jeopardizing my work.

  • [Craig Alan] “The Apple certification exam for FCP 6/7 for example (which has little to do with the professional world) often asks the three ways you can apply a blah blah blah.

    Ah! I get it now.

    [Craig Alan] “I get you. You’re in trim mode. I tend to work on a section of the time line rather than a function. I’m not very fluent. “

    I go back and forth. I’m not a mode maniac by any means, but I’ve enjoyed it more this time around. It’s kind of fun to get in a grove for a few minutes where you don’t think of anything other than cuts and transitions and how they work together. Still, I do most of my work sectionally, moving between modes.

    [Craig Alan] “Very true about Apple and X. I was really thinking of FCP legacy. And I think this was the Apple way and others borrowed from it. “

    I can certainly agree with that. For me, the most beautiful thing about Legacy is/was how flexible it was/is. You could come at it from almost any angle and find a way to make it work. It was really quite brilliant, and I’m still a touch sad that it got junked. But that was then, and this is now. You are right, though; a minimum of three different ways to do everything.

  • [Mitchel Hansen] “Wow, thank you so much, Nate, for offering absolutely no advice or help to anyone here and simply praising yourself for the sake of…well…let’s face it, being egotistical. Have you taken over the world yet?

    Are you aware that you are bagging on someone for a post that is almost two years old?

    Nate’s point, btw, was that he was making FCP X work, and was excited about it. In the context of the time, just after FCP X’s release, what he was saying makes perfect sense, even though I would have–at that time–vehemently disagreed with him. It was undoubtedly helpful for some to hear it, and, I find nothing at all egotistical about it.

  • Chris Harlan

    April 22, 2013 at 3:20 am in reply to: Why we will be choosing PremierePro over FCPX

    [Ievgenii Larin] “I agree with everything except your point about Motion 5. Motion 5 is awesome inexpensive piece of software that allows very flexible manipulations with titles and effects in FCPX.”

    I happen to agree with you about Motion.

  • [Craig Alan] “It would be cool to be able to go back in the other direction. Trim to no frames, play around play head, add back a second of frames, play around play head.”

    Depends. I personally prefer that you are now trimming the new cut. But we are getting beyond granular in focus, here; aren’t we?

    [Craig Alan] “But delete will delete the entire clip and I thought the logic here was extending the trim function from zero to end of clip’s media.”

    No. The point is that you don’t have to leave trimming mode. But, hey, if it suits you delete it instead.

    [Craig Alan] “Personally I like Apple’s decision to have three ways of doing many operations. It helps prevent fatigue and carpal tunnel syndrome.”

    Yes, that’s nice. But why do you think that’s “Apple’s way.” If anything, X offers much less choice than it has in the past. And both Premiere and Media Composer offer many different approaches to any particular operation. As far as trimming variations go, MC is probably the current winner. Premiere Next might take that; we’ll have to see.

  • Chris Harlan

    April 22, 2013 at 1:45 am in reply to: Why we will be choosing PremierePro over FCPX

    [Bill Davis] “A – I need to keep working the way I always have because my investment in process is too deep to jettison.
    (which is an extremely defensible contention, by the way)

    or

    B – I’m willing to explore new ways to work in order to potentially benefit from some new ideas and thinking.

    Everyone fits in one camp or the other.

    Just NOT true, Bill. It isn’t one or the other however hard you try to make it so. Or how many times you say it. I’m not working the way I always have when I’m working on an Avid. My methodology is quite different. In some respects, working in X might even be closer.

    There are some things X does really well. There are some things it doesn’t do well. There are even some things it does badly. If most of what you do fits into group one, than X is probably for you. If a sizable chunk of what you do fits into group three–like a lot of what I do does–than it will probably be a long while before you want to use X.

  • [Craig Alan] “Can you add back frames after you’ve trimmed to zero?”

    No. Cmd Z to fix. I see I also failed to mention that when dynamic trimming, you need to nudge the trim key for the last frame.

Page 65 of 282

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy