-
10.06 On Apple’s Website Now
-
It is clear after reading the really really long PIOP thread from earlier this year, I see this way different than some people. In that thread, I think I was the only person who didn’t want PIOPs, or saw favorites as way to get user selectable PIOPS with very minimal fuss. I think it might be very hard for me to explain why I don’t like PIOPs in FCPX.
[Oliver Peters] “I still don’t get the reason for the complaint. You didn’t lose anything. You simply gained a second way of working. What’s the problem?”
I thought I explained it decently in the long post before this one. I’ll have to find time for a screenshot-a-thon later.
[Oliver Peters] “Don’t use it and continue to use range-based favorites as you always have.”
Therein lies the problem. I have no choice but to use them as they are always there. In order to not use them, Id’ mark a range, add it to the timeline, go back to the clip and deselect the range. What a pain in the ass. I have specific examples, but I’ll back them up with screenshots later. I wish I could turn them off.
[Oliver Peters] “I also see no element of “the software being dumbed down and making decisions for you” in this instance.”
Because FCPX is making a decision that it’s going to hold on to that range. When I add tags to that clip, it will only tag that range, and that might not be what I want. When you select a large group of clips, you have no idea if there’s any PIOPs on them or not unless I am sorted in to filmstrip view. I use list view a lot more than filmstrip. It basically creates more clicks for me and slows down the workflow. I rather liked the speed at which I could move before PIOPs.
Without PIOPs, I had full control over what I wanted tagged or not. Now with PIOPs, I have to take extra steps.
I do like the multiple ranges, but I wish they wouldn’t stick around.
More later.
-
[Keith Koby] “This is a big step forward in getting wider adoption and like Oliver, I can’t find that it’s some huge hindrance to the old way. It seems that it has even given you a way to keyword ranges on multiple clips simultaneously. I haven’t tried that, but it seems it would work.”
I understand.
People had a really tough time with favorites for some reason. I really liked them. Ranges now work completely differently. I can still favorite a clip, but then that range is held on to not only by a favorite, but a PIOP as well (unless I clear the range after adding the clip to the timeline).
This works exactly like FCP7 did, but FCPX works differently than FCP7 so I feel this is a step backwards. I know this is not a popular view point. So be it.
If you editors that you are training don’t use keywords, rejections, or any other tags, range or clip based, PIOPs work very well.
With other NLEs, most of the organization is done right up front, almost before editing.
WIth FCPX, I can constantly reorganize clips, or groups of clips, for different purposes (which is one of the huge reasons I like FCPX, clips can be here AND here, not here OR here). PIOPs now add extra steps in order for me to continue organizing the way I’d like, and there’s no visual cue in list view of which clips have PIOPs. If there was a visual cue, then they would just turn in to another favoriting system.
I’ll have to show you later.
Jeremy
-
[David Lawrence] “Doesn’t Command-A take care of everything?”
It doesn’t.
-
Jeremy, this makes sense to me.
I maintain that range selection was too transient before, and that it was too easy to lose user data, but now I wonder if the current range selection is too persistent, making it too hard for the user to manage.
This is in part why I why I backed down to wanting selections pushed onto the undo stack. Mitigate loss of user data without mucking too much with the good parts of the new selection and object models.
I’m going to have to spend some time with this next week to form a more informed opinion, but I totally see where you’re coming from.
Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog – What I’m thinking when my workstation’s thinking
Creative Cow Forum Host: Live & Stage Events -
[Erik Lindahl] “Use the view to “open clip from timeline”. Why can’t I do this?”
Select the clip in the timeline (there’s keyboards shortcuts for that), then SHIFT-F.
-
That’s not the same thing. That command shows the clip in the event browser not the timeline. I.e. any change done in the timeline isn’t reflected to the clip in the event viewer which is bad and renders the tool less useful I’d say.
-
[Erik Lindahl] “That’s not the same thing. That command shows the clip in the event browser not the timeline. I.e. any change done in the timeline isn’t reflected to the clip in the event viewer which is bad and renders the tool less useful I’d say.”
Just curios, but what would you need this feature for? The Viewer does what you’re asking, there’s no need to load the clip in the Event Viewer just so that you can see what you’re doing in the timeline, doubled.
With FCP7, you had to do this in order to access the Motion panel, with X, you have access to the control in the inspector.
Jeremy
-
Were are you getting that 10.7 is required? All I am finding under “Requirements” on Apple sites is 10.6.8.
-
The app store won’t let you download and install without 10.7.5. It says something like “this update requires 10.7.5 first…”
Keith Koby
Sr. Director Post-Production Engineering
iNDEMAND NETWORKS
Howard TV!/Movies On Demand/iNDEMAND Pay-Per-View/iNDEMAND 3D -
Yes 10.6.8 (not in app store of course), 10.7.5, 10.8.2
Only current versions of Snow Leopard, Lion, Mountain Lion.
You’re not going to find 10.6.8 in the app store and 10.7.4 or 10.8.1 doesn’t meet the spec.
Reply to this Discussion! Login or Sign Up