Blackmagic Forum

I am using the sync bin extensively with multiple camera angles which have the audio swamped by engine noise, and a camera with a clean audio track.

The process would be wonderful except for the fact that I can't isolate the good audio or control it's mix using the sync bin. My goal is to edit in the different camera angles based on the audio, but cannot hear over all the engine noise.

My current workaround is to duplicate all the noisy clips dropping the audio, however I still need the full audio versions for other reasons. This means hundreds of gigabytes of duplication for each project.

Is there a way to mute or solo clips when editing in the cut page with the sync bin that I am not aware of?

If not, how do I submit a feature request - this seems like a pretty valuable addition.

You might be better off working with Multicam on the Edit page.

Jim Simon wrote:You might be better off working with Multicam on the Edit page.

Yes - I know that's the alternative, but really hoping to avoid it. Sync-Bin is such a game changer and speeds up the flow (once I duplicate the clips without audio) massively. It is so much better than a multicam time line.

Such a pity it lacks one simple control.

I'm keen to know how to submit a feature request if anyone knows.

For anyone else who might stumble across this looking for a solution, I have come up with a workaround through a mix of experimentation and accidental good luck.

Unfortunately it's not as good as a solo or mute control built into the sync bin, but it gets the job done without duplicating media with silent copies, which wastes storage needlessly, and takes extra processing time to generate.

Before creating the sync settings, select the clip(s) in the bin you are syncing that you want to silence, and right click to select "Clip Attributes". Under the Audio section mute the embedded channels.

Clip Attributes are associated with the clip, not the media, so you can create clips from the same media in other bins and not mute the audio channels.

I still hope Blackmagic fix this obvious oversight, but this is much better than my first work around.