Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations 10.06 On Apple’s Website Now

  • Erik Lindahl

    October 24, 2012 at 6:11 pm

    Review A/B shots or gang just about anything the current timeline. FCP7 also supported extra viewers – I’ve been working with 4-up on some projects. For CC-work its great to be able to see for example next edit, previous edit, reference frame X and / or perhaps current frame with out filters.

    The list goes on virtually. The current dual viewer is step in the right direction but they could make it 10-times more flexible.

  • Jeremy Garchow

    October 24, 2012 at 6:26 pm

    [Erik Lindahl] “FCP7 also supported extra viewers – I’ve been working with 4-up on some projects. For CC-work its great to be able to see for example next edit, previous edit, reference frame X and / or perhaps current frame with out filters.”

    Yes, that I can see. More than two viewers I completely understand.

    Jeremy

  • Erik Lindahl

    October 24, 2012 at 8:22 pm

    The dual viewers COULD be more powerful than they are. Locking them like now feels almost lazy.

  • Jeremy Garchow

    October 24, 2012 at 9:09 pm

    [Erik Lindahl] “The dual viewers COULD be more powerful than they are. Locking them like now feels almost lazy.”

    Do you use two monitors?

  • Erik Lindahl

    October 24, 2012 at 9:17 pm

    Two computer monitors and two video-outputs via the Kona 3.

    Speaking of which, FCPX could handle two monitors far better.

  • Jeremy Garchow

    October 24, 2012 at 9:28 pm

    [Erik Lindahl] “Speaking of which, FCPX could handle two monitors far better.”

    There’s a ton of stuff that could be “better”, I could say the same about almost any NLE and life in general. 🙂

    I do like messing around with the dual monitor setups, along with the scopes.

    Especially with video out, having the Event and timeline on one screen with the viewers on another I find to be pretty good.

    It is certainly different, but I am OK with different. I don’t need FCPX to be FCP8.

    It is more useful than what we had before the update. I still miss ganging, but I can now at least match frame edits between Event and timeline with a lot less trouble.

  • Oliver Peters

    October 24, 2012 at 11:13 pm

    [Jeremy Garchow] “add it to the timeline, go back to the clip and deselect the range.”

    Why?????? This makes absolutely no sense to me.

    Oh, never mind, I give up!

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Jeremy Garchow

    October 25, 2012 at 12:02 am

    [Oliver Peters] “Why?????? This makes absolutely no sense to me.

    Oh, never mind, I give up!”

    I can’t work without ranges.

    I mark a range, and I add a clip to the timeline, and that range is stored in the Event (or multiple ranges if I have marked multiple ranges).

    Those ranges are now saved forever until I remember to delete them.

    Can we at least agree on that much?

    Let’s say two weeks from now client calls and needs changes. All of the clips from one keyword collection in my timeline have failed legal due to lost name and likeness releases, and I need to reedit the piece to get rid of one location.

    I take all the clips in the Event that have failed legal, and reject them.

    But, since there’s PIOPs, only the PIOP range gets rejected, not the entire clip, so when I go to hide rejected, only the PIOP ranges disappear instead of whole clips.

    Before PIOPs, I could do what I want. I ranged favorites, which meant I wanted to explicitly keep or reject those ranges. Now, I have to manage those PIOPs, and since I can’t see them very well (the software does not have a method to track these PIOPs except in filmstrip view), it’s much harder to manage than it was to hit ‘f’ after marking a range.

    I also can’t sort clips by PIOP range in the Event like I can with keywords, favorites, or rejects.

    Sorry, but I don’t like it, and rather breaks a really good thing that FCPX had going, in my very unpopular opinion.

    Jeremy

  • John Davidson

    October 25, 2012 at 12:08 am

    Whatever floats your boat dude! I’m sure you’re figure out a workaround.

    I think the reason I have a hard time understanding why it’s a negative is that I’ve never rejected a clip, so it’s not a muscle memory that I have to unlearn.

    John Davidson | President / Creative Director | Magic Feather Inc.

  • Jeremy Garchow

    October 25, 2012 at 12:17 am

    [John Davidson] “I think the reason I have a hard time understanding why it’s a negative is that I’ve never rejected a clip, so it’s not a muscle memory that I have to unlearn.”

    It can go the other way.

    If I want to keyword or favorite or tag anything with an entire clip, but that clip has PIOPs, the PIOP range is always respected.

    The work around is to clear every PIOP after every edit (gag).

    Or constantly select all the clips in the Event and clear the selected PIOPs (gag x2).

    Jeremy

Page 11 of 15

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