If you are thinking of switching from FCP7 or FCPX or Avid or another editing program to Premiere Pro CS6, there are MANY great reasons to do so, HOWEVER, if you deal with editing multiple cameras (multicam) then you may want to think twice about it until this issue is resolved.
How to edit multicam in Adobe Premiere Pro CS6? What is the best editing program for mulitcam or multiple camera editing? - The answer, until the issue below is fixed, is NOT Adobe Premiere Pro! As of CS6 (version 6.0.2), this "design" flaw or "quirk" described below makes multicam editing very difficult and inefficient in Premiere Pro. Those first two questions above are what I google searched in hope of a fix to an issue that has plagued Adobe Premiere Pro for years, literally. Unfortunately, in the new Premiere CS6, with so many other great new features, the issue still remains making it very difficult to do a multicam edit compared to FCPX, Final Cut Pro 7, Avid, Sony Vegas, etc. They all handle multicam editing in different ways but, having recently switched away from FCP7, and worked on several mulitcam edits, Premiere Pro CS6 (and CS5, and CS5.5) has serious issues/problems with the multicam feature that is broken as of right now (version 6.0.2) in Premiere CS6 and makes editing multicam a VERY frustrating experience and much less efficient compared to other NLE's. If its a design, then its flawed as yes, you can get around it and fix what you've done, but why should you have to keep wasting valuble time "fixing" things like this anyway? Just doesn't make sense.
The issue:
Hitting the spacebar or pause or stop button during a multicam edit actually stops the edit, makes a cut in your edit (timeline), and then switches to a different camera (angle or shot) whether you want it to or not!
This issue has been known by Adobe for over two years but they push it aside, call it a design quirk, and ultimately avoid fixing the issue as noted in this thread: http://forums.adobe.com/thread/738084?start=0&tstart=0
Having your editing program make cuts and switch angles on you when you simply pause or stop playback is a huge issue. If this were happening in the normal timeline then I'm guessing it would have been fixed, but it hasn't been fixed and it causes the editor to have to go back and remove the un-intended cuts and switch shots back to where they should be. The PAUSE button should only PAUSE or STOP the playback as it does in other programs. But in Premiere it pauses, makes a cut in your timeline, and then switches back to the first angle or shot that you started with whether you want to or not. There is no way to stop this from happening as of right now on CS6. The other thread that talks about the issue brings up the fact that the "issue does not have the numbers" to make it a priority to be fixed and there are other "more important issues" that need to be fixed first which makes me wonder if Adobe really does listen to their user's feedback. I mean, 2 years of people complaining about this and no fixes. Their response has been "add it to the wish list" or "it's not a bug, its a quirk, so make a feature request" or "its designed that way." Designed that way? Who would actually want it that way? No other NLE does this and for good reason. If the pause button just paused playback and that's it, do you think there would be a thread lasting for 2 years about how hitting pause "should also make a cut in the timeline and switch shots"? I doubt it. Its a design flaw. I feel strange asking for the feature "please make the pause button pause" or "please make the stop button stop playback". Sounds like its broken to me.
If multicam fuctionality is a major focus for the Adobe Premiere team going forward, which I believe it is, then please start by making even the basic functions work as one would expect them to. PAUSE=PAUSE. STOP=STOP. Whew! That was tough. Done. Fixed. Moving on! Right now, this design is counter-productive, not intuitive, helps no one, and only wastes valuable time while the editor has to quickly "fix" the issue.
Well, I figured I'd do two things here:
1) Start a thread with as many keywords as possible so that this issue gets "the numbers" both in this forum and in Google searches. Hopefully soon when you google "Premiere Pro multicam" this will be the first topic on the first page. My hope is that I can put a nice "SOLVED" or "FIXED" label on this thread one day soon (and I will for sure!). If that's the case, its a testament to the squeeky wheel theory combined with a little web analytics.
2) Make this a new thread rather than continue in the old thread because it's time to ask a new question: how long will it take for Adobe to fix an issue when its design is essentially broken causing all users to have to do a "fix" every time? Right now it's going on two years! This isn't a feature request...its a broken function within Premiere. A design...flaw. I do know Adobe listens and that they care about certain things, but how fast do they act? That's my real question.
I wonder if this thread will populate with more "we've got more important things to fix" or "it isn't that big of an issue" or "its not an issue at all, its a quirk" or "you can just go back and fix the problem every time you have to stop as it only takes a few seconds" or "its not broken, its designed to be counter-productive and frustrating to users". Time will tell. Well, if you do as many mulitcam edits as I do then those "few seconds" add up. If it is designed that way, then Adobe, I ask you this: If you hit the pause button on your TV remote and it paused the live TV, but then also turned the volume all the way down and changed channels...would you still just call that a quirk? Would it make sense to design a remote that way? I'd say that the button on your remote doesn't work right and should be fixed. Yes, you could fix it quickly by hitting the "last" or "recall" button and then hitting the volume up button, but shouldn't the PAUSE button on your remote do just that and only that: PAUSE?
Please, do respond...we apparently need the numbers. 
1 Correct answer
Have you tried what a user suggested earlier in the thread? Although it takes a little getting used to, it works for me perfectly.
"Before to stop the playback press the key 0 (zero) of the keyboard and then you can stop the play (with the Space bar) without the cut in the timeline."
44
Replies
Kevin Monahan wrote:
Before I got into the software biz, I was an editor just like you. Back then, I found it hard to understand why fixes couldn't be made more quickly by companies like Apple or Avid. For example, some things about FCP never "got fixed" through seven full versions, and will forever remain broken, despite me being very vocal about those problems in forums like this. I found that an enhancement like the one you're requesting, might break several other things, or might require a full rewrite of the code for that interface. There are also priorities based on user feedback. We, as editors, can't know about these difficulties, but should be aware of them. Creating software is complex and time consuming. To change an interface feature, like the multicamera monitor, might take more than a few versions to satisfy editors.
Oh boy. Don't I know about some of the things in FCP that never "got fixed" through 7 versions. That's why I was glad to switch to another NLE. There's a lot to like about FCPX. There's a lot to like about Premiere Pro. My fear, like Bill's and many others, is that by calling this a feature request and not a broken functionality will push it to the end of the priority line and we'll see CS6, CS7, CS8 and so on before we see it this "get fixed". I totally understand the hierarchy of programming. I do. And I know its not simple because everything is interconnected and you can't just say "make the pause button pause" or something simple like that. It goes much deeper and may, as you say require a full rewrite of the code for that interface. My brother works for Sony doing web coding and I know first hand that requests for "simple fixes" aren't always as simple as they appear. But your next sentence says it all: "There are also priorities based on user feedback" My goal in creating this new thread was not to make you aware of the issue because you (bing the staff of Adobe, not necessarily you personally) were aware of it in 2010. It was to make it a priority. That won't be done overnight. I know. But with every new post to the thread and every new user who wonders "WTF?!" when they sit down to do their first multicam edit, they'll know there's a clear thread that is alive and well that addresses this issue and maybe one day will move its way up the google search ladder until you can't miss the fact that its broken when you search for "Premiere Pro Multicam". Maybe then it'll get more user feedback because it'll get more hits and it'll be a bigger priority. It just so happens that this drives me nuts every day of the week as I edit full time 6 days a week. There are other actual true "FEATURES" that I wish CS6 would incorporate that either FCP7 or FCPX have, but those things are actual "features" that would simply ENHANCE the user experience...unlike this, which is something that without it the basic functionality of the workflow is crippled.
I'm glad there is an apparent workaround. But that still doesn't take away from the fact that its a broken feature and should be fixed. If multicam is a priority for the Premiere Pro team, then fixing a broken feature that is integral to is basic functionality should be a top priority. I get the feeling though that its not. So I'll keep checking in. I'm stubborn that way 
But its only for the greater good as I desperately want to stamp "RESOLVED" on the top of this thread and be able to whole heartedly recommend PPro to other users in forums/threads/etc. I can't however until its actually resolved. Like I said before I do appreciate your help. You've been great. I agree with Bill in pretty much everything his last post says. It would be a shame if a while from now we're saying the same things about Premiere that drove so many of us away from FCP7 in so far as their tendency to leave things broken for years and years and years.
It's all in the wording I guess.
Don't get frustrated by this fight. It's not important to you but to me and many others who deal with it on a daily basis we consider it a major problem. Premiere is a great program no doubt. But until this is fixed, I'll call it broken. You disagree about that wording and that's okay. It's harsh, yes, but its worded that way to catch people's attention and bring users from all over to this thread so that they too recognize this flaw and submit a request to have this fixed and we can all go about our merry way.
If there was a 3rd option beyond "feature" and "bug" to make this problematic issue a higher priority I would call it that. But sadly, there's not. It's just hard for me to wrap my head around putting this in the same category as other feature requests like "Audio Sync", etc. which would make the multicam workflow better. That is a legitimate feature. This flaw is not. We all agree that Premiere is a great program and I have no doubt they are constantly working to make it even better...but until this get's fixed, in my little world MULTICAM IS BROKEN...to me.
Sure I can make it work. In a round-about way. And yes, its doing what it was designed to do. But that doesn't take away from the fact that no one in their right mind would ever WANT it to work the way it's designed currently. Don't get frustrated. This will be a very POSITIVE post some day soon when this issue is fixed. That's my goal.
AdChoices