Creative COW SIGN IN :: SPONSORS :: ADVERTISING :: ABOUT US :: CONTACT US
Creative COW's LinkedIn GroupCreative COW's Facebook PageCreative COW on TwitterCreative COW's Google+ PageCreative COW on YouTube
APPLE FINAL CUT PRO:HomeFCP ForumFCP XFCPX TechniquesFCP TutorialsFC ServerBasics ForumTrainingPodcastFAQ

Re: Editing scenario - Why PIOPs might not be easy

COW Forums : Apple FCPX or Not: The Debate

VIEW ALL   •   ADD A NEW POST   •   PRINT
Share on Facebook
Respond to this post   •   Return to posts index   •   Read entire thread


Walter SoykaRe: Editing scenario - Why PIOPs might not be easy
by on May 22, 2012 at 7:11:25 pm

[Jeremy Garchow] "There is today, an I think that's Philip H's point. Everything is associated to that clip. It's how it works, at least for now. Favorites are simply a "sort" or an alternate display of data assigned to that clip. "

But -- the interface can present those alternate displays of data as if they WERE clips, even though it may not represent them as clips internally. This can create a problem any time you might want to consider a clip as an instance of a specific range of content (from a UX perspective), as we see here.

Although your "everything is associated to that clip" line may explain why favorites can't overlap. You'd have to show either a partial range (which would be false and misleading), you'd have to show the entire range (which would erroneously extend the current favorite), you'd have to not show the range at all (which breaks the association back to the clip), or you'd have to come up with a new way to indicate that the other range is incomplete (which could be too confusing or complicated).


[Jeremy Garchow] "An in/out range is no different. So, if X could remember piops on every single instance of one clip, in order to keep track of all this info on the near infinite combinations of data "sorts", it seems that FCPX would have to create some sort of io category, and then constantly track all those changes and update them. Maybe that sort of thing is possible, but is it really necessary?"

Is it necessary? Of course not. It's a feature request. Developers ignore them all the time.

My version of the question is this: is the app better or worse without PIOPs? If users really want them, will it hurt the application to include them? Was it a good idea to design the app so it couldn't have them in the first place?

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


Posts IndexRead Thread
Reply   Like  
Share on Facebook


Current Message Thread:




LOGIN TO REPLY



FORUMSTUTORIALSMAGAZINESTOCKYARDVIDEOSPODCASTSEVENTSSERVICESNEWSLETTERNEWSBLOGS

Creative COW LinkedIn Group Creative COW Facebook Page Creative COW on Twitter
© 2013 CreativeCOW.net All rights are reserved. - Privacy Policy

[Top]