BillVincent wrote:
To sum up the reason why I am so frustrated over this is because as a professional editor, I don't appreciate someone telling me that something is supposed to be a certain way on purpose, when it is most definitely wrong! 1
I learned multicam on Avid back in the 90's, and FCP took 7 major versions to have anything similar to that. FCP 1.0? No. FCP 1.01? No. FCP 2? No. FCP 3? No. FCP 4? No. FCP HD (4.5) No. FCP 5? Finally! Also keep in mind the basic things that never were implemented in FCP that were really important to editors coming from Avid (Virtual KEM, dynamic trimming, etc.).
Premiere Pro is going through similar growing pains. I don't mean to insult your intelligence, and I do agree with you that the multicamera tool should offer an editor the choice to make a cut or leave the cut alone. A feature request is the best weapon in getting what you want. And be specific. Rants don't get you anywhere, but feature requests do. I don't mind impassioned discussion, but please, giant blue letters are not necessary. Let's have a discussion about it.
BillVincent wrote:
You can't tell me that this behavior is correct for ANY timeline, not just multicam. I say again, if the normal timeline created an edit every time you stopped playback, people would be screaming bloody murder until something was done.
I don't think of it that way, since multicamera editing uses a wholly different mode. Let's just say that I agree that when stopping playback in multicamera session, it should not behave as it currently does--the Space Bar should merely stop playback.
BillVincent wrote:
Don't insult my professional intelligence by saying this is appropriate behavior for the software. And I also would like to see even ONE pro editor try to use multicam and tell me it behaves as it should, or that the behavior is preferred for any long form edit.
I'm agreeing with you, the behavior is wrong. It should be modified. Whether or not it's the appropriate behavior of the tool, it is the way it was originally designed, and that's the unfortunate reality we're dealing with. I have no idea why it was designed that way either. Please know that this is a change most pro editors would want.
Believe it or not, I'm an editor too. Before I came to the video software business, I also found it hard to understand why fixes and new features took so long to implement. Let's say you create this cool new feature, but when you check it in to the main branch, other tools get broken. Those are the kinds of things engineers and QA has to deal with.
BillVincent wrote:
Why ARE we going around and around about this? Why can't Adobe admit this fault? Is there a legal issue behind this somehow? Are we not getting the full story? Why is it so hard to call this a bug? Why continue to provide excuses and arguments instead of addressing this issue head on?
We're going round and round about this because it is an important workflow that is not optimal and could use a modification for those that are FCP switchers, and others, used to a different behavior. I'm an Adobe employee. Here's the straight dope: the tool as designed is not working the way we want, and we as pro editors agree that it should be fixed. Since CS5.5 (post FCPX), more and more FCP editors have been coming into the fray expecting absolutely everything should work precisely the way FCP does. Tough road to hoe! We've been doing our best, and most have appreciated the work we have done over the past few releases, but we admit we have a lot left to do. I am addressing the issue head on by telling you to file a feature request. The more feature requests on any one feature, the more weight it gets for consideration on an upcoming release. For those new to the Adobe community, that's exactly the way we've always dealt with issues like this. Sorry if you weren't aware of that. I also meet with the team to tell them of customer complaints, I'll make sure to let them know that people are still disappointed that the feature has not yet been modified to the way it should.
BillVincent wrote:
Don't just give the same story again. Tell me why the normal timeline doesn't create an edit when the playback stops and multicam does, along with changing back to the first angle before playback began. Explain the reasoning, and maybe I can somehow understand. Was this behavior on the advice of a pro editor? Who, and why?
Let's not waste time as to the reasoning about the way the tool was designed. It is what it is. Let's just both agree that this behavior should be fixed and let's work towards that.
BillVincent wrote:
The level of frustration over this is huge, not just because of the problem itself, but because of the way we are being sold down the river by being told it is intentional behavior.
Sold down the river? I'm just telling you that it was the way the tool was designed. We agree that we don't like the way it was designed and should file feature requests about how it should be working. That sums it up, but unfortunately, a lot of multicamera editors coming from FCP or Avid are going to have to be patient.
BillVincent wrote:
What once was just a technical issue has now become ths ridiculous sideshow of back and forth. You have made this issue personal by being so obstinate about it. Maybe a supervisor needs to review this issue. I am furious not over the issue, but from the attitude Adobe has taken toward it's users over it.
I'm just telling you the way it is. Nothing changes without a feature request. It's too bad I can't snap my fingers and give you the feature you want. Also, that I agree with you. I'm on your side. I think you'll get much further by adding your voice in a feature request or bug report: http://www.adobe.com/go/wish.