I am starting this thread to try to get some attention paid to this issue again - after fighting along with several other people to try and get this issue resolved. What issue could be so important, yet so ignored on the part of Adobe? It is simply this:
THE MULTICAM FUNCTIONALITY IS FLAWED, AND PRESSING THE SPACEBAR DURING A MULTICAM EDIT CAUSES AN UNINTENDED EDIT BACK TO THE FIRST CAMERA SOURCE SELECTED WHEN THE PROJECT STARTS TO PLAY.
Nowhere in the civilized world would any editor want to create an edit when stopping playback - yet in Multicam mode with Premiere that's exactly what it does when you stop. Adobe has claimed over and over that this is just a design quirk, and not a flaw. How they justify this is anyone's guess. I'm here to stand up and say that they are being unreasonable, unfair, and absolutely unacceptable in their judgement on this issue. This IS a flaw, plain and simple, and it has kept me (and is still keeping me) from doing the most important work I have to do in Premiere as opposed to FCP or Media Composer.
They also came out and said that there is a "workaround" to this "quirk" by pressing the "0" key before you stop playback. THIS WORKAROUND DOES NOT WORK ON A MAC, AND THEREFORE DOES NOT WORK, AND IS NOT AN ACCEPTABLE ANSWER.
After two years of people complaining about this issue it is both INFURIATING AND UNACCEPTABLE that Adobe pushes this issue off while other issues which would seemingly be much less important are dealt with via updates.
I CANNOT DO MY WORK WITH THIS ISSUE STILL HAPPENING!! Multicam editing is too important, and this problem slows me down to the point where it is absolutely unusable for me.
Kevin Monihan, a forum moderator went around and around with users on this issue in another thread that has since been LOCKED without resolution. (http://forums.adobe.com/thread/1069438?start=40&tstart=0)
Locking a thread will not cause your issue (or all of the users who cannot accept this explanation from Adobe) TO GO AWAY. It is NOT a design "quirk" if your "workaround" does not behave the same in Windows as it does on a Mac - and further, it's not a quirk, it's a mistake. Compare it to any and every other editor out there, and it is WRONG BEHAVIOR. Don't tell us it's the way it is supposed to behave - we aren't stupid, and it's an insult to me and all the other professional editors out there who agree and have brought this issue up in this forum!!
Yes, I am angry.
ADOBE - FIX THIS ISSUE ONCE AND FOR ALL. NOW.