Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Forums Avid Media Composer “Name” column shows TapeID when importing audio

  • “Name” column shows TapeID when importing audio

     Sean Lewis updated 1 week, 3 days ago 5 Members · 15 Posts
  • Sean Lewis

    January 6, 2021 at 9:45 pm

    Hey there,

    Hoping someone can shed some light on this strange issue.

    I’m using MC 2020.10.0, assistant editing on a scripted show. When I import the location audio files (.wav), usually the info in the Name column should take the sound recordist’s metadata of scene-shot/take. Eg:


    But I’m just getting the tape ID (same as file name). Eg:


    I did a test today and used the editor’s computer to import. He has MC 2018, and the file came in with 2-45/1 in the name column.

    So does anybody know if there’s a setting in 2020 that might be causing this? The closest thing to the slate that I’m getting is written in the Scene column, but it doesn’t include the take number, so it just says “2-45”.

    Any help would be really appreciated.


  • Pat Horridge

    January 6, 2021 at 10:03 pm

    What do you get if you AMA link instead of import? (you can the transcode if you need it to be Avid media)

  • Sean Lewis

    January 6, 2021 at 10:39 pm

    Woah. AMA linking fixes it! Thanks Pat!!!!

    Any idea why, and if I can get it to simply import that way?

  • Robert Ober

    January 7, 2021 at 2:05 pm

    Import is mostly deprecated. The emphasis now is on linking and editing with linked files or linking and transcoding or rewrapping.

  • Sean Lewis

    January 7, 2021 at 9:31 pm

    I found that the AMA linking helped, but there were some setbacks too.

    I’m in a film project (for perf-slip abilities). After transcoding the AMA audio, and creating subclips, these couldn’t be perf-slipped.

    So in the end I have to import as usual, PLUS AMA link, and copy-paste the names from the linked clips onto the imported clips.

    Very odd. Importing audio used to be fine…?

  • Robert Ober

    January 8, 2021 at 4:29 pm

    BTW, I agree that any importing that previously worked should still work and if it doesn’t that’s a bug.

    You said, “After transcoding the AMA audio, and creating subclips, these couldn’t be perf-slipped.”, I’m thinking that is not by design. What was the original clip codec and wrapper and to which codec/wrapper did you transcode?



  • Glenn Sakatch

    January 9, 2021 at 4:27 pm

    you can perf slip linked audio in the source files settings page. Don’t need to be in a film project anymore.

  • Job ter Burg

    January 9, 2021 at 5:54 pm

    Slipping Audio in Source Settings is not Perf Slip and I don’t think it translates to Pro Tools etc.

    Traditional import should still append metadata, but if the recorder in questions doesn’t write this basic data into the Bext section of the WAV metadata, it will likely not be seen by traditional import. The iXML section of the medata is not seen by traditional import, and it is seen by AMA, AFAIK.

    But I don’t think there should be a difference between 2018.x and 2020.x in any of this.

    You mention being on 2020.10, have you been able to try it on 2020.12?

    Oh, one more thing, on 2020.10, under the Audio Import settings, I see a tick box that says “Use Broadcast Wave Scene and Take for Clip Names”. Seems that it a setting you should double check. If that setting does not show, you are likely using older user settings on a newer version of MC. Rebuild your settings (or at the very least create fresh Import settings).

  • Robert Ober

    January 9, 2021 at 8:04 pm

    Hey Job,

    Isn’t it also true that some metadata will not translate to some codecs or did I dream that?



  • Job ter Burg

    January 9, 2021 at 9:02 pm

    Since we’re talking production sound, this would normally be relatively plain WAVE (BWAV) files, there is no codec. It’s uncompressed PCM in a WAV container with metadata (the BWAV part of the equation).

    Also, if a source file has metadata that Avid can read, there is no reason the codec itself has an influence. Plus Avid can track metadata at the bin/clip level, and that would not need to care about the codec the media is in. So I can’t think of any reason or example, to be honest.

Viewing 1 - 10 of 15 posts

Log in to reply.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy