Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Avid Media Composer That AMA Consolidate/Transcode thing again – Problems with KiPro ProRes 422 files

  • That AMA Consolidate/Transcode thing again – Problems with KiPro ProRes 422 files

    Posted by James Sapione on December 4, 2014 at 6:47 pm

    Oh boy here we go again. I’ve read countless posts on different sites about the AMA workflow and I’m still somewhat confused. Here is my issues (and thanks to anyone for reading this)

    MacBook Pro 2.6ghz i7, 8gig ram
    Mac OS 10.8.5
    Avid MC 7.0.0

    Currently I’m trying to cut, (as fast as possible), a show that has a Linecut and 4 ISO’s. All ISO’s and the Linecut were recorded using AJA KiPro – set to ProRes422
    I can AMA to the footage no problem. I see it, it plays fine via AMA. Now i need to cover the mistakes made in the Linecut. I thought the best method to begin with would be to CONSOLIDATE the footage first, (which puts it into a MXF wrapper which should make the edit more stable). This should make the edit faster. The first problem i encounter – Error message –
    Some of the items selected for Consolidate contained foreign compression types, which could not be consolidated.
    See the console for details.
    To Consolidate these clips, please transcode them to a native compression type first

    OK – any thoughts why? I thought ProRes was native to Avid? (And this is just regular ProRes422 – Not LT or HQ)
    So I’m at a blank here. Some setting I’m missing?

    2) Ok, so i have to crank this edit out regardless of the issue above. (time sensitive stuff) So I’ve now decided to Transcode. Here’s my question with TRANSCODING.
    – The original footage is all captured as ProRes422, 1080i, 29.97. When i open the dialog box to transcode – I have many options….like AVCIntra, DNxHD 145, 220, ProRes LT, HQ,etc, etc, etc. If the footage is ProRes to begin with – Shouldn’t I keep it as ProRes? If thats the case – why do i have to transcode?
    To pharse it another way – assuming all your footage is the same codec/frame rate…… Should you keep it as that codec or should you always go to DNxHD because despite what Avid claims – Avid only works by Transcoding to DNxHD???? I mean – that seems to be the constant story here and other forums. All this talk about Avid being able to handle anything is really….at its core —- a bunch bull! I’d like to be wrong on this but from my own experience and what i read doesn’t appear that way.

    If your end result is to bring it into compression software, like Sorenson, where you would compress the hell out of it – does it matter what codec you convert too? My line cut is over 2hours long and I thought this would be alot faster…… now im screwed.

    Please, anyone have any insights? Should i finally give up on Avid? This “should i stay or should I go” debate has raged with Avid editors for a LONG LONG TIME….. nothing changes it seems. I need the fastest workflow possible

    John Pale replied 10 years, 1 month ago 3 Members · 2 Replies
  • 2 Replies
  • Michael Hancock

    December 4, 2014 at 6:53 pm

    If the audio and video are part of the same file, subclip the video and try to consolidate that.

    Otherwise, if you’re getting adequate performance via AMA, just leave it as AMA. This doesn’t sound like a complicated edit so you’ll probably be fine.

    If you’re going to transcode, either set it to transcode to ProRes and have it run in the background so you can keep working while it chugs away. Then once the edit is done, do a little more testing to try to figure out what’s wrong with the ProRes files off the KiPro. I’ve never used one so I don’t know why it’s not working.

    —————-
    Michael Hancock
    Editor

  • John Pale

    December 4, 2014 at 7:48 pm

    I’ve seen that too. I think its sort of a bogus error message, as I have even gotten it with DNX recorded footage. There’s probably a bad frame in there somewhere…might even be the first frame, or cutting out of color bars (if present). If you can subclip it into smaller chunks and consolidate those, it might help.

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