Thanks for the contacting adobe forums,
Please check this link, it will help you a lot :
yes i've seen that, and if you look at the comments in response to that page, there's a lot about the very problems i'm talking about in number 1 above. is there a solution to this?
in addition, that link doesn't address number 3 above in any way, so if you're going to respond, please respond in a manner that addresses the issues and not just take the easy route of providing a general link.
1. You don't cut in the Source Monitor, you cut in the sequence using the Multicam view of the Program Monitor.
2. You can't. What I do is just replace the audio track after cutting, then mix in the original sequence.
3. Not sure what's going on here.
thanks Jon. re: 3 - it seems Premiere has problems when a sequence contains multicamera and non-multicamera material? If I'm in multicam view of the program monitor it doesn't show anything which isn't multicam, so if i've got a bit of an interview clip, for example, that pops in during some multicam footage, then it doesn't show up! seems like there might be a few deficiencies in Premiere's multicamera implementation, but perhaps I just need to get my head around workarounds!
That behavior is normal and expected.
that's neither normal nor expected behavior for me! the multicam view should be smart enough to show you what's going on in your sequence, not go black when it hits material that doesn't classify as multicamera! that's just not helpful.
The purpose of multicam view is to cut between angles, so it makes sense that it only shows you available angles. Once cut, you can edit normally in the Composite view.
yes but maybe i've got a sequence where the multicam material cuts to an interview and back again and I want to see how it all flows, for example. I currently need to cut the multicam material, switch to composite mode, play, and switch back to multicam to refine if I need to. that's too may steps, IMHO.
and why would it need to display BLACK when it hits non-multicam material? that's simply not useful in any sense of the word!
anyway, i'll bring this up in the features/bug section;