Re: Editing scenario - Why PIOPs might not be easy

[Walter Soyka] "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."

I think we are losing focus here.

There's a clip in FCPX. On that clip, everything happens.

FCPX does not treat alternate displays as new clips, everything always "attaches" to that one clip.

So, in that picture that I sent earlier, even though you see 5 instances, the data assigned to any instance, is universal to that clip. If I added a marker to what looks to be the 5th "clip" in favorites view, I could assemble the 4th clip on to the timeline, and if I extended that clip long enough, that marker would also show up in the timeline, even though I added the information what looks like the "5th" clip. If I unfavorite one of those clips, that range disappears from the master clip, not just that one favorite.

So now, if you want piops, let's say I set a range on the 5th instance, I set a range on the 4th instance, I set a range on the 3rd instance, and since FCPX now remembers everything, I sort to "all clips".

This means I now am viewing the master clip. This means that I will now have three ranges on that one clip. I select a range on the master clip that happens to fit in to one of the favorites. Does this create a new range, or does it add to the ranges that already exist? Let's say it creates a new range.

I now want to sort back to favorites, so I do.

Now, the range I just made on the master is replaced with the range I made when I was sorted by favorites not a moment ago.

See what I mean? Why do we need all of this? Why not simply hold on to the ranges you want to with some favorites or keywords that will stick with you as you intended instead of X trying to guess what you want all of the time?

[Walter Soyka] "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?
"

Again? I'll get guff for this but:

It DOES have them, but it works differently. It works differently as it has to.

The whole application works differently than FCP7.

It is up to an individual to see if it's better or worse.