Craig Melville

Resolve imports multitrack field audio via XMLs and AAFs incorrectly. Sets timeline audio clips 'source channel' to 'mute' rather than the correct channel.

Recommended Posts


I've come across this issue many times coming when exporting  and edit from Premiere via XML or AAF to Resolve 15-16 and 17.  

Audio clips from the field audio recorder come in correctly placed in the timeline - but the audio clips 'source channel' defaults to 'mute'.

I can manually fix each clip by individually setting the clips 'source channel' using 'clip attributes'. But it's a pain and it's not a workable solution on a complex job. You can apply those changes to multiple clips at a time, however on a timeline that has hundreds of carefully placed and manipulated audio clips, it's a time consuming process and prone to causing errors.  

Interestingly, if I go to the audio file in the media pool and view its attributes there (rather than via the clip attributes in the timeline), the channels are mapped correctly and not muted. So the source clips play as you'd expect in the media pool.  It's only the instances in the timeline that get imported with muted audio channel settings. I'm assuming the issues is the XML can't handle the multitrack audio clip and can't pass the channel patching information through. Which does seem weird - because on each timeline clip, I can see the label of the channel appended to the clips file name.  i.e. in the timeline I'll see the filename plus the "boom" or "Lav 1" appended. That's metadata coming through - not a file or clip name. So the clip is indicating what track it's supposed to be but the system is just not patching it correctly.   

Is there some way to solve this? 

This issue appears when I'm using multichannel field audio files from Sound Devices recorders. Music tracks and other audio comes in fine. 

One other note: If I open the Premier XML in FCPX, the audio clips are not muted - but they are also not correct either.  FCPX basically switches on all of the multitrack clips. So that's not ideal either.   

My guess here is these multichannel field audio grouped tracks are causing the issue. 

Surely for Resolve and Fairlight to be a viable solution to finishing audio there must be a way to do this in an automated way.  Or should I prepare the audio files in a different way.  

AAF from Premiere can be read by ProTools and other apps without these issues - so I assume it must be possible to translate the information.  

Thanks for any thoughts to solve this. Or ideas on how to better set this up in future.


Screen Shot 2021-02-02 at 12.50.44 AM.png

Screen Shot 2021-02-02 at 2.25.14 AM.png

Edited by Craig Melville
clarifying the information.
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.