Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Alexa Footage – Media Manager Error 34

  • Alexa Footage – Media Manager Error 34

    Posted by Eddie Kesler on January 25, 2011 at 8:40 pm

    I have a large commercial project I’m working on in FCP that was shot on a new Arri Alexa. We’re utilizing the ProRes422 HQ output from the camera with merged WAV audio (there were many sync issues!). We’re color correcting on a new Mac based DaVinci Resolve. We’ve already CC’d two of the 5 spots on it, but in preparing the select files for the next session, I wanted to use Media Manager to pull only the clips needed in the sequences with 2 second handles. For the first two, I gave the colorist the whole clip of each scene. There weren’t as many scenes, but its a lot of GB to juggle. Everything was fine on the DaVinci at least.

    This time, I set Media Manager to Copy the sequence clips to a new folder with handles and for some reason, it’s only copying and flattening the selects from the only two clips that aren’t ProRes HQ. They are just standard ProRes and were shot on a Phantom camera. Final Cut is giving me an error #34 on all the others and asking if I want to retry, continue or abort. It put files in the folder, but they look as if they aren’t flattened and doesn’t know what app to open them in. I can open them in QT and they play, but I’m not sure why it’s telling me it’s “failed” with this error and why it won’t flatten the file.

    Any ideas?

    Thanks,
    Eddie

    https://www.jamedit.com

    Christopher Travis replied 13 years, 11 months ago 9 Members · 28 Replies
  • 28 Replies
  • Jeremy Garchow

    January 26, 2011 at 12:16 am

    First, no Alexa experience, just trying to help.

    [Eddie Kesler] ” It put files in the folder, but they look as if they aren’t flattened and doesn’t know what app to open them in. I can open them in QT and they play, but I’m not sure why it’s telling me it’s “failed” with this error and why it won’t flatten the file.”

    Sorry, can you explain this?

    Also, did you use the Alexa XMLs when you originally imported?

  • John Heagy

    January 26, 2011 at 12:23 am
  • Jeremy Garchow

    January 26, 2011 at 12:32 am

    Can you just run them through Cinema Tools instead of recompressing? (simply conform to the same frame rate). Might do enough to shake up the index, if that’s the problem.

    Also, there’s this, but might not be applicable:

    https://www.spherico.com/filmtools/

    And finally ProRes 4×4 doesn’t play on kipros no matter what the source.

    Jeremy

  • Richard Sanchez

    January 26, 2011 at 1:14 am

    I think error 34 is hard drive full. How much space do you have on the drive where you’re copying the footage?

    Richard Sanchez
    North Hollywood, CA

    “We are the facilitators of our own creative evolution.” – Bill Hicks

  • John Heagy

    January 26, 2011 at 3:14 pm

    [Jeremy Garchow] “And finally ProRes 4×4 doesn’t play on kipros no matter what the source.”

    Correct… These were ProRes(HQ) directly from an Alexa and would not play on a KiPro unless exported from a FCP timeline or via a QT Save As…

    The Media Manager and KiPro issue point to a QT wrapper/media disconnect. I know for a fact the KiPro ignores the wrapper and looks at the media track. Try trimming a movie in QT and see if the KiPro respects it… it won’t.

    John Heagy

  • Jeremy Garchow

    January 26, 2011 at 3:35 pm

    [John Heagy] “Correct… These were ProRes(HQ) directly from an Alexa and would not play on a KiPro unless exported from a FCP timeline or via a QT Save As…”

    Did you try a quick conform in CT?

    [John Heagy] “Try trimming a movie in QT and see if the KiPro respects it… it won’t. “

    Meaning without resaving as a self contained?

    Just curious as all as Alexa could be coming our way soon.

  • John Heagy

    January 26, 2011 at 6:00 pm

    [Jeremy Garchow] “Did you try a quick conform in CT?”

    The Conform button is grayed out when opening original Alexa QTs. We also captured footage direct to a KiPro (needed audio) and conform is active for those. Definitely someth’n up with Alexa QTs.

    Modifying Camera Original files is something we would never consider anyway… even names. We would need to copy them first, in which case I’d just use CatDV to batch export as self contained and fix them that way.

    [Jeremy Garchow] “Meaning without resaving as a self contained?”

    Yes trim then Save, modifying the original file.

  • Jeremy Garchow

    January 26, 2011 at 6:03 pm

    [John Heagy] “The Conform button is grayed out when opening original Alexa QTs. We also captured footage direct to a KiPro (needed audio) and conform is active for those. Definitely someth’n up with Alexa QTs.”

    Hmm. Wonder what the TypeCode is?

    [John Heagy] “Yes trim then Save, modifying the original file.”

    What if you mark in and out on the orig, copy, make a new container, paste and save as self contained?

  • John Heagy

    January 26, 2011 at 7:06 pm

    [Jeremy Garchow] “Hmm. Wonder what the TypeCode is?”

    No MacType, should be MooV, and no CreaterType, FCP is KeyG and QT is TVOD

    [Jeremy Garchow] “What if you mark in and out on the orig, copy, make a new container, paste and save as self contained?”

    That should work.

  • Jeremy Garchow

    January 26, 2011 at 8:17 pm

    [John Heagy] “No MacType, should be MooV, and no CreaterType, FCP is KeyG and QT is TVOD “

    Might have something to do with OPs media management problem.

Page 1 of 3

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