Hi Job:
I tried using AMA to bring in BWAV files for 2 reasons:
1. I've never seen anything in Avid documentation to suggest this
workflow is unsupported. I see nothing in the Symphony help files, for
instance, and Avid's document "Avid Editing Systems - Supported Formats"
makes no reference to audio formats at all. Avid will link to BWAVs
(and other audio formats) via AMA without complaint -- so why should I
have anticipated a problem?
2. What the Symphony v.6 docs do state is this:
"You should not mix workflows. Either use the AMA method or use
the traditional import/batch import method."
This implies that it's a bad idea to use AMA to bring in video clips
while using traditional import for audio. This is why I tried using AMA
for my audio initially (and quickly gave up on the idea when I saw the
timecode did not come in properly for BWAVs via AMA.)
You may not think this is a bug, but perhaps you would agree the docs
are obscure, if not outright misleading. If this workflow is
unsupported, as it appears to be, then don't you think that should be
made obvious? I'd like to see a warning dialogue when using AMA to link
to unsupported formats.
When I was searching for an answer to why I was getting these
CM_INVALID_TRIM errors and quarantined audio files I found others asking
about the same problem, but no answers for why it might be happening,
which is why I've posted my results at some length.
In that vein, it might be worth noting that this error is not
limited to .wav files -- I had the same problem with .mp3 files which
were AMA'd and transcoded in a project with 'film options' enabled.
Regards,
--Michael
On 13-02-09 1:03 PM, Job ter Burg (L2B) wrote:
>
>
> Michael,
>
> The most important question here is: why are you using AMA to bring in
> BWAV files? AMA was never designed to support this workflow, and by
> using it, you are risking all kinds of issues - depending on the
> project format and sample rate.
>
> BWF/BWAV/WAV is supported through File->Import, and that is the way
> you should go about this. Using AMA will - IIRC - essentially rely on
> whatever the AMA QT plugin passes on to MC. That's not a reliable
> source for this type of file at all.
>
> File->Import has some specific properties that allow for proper BEXT
> chunk metadata extraction as well as proper sample rate handling
> (including pullup/pulldown rates).
>
> Import is the ONLY supported way to bring in BWAV files.
>
> Job
>
> On 9 feb. 2013, at 21:34, Michael Brockington brocking@sfu.ca
> > wrote:
>
> >
> > - import .wav files via AMA, and consolidate them to an empty MXF/1
> folder
> >
>
>
[Non-text portions of this message have been removed]
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (25) |
No comments:
Post a Comment