Skip to main content
Lewiz
Lewiz
Inspiring
January 3, 2014
Answered

MXF frame read errors and general render errors since update to CC

  • January 3, 2014
  • 10 replies
  • 22808 views

Hi there folks,

Being a Creative Cloud member for a while now I share the benefits of immediate updates of CC products. However, I also get to deal with the downsides, it seems.

Since I updated to CC versions of the entire Adobe Collection I experienced unprecedented trouble with After Effects. I'll mention the most pertinent errors:

- I used to render short compositions to uncompressed HD Quicktime, functioning as a master render for future sorts of output for my clients or just to have optimum quality before further conversions. For some reason AE CC has been generating all sorts of video dropouts lately, especially when audio render is set to 'auto'. Furthermore I noticed that the only audio res that I can choose in case of an uncompressed QT render is 8000 Hz. This is new in AE CC, I don't understand the reason for this modification since the previous AE versions never had this limitation.

I must mention the fact that other output formats and codecs also suffer from dropouts, be it less frequently than QT uncompressed.

- Imported MXF files from my customers which I incorporate in AE compositions are also full of dropouts. Every dropout shows up as a single frame (two fields) of red or black. Premiere Pro encounters the same problem and reports the dropouts as frames with a read or decode error. I checked some older MXF files in previous AE projects that have been rendered and delivered perfectly in the past, but these old MXFs now appear to have the same issue. I tested the older and the new MXF on another PC that wasn't updated to CC versions and found no dropouts at all. Something must have changed in the updated codecs that belong to the CC version. All MXFs play fine in VLC player on all systems, so it's not the video source being faulty. Anyone recognize this?

I do get notifications of CC product updates, but is there a way to just update the codecs? Maybe there is a better codec for MXF.

Any help is truy appreciated!

    This topic has been closed for replies.
    Correct answer Kevin J. Monahan Jr.

    Give that a try and let me know how well it works

    _n.

    That post was from a year ago. Most of these red frames issues should be resolved. Glad you were able to solve your own issues.

    Kevin

    10 replies

    5
    55878965
    Inspiring
    September 11, 2024

     MXF XACV-L 35MBPS

    Still has errors.

    PP 24.6.1 Build 2

    Forget trying to import an AVI, just in case anyone does that by mistake.

    U
    UniversumMedia
    Participant
    June 7, 2016

    I am having a red frame issue. This is the first time I used Premiere with XMF files. It works perfect with P2.  I am using 2015.2. What is the best way to have premiere and encoder work with MXF?

    Thanks

    Scott

    Bartman_67
    Bartman_67
    Participant
    January 26, 2015

    still got them (red frames) over here.

    no fun exporting at all....

    only in MXf files.

    N
    nikpavlov
    Participant
    February 1, 2016

    downgrading Premiere and Media Encoder back down to 2014.1 will resolve the red flash issues in mxf files and .h264

    we've been using 2014.1 for several months now without any issues. 2015.2 might have fixed some of this but we've noticed too many bugs still in it so were sticking with what we know works, which is 2014.1

    heres the best way to do it. uninstall premiere and media encoder inside creative cloud. then under apps tab, scroll to find additional apps and click previous versions. then go to premiere pro and click install CC2014. heres where you have to watch the install. keep an eye on the installation in creative cloud and then when you see it change to updating, click the X to cancel. this will keep the original CC2014 version without updating it.

    Now do the same thing with media encoder CC2014 but cancel before the update.

    Finally go this site and download the CC2014.1 update for both Premiere Pro and Media Encoder

    MAC - http://prodesigntools.com/adobe-cc-2014-updates-links-mac.html

    WINDOWS - http://prodesigntools.com/adobe-cc-2014-updates-links-windows.html

    once downloaded, install the CC2014.1 updates and reboot.

    THANK YOU PRO DESIGN TOOLS for keeping all the individual updates!! Without them this solution wouldnt be possible. Big props to them!

    Give that a try and let me know how well it works

    _n.

    Kevin J. Monahan Jr.
    Community Manager
    Kevin J. Monahan Jr.Community ManagerCorrect answer
    Community Manager
    February 2, 2016

    Give that a try and let me know how well it works

    _n.

    That post was from a year ago. Most of these red frames issues should be resolved. Glad you were able to solve your own issues.

    Kevin

    Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
    Bartman_67
    Bartman_67
    Participant
    January 13, 2015

    We still find red frames in exports to H264

    original files in this codec:

    Format XDCAM HD 422

    Codec MPEG2

    4:2:2 Profile (422P) @ High Level (HL)

    Bitrate 50 Mbps

    Constant Bit Rate (CBR)

    Display aspect ratio 16:9

    1080i/25 1920 x 1080 25, 50 fields Interlaced

    adobe premiere pro cc 2014.2 release 8.20.0 (65) build

    Mac Pro Mid 2012 Yosemite

    24 GB RAM

    Nvidia Quadro K5000

    No problem until last update...

    Any solution or update in future?

    Hope to hear from Adobe.

    Bart

    Lewiz
    LewizAuthor
    Inspiring
    January 16, 2015

    Like often, it's better to wait a little until there's enough people experiencing the same problem. So everyone here: thanks for responding to my post! In the end it seems to have helped, considering the update of Adobe. I am still a little precautious, because some MXFs give no red frames at all (input side I'm talking about) and others still do, but then the strange thing is that scrubbing the MXFs forth and back a bit results in having less red frames to none at all in the end. The red frames now disappear and then re-appear on different points in time of the MXF file, whereas I always found them being bound to specific and unchanging points, especially on the first frame of a scene change for instance.

    Anyway, Adobe Media Encoder is not suffering from this problem, so there is a workaround, converting the footage before using it in AE and Premiere. That's good enough for now. But the problem hasn't vanished yet. Another problem that I had with rendering uncompressed HD Quicktime videos that always generated dropouts has all of a sudden magically disappeared. Thanks Adobe. I see progress.

    5neaky C
    5neaky C
    Participating Frequently
    October 31, 2014

    My whole production house has this Red Frame MXF read issue since the 8.1 update.

    It is serious. You are not alone.

    Dumping cache and other general fixes are not exporting video consistently with out errors.

    I have lost weeks worth of work. I am redoing them in CS6 - which still runs solid.

    Soooo sad. keeping my eyes open for a fix or a new patch from Adobe.

    Bests!

    A
    AllTheGoodNamesAreGone
    Participating Frequently
    October 28, 2014

    Yep, having this EXACT same issue as well. Have deleted cache and tried various suggestions in the forums. Nothing seems to help.

    The only thing that temporarily solves it is restarting Premiere... I'll get a few minutes of editing without the issue, then it just pops back up.

    Any bug fixes in the works??

    Premiere CC 2014 8.1.0 (81) build

    Mac OS 10.9.5

    GTX680 card

    MXF File details:

    Wrapper type: MXF OP1a (type: SingleItem SinglePackage MultiTrack Stream Internal)

    File generated by: CANON, EOS C300 PL (1.00)

    MPEG-2 422 Long-GOP

    Lars Wittrock
    Lars Wittrock
    Participant
    October 18, 2014

    Having same issue in premiere pro cc 2014

    In timeline the frame is red and even exporting a few frames of the clip takes a long time.

    br Lars

    B
    brdcphoto
    Known Participant
    September 25, 2014

    I have to same problem.  MXF files are stored locally and are playing OK, but when I use transitions or FX it give the decode error.

    Also rendering does not work.

    I deleted cache, but nothing worked.

    K
    kbs777
    Participant
    February 26, 2014

    we have exactly the same troubles...

    in premiere, prelude and AE.

    on two different computers. (same OS, and latest AdobeCC)

    OSX 10.9.1

    MXF:

    Codec: 422P@HL Long-GOP 50Mb

    UpperField Interlaced

    we worked with these mxf-files in the past with adobe applications and also with other apps like QT and FCP without any trouble.

    now there is a (codec?) - problem in all adobe-apps...but only in the adobe-apps.

      Todd_Kopriva
      Todd_Kopriva
      Inspiring
      January 3, 2014

      See this regarding the audio issue:

      http://forums.adobe.com/message/5938627#5938627

      Regarding your MXF issue: We need more information. MXF is just a broad container type. What exact kinds of MXF files are you having trouble with?

      Lewiz
      LewizAuthor
      Inspiring
      January 6, 2014

      Hi Todd and thanks for your answer. I am a bit late responding, but nevertheless.

      Audio issue is clear now, thanks for the link. Leaves me with the questions regarding video dropouts that occur quite often in any rendered output format and codec, whereas AE very rarely used to generate dropouts in the past, almost never actually; and the other question regarding the MXF frame read/decode errors in both Premiere and After Effects and even the Media Encoder.

      In answer to your question: the specs of the troublesome MXF files are:

      Format XDCAM HD 422
      Codec MPEG2
      4:2:2 Profile (422P) @ High Level (HL)
      Bitrate 50 Mbps
      Constant Bit Rate (CBR)
      Display aspect ratio 16:9
      1080i/25 1920 x 1080 25, 50 fields Interlaced

      Export from Avid. Used to work flawlessly until CC update.

      Hope this rings a hidden bell :-)

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices