Editing Multiple Multicam Layers

I am curious if anyone has worked with multiple multicam layers?

I am editing game footage from an event and it contains 1 POV multicam and 1 PiP multicam.

I have the PiP layered on top of the POV multicam. I can edit and select the multicam on the top layer (the PiP layer), but when I try to edit the layer below it (the POV) I don't get the multicam option for quick razor editing in the viewport.

I have tried hiding the video track with the upper PiP layer, double clicking... pretty much everything intuitive one could think to do. Is there some specific method for getting access to the editing window of multilayered multicam clips?

Try de-activating the auto select button in the track header (<>) of the upper layer. Not sitting in front of Resolve right now. 100% certain there is a way, 90% sure that’s what it is.


Sent from my iPad using Tapatalk

Try de-activating the auto select button in the track header (<>) of the upper layer. Not sitting in front of Resolve right now. 100% certain there is a way, 90% sure that’s what it is.


Sent from my iPad using Tapatalk

Thanks for the suggestion. This does not work. As you can see from the image, as soon as I select Multicam in the dropdown, it switches back to the top layer rather than the one I had selected.

Screenshot_1.jpg (151.06 KiB) Viewed 330 times

I am curious if anyone has worked with multiple multicam layers?

I am editing game footage from an event and it contains 1 POV multicam and 1 PiP multicam.

I have the PiP layered on top of the POV multicam. I can edit and select the multicam on the top layer (the PiP layer), but when I try to edit the layer below it (the POV) I don't get the multicam option for quick razor editing in the viewport.

I have tried hiding the video track with the upper PiP layer, double clicking... pretty much everything intuitive one could think to do. Is there some specific method for getting access to the editing window of multilayered multicam clips?

I emailed support and they did inform me that this is a bug and they've reported it.