Latest post Sat, Dec 9 2017 12:07 AM by rdmartin. 21 replies.
Page 1 of 2 (22 items) 1 2 Next >
Sort Posts: Previous Next
  • Mon, Nov 27 2017 4:39 AM

    • rdmartin
    • Not Ranked
    • Joined on Fri, Jan 4 2013
    • Posts 32
    • Points 460

    All import methods Failing

    This is so absurd. I cannot import any type of media at all. It never used to be this convoluted.

    I'm running MC 8.9.3

     

    1) Every single time I try to import a Quicktime 1080p proress4444 file the entire application will crash when the upload bar gets to 100%

    Why the heck am I unable to import a QuickTime as an MXF... I have no idea as to how to solve it since MC comes with the quicktime ama plug-in so what should I do?

     

    2) Well, I decided fine, I'll convert those CinemaDNG's into MXF files instead and just drag and drop. Nope. Even worse problems with these MXF OP1A 10bit files out of Resolve. 

    Going into source window: dragging and dropping creates an error. when clicking link, it creates a different error, when I even try to import the MXF as an MXF it creates an error.

    See the screenshots.

     

     

    3) so then I figure I move all those MFX fiies into the Avid Mediafiles folder-->folder 1.

    I get an even stranger error. Come on.....

     

     

  • Mon, Nov 27 2017 5:41 AM In reply to

    Re: All import methods Failing

    I would rename your 1 folder to 10 and make a new 1 folder.

    Go to Resolve and Select the original files and go to the Deliver page.
    Choose the Export to Avid Template and choose the desired resolution.
    Set the destination folder to ther new 1 folder  (Drivename\Avid MediaFiles\MXF\1)
    Process.

    Open MC and watch MC update the 1 folders database.  Open the project
    Go to the desktop and open Drivename\Avid MediaFiles\MXF\1.
    Find the Resolve created AAF and drag it into a bin in the project.

    The bin should then populate with all the clips.

    FWIW this method makes it easy to export an AAF of the edited timeline back to the Resolve Project.   You can then grade using the original clips.      Test with a few clips. When you know it works it would allow you to use a lower Resolution output from Resolve in the first export and effectively do an offline in MC knowing you can link to the original clips back in Resolve for your online.

  • Mon, Nov 27 2017 7:20 PM In reply to

    • Marianna
    • Top 10 Contributor
    • Joined on Thu, Oct 13 2005
    • Avid
    • Posts 11,565
    • Points 255,455
    • Avid Beta Moderators
      Avid Customer Advocate
      Avid Developer Moderator
      BlogAuthor
      SystemAdministrator

    Re: All import methods Failing

    Andrew is spot on.....

    Report back as if this doesnt work I will get support on it.

    Marianna

    Director of CSM | Customer Advocate [view my complete system specs]
  • Mon, Nov 27 2017 10:08 PM In reply to

    • rdmartin
    • Not Ranked
    • Joined on Fri, Jan 4 2013
    • Posts 32
    • Points 460

    Re: All import methods Failing

    step 1) remame folder 1 to 10

    step 2) create new folder 1

    What problem will this solve? not being able to import Quicktimes to an MC bin or not being able to Link or drag and drop MXF files? Because I need to resolve both problems.

     

    Export to Avid Template results in which file types? MFX files and an associated MFX?

    "Use a lower Resolution output from Resolve in the first export and effectively do an offline in MC knowing you can link to the original clips back in Resolve for your online."

    --- I do not want to do a round trip at all and would like to avoid AAF's. I shot in a baked in color profile  on purpose and have already done the slight adjustments to those CinemaDNG's in Resolve. I just want to export those clips from resolve -->import those into MC for editing--> do final exports directly out of MC from the timeline sequence.

     

    Thanks guys!

  • Mon, Nov 27 2017 10:54 PM In reply to

    Re: All import methods Failing

    rdmartin:
    step 1) remame folder 1 to 10
    step 2) create new folder 1
    What problem will this solve?
    It does not solve anything.   It does give you a valid media folder that will  isolates just the clips you are currently working with. Could make it easier to trace issues and find the .aaf file.  If you do not want to use the AAF (Resolve creates it automatically with its to Avid deliver template) it would also allow you to drag the Avid database file from the 1 folder into a bin and just see the media files Resolve created.  

    rdmartin:
    Export to Avid Template results in which file types? MFX files and an associated MFX?
    Valid Avid MXF files.  These files cannot be imported into MC. They need to be placed into a valid, number only named folder inside an Avid MediaFiles/MXF/ folder.  From there you need a method to open the media in a bin.  2 options. drag the AAF to a bin as suggected or drag the msmMMOB.mdb from the media folder into a bin.  Both achieve the same result.

    rdmartin:
    "Use a lower Resolution output from Resolve in the first export and effectively do an offline in MC knowing you can link to the original clips back in Resolve for your online."
    It is not necessary and was only added as a FWIW so you had it as an option if you wanted it.    You posted  you were working with 444 media so offlining might have been a good option.

    rdmartin:
    I do not want to do a round trip at all and would like to avoid AAF's.
    As mentioned above Resolve creates the AAF automatically when using the Avid delivery template.

    rdmartin:
    I shot in a baked in color profile  on purpose and have already done the slight adjustments to those CinemaDNG's in Resolve.
    For future information exporting an AAF of your edited timeline back into the original Resolve Project allows Resolve to use the original clips WITH the adjustments you made for the initial delivery.

  • Tue, Nov 28 2017 12:40 AM In reply to

    • rdmartin
    • Not Ranked
    • Joined on Fri, Jan 4 2013
    • Posts 32
    • Points 460

    Re: All import methods Failing

    Great I'm going to try this test.

    Though for clarification beforehand: So because I just decided to choose OP1A MXF's as the output as well as not selecting the file destination to folder 1 (or creating say a folder 2 directly from Resolve) it invalidated my MXFs from being able to be imported into a MC project?

    If so, I have no other choice then to redo the export of all these clips out of Resolve all over again?

     

    Also, when creating a new folder 1, after changing folder 1 to 10, will I have to create a new msmMMOB.mdb or msmFMID.pmr files or will simply these be created/generated automatically when I open up a new project and load that new folder 1 via the source monitor?

     

    Thank you guys!

     

  • Tue, Nov 28 2017 1:42 AM In reply to

    Re: All import methods Failing

    rdmartin:
    it invalidated my MXFs from being able to be imported into a MC project?
    Avid does not allow you to IMPORT those MXF files.  Avid needs them to be in a number named folder inside a Avid MediaFiles\MXF\ folder. 

    You can move them from their current location to Avid MediaFiles\MXF\(any number only named) folder)

    rdmartin:
    will I have to create a new msmMMOB.mdb or msmFMID.pmr files
    NO 

    rdmartin:
    will simply these be created/generated automatically
    YES as long as it is a number only named folder   (1, 2, 3, .............100,001, 100002..... etc) inside the Avid MediaFiles\MXF\ folder.

    rdmartin:
    when I open up a new project and load that new folder 1 via the source monitor?
    Not exactly.    MC creates (and or updates)  these databases everytime it opens.     To get your MXF type files to show in any project you need to open the required project. Open a new bin.   Drag either the msmMMOB.mdb or the Resolve created AAF from the Number named folder into the bin.  Avid will then automatically load the clips into that bin.

    BE AWARE that if you have other files already in that number named folder (previous imports etc) these will also show in this bin if you use the msmMMOB.mdb.      The reason for my suggesting you make a new 1 folder in my earlier post.

    Good Luck.

  • Tue, Nov 28 2017 4:15 AM In reply to

    • rdmartin
    • Not Ranked
    • Joined on Fri, Jan 4 2013
    • Posts 32
    • Points 460

    Re: All import methods Failing

    Yeah it's no good.

    I renamed folder 1 to folder 10

    created a new folder 1

    and then moved those MXF files into the new folder 1.

    Created a new project on the root of the external drive and immediately got this error from the source media folder

     

    Then when I kept hitting ignore all it kept popping back up until this error message....

     

     

    So I clicked ignore all on this critical error screen and then try to "abort" on the initial error prompt instead and I get this message.

     

    so then i'm basically stuck and I needed to force quit.

     

    So the drag and drop of those MXFs into a new folder 1 didn't work since now I cannot even do anything in a new project to begin with.

     

    By the way, is there something wrong with the external drive and it's read/write permissions? Within the Avid MediaFiles/MXF folder I was prompted to enter my system user password for even rename the folder 1 to 10 and also had to enter one to add the new folder 1..... is that usual?

     

    Thoughts? This is now potentially a third problem because editors moving MFX files around from folder to folders is pretty common but even this is messed up.

  • Tue, Nov 28 2017 5:00 AM In reply to

    Re: All import methods Failing

    rdmartin:
    and then moved those MXF files into the new folder 1.
    If you look in the 1 folder are the 2 Avid Database Files there?

    The error message 1 indicates that the files you moved into the 1 folder are not valid Avid MXF files (according to MC). 

    I have seen some posts that there have been issues with Avid MXF's from some versions of Resolve and maybe only if they were using 444 colour space.  I thought I had seen that the most recent versions of Resolve had fixed this but not 100% sure. So a few questions
    Are these from your initial Resolve export (deliver)
    Did you use the Avid AAF deliver template
    What resolution and colour space are they?
    Which version of Resolve are you using?

    Error message 2 confirms that the files are there but not valid MXF's so MC wont see them.

    Error Message 3 shows that the Source Browser cannot handle them. This is to be expected as MC's Source browser cannot Import or Link to that type of file.

    Sorry it is the end of my day and I will not be online in the Forums for the next 12 hours.

  • Tue, Nov 28 2017 5:16 AM In reply to

    • rdmartin
    • Not Ranked
    • Joined on Fri, Jan 4 2013
    • Posts 32
    • Points 460

    Re: All import methods Failing

    it appears that creating that new project starting fresh from a newly created folder 1 with the MXF files dropped into it only generated a msmFMID.pmr

    I am using Davinci Resolve 14.1.1

    Both quicktimes and the MXFs are from my initial Resolve deliver (two seperate renders).

    I did not use the Avid AAF template.

    I created my quicktimes (HD prores4444) from the Custom menu output...

    Then I just figured I stick with Custom: format: MXF OP1A: DNxHD 10bit

    Perhaps I should have been using the Avid Template instead... but that still doesn't solve the issue with not being able to import quicktime files. 

     

  • Tue, Nov 28 2017 8:34 PM In reply to

    Re: All import methods Failing

    I have Resolve 14.1.1 and MC 8.9.3 here so do you have 1 or 2 small original footage clips (One of your early posts here showed at least a couple of files at around 500MB) that I could download and run some tests with here? If so email mail me a download address (andrewatactiontvnz.com)

  • Tue, Nov 28 2017 10:57 PM In reply to

    • catalino
    • Not Ranked
    • Joined on Tue, Nov 28 2017
    • Posts 1
    • Points 5

    Re: All import methods Failing

    Hi there,

     

    I tested 3 working ways of what your are trying to do so here is the right way to avoid error messages and to give avid what it needs to work properly.

     

    Method 1: QT-Import

     

    If you really want to import files one by another you should do the following out of Davinci.

     

    Choose your files and go to the Deliver-tab.

    Choose Quicktime and your prefered codec out of the codec dropdown, in your case prores444.

    Just avoid the sourcebrowser, just Drag&Drop out of the Finder/Explorer into the Avid-bin.

    If you hold OPT/ALT while dragging, the file only gets linked into your bin and you can transcode later or in the background to save quite some time....the big disadvantage of the old fashioned IMPORT.


    If your MC keeps crashing i would delete and reinstall Avid to start from scratch!

     

    Method 2: OP-ATOM MXF vs MXF OP1A 

     

    You are just using the wrong MXF-Container, exactly what Avid ist trying to say in the Error-Messages.

    " ….file is NOT MXF op-Atom....an error occurred scanning the file..."

     

    You just have to choose the right container from the Deliver-tab.

    Once your MXF files are created out of Davinci you have to put them into your Avid Mediafiles Folder, doesn't matter what number it has or you may changed it later on. (Try not to change it every day ;))

    I would recommend to keep them seperately to already existing MXF-files and folders with already existing numbers in the root-directory of the Avid MediaFiles folder.

    Once you start up your Avid MC the new folder, lets say number 10 with your new MXF-files out of Davinci will get scanned and Avid will give the folder a new file called msmMMOB.

    In your Project just create a new bin for your Footage an drag this file into the bin, once again...from the Finder/Explorer.

    No need of the stupid sourcebrowser at all!

    Avid will populate your Davinci MXF-files into that bin and the footage will get online, ready to cut.

    No further importing needed....WHY would you want to import?!

     

     

    Method 3 Creating MXF(OP-ATOM) and AAF File automatically

     

    Instead of Custom, just use the Davinci preset for the Avid-AAF.

     

    Once created and copied or directly rendered to the Avid MediaFiles/MXF/1....1000 folderstructur, just import or drag and drop the automatically created AAF File to your footage bin within a new project. (you have too look for it somewhere between the created MXF-files)

    Once again Avid will populate all the clips into the bin ready to cut. DONE.

     

     

     

     

    You can handle the exchange between AMC and DaVinci in more than one way but if you really want to keep the best quality out of your media AND want to be more faster AND more professional, try to master the workaround with AAF File export and Import.

     

    You just have to set it up right in the beginning!

    This article helped me a lot für my Davinci/AMC Workflow.

     

    Best of Luck!

     

    http://www.avidblogs.com/how-to-roundtrip-davinci-resolve-to-avid-media-composer-tutorial/

     

     

     

     


  • Wed, Nov 29 2017 2:03 AM In reply to

    • jef
    • Top 25 Contributor
    • Joined on Sun, Feb 26 2006
    • Maryland
    • Posts 3,925
    • Points 47,380

    Re: All import methods Failing

    rdmartin:

    .

    Then I just figured I stick with Custom: format: MXF OP1A: DNxHD 10bit

    Perhaps I should have been using the Avid Template instead... but that still doesn't solve the issue with not being able to import quicktime files. 

     

    One thing I see when wading thru this thread.  If I understand you, you are creating OP1A files and putting them in the MXF / 1 folder.  You should be creating OP-Atom.  That is what Avid wants in it's media folders.  That is part of the Avid round trip setting in Resolve I believe.

    And as Andrew noted there has been some bugs with DNx 444 from Resolve.  

    Just to try and clear some things up, I would make some regular DNx 422 OP-Atom files and try the method Andrew suggested.

    Good luck,

    Jef

    Avid DS 11.0.2 R.I.P | MC "Well, it depends ..." 2021 iMac w Big Sur [view my complete system specs]

    _____________________________________________

    Jef Huey

    Senior Editor

  • Thu, Nov 30 2017 5:05 AM In reply to

    • rdmartin
    • Not Ranked
    • Joined on Fri, Jan 4 2013
    • Posts 32
    • Points 460

    Re: All import methods Failing

    I exported a new batch of MXFs from the Avid template to start over

    I chose: MXF OP-Atom: DNxHD 175 10bit

    For audio I chose: Same as Source and Linear PCM (the only option.

     

    I dragged the MXFs and the AAF from the export into the Avid MediaFiles:1 folder of a new external drive.

    I opened a new project created on the root of that external drive. From the source media window, when I went to drag and drop the BIN file, it prompted me that it could not be Linked but can be Imported. I did so and the project bin was successfully populated with all the MXF files.

    Though there is a problem: the Audio is all messed up. Some MXF files I double click into the source media window have their audio and is all fine, others are not (it's just a blank muted humm like when speakers are shooting static) even within the soure media folder. Then the ones that were fine, are not without audio after dragging that bin file in to populate with all the clips.

    So then I try a different method: I click on a MXF file from source media (from folder 1) and select import: it says it can't be imported but can be linked and or transcoded. I select apply to all and then Avid crashes during the dowload window bar of that single file.

    So then I decide to create a new bin and drag and drop the AAF into that. The bin populates and everything works out perfectly.

    Of note, as i scroll throuhg this bin, I come to find this single files (of which were created as a result of this comparison tests of trying to make this work) that have a different thumbnail symbol... which I don't know the difference between, but sure enough those files are lacking in audio, they just have the singnal noise.

    So for MXF files, the only method that works for me is dragging the AAF into the project. The generated Bin file doesn't work and either does linking/transcoding. Seems limited, yes?

     

    FOR QUICKTIMES

    I tried that very same file, it's quicktime Prores4444 equivalent that I exported from resolve. Double clicked it in the source media, it's color and sound work and look great and match the MXFs. Then I import from the source media window as DNxHD175 10bit. It does import into my bin successfully (avid no longer crashes from a quicktime export like before), the sounds does work, but the color has become muted/more flat... which is just bad...

    So unfortunate why that happens.... for instance, if I have quicktime files created right out of camera... say just for an example from the Alexa camera at prores4444, or from any type of camera for that matter, the color will shift when transcoding to DNxHD 175 10bit.... is the a 4444 thing? I would just think that 175 10 bit would maintain videlity of any orginal file....

     

    So I try a different method: the good old fashioned File, Input: Import media

    But that fails because it said it couldn't locate the AMA plug-in file type....how could this be?

     

    So to sum it up, I can start editing now, but the only viable way to do this from starting with CinemaDNGs in Resolve is with exporting MXF files and draging in the AAF file.

     

     

     

  • Thu, Nov 30 2017 6:33 AM In reply to

    Re: All import methods Failing

    rdmartin:
    It's quicktime Prores4444 equivalent that I exported from resolve. Double clicked it in the source media, it's color and sound work and look great and match the MXFs. Then I import from the source media window as DNxHD175 10bit.
    What happens if you use the Source Browser and Link directly to the ProRes444 export from Resolve?

    rdmartin:
    It does import into my bin successfully (avid no longer crashes from a quicktime export like before), the sounds does work, but the color has become muted/more flat... which is just bad...
    What happens if you choose to Import but Set the RGB / Rec 709 option to the opposite of the one you used when you got the flat  muted clips?

Page 1 of 2 (22 items) 1 2 Next >

© Copyright 2011 Avid Technology, Inc.  Terms of Use |  Privacy Policy |  Site Map |  Find a Reseller