Hahaha... yes, you were right, Carl, but don't drink the Moscato just yet! ;) While removing the character "/" from the file path within each file on my desktop work, it still didn't work when I tried to ingest files to my clips bin from my Source Browser via my external hard drive. I guess, I figure it out somehow thru deduction. So in that case, I will send you only a half bottle of Moscato!! ;)

Haha!

Can you post a screen shot showing the entire file path on your external drive? It might help to figure it out.

I see this thread kinda went dark. Here we are 2 years later and the same issues remain. Has anyone really tried to solve it? I think the issue may be the Mp4/.mov files do not appear to have time code or a raster size which gives me this error. It's a number of files.

And I have the same problem. My .mp4 files can't be imported, no matter name chang or place (moved them to the desktop).

I'm working i Mojave and MC 2019.

Getting tired of not solving this....

/Elisabet

Quite sure You might get better help over the Mac forum. As a PC guy I ask if the footage is h265 by any chance.

Oh, I didn't see that this was a PC group.

And yes, its a  HEVC-file which means h265, didn't see that! What do I do then..?

MC's support for h265 is not here yet, throw the footage to ShutterEncoder, Resolve, or Your favourite encoder, turn it into an Avid friendly format and bring into MC as usual.

First of all this is not a dumb quwstion at all.

I am a verteran AVID Editor (creative), not an assistant. I feel like I know a great great deal about AVID but with new CODEKs and workflows everythign is changing; getting easier in some ways and more complicated in others.

Thank you for this post because I have been struggling to find out why I could import .mov in one instance and not another. I thought it was how the file was wrapped using Adobe Encoder to no avail. 

It gets really confusing because I have always been told how the clip is named is important but I had no idea that how the path, of the clip, is named is equally important. 

I had one folder in the path named CLIPS-03-24-21 and that caused all my problems. changing the folder name to CLIPS_03_24_21 made all the difference. 

Anyway, thank you for this thread. In 2021 it was very helpful.