(Re-submitting this post. Not sure if the first one submitted successfully)...
I work at a TV station. We produce long form music and doc style programs. Our workflow involves video cut together by videographers on a workstation with Media Composer. The rough cut is then handed off to audio specialists who may incorporate post-multitrack mix downs of concerts and will also do cleaning and sweetening to the audio in the video cuts.
We have been using the AAF export from MC to Pro Tools to transfer the projects back and forth.
We've run into a problem with this work flow. The problem is that when a video editor uses the volume automation tools in a MC sequence--for example to cross-fade music tracks or dip-audio under when there is a voice over or something--those volume automation instructions are improperly translated by Pro Tools. We've found that PT is using a different resolution and curve when there is a fade down or up over time.
The problem was identified because we handed back a bounced stereo mix to a video editor and they said it was different than their original rough cut and the cross fades and audio dips were wrong.
To test the theory, we ran 400 Hz tone into MC at 16 bit 48 kHz at -20dBfs. In the MC sequence, I added a volume "rubber band" or automation envelope to attenuate the output of the track in steps at 5 second intervals. (I've attached a picture for a visual representation) The steps down were snapped to the "decibel lines" on the audio tracks in MC.
I exported a mix-down of the audio from MC using the project settings (16/48, stereo, *.wav) and brought both the rendered audio and an exported AAF with the project media into a PT project using matching settings (16/48).
We then bounced the audio from the AAF imported into the PT timeline and compared to bounced audio from MC to the bounced file from PT.
We confirmed that when the volume is attenuating down, Pro Tools is using a faster fade curve than MC is and is creating different results.
To further test this, I brought the same AAF into a different DAW (Nuendo) and did the same thing (exported a rendered file from Nuendo).
What surprised me is that Nuendo interpreted the MC volume rides correctly (or at least the same as MC did). Pro Tools was different. Nuendo was not.
This is a huge problem for us, and it doesn't seem like we're asking the software to do something obscure or out of the ordinary. It's voice-overs with audio dips and cross fades.
We're using the latest update of Pro Tools 11 (not HD) on a Mac Pro tower (6-Core Intel Xeon, OS X 10.9.5). We ran the same test on a different install of Pro Tools on a Mac Book Pro and had the same results.
The Media Composer software is version 7 installed on AVID blessed computers.
Anyone have any ideas if we're doing something wrong or if there is a bug/problem with the software here?
Many thanks.
I work at a TV station. We produce long form music and doc style programs. Our workflow involves video cut together by videographers on a workstation with Media Composer. The rough cut is then handed off to audio specialists who may incorporate post-multitrack mix downs of concerts and will also do cleaning and sweetening to the audio in the video cuts.
We have been using the AAF export from MC to Pro Tools to transfer the projects back and forth.
We've run into a problem with this work flow. The problem is that when a video editor uses the volume automation tools in a MC sequence--for example to cross-fade music tracks or dip-audio under when there is a voice over or something--those volume automation instructions are improperly translated by Pro Tools. We've found that PT is using a different resolution and curve when there is a fade down or up over time.
The problem was identified because we handed back a bounced stereo mix to a video editor and they said it was different than their original rough cut and the cross fades and audio dips were wrong.
To test the theory, we ran 400 Hz tone into MC at 16 bit 48 kHz at -20dBfs. In the MC sequence, I added a volume "rubber band" or automation envelope to attenuate the output of the track in steps at 5 second intervals. (I've attached a picture for a visual representation) The steps down were snapped to the "decibel lines" on the audio tracks in MC.
I exported a mix-down of the audio from MC using the project settings (16/48, stereo, *.wav) and brought both the rendered audio and an exported AAF with the project media into a PT project using matching settings (16/48).
We then bounced the audio from the AAF imported into the PT timeline and compared to bounced audio from MC to the bounced file from PT.
We confirmed that when the volume is attenuating down, Pro Tools is using a faster fade curve than MC is and is creating different results.
To further test this, I brought the same AAF into a different DAW (Nuendo) and did the same thing (exported a rendered file from Nuendo).
What surprised me is that Nuendo interpreted the MC volume rides correctly (or at least the same as MC did). Pro Tools was different. Nuendo was not.
This is a huge problem for us, and it doesn't seem like we're asking the software to do something obscure or out of the ordinary. It's voice-overs with audio dips and cross fades.
We're using the latest update of Pro Tools 11 (not HD) on a Mac Pro tower (6-Core Intel Xeon, OS X 10.9.5). We ran the same test on a different install of Pro Tools on a Mac Book Pro and had the same results.
The Media Composer software is version 7 installed on AVID blessed computers.
Anyone have any ideas if we're doing something wrong or if there is a bug/problem with the software here?
Many thanks.
Aucun commentaire:
Enregistrer un commentaire