I realized that since the 2019 version and on the 2020 and 2021 versions of Media Composer, the "Batch re-import" function no longer works. The message: "Imported 0 of 1 clips. See console for more information." So I've attached a screenshot of the console (and the Batch re-import window) in this post

For information:

I use Media Composer on Mac and I tried the Batch re-import function on Media Composer 2018, 2019, 2020 and 2021 and it only worked with 2018.

Features on my Mac:

27" 5K 2020 iMac (20.1) - Intel Core i9 10 cores at 3.6 GHz - AMD Radeon Pro 5700XT 16GB VRAM - RAM = 32 GB

macOS Catalina 10.15.7

I also tried with other Mac models: Mac Pro, MacBook Pro and this on macOS Mojave and Catalina.

Concerning the rushs I tried to re-import :

I tried with different types of dailies all transcoded to MXF OP-Atom in DNxHD and HR (LB, SQ, HQ...) on Avid Media Composer (via the Consolidate/Transcode function after a "Link" or via the "Import" function) as well as with DaVinci Resolve.

So, having tried with multiple dailies of different formats, resolutions, frame rate, on different Macs and different types of MC versions, I can say that the problem is indeed with Media Composer, since versions 2019 to 2021. This problem is very annoying because it is of course a very used feature of the software and this bug prevents professionals from updating their software.

Have you also encountered this problem?

Best regards,

Oscar Ito

oscar_ito:

I realized that since the 2019 version and on the 2020 and 2021 versions of Media Composer, the "Batch re-import" function no longer works. The message: "Imported 0 of 1 clips. See console for more information." So I've attached a screenshot of the console (and the Batch re-import window) in this post

 

For information:

 

I use Media Composer on Mac and I tried the Batch re-import function on Media Composer 2018, 2019, 2020 and 2021 and it only worked with 2018.

 

Features on my Mac:

27" 5K 2020 iMac (20.1) - Intel Core i9 10 cores at 3.6 GHz - AMD Radeon Pro 5700XT 16GB VRAM - RAM = 32 GB

macOS Catalina 10.15.7

 

I also tried with other Mac models: Mac Pro, MacBook Pro and this on macOS Mojave and Catalina.

 

Concerning the rushs I tried to re-import :

 

I tried with different types of dailies all transcoded to MXF OP-Atom in DNxHD and HR (LB, SQ, HQ...) on Avid Media Composer (via the Consolidate/Transcode function after a "Link" or via the "Import" function) as well as with DaVinci Resolve.

 

So, having tried with multiple dailies of different formats, resolutions, frame rate, on different Macs and different types of MC versions, I can say that the problem is indeed with Media Composer, since versions 2019 to 2021. This problem is very annoying because it is of course a very used feature of the software and this bug prevents professionals from updating their software.

 

Have you also encountered this problem?

 

Best regards,

 

Oscar Ito

I haven't encountered this problem. Are you sure that you are batch re-importing to the correct clip? I know it's a silly question but you'd be surprised...

Create a support case: https://avid.secure.force.com/pkb/articles/en_US/how_to/Support-Plan-Case-Creation

and if it's a bug, it will be reported to the engineering department.

Same problem here with 2020.9

Batch import doesn't work. 

Avid starts to create the mediafiles and then a message appears "imported 0 of xx clip, see consoles for more information". 

Console says:

Track - 1 not found

Is it a bug?

Thanks 

I concur. I have the same issue here as well I had to clear out some MXF files and a project happened to have a small bin with older files that I still needed. I've been trying to re-import, move things around and try almost everything I could think of.

All the original files (that got imported) exist at the same exact locations, but I get 0 out of 1 clips too.

Same issue here running version: 2021.6. on Big Sur 11.6 MacBook Pro (16-inch, 2019)

It works if I import and then batch a file in a current project but projects from a few years ago are a no go.

Here is what worked for me. Hit the "overide clip settings with with current settings" during the batch import.

Riley Harlton:

Here is what worked for me. Hit the "overide clip settings with with current settings" during the batch import.

Thanks for updating the forum :)

I rarely import media nowadays. I consider importing a legacy ingest method. 

I use link and then transcode. 

So at conform I just relink to the original rushes. 

So just don't need to re-import.

That said I have demonstrated batch import on 2021,(on PC) and that did work. 

We're trying to re-import material that has been transcoded initially and encounter the same problem: Batch imported 0 clips, see console.

If this is a bug it really needs fixing because it's an important feature!

Or do transcoded clips require a different workflow to re-import them?

Mirja:

We're trying to re-import material that has been transcoded initially

What was the exact workflow you used when you first brought the material into the system?

Mirja:

Or do transcoded clips require a different workflow to re-import them?

If you linked and then transcoded, batch import is not going to work. You need to relink to the original files.

Will that media not AMA link in? And if its in the required codec then it can be used like that (just relink the sequence to those clips) if you need it as Avid media then consolidate those linked clips.

But agreed unless Avid has deprecated the re-import function (and if they have they should give a sensible warning of that) then it should work.

Mirja:

We're trying to re-import material that has been transcoded initially and encounter the same problem: Batch imported 0 clips, see console.

 

If this is a bug it really needs fixing because it's an important feature!

 

Or do transcoded clips require a different workflow to re-import them?

We now found two solutions to the problem:

On the computer where the problem occured we're working with MC 2021.12.0.

I made a new bin and linked the missing footage into it, then transcoded it (with the same settings as before) and then used the relink-tool to relink the original offline clips to the new mediafiles.

Following the observation of our collegue who raised this topic, we also tried using the re-capture function on a computer that's still running a 2018-version - and it really worked! Even though our footage had been transcoded initially, we could use the re-import function in the MC2018 to get our footage back online.

So it's really an issue with the more current versions!

Also, 2021.12.0 wouldn't transcode some of our clips, giving me an error message "NEMFileWriter has detected upstream pipe stall".

This also didn't occur with the 2018-version. MC2018 allowed me to transcode all my footage and use the re-import :)

Thanks for the reply!

We initially linked our footage into the bin and transcoded it.

For some reason, a MC2018-version allows us to use re-import for these clips :)

We have been wondering: If we have a bin with masterclips that are offline. Is there a way to link them back with the source files so they'd turn into AMA-clips again?

And then transcode them again and they'd all be linked to our sequences?

That would be great! So far, I only know how to link a sequence to source files and create an entirely new master-clip.

Pat Horridge:

Will that media not AMA link in? And if its in the required codec then it can be used like that (just relink the sequence to those clips) if you need it as Avid media then consolidate those linked clips.

But agreed unless Avid has deprecated the re-import function (and if they have they should give a sensible warning of that) then it should work.

Ok, thanks!

I had to read your suggested solution twice before I understood. But yes, that should work, too!

Just that in our 2021.12.0-version some of our clips wouldn't AMA-link! So that would have made it more complicated.

The project has been set up on yet another version and machine ...

If you linked and then transcoded, batch import is not going to work. You need to relink to the original files.