Skip to main content
Inspiring
December 8, 2017
Answered

Matrox and MXF errors - importer issues and frames not loading/Media Pending

  • December 8, 2017
  • 1 reply
  • 434 views

These issues embody themselves in three ways

1. Media Pending forever

2. Media Disconnected, despite being easily found on a network drive

3. Receiving the Red Frame error

I know these are common errors, however many of the previously explained solves on the forums aren't working for me, including:

1. Uninstalling drivers, clearing out remaining files and then reinstalling drivers.

2. Disconnecting and reconnecting media

3. Disabling and Enabling clips

4. Nesting sequences

5. Clearing the cache and re-pointing it, as well as deleting rendered frames.

6. Move files from networked drive to local drive (C:)

7. Slicing offending clips into tiny fragments to improve indexing in project

8. Creating proxies and reconnecting

Further, we have to workstations to edit from where I work. One of them works fine with the Matrox codecs and fails with the other issues, the other just keeps failing in all scenarios.

I wonder whether I need to hold out for an update to CC 2018. I jumped in too early and there seems to be a few bugs that others are posting about.

I guess another question might be: is there such a thing as an Adobe Specialist to call in and how do I find one? There's clearly an issue with our set up.

Or maybe there's a Premiere Pro resource monitor of some kind where I can follow along the processes that Premiere is attempting, other than assuming my computer is doing nothing for half an hour despite consuming huge amounts of memory and CPU power.

Specs:

Operating System

Windows 10 Pro 64-bit

CPU

Intel Core i7 6850K @ 3.60GHz 45 °C

Broadwell-E/EP 14nm Technology

RAM

32.0GB Unknown @ 1066MHz (15-15-15-36)

Motherboard

ASUSTeK COMPUTER INC. X99-A II (SOCKET 2011) 52 °C

Graphics

VW24A (1920x1080@60Hz)

VW24A (1920x1080@60Hz)

4095MB NVIDIA Quadro M4000 (NVIDIA) 49 °C

Storage

11176GB LSI MR9265-8i SCSI Disk Device (RAID)

476GB Samsung SSD 850 PRO 512GB (SSD) 43 °C

Optical Drives

No optical disk drives detected

Audio

Avid Fast Track Solo

This topic has been closed for replies.
Correct answer xleggs

I'm having issues with Matrox codecs as well. In the last version of Encode CC 2018, I was at least able to load the Matrox encoded AVIs into encoder, then export them into something more universal depending whether or not they needed alpha. In the newest updates- to 2019 that we did today, the AVIs fail in Premiere (and crash the program), but also will not read in encoder.

It's not like we need the Matrox MX02 LE with Max boxes that we have running- we just keep them hooked up to support the codecs because we re-use a lot of old graphics movies and are always opening old projects that require them.

We went backwards and installed Encoder CC 2017, and that works to read the files- but this will be a big pain if we have to re-encode all the old stuff.

1 reply

xleggsCorrect answer
Participant
October 19, 2018

I'm having issues with Matrox codecs as well. In the last version of Encode CC 2018, I was at least able to load the Matrox encoded AVIs into encoder, then export them into something more universal depending whether or not they needed alpha. In the newest updates- to 2019 that we did today, the AVIs fail in Premiere (and crash the program), but also will not read in encoder.

It's not like we need the Matrox MX02 LE with Max boxes that we have running- we just keep them hooked up to support the codecs because we re-use a lot of old graphics movies and are always opening old projects that require them.

We went backwards and installed Encoder CC 2017, and that works to read the files- but this will be a big pain if we have to re-encode all the old stuff.