MXF decode errors and red frames in exports

Ever since upgrading to Premiere Pro release 2014.2 (8.2.0 (65) Build) we've been having problems with random red frames appearing in our exports.  These errors are always associated with our Sony PMW-200 media files (.mxf files.)  Red frames during editing happen very rarely, but are usually present in our exports.  For short form work re-exporting the sequence will work sometimes, but may cause red frames to appear elsewhere...  For long form work we've adopted a very lengthy work-around to fix the errors after exporting.
Phone support recommended deleting the media cache files, but we've tried that and the problem still exists.  This problem is happening with new media that has been imported since the upgrade as well as old media that we imported before the upgrade.  We're editing with many mixed media files all in their native codec and the only media files that get flagged with decode errors are the .mxf files.
We edit a large volume of work daily and this problem is a huge setback in our confidence with our exports as well as Adobe products.
For the record were editing with Mac Pros that are about a 3-5 years old with OS X 10.8.5 and an Xsan shared storage system.  We have a Cloud for Teams subscription and all our software is updated frequently.
Any thoughts would be helpful.  Personally I would love to escalate this problem to a higher level support team.
Regards,
Eric

I have the same problem running Adobe CC on high-end PCs. - My business is smalish, but this leads to having a rather big impact on my confidence.
MXF-files from Canon C300 and Sony FS7 platforms.
- With FS7 footage I've had the frames appear throughout a clip with perfect distance (16 frames apart) - when applying Denoiser 2 from Red Giant. - The plugin simply stopped the frames from appearing on a random basis.
- I've also experienced that when the error was present, dissolves became cuts.
- I've tried to isolate software/hardware rendering, but it does not seem to change anything to select one over the other.
I try work around it by rendering uncompressed sections of the timeline and replace it where it works, and then try again and again. - Very time-consuming and cumbersome.
Best
Torsten
Denmark

Similar Messages

  • Red frames and MXF decode error

    Hi there,
    I have Premiere Pro CC and running Mac OSX 10.9.5. I have one long 32 minute long C300 MXF clip in my timeline which seems to be fine until around the 26 minute mark, where the entire frame goes red. The audio still works, but I can't see anything. I have tried to convert the clip to ProRes in Media Encoder also, but the same issue happens.
    In the report log from Media Encoder I get the following message repeated many times:
    MXF decode error in "[FOOTAGE LOCATION]/Card 1/CONTENTS/CLIPS001/E51151/E5115107.MXF" at frame 47650. Frame 47618 was substituted.
    And then occasionally it says:
    MXF read error in "[FOOTAGE LOCATION]/Card 1/CONTENTS/CLIPS001/E51151/E5115107.MXF" at frame 239.
    Any advice about this??
    Thanks,
    Simon

    Hi there,
    I have Premiere Pro CC and running Mac OSX 10.9.5. I have one long 32 minute long C300 MXF clip in my timeline which seems to be fine until around the 26 minute mark, where the entire frame goes red. The audio still works, but I can't see anything. I have tried to convert the clip to ProRes in Media Encoder also, but the same issue happens.
    In the report log from Media Encoder I get the following message repeated many times:
    MXF decode error in "[FOOTAGE LOCATION]/Card 1/CONTENTS/CLIPS001/E51151/E5115107.MXF" at frame 47650. Frame 47618 was substituted.
    And then occasionally it says:
    MXF read error in "[FOOTAGE LOCATION]/Card 1/CONTENTS/CLIPS001/E51151/E5115107.MXF" at frame 239.
    Any advice about this??
    Thanks,
    Simon

  • Getting red frames when export from cc 2014.2 codec used panasonic mxf format long GOP 50p. If any solution please help on that

    getting red frames when export from cc 2014.2 codec used panasonic mxf format long GOP 50p. If any solution please help on that

    i solve my red frame problem. originally my project was done in premiere pro cc 2014.2 & i render in Encoder cc 2014. in newer version i get lots of red frames. i complain a lot to adobe customer support . they said they know the issues but they couldn't solve. I was so tired from adobe customer support. one of the worse customer services i had. My friend got the mac pro & e got premiere pro cc 7.2 version. i convert all my footage mxf to mp4 in encoder cc 7.2 version and i succeed. i don't get any red frames.
    So i think the problem is in adobe encoder cc 2014.2 version. newer version.

  • Red Frames in export to h.264 original files XDCAM MXF

    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

    We are having the same issue at our shop.  We have 8 suites, all are experiencing red flashes ever since we upgraded to 7.2.1.
    All the systems are Win7, and we've encountered red flashes with XDCam 35, XDCam 422 and Mpeg4 clips.  We haven't been to develop a workaround as the flashes occur in very inconsistent patterns.
    For example, just a moment ago an editor called me in because he was getting red flashes on his exports.  We went to his timeline, and the timeline was showing red flashes as well.  We deleted the clip (an XDCam 422 clip) from the bin, and re-imported it.  It played in the viewer fine with no flashes.  We put it on the timeline and again it played fine.  We exported the sequence directly out of Premiere as an XDCam 422 clip (delivery format needed for the client) and the exported file contained red flashes.  We went back to the timeline and it had red flashes, and the clip in question had red flashes when viewed directly! WTF?! 
    So we deleted the clip again, and re-imported it.  Played fine with no red flashes.  Put it on the timeline - no red flashes.  This time we exported the timeline as an AVC-I 100, and the exported file had no flashes.  As a test we went back and exported the timeline again as XDCam 422...and red flashes on the exported file, AND the timeline and original clip had red-flashes as well.
    Could it be something with XDCam and/or MPEG compressed clips in general?  We've only done one more test with AVC-I (which was successful) but I'm not confident enough yet to say that exporting as AVC-I is a consistent workaround. 

  • MXF decode error

    When I tried to render my sequence I got an error message.  In Premiere I saw "MXF decode error".
    It only happens on the spots where I used opacity and transitions.
    Deleted cache and all the usual things I could do, but nothing helps.
    Cheers

    Try to convert your MXF files into other format like MPEG. Or just find go for another edit software like FCP X, the 10.1.4 can support MXF files natively and as well as 4K . But if you just get used to this Adobe premiere , here are some free converters for you : Handbrake, ffMPEG(_this one I am not very recommended, it will mess all your original video and database), MPEG Stream clip, any video converter. I used now is this MXF Converter from pav, and the quality is good.

  • Errors and Red Flashes with MXF files

    Hi all and Adobe, this is the third time i have posted hear about this and it is now getting very serious as the problem is affecting my income as I run a small one man video production business.
    When I encode video that has any MXF file in the timeline, and most of my projects do as I generally am editing two to three camera shoots with one of the cameras being a Canon XF300.
    I get many errors, and multiple red flashes in the encoded video.
    I run all of my Adobe CC applications on a 2013 iMac 27" 3.5 Intel Core i7 32 gig Ram Nvidia GeForce GTX 780m 4096MB
    There is no bottleneck regarding disk drive as I am using a dedicated GRaid 8TB Thunderbolt drive.
    I first ran into this problem within a week of upgrading to the latest Premiere Pro CC 8.1 Caravan. I then noticed it when using Media Encoder when encoding both Premiere and After Effects projects Smith MXF files involved.
    I at first thought the problem may have been corrupted cache file so deleted them all and re conformed. I even uninstalled Premiere cleaned out all relevant directories then reinstalled.
    No matter what I tried the problem will not go away.
    I went online and noticed in many forums people complaining about the same problem and coincidently most seem to have the problem appear since the last upgrade.
    I then rang support and after a very long wait spoke to a man who advised I need to select Cuda in the GPU settings and delete all previews, so I did this while on the phone to him then started encoding a project and to my delight no errors.
    I was so excited I jumped on here to tell another person who had a similar problem the solution.
    But then within a day the errors were back and with vengeance, at the end of one of my last encodes yesterday I had an error log window that filled an iMac 27" screen not good.
    I then rang support again and as with the previous call a long wait ensured.
    After explaining my problem and indicating the discussion I had with the previous support person he indicated that Adobe was aware of this problem and they were trying to fix it.
    He suggested a work around and that was to encode only using the Mercury software not any GPU settings.
    So off I went and encoded the same project and guess what happened, more errors many errors.
    Also please note to be thorough I tried encoding a project from 2013 that has worked perfectly before on previous versions of Premiere but as soon as it is loaded into this version the errors appear.
    I also wish to bring to attention the abysmal support mechanism Adobe has established.
    There seems to be no way to fast track serious problems.
    I and many people like me need this problem solved as we rely on Adobe for our living.
    If this continues for much longer I will have to reconsider my investment in the Adobe CC product.
    Any assistance would be greatly appreciated.
    Regards, Cliff elliott

    Over the last couple of hours I tried an experiment using the same project which contains a two camera edits containing video from Canon XF300 and XHA1 cameras.
    The experiment was to encode out form the project on three separate Macs.
    As I have explained in the first post my main Machine the 2013 iMac gives errors on any setting including GPU selections.
    I then tried it on an older iMac a 2010 model 2.93 GHz Intel Core i7 which has an ATI Radeon HD 5750 1024 MB GPU and the same problem occurs.
    Next came an old Mac Book Pro 2011 that does not have GPU support. The project rendered without any errors but took about so long compared to the 2013 iMac which is to be expected.
    So the problem seems to be related to the relationship between Premiere and the GPU's.
    I hope this helps the Adobe engineers sort this out.

  • Red frames in export with version 7.2.1

    Sometimes when I export a material appears in any part of the video a red frame. Would i like to know what to do to solve my problem?
    I have a MAC PRO OS X 10.8.5 and i'm using premiere pro cc 7.2.1.
    Thanks!!

    Hi William,
    Can you update Premiere Pro to Premiere Pro CC (7.2.2) or CC 2014? That should solve your issue.
    Thanks,
    Kevin

  • Red frames when exporting mfx from new media encoder

    I edit TV programs each week that are mastered as MXF comps. Updated to premiere pro 8.2 (MacPro Late 2013) yesterday. Now when I export a program using the updated Media Encoder que, I'm getting full page red frames intermittently. How can I go back to the previous release? I can't wait for the bugs to be worked out.

    This should guide you through rolling back: Install a previous version of any Creative Cloud application

  • Red frames when exported to encore

    Not sure if this is an encore or a premiere pro problem
    I am trying to create a blu ray disc from a video shot in HDV.
    I have captured and edited my video in premiere pro and it looks great but I am having problems getting it on to a blu ray disc. I am using premiere pro CS3.
    If I export to encore or use the adobe media encoder I end up with a few clips being affected by being replaced with bright red frames.
    Now I have tried this on two projects and its always the same clips which are affected
    so I have started a new project gone back to the source footage and captured just a clip which was affected and tried to encode that single clip with the same results it gets corrupted into red frames.
    The clip plays perfectly well in premiere pro and can be exported back to tape without any problems ...so what is going on

    Thanks for responding Jeff.
    Its hard to know what has corrupted the frames as sometimes after encoding i get some completely red frames and some whith a little of what should be there showing through.
    It happens consistantly on two clips that I have been using in different projects.
    so as I said before I have created a new project gone back to the original and recaptured those two clips into my new project and tried to encode them in several different ways but all fail to encode properly.
    This is a Pal Project recorded captured and edited in HDV
    I used the MPEG2 settings and frame size of 1440X1080.
    I first used the default setting for 1440x1080 quality high, with a default qualty of 4 and then increased the quality to 5 without improving things.
    Ive tried reducing the target bit rate from the default to 20, still the same.
    Ive tried using CBR instead of VBR 2 pass. still no difference.
    My machine is a Dual Quadcore Xeon processors. with 4 GB of ram and a Matrox RTX2 card. both my video hard discs have around 50% free.
    I really am struggling to know what is wrong.

  • Screen splitting error and red boot screen

    Hi, I was using my macbook pro just now and the screen started to glitch and show black vertical bars and the displayed image was split up. I tried to see if there's an unresponsive program that i can force quit then the screen just turned grey and was stuck there.
    I then manually restarted the mac, it prompted me with a press button to continue booting up screen then it was stuck on the grey screen again.
    I tried to start in safe mode then it booted with a red screen and i believed did a system check. But I'm not sure. It then got stuck on the grey screen again.
    I rebooted the machine manually and then now it booted up fine.
    It has happened twice before. Once the split screen issue was solved by quitting Spotify and the second time similar events happened as described above.
    I have previously taken the mac to the genius bar and they ran a hardware check and found that everything was fine. Since I couldn't reproduce the error whilst being in the store they said there was nothing they could do.
    Update:
    The screen splitting issue has occurred at least twice since the event happened above. I have managed to collect another problem report which i can show in addition to the first one.
    I believe that there is a problem with the dedicated graphics card since whenever i use gfxCardStatus to switch to the AMD Radeon HD 6490M graphics card the screen splitting problem occurs. The problem also occurs when the machine automatically switches to the dedicated graphics card with things like Spotify, Google maps and other more intensive applications. Moreover, the second time the problem occurred when i was streaming a TV show and gfxCardStatus showed that the machine has switched to the dedicated Radeon card.
    I'm not sure what i can do about it right now other than trying not to use the dedicated graphics card.  Any help would be very much appreciated, thanks!
    If it helps, I've upgraded the ram myself previously. But that was a few years ago and didn't show any problems when i first installed it.
    It is an early 2011 Macbook Pro with OS X Mavericks 10.9.4
    The split screen issue looks like this:
    Apologies for the rotated image I don't know how to rotate it on the site.
    It also appears identical to the one shown here, three posts down: https://discussions.apple.com/message/15920113
    The problem report of the first event is shown here:
    Anonymous UUID: 81B375DF-0157-0360-53AE-96FF39CBAC4B
    Wed Jul 2 01:41:51 2014
    Machine-check capabilities: 0x0000000000000c09
    family: 6 model: 42 stepping: 7 microcode: 40
    signature: 0x206a7
    Intel(R) Core(TM) i7-2635QM CPU @ 2.00GHz
    9 error-reporting banks
    Processor 0: IA32_MCG_STATUS: 0x0000000000000004
    IA32_MC3_STATUS(0x40d): 0xbe00000000800400
    IA32_MC3_ADDR(0x40e): 0x00003f7f8f9ccb5f
    IA32_MC3_MISC(0x40f): 0x000000000003ffff
    Processor 1: IA32_MCG_STATUS: 0x0000000000000005
    IA32_MC3_STATUS(0x40d): 0xbe00000000800400
    IA32_MC3_ADDR(0x40e): 0x00003f7f8f9ccb5f
    IA32_MC3_MISC(0x40f): 0x000000000003ffff
    Processor 2: IA32_MCG_STATUS: 0x0000000000000004
    IA32_MC3_STATUS(0x40d): 0xbe00000000800400
    IA32_MC3_ADDR(0x40e): 0x00003f7f910c5aa8
    IA32_MC3_MISC(0x40f): 0x000000000003ffff
    Processor 3: IA32_MCG_STATUS: 0x0000000000000005
    IA32_MC3_STATUS(0x40d): 0xbe00000000800400
    IA32_MC3_ADDR(0x40e): 0x00003f7f910c5aa8
    IA32_MC3_MISC(0x40f): 0x000000000003ffff
    Processor 4: IA32_MCG_STATUS: 0x0000000000000004
    IA32_MC3_STATUS(0x40d): 0xbe00000000800400
    IA32_MC3_ADDR(0x40e): 0x00003f7f90a09905
    IA32_MC3_MISC(0x40f): 0x000000000003ffff
    Processor 5: IA32_MCG_STATUS: 0x0000000000000005
    IA32_MC3_STATUS(0x40d): 0xbe00000000800400
    IA32_MC3_ADDR(0x40e): 0x00003f7f90a09905
    IA32_MC3_MISC(0x40f): 0x000000000003ffff
    panic(cpu 4 caller 0xffffff800ecdcad9): "Machine Check at 0xffffff7f90a09905, registers:\n" "CR0: 0x000000008001003b, CR2: 0x00000001089ba000, CR3: 0x0000000011ba1000, CR4: 0x00000000000606e0\n" "RAX: 0xffffff8119485100, RBX: 0xffffff8021c65c00, RCX: 0x0000000000002833, RDX: 0xffffff8021c74c80\n" "RSP: 0xffffff811ab1bed0, RBP: 0xffffff811ab1bf10, RSI: 0x000000001dcd64ff, RDI: 0xffffff8021c65c00\n" "R8: 0xffffff8111bfd078, R9: 0x0000000000000000, R10: 0xffffff811ab1be20, R11: 0x0000000000000200\n" "R12: 0x00000000ffffffff, R13: 0x00000000ffffffff, R14: 0x0000000000000000, R15: 0x0000000000400001\n" "RFL: 0x0000000000010246, RIP: 0xffffff7f90a09905, CS: 0x0000000000000008, SS: 0x0000000000000010\n" "Error code: 0x0000000000000000\n"@/SourceCache/xnu/xnu-2422.110.17/osfmk/i386/trap_native.c :168
    Backtrace (CPU 4), Frame : Return Address
    0xffffff8111bede80 : 0xffffff800ec22f79
    0xffffff8111bedf00 : 0xffffff800ecdcad9
    0xffffff8111bee060 : 0xffffff800ecf3fef
    0xffffff811ab1bf10 : 0xffffff7f90a0c023
    0xffffff811ab1bf30 : 0xffffff800f0af292
    0xffffff811ab1bf80 : 0xffffff800f0af367
    0xffffff811ab1bfb0 : 0xffffff800ecd7417
    Kernel Extensions in backtrace:
    com.apple.driver.AppleAHCIPort(3.0.5)[7F56F309-28C2-342A-82C0-3908C164EBCC]@0xf fffff7f90a02000->0xffffff7f90a1bfff
    dependency: com.apple.iokit.IOAHCIFamily(2.6.5)[AB2D7D6A-B59B-3039-AE08-CBCC38208911]@0xfff fff7f8fd72000
    dependency: com.apple.iokit.IOPCIFamily(2.9)[4662B11D-2ECA-315D-875C-618C97CDAB2A]@0xffffff 7f8f27c000
    BSD process name corresponding to current thread: kernel_task
    Mac OS version:
    13E28
    Kernel version:
    Darwin Kernel Version 13.3.0: Tue Jun 3 21:27:35 PDT 2014; root:xnu-2422.110.17~1/RELEASE_X86_64
    Kernel UUID: BBFADD17-672B-35A2-9B7F-E4B12213E4B8
    Kernel slide: 0x000000000ea00000
    Kernel text base: 0xffffff800ec00000
    System model name: MacBookPro8,2 (Mac-94245A3940C91C80)
    System uptime in nanoseconds: 117766305248
    last loaded kext at 88599052330: com.tuxera.filesystems.tufsfs.fusefs_txantfs 2010.12.28 (addr 0xffffff7f914ef000, size 94208)
    loaded kexts:
    com.tuxera.filesystems.tufsfs.fusefs_txantfs 2010.12.28
    com.orderedbytes.driver.ControllerMateFamily 4.4.3
    com.orderedbytes.driver.CMUSBDevices 4.4.3
    com.apple.driver.AppleHWSensor 1.9.5d0
    com.apple.driver.AudioAUUC 1.60
    com.apple.macos.driver.AppleUSBEthernetHost 7.0
    com.apple.driver.AppleTyMCEDriver 1.0.2d2
    com.apple.driver.AGPM 100.14.28
    com.apple.iokit.IOBluetoothSerialManager 4.2.6f1
    com.apple.filesystems.autofs 3.0
    com.apple.driver.AppleMikeyHIDDriver 124
    com.apple.driver.AppleHDAHardwareConfigDriver 2.6.3f4
    com.apple.driver.AppleHDA 2.6.3f4
    com.apple.iokit.IOUserEthernet 1.0.0d1
    com.apple.Dont_Steal_Mac_OS_X 7.0.0
    com.apple.driver.AppleUpstreamUserClient 3.5.13
    com.apple.driver.AppleHWAccess 1
    com.apple.iokit.IOBluetoothUSBDFU 4.2.6f1
    com.apple.driver.SMCMotionSensor 3.0.4d1
    com.apple.driver.AppleLPC 1.7.0
    com.apple.driver.ApplePolicyControl 3.6.22
    com.apple.kext.AMDFramebuffer 1.2.4
    com.apple.driver.AppleIntelMCEReporter 104
    com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.2.6f1
    com.apple.driver.AppleMikeyDriver 2.6.3f4
    com.apple.driver.AppleBacklight 170.3.5
    com.apple.driver.AppleMCCSControl 1.2.5
    com.apple.AMDRadeonX3000 1.2.4
    com.apple.driver.AppleSMCLMU 2.0.4d1
    com.apple.driver.AppleMuxControl 3.6.22
    com.apple.driver.AppleSMCPDRC 1.0.0
    com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
    com.apple.kext.AMD6000Controller 1.2.4
    com.apple.driver.AppleIntelHD3000Graphics 8.2.4
    com.apple.driver.AppleIntelSNBGraphicsFB 8.2.4
    com.apple.driver.AppleThunderboltIP 1.1.2
    com.apple.driver.AppleUSBTCButtons 240.2
    com.apple.driver.AppleUSBTCKeyEventDriver 240.2
    com.apple.driver.AppleUSBTCKeyboard 240.2
    com.apple.driver.AppleIRController 325.7
    com.apple.driver.AppleFileSystemDriver 3.0.1
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeLZVN 1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
    com.apple.BootCache 35
    com.apple.iokit.SCSITaskUserClient 3.6.6
    com.apple.driver.XsanFilter 404
    com.apple.iokit.IOAHCIBlockStorage 2.6.0
    com.apple.driver.AppleUSBHub 683.4.0
    com.apple.driver.AppleSDXC 1.5.2
    com.apple.iokit.AppleBCM5701Ethernet 3.8.1b2
    com.apple.driver.AirPort.Brcm4331 700.20.22
    com.apple.driver.AppleFWOHCI 5.0.2
    com.apple.driver.AppleAHCIPort 3.0.5
    com.apple.driver.AppleUSBEHCI 660.4.0
    com.apple.driver.AppleUSBUHCI 656.4.1
    com.apple.driver.AppleSmartBatteryManager 161.0.0
    com.apple.driver.AppleHPET 1.8
    com.apple.driver.AppleACPIButtons 2.0
    com.apple.driver.AppleRTC 2.0
    com.apple.driver.AppleSMBIOS 2.1
    com.apple.driver.AppleACPIEC 2.0
    com.apple.driver.AppleAPIC 1.7
    com.apple.driver.AppleIntelCPUPowerManagementClient 217.92.1
    com.apple.nke.applicationfirewall 153
    com.apple.security.quarantine 3
    com.apple.driver.AppleIntelCPUPowerManagement 217.92.1
    com.apple.iokit.IOSerialFamily 10.0.7
    com.apple.kext.triggers 1.0
    com.apple.driver.DspFuncLib 2.6.3f4
    com.apple.vecLib.kext 1.0.0
    com.apple.iokit.IOAudioFamily 1.9.7fc2
    com.apple.kext.OSvKernDSPLib 1.14
    com.apple.iokit.IOSurface 91.1
    com.apple.iokit.IOBluetoothFamily 4.2.6f1
    com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.2.6f1
    com.apple.driver.AppleHDAController 2.6.3f4
    com.apple.iokit.IOHDAFamily 2.6.3f4
    com.apple.driver.AppleSMBusController 1.0.12d1
    com.apple.iokit.IOAcceleratorFamily 98.22
    com.apple.iokit.IOFireWireIP 2.2.6
    com.apple.driver.AppleBacklightExpert 1.0.4
    com.apple.driver.AppleGraphicsControl 3.6.22
    com.apple.driver.AppleSMBusPCI 1.0.12d1
    com.apple.driver.AppleSMC 3.1.8
    com.apple.driver.IOPlatformPluginLegacy 1.0.0
    com.apple.driver.IOPlatformPluginFamily 5.7.1d6
    com.apple.kext.AMDSupport 1.2.4
    com.apple.AppleGraphicsDeviceControl 3.6.22
    com.apple.iokit.IONDRVSupport 2.4.1
    com.apple.iokit.IOGraphicsFamily 2.4.1
    com.apple.driver.AppleThunderboltEDMSink 2.1.3
    com.apple.driver.AppleThunderboltDPOutAdapter 3.1.7
    com.apple.driver.AppleThunderboltDPInAdapter 3.1.7
    com.apple.driver.AppleThunderboltDPAdapterFamily 3.1.7
    com.apple.driver.AppleThunderboltPCIDownAdapter 1.4.5
    com.apple.driver.AppleUSBMultitouch 240.9
    com.apple.iokit.IOUSBHIDDriver 660.4.0
    com.apple.driver.AppleUSBMergeNub 650.4.0
    com.apple.driver.AppleUSBComposite 656.4.1
    com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.6.6
    com.apple.iokit.IOBDStorageFamily 1.7
    com.apple.iokit.IODVDStorageFamily 1.7.1
    com.apple.iokit.IOCDStorageFamily 1.7.1
    com.apple.iokit.IOAHCISerialATAPI 2.6.1
    com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.6
    com.apple.driver.AppleThunderboltNHI 2.0.1
    com.apple.iokit.IOThunderboltFamily 3.3.1
    com.apple.iokit.IOUSBUserClient 660.4.2
    com.apple.iokit.IOEthernetAVBController 1.0.3b4
    com.apple.driver.mDNSOffloadUserClient 1.0.1b5
    com.apple.iokit.IO80211Family 640.36
    com.apple.iokit.IONetworkingFamily 3.2
    com.apple.iokit.IOFireWireFamily 4.5.5
    com.apple.iokit.IOAHCIFamily 2.6.5
    com.apple.iokit.IOUSBFamily 683.4.0
    com.apple.driver.AppleEFINVRAM 2.0
    com.apple.driver.AppleEFIRuntime 2.0
    com.apple.iokit.IOHIDFamily 2.0.0
    com.apple.iokit.IOSMBusFamily 1.1
    com.apple.security.sandbox 278.11.1
    com.apple.kext.AppleMatch 1.0.0d1
    com.apple.security.TMSafetyNet 7
    com.apple.driver.AppleKeyStore 2
    com.apple.driver.DiskImages 371.1
    com.apple.iokit.IOStorageFamily 1.9
    com.apple.iokit.IOReportFamily 23
    com.apple.driver.AppleFDEKeyStore 28.30
    com.apple.driver.AppleACPIPlatform 2.0
    com.apple.iokit.IOPCIFamily 2.9
    com.apple.iokit.IOACPIFamily 1.4
    com.apple.kec.pthread 1
    com.apple.kec.corecrypto 1.0
    Model: MacBookPro8,2, BootROM MBP81.0047.B27, 4 processors, Intel Core i7, 2 GHz, 8 GB, SMC 1.69f4
    Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 512 MB
    Graphics: AMD Radeon HD 6490M, AMD Radeon HD 6490M, PCIe, 256 MB
    Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1333 MHz, 0x014F, 0x4A4D313333334B534E2D3447202020202020
    Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1333 MHz, 0x014F, 0x4A4D313333334B534E2D3447202020202020
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.100.22)
    Bluetooth: Version 4.2.6f1 14216, 3 services, 15 devices, 1 incoming serial ports
    Serial ATA Device: TOSHIBA MK5065GSXF, 500.11 GB
    Serial ATA Device: MATSHITADVD-R UJ-898
    USB Device: FaceTime HD Camera (Built-in)
    USB Device: Hub
    USB Device: Apple Internal Keyboard / Trackpad
    USB Device: BRCM2070 Hub
    USB Device: Bluetooth USB Host Controller
    USB Device: Hub
    USB Device: IR Receiver
    Thunderbolt Bus: MacBook Pro, Apple Inc., 22.1

    You might try removing these 3rd party applications and see if there is an improvement.
    com.tuxera.filesystems.tufsfs.fusefs_txantfs 2010.12.28
    com.orderedbytes.driver.ControllerMateFamily 4.4.3
    com.orderedbytes.driver.CMUSBDevices 4.4.3

  • Premiere CC 7.1 - Red frames in playback and export

    Having some problems after the 7.1 update.
    In a variety of projects, on a variety of footage, we're experiencing random fully red frames (#ff000). Sometimes there are 1-2 frames in a clip, and occaisionally it's 80%-90% of the frames in a clip (this is less frequent). It has never been all of the frames of a clip.
    This happens:
    - On an undrendered timeline (you'll be watching an edit and you'll see a red frame - if you scrub back to it it'll still be there)
    - On a rendered timeline
    - In exports
    Red frames that are visible on a timeline, are sometimes carried through to the export and sometimes not. Sometimes an exported file will display red frames that were not present on the timeline.
    Red frames seem to be based on clips, not sequence frames. For example, in one of my exports, I had video footage with a lower third graphic over it. In one frame of the export, a red box appeared over the graphic, but the main shot was not affected.
    This has happened to the following types of footage:
    - .MTS (from C100)
    - .MXF (from C300)
    - ProRes 422 MOV
    - ProRes 4444 MOV with alpha channel
    Fixes that seem to work:
    - If an export has red frames, re-export. Watch the new one like a hawk. Repeat until you get lucky.
    - If a clip on a timeline has red frames, force a re-render via a Crop filter or similar
    - Quit Premiere and reopen it
    System/environment details:
    - OSX 10.8.5
    - Premiere Pro CC 7.1
    - Mercury Playback Engine Software Only
    - Often (always?) I-Frame Only MPEG sequence settings
    - Much (all?) of the footage we've been working with has been on AFP shares via GigE with MTU of 9000
    I haven't been able to confirm yet:
    - Whether this ever happens with locally stored footage
    - Whether this ever happens when Queueing to media encoder (rather than Exporting from Premiere)
    - Whether changing to a QuickTime Desktop based sequence setting resolves the issue
    Is anyone else experiencing this issue? It's frutstratingly un-testable, since it seems to happen at random. We'll continue to gather data points though and see if we notice any other trends.
    Edit: Added additional system context

    the error also appears with PRORES 422 files, but only after a certain amount of source data from prores 422 clips is processed / read
    i made a test comp in AE with only one gigantic prores 422 source clip (8000 pixels x 1000 pixels @25fps) and the error first appeared at around 1500 frames read from the source file (equalling a few GB of source read and processed). after the red frames error appears once, the erroneous red frames appear more often but never in the same place when rendering the same comp several times)
    i also made a test comp containing only a few full HD prores 422 clips (1920 x 1080, @25fps), there the error appeared only seldom (but still randomly). so it can be that a broader user base never experiences this erroneous behaviour at all.
    i also made a testcomp containing about 40 full HD prores 422 clips (each 1920 x 1080, scaled down to 10% in size and distributed all over the comp so i can see them all at once). the erroneous red frames appeared within the first rendered frames!! obviously, many qt files had to be open and read in parallel, and so the error appeared from the very beginning of the rendering / export.
    i suspect that the AE / PR applications open a RAM buffer for each open prores source file they need to read, and that this buffers somehow becomes compromised when it overflows and when buffer resize / buffer clear / flush operations take place.
    of course i tested all sorts of RAM assignents for MP rendering (1GB per core, 2GB, 4GB, 6GB) and i rendered with several different settings of how many cores and ram should be available to other tasks. but the error always appeared. randomly.
    --> fact in AE is, that nearly all MP renders / exports using prores clips as source files contained the bad red frames. when rendering without the MP option on (but of course up to 20x slower) so far i never experienced this error (of course always after fresh restarts once the error appeared)
    PLEASE FIX THIS ASAP
    mac pro 2011, 12 cores, osx 10.8.5, 64 GB ram, angelbird SSD, ati hd radeon 5770 1GB

  • Still Having Random Red Frame Issues

    I've been reading several threads about the dreaded red frames when exporting through Premiere Pro CC or Adobe Media Encoder CC.  I have installed the Premiere Pro CC (7.2.1) update and I have cleared my cache and re-rendered previews for the sequence.  My source clips in my sequence are MXF files (XDCAM HD 35) and I am operating on a Mac OSX-Version 10.8.5
    What is really frustrating is that I'm dealing with multiple clips in this format and it is totally random as to which ones are affected.  Sometimes I don't even see the red frame when watching the clip through, but when I export it, it's there.  I know that the fix mentioned in the previous thread was supposed to help those using ProRes files, but the MXF files are still being affected.
    Thanks for any and all help.

    Hi Kevin,
    I'm still having this problem with the red frame errors.  Also, it's not
    limited to Premiere Pro.  Just trying to convert one .mxf file to a .mov or
    .mpg file through Media Encoder (while bypassing Media Encoder) is causing
    the same issue.  And it's totally random and intermittent with respect to
    which file I send through.  Also, sometimes, sending the file that didn't
    work the first time back through AME again, sometimes converts successfully
    and sometimes doesn't.  There is no constant which makes it very difficult
    to pinpoint the problem.
    On Thu, Jan 16, 2014 at 11:51 AM, Michael Nanus

  • That red frame discussion

    So i have been dealing with red frames for about a year and a half now -
    - In Premiere pro CC and early CC 2014 versions, .MXF footage used to red frames and relink badly on multi spanned clips if the sidecar files were detected by premiere. This was a major bug because your edit would now relink to bad timecode. The handling for that was deleting any kind of metadata before importing your .MXF files. this worked 99% of the time for me - did not get much bugs after that.
    - Skip to what i believe was the 8.0.0 version, and most importantly the 8.0.2 - i do not have re link issues, however red frames appear on export nearly everytime. With the media encoder log you can see how much red frames you have, but no timecode and its still a pain in the *** to double export(correcting the red frames on the first export file).
    - From the few adobe employee posts i have read, the way to counter this is - import the card while maintaining the structure, then import footage via the Media browser. This should technically handle any bugs. I have not tested this yet, however i already know that sometimes i get mxf files without card structure(director's sometimes create their bins at the Mac OS X Finder level)
    Im hoping adobe fixes this issue ASAP - i undestand that red frames are only an indicator of a bigger problem, but this problem is making me consider converting all my footage to prores before import, thus turning my premiere pro cc in FCP 7.

    Hello Adaptat1on,
    - From the few adobe employee posts i have read, the way to counter this is - import the card while maintaining the structure, then import footage via the Media browser. This should technically handle any bugs.
    With the release of Premiere Pro CC 2014.2 (8.2), we believe we have solved the "red frames" issue with .mxf files.
    If you are working with an earlier version of Premiere Pro or have updated a project file from a previous version of Premiere Pro to 8.2, you might still see them.
    The method of importing these files is correct as you outlined above. Copy the SD card to your HD, then import via the Media Browser.
    I have not tested this yet
    However, this is precisely the right way to import footage coming from a camera's SD card.
    However i already know that sometimes i get mxf files without card structure(director's sometimes create their bins at the Mac OS X Finder level).
    I would communicate with your colleagues and inform them of how you would like your footage prepared. You should state that you will be saving them money by doing so as you won't have to troubleshoot red frames issues which could still occur with raw .mxf files even in 8.2. Tell them turn around time will be faster, as well. They will listen to you when you speak their language (saving them time and money gets their attention quickly).
    Im hoping adobe fixes this issue ASAP - i undestand that red frames are only an indicator of a bigger problem
    All our fixes are in 8.2. Please create new projects in version 8.2, ingest the footage correctly, and you should have no trouble with red frames. If you do, please file a bug report and send me a PM.
    This problem is making me consider converting all my footage to prores before import, thus turning my premiere pro cc in FCP 7.
    That's certainly an alternative, but I'd try the method previously outlined before doing anything rash like transcoding. That said, certain cameras produce beautiful pictures but create files which perform poorly in Premiere Pro. I'm most frequently tempted to transcode Canon footage, as that gives my Mac Book Pro the most trouble.
    Hope this info helps.
    Thanks,
    Kevin

  • Can't get rid of Red Frames or Audio dropouts on PPCC7.2.2

    I'm on a Mac OSX 10.9.1 using PPro CC and Encoder 7.2.2(33). 
    Have tried using the "clear the media cache" trick; worked once, but not the second time.
    Still getting Red Frames on long exports (more then 8 min).
    Also, I get blasts of white noise now and again which scare me out of my chair.
    The Noise blasts and red frames happen about 5x in a 00:28:30 Export.
    What can I do to rid myself of these problems?

    Ask in the Premiere forum and by all means be a lot more specific - proper system info, exact sequence settings, source file info, export settings.
    Mylenium

  • Red Frames and .mxf read failures PP CC 2014 8.1 update. Oct 6.  Anyone else see the new update fail? Any suggestions?

    Hi,
    I cut 9 hours worth of broadcast video in PP CC 2014 8.0. (The yellow interface.) I had no issues. It was all great. For some reason, before I exported the finished cuts for broadcast, I updated the Adobe CC 2014 suite to v1.8.0.447 (PP has the blue interface). I feel stupid. I broke my own rule of not updating software until the projects you work on are done. Now I can't open this project without Red Frames in my timeline and in my exports. I have been reading about this Red Frame that seemed to first appear in PP CC 7. (Maybe even as early as 2006) I never had the problem then, I run Premiere Pro everyday.
    My Issue seems to be a bit different than most of the issues that have read. I have cleared the cache, & I have ditched the preview files. This did not fix it as stated it would in previous forum posts.  I have moved the footage location from a server to a local thunderbolt SSDrive and renamed the folders and re-linked the video footage. Still Red Frames.
    What is odd, is when I boot up the project and after all media has loaded, it looks like it is going to work for a few minutes. I get happy and scrub the timeline checking for the red frames, hoping the problem solved when I cleaned the cache etc.. Everything seems to be fine, audio synch, picture, lower thirds and graphics all appear fine. Then the red frames appear over time, and by 5 minutes after scrubbing, I see mostly red frames. Audio is still there though. Even weirder, is that when I resize the height of the video track, the red frame comes and goes with no real pattern.  The clip preview picture flickers with the red frame. The red frames export through through Premiere and through a Media Encoder cue which say .MXF read error so I'm hooped. ( it does render the video, but has the red frames )
    I run a Mac Pro;
    OSX Yosemite 10.10
    3.5 GHz 6-cor Intel Xeon E5
    16 GB Ram
    AMD FirePro D500 3072 MB
    Canon XF-305
    .MXF files
    1080p 29.97
    5 Cam Multicam Seq.
    Adobe CC 2014
    Version 1.8.0.447
    released on October 6, 2014
    I am noticing something interesting with my source footage folders. I am getting some .mxfindex files with really long names, like temp files almost, that don't go away. I still get Red Frames after deleting them, clearing cache, changing drive locations and file and folder names and relinking. When I delete these long files the software wont boot the project very well and crashes a few times before it opens, still with red frames. This problem with this project occurs on every computer (4)  in the studio, which are the same as mine, we all updated at the same time. 
    Files look like this:
    What happened in that update? Is there a fix for this? Any suggestions? If not, Is it possible for me to roll back my whole CC 2014 version to 8.0?  I am terrified to open any other of our projects... I am under time pressure and am starting to do the re-edit of this in CS6 which seems to run flawlessly, but because of Adobe's RIDICULOUS FAIL in backward compatibility, I can not open this project in anything but PP CC 2014. 120 hrs of lost editing will certainly have me scratching my head about continued use. Any suggestion, links or information would be appreciated.
    Thanks .

    Hi 5neaky c,
    5neaky c wrote:
    For some reason, before I exported the finished cuts for broadcast, I updated the Adobe CC 2014 suite to v1.8.0.447 I feel stupid. I broke my own rule of not updating software until the projects you work on are done. Now I can't open this project without Red Frames in my timeline and in my exports.
    You should still have a Premiere Pro CC 2014.0.1 (8.0.1) project file available to you by default. Can't you go back to that version and complete your project? That's what I'm recommending those having this problem do.
    5neaky c wrote:
    I have been reading about this Red Frame that seemed to first appear in PP CC 7. (Maybe even as early as 2006) I never had the problem then, I run Premiere Pro everyday.
    As long as you ingest the footage via the Media Browser and do not update the project file, you shouldn't have issues like this. I have heard complaints in new projects with Premiere Pro CC 2014.1 (8.1), so I have reopened a previously closed bug.
    5neaky c wrote:
    My Issue seems to be a bit different than most of the issues that have read. I have cleared the cache, & I have ditched the preview files. This did not fix it as stated it would in previous forum posts.  I have moved the footage location from a server to a local thunderbolt SSDrive and renamed the folders and re-linked the video footage. Still Red Frames.
    If this is not working, please complete your project in Premiere Pro CC 2014.0.1 (8.0.1)
    5neaky c wrote:
    What is odd, is ...
    Everything seems to be fine...
    Then the red frames appear over time….
    Yes, I've seen this with another customer's updated project.
    5neaky c wrote:
    I am noticing something interesting with my source footage folders. I am getting some .mxfindex files with really long names, like temp files almost, that don't go away. I still get Red Frames after deleting them, clearing cache, changing drive locations and file and folder names and relinking. When I delete these long files the software wont boot the project very well and crashes a few times before it opens, still with red frames. This problem with this project occurs on every computer (4)  in the studio, which are the same as mine, we all updated at the same time.
    Sometimes, deleting sidecar files can help the situation but not always. It looks like you are having trouble when deleting them.
    5neaky c wrote:
    What happened in that update? Is there a fix for this?
    A bug that was fixed for red frames in 8.1 was somehow broken by the time we shipped this version. We have reopened the bug, but currently, there is no fix.
    5neaky c wrote:
    If not, Is it possible for me to roll back my whole CC 2014 version to 8.0?
    Yes, see my blog post here: Install a previous version of any Creative Cloud application
    Included in the post is a patch for Premiere Pro CC 2014.0.1 (8.0.1).
    5neaky c wrote:
    I am under time pressure and am starting to do the re-edit of this in CS6 which seems to run flawlessly, but because of Adobe's RIDICULOUS FAIL in backward compatibility, I can not open this project in anything but PP CC 2014.
    Thanks .
    You can always try exporting a FCPXML for backward compatibility, but for complex sequences (like multicamera), this isn't always an option. There aren't many NLEs providing backward compatibility, sorry. Feel free to request that, if you like, here: http://adobe.ly/feature_request
    Thanks,
    Kevin

Maybe you are looking for