-
10.06 On Apple’s Website Now
-
[Jeremy Garchow] “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.”
Would a “Forget Ranges” command that could be applied after selecting clips in the event browser fix it for you?
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Jeremy Garchow] “Those ranges are now saved forever until I remember to delete them…..
……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.”Aah, OK, now I see the issue. It’s not a problem with PIOPs at all. The problem is that Apple BROKE the show/hide rated clips mechanism when they added PIOP. So I think your frustration is actually misdirected, IMHO.
[Jeremy Garchow] “I also can’t sort clips by PIOP range in the Event like I can with keywords, favorites, or rejects.”
Time to go back to Media Composer 😉
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Ok, I think I’m getting it a little bit. Look on the bright side though. If you have an event with a ton of sfx, sometimes the sfx makers give you way too much in the way of handles. Maintaining the range will save you the annoyance of having to either trimming the inserted clip to the usable area or having to favorite the clip. No?
We do lots of sfx so it makes that a little easier.
I could be totally wrong.
John Davidson | President / Creative Director | Magic Feather Inc.
-
[Oliver Peters] “Aah, OK, now I see the issue. It’s not a problem with PIOPs at all. The problem is that Apple BROKE the show/hide rated clips mechanism when they added PIOP. So I think your frustration is actually misdirected, IMHO.”
That’s part of what I said much earlier on. There’s no visual cue (like a key, a star, a red x that show up in list view in the Event) and there’s no way to control PIOPs like you can with the other range capabilities in FCPX.
I do not think it’s misdirected at all (imagine that).
If you add capability to PIOPs like Favorite, Keyword, or Rejected ranges, then you have just added the exact same capability that was already in the software, so what’s the point of adding them in the first place?
Or did I lose you again?
It IS a problem with PIOPs and how they work. If they were just a stored ranges like favorites (with perhaps a little yellow bar instead of a range that is ignored until clicked on) it might be better.
Now, when I mark a range as a favorite, not only have I stored that range as a favorite, but FCPX stores that range as a PIOP unless I option-x all the time. It is now double stored.
It’s f*cked up.
Jeremy
-
[Jeremy Garchow] “It IS a problem with PIOPs and how they work. If they were just a stored ranges like favorites (with perhaps a little yellow bar instead of a range that is ignored until clicked on) it might be better.”
I do see where you are coming from. I think the core of the problem is allowing multiple PIOPs per clip, instead of simply holding the last In-Out. Maybe another case of Apple over-thinking things.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[John Davidson] “We do lots of sfx so it makes that a little easier.
I could be totally wrong.”
You aren’t wrong. I use PIOPs all the time in other NLEs because they work that way.
FCPX has different methods that I quite enjoyed and allowed a level of flexibility that I can’t get out of other NLEs.
I would just like the capability back without all the extra steps.
A user preference would be nice:
PIOPs, YES/NO
Jeremy
-
[Oliver Peters] “I think the core of the problem is allowing multiple PIOPs per clip, instead of simply holding the last In-Out.”
But it doesn’t matter. One range or 14 ranges. It’s all the same. It’s always one too many if you don’t want them.
-
[Jeremy Garchow] “But it doesn’t matter. One range or 14 ranges. It’s all the same. It’s always one too many if you don’t want them.”
I think you missed my point. The core of your complaint is how it’s affecting the organizational methods. If that had been left unchanged and there was simply a single PIOP set held that didn’t interact with these, I doubt you’d have a problem with this. Obviously the way this was implemented has caused unwanted and unnecessary changes. If by design, then it’s “engineering over-think”. If not, then it’s a bug.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “I think you missed my point. The core of your complaint is how it’s affecting the organizational methods. If that had been left unchanged and there was simply a single PIOP set held that didn’t interact with these, I doubt you’d have a problem with this. Obviously the way this was implemented has caused unwanted and unnecessary changes. If by design, then it’s “engineering over-think”. If not, then it’s a bug.”
Even if there’s only one PIOP, it still interacts. Multiple PIOPs really have nothing to do with it.
If PIOPs didn’t interact with the other range capabilities, then yes, I wouldn’t have a problem, but how would that work since PIOPs are a range themselves? There’s no way a PIOP can and can’t be a range, unless of course, you define two types of ranges. Command drag for persistent, drag for forgetful. ‘option-i’ for persistent, ‘i’ for forgetful.
I think it is Apple reacting to the insurmountable amount of backlash, and destroyed a good idea in the process. I guess that could be considered over thinking.
I can’t say that I blame them, it’s just too bad they had to make such a harsh compromise.
There is a lot to like in this update. I am glad Apple is listening. The other benefits outweigh the PIOP change. The flexible connections are very helpful, for example.
Jeremy
-
[Jeremy Garchow] “If PIOPs didn’t interact with the other range capabilities, then yes, I wouldn’t have a problem, but how would that work since PIOPs are a range themselves? “
Why? The organization function is based on rating the range. As long as these stay unrated, its shouldn’t be affected. I’ll agree that the design, as currently implemented, has had unintended consequences.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com
Reply to this Discussion! Login or Sign Up