Forum Replies Created

Page 178 of 285
  • Simon Ubsdell

    May 15, 2012 at 6:02 pm in reply to: Editing scenario

    [Jeremy Garchow] “I guess I need to ask you. How do use i or o separately? Is it not to do a three point edit?”

    Well, there are two parts to this answer.

    One is that I often use I OR O as very temporary placeholders, as I’m sure a lot of editors do. I don’t want to have to use a favorite for this. Chiefly because using favorites for something so fleeting means continually having to Unfavorite (this gets very necessary when you are trying out different source edit points in the same clip which must be pretty common and certainly is in my experience) – and to worry about overwriting existing favorites which will always happen if I’m only interested in EITHER the I OR the O because the untended I or O will always default to either the beginning or the end of the clip.

    The second point about three point editing in FCPX is that (unless it’s something I’ve been overlooking all this time) you can’t backtime a three point edit using only and I or an O in the Browser. (You can of course do this if you set a range in the Browser and use Shift/Edit Function, but that’s different.)

    The point is that in FCPX every selection MUST be a range whether you like it or not. And a lot of the time I don’t actually want a range. I only want an I OR an O.

    Simon Ubsdell
    http://www.tokyo-uk.com

  • Simon Ubsdell

    May 15, 2012 at 5:43 pm in reply to: Editing scenario

    [Jeremy Garchow] ”
    This is a totally different discussion.

    In that earlier Andy thread, I said that you can still do three point edits in FCPX. So while you have to mark on O with your I, or an I with your O, you still have three point capability from either the in or the out.”

    I don’t see how it’s a different discussion – could you explain?

    And I’m absolutely sure I didn’t say you couldn’t do three point editing in FCPX.

    Simon Ubsdell
    http://www.tokyo-uk.com

  • Simon Ubsdell

    May 15, 2012 at 5:25 pm in reply to: Editing scenario

    [Walter Soyka] “Apple designed the software and could have included persistent/remembered/whatever IO points if they wanted to. Why might they choose not to? How is it better for the user to have their IO point decisions blasted away if they click off a clip without first making it their selection a favorite range?”

    As I’ve mentioned before, the range selection process is a holdover from iMovie and there may be some fundamental residual design issues that are hampering the provision of persistent IO.

    I would suggest that IO functionality was grafted on to the underlying range selection process but IO doesn’t “exist” in the same way as in the past – it’s merely a keyboard way of delineating the start and end of a range that “mimics” the mouse action.

    BUT – the point that keeps getting lost in this whole discussion is that what’s really important is not persistent I and O but rather persistent I or O. Yes, you can more or less cope with the lack of persistent IO “ranges” by using the favorite function. But there is no way of simply keeping EITHER an I OR an O.

    And this for me and I’m sure many, many others is far more of a pain. I don’t believe I mark BOTH I and O in the browser more than 20% of the time (probably more like 10% but I’m being very generous). On the other hand I rely on using EITHER a single I OR a single O on every other occasion.

    If I use Favorites as a way of trying to keep this functionality, each new Favorite extends all the way to the beginning or the end of the entire clip, thereby overwriting any previously assigned favorite or favorites. Because you can’t have overlapping favorites as everybody knows. That’s a really significant thing.

    So to reiterate, please let’s stop arguing about persistent I and O, and let’s start a discussion about persistent I only. Or persistent O only. The difference between AND and OR is the crucial one. FCPX allows for AND (kind of) but won’t allow OR in any useful sense.

    Simon Ubsdell
    http://www.tokyo-uk.com

  • If you want to animate a zoom, then add a Ramp behavior to the layer’s scale (master) value.

    Adjust the End Value of the Ramp bevahior to get the amount of scaling you want (or publish it if you prefer).

    Publish End Offset of the Ramp behavior to give control over the duration of the animation (preferably via a widget). Note that this works backwards from the end of the behavior, so if you had a 100 frame project and you wanted the animation to last 30 frames you’d need an offset of 70 frames. And so on. If you are using a widget you can make this easier to read for the FCPX user with a few extra steps.

    Simon Ubsdell
    http://www.tokyo-uk.com

  • Use the Ramp behavior on any parameter for which you want to publish the animation times. Alternatively, Exponential and Logarithmic give you dufferent animation curves that you may prefer.

    Simon Ubsdell
    http://www.tokyo-uk.com

  • Simon Ubsdell

    May 14, 2012 at 1:19 pm in reply to: Editing scenario

    [tony west] “It’s a good question, because auditions works fine for this very purpose.

    I have not really counted, but it seems like auditions is more key strokes than the way I do it.

    When I stack graphics it’s fast to toggle back in forth this way.

    It’s ONE key V V V V back and forth

    One of the things I like most about apple products is there are often many ways to do the same thing.

    Let’s say I have 3 employees stacked up.

    They pick employee #2

    Employees 1 and 3 are still sitting there in the timeline and I can just grab one of them and drag it further down in the timeline to replace another shot.

    I like having them sitting there. It just seems faster to me.”

    This is one of the things I have being doing in FCP Legacy for years – CtrlB (or whatever else you want to map) toggles the visibility in Legacy (and Ctrl S toggles Solo) just as V toggles the visibility in X. It’s interesting that you prefer the “old way” of doing it rather than using Auditions 😉

    Simon Ubsdell
    http://www.tokyo-uk.com

  • Simon Ubsdell

    May 13, 2012 at 8:08 pm in reply to: Editing scenario

    [Steve Connor] “Oliver is actually talking about a corporate video”

    Yes, my mistake.

    [Steve Connor] “it’s also a little patronising to suggest that corporate videos don’t have the same complexity as broadcast.”

    I certainly didn’t mean to sound patronising (and I did specifically include a disclaimer) but if I did then apologies.

    I think though there is a difference let’s say rather between long form documentary editing and short form advertising type editing (which is more the kind of thing Oliver was describing even though it’s technically a “corporate”) – and this might be where FCPX suits the former rather better than the latter. Complexity in this case is not about whether one or the other is more creatively demanding but rather about the level of intricacy that is called for in the actual cutting.

    Simon Ubsdell
    http://www.tokyo-uk.com

  • Simon Ubsdell

    May 13, 2012 at 7:32 pm in reply to: Editing scenario

    [David Lawrence] “This thread is a great example of the kind of real-world problems that I don’t think the FCPX engineers and UI designers thought about when they designed the FCPX timeline.”

    I think what’s interesting is that Oliver is describing a type of editing that some of us are very familiar with which is intrinsically very fiddly.

    I have noticed that the editors who are most happy with FCPX tend to be those who work in documentary or corporate where (and this is not at all suggesting the work is any less “creative” or demanding) these kind of complexity issues don’t have to be faced to anything like the same degree.

    Simon Ubsdell
    http://www.tokyo-uk.com

  • Simon Ubsdell

    May 13, 2012 at 7:29 pm in reply to: Editing scenario

    [Bret Williams] “When hey demoed x at he super meet, Randy ( the designer) didn’t mix broll in the primary. So they obviously weren’t thinking that way.”

    It’s worth mentioning that connected clips in iMovie (yes, they are the same thing) are called Cutaways which I think shows that indeed you are right and that, in Apples’ mind at least, B-roll is “meant” to be added as connected clips.

    Simon Ubsdell
    http://www.tokyo-uk.com

  • Simon Ubsdell

    May 13, 2012 at 4:34 pm in reply to: Editing scenario

    [Andy Neil] ”
    One of the workflows that editors use in a track system that is hardest to drop in X, is the notion that soundbites need to be in track 1, and broll shots in track 2. We do this in track systems because it makes it easier to keep track of things, and to make changes to bites. In X, it’s actually easier NOT to do things this way because of the nature of connected clips.”

    This does raise the question which most of the time seems to be the hardest thing to get right, namely what actually DOES go into the primary storyline. A lot of the time you end up wondering whether it’s not easier to dispense with the primary altogether, leave it as a gap clip (or several) and just have stuff hanging off it …

    Simon Ubsdell
    http://www.tokyo-uk.com

Page 178 of 285

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