I encountered an issue in 2020.5 where a project with source media originally compressed in DnxHD 220X is now showing up as "Not Supported" in the video column bin display. Any sequence referencing that source media is unplayable and the media itself is unplayable. This problem occurred after I upgraded from 2019.11 to 2020.5.

The error message is attached.

Any idea how to fix or why this happened in the first place?

Hi LucilleGirl,

It would help to know your system specifications. Which specific version of Media Composer are you using? Which specific operating system? Processor? Amount of RAM? Video card? Is your media linked, transcoded, or imported? Where is your media stored? Look at my profile at the bottom of this post for an example.

If you fill out this information in your profile, you won't have to type it out every time you need help.

Media Composer 2020.5

Windows 10 Enterprise

Intel(R) Core(TM) i9-990K CPU @ 3.60GHz

64 GB RAM

GeForce GTX 1060 6GB

Media was originally transcoded at DnxHD 220X resolution and is stored on a 1TB SSD

Again, the problem is since upgrading from 2019.11, and upon opening this project created on that version of MC, the media originally transcoded in DnxHD 220X resolution now appears as "not supported" and is unplayable (also causing the sequence to be unplayable).

Thanks!

Just to make sure I understand the timeline, is this the order:

1. Media linked/transcoded to DNxHD 220X in MC 2019.11. Everything worked fine.

2. Upgraded MC from 2019.11 to 2020.5. Now media is 'not supported' and will not play.

Is that correct?

Correct

Bumping this back up...any other possible solutions to my problem?

Am I leaving out any pertinent information that might be helpful in fixing my problem?

LucilleGirl:

Am I leaving out any pertinent information that might be helpful in fixing my problem?

No, and I'm sorry I haven't responded in so long. I looked through the What's New doc for 2020.x to see if there's something that would explain what you're seeing, but there's not. I also looked through some other posts with similar issues, but they all seem to point to corrupt media, which doesn't sound like your problem because ALL your media is affected. I only have 2 suggestions, and they're both shots in the dark.

1. Delete your media database files and let Media Composer rebuild them when you restart.

2. Split your sequence in half. (Make a duplicate of it first.) Try to load up just one half at a time. If half of it works/displays, then you've got a problem in the other half.

Sorry I don't have a better idea.

Sorry for the misunderstanding and thanks for your help.

The problem is isolated to three source media clips originally transcoded in DnxHD220X resolution (which MC 2020 seems to no longer support).

I cannot play those three clips in the source browser. Also, I cannot play any sequence that includes those clips.

All other source media clips in the project play fine.

I did try deleting the media database files with no success.

Steve

LucilleGirl:

The problem is isolated to three source media clips originally transcoded in DnxHD220X resolution (which MC 2020 seems to no longer support).

Ah, ok. MC 2020.x does still support DNxHD 220x resolutions, they just changed the name of it. There's a list on page 8.

http://resources.avid.com/SupportFiles/attach/WhatsNew_MediaComposer_v20.4.pdf

LucilleGirl:

I cannot play those three clips in the source browser. Also, I cannot play any sequence that includes those clips.

Do you still have the original footage? How did the footage originally come into the system? Was it imported, linked and transcoded?

It was transcoded, and yes I do have the original footage.

LucilleGirl:

It was transcoded, and yes I do have the original footage.

If it's only 3 clips causing the problem, I'd try linking back to the original footage and retranscoding it.

I'm here to try and figure this out, as well. Sounds like we have a similar issue.

Just downloaded 2020.6.0 today with the free trial, and I get "Video compression is not recognized" every time I try to relink to the MXF file. I also have no option for DNxHD LB as it was ingested with. Not sure why that's missing from mine as far as options go. Most likely user error...

Quick story is I was sent a hard drive, clond it, opened their project, and most footage relinked fine. Came to a massive amount of video that would NOT relink with the above text (and crashing often).

The original footage is AVC Long-GOP Main (HD720p). I ingested it as a test with DNxUncompressed 4:2:2 8bit since LB isn't offered on my computer, and it plays fine. Doesn't help the group since pulling selects won't be from the same source, though.

I've tried remaking the databse a couple of times, as well.

Any thoughts? No worries if not as I'll continue following this thread anyway.

I'm runing a MacBook Pro Retina on 10.14.6 

2.8GHz Intel Core i7

16GB memory

AMD Radeon R9 M370X 2GB

SOLUTION for my problem

In short: I copied all the original Avid Project Files onto my cloned hard drive, thereby erasing and overriding the newest files, and it worked. 

My Project Files were made in MC 2018, but when I opened the hard drive on my MC 7 this version couldn't recognize the new data thus "not recognized." This data from the newly saved Project Files must've remained the same when I upgraded to 2020 to failure, and then installed 2018 also to failure. As soon as I copied the orignal project files back onto the cloned hard drive now running MC 2018, they loaded perfectly.

Hope that made sense and hope it helps someone else down the line!

I always advice clients to not move projects between MC versions.

I always make a new project on the new system (same project name)

I then make sure my project settings are correct in that new project. Ensure I have a new users setting created.

Then copy the relevant bins from the old project to the new project.

This ensures the original project isn't altered by opening it in a new version of MC and it prevents any legacy issues being dragged into the new MC version.