Red flash frames on C300 sequence exports

Still no fix for this widely noted issue, Adobe?
I'm currently trying to get a job completed and the process of getting anything out of Premiere is absolutely painful...
I have tried all the suggested solutions - trashing preferences and media cache files. I saw somewhere that removing any clips that are a different codec to your footage (in this case it's MXF files from a C300) fixed the problem. Tried switching hardware GPU acceleration off. None of these things have worked. I've had to export the sequence several different times and then stitch these exports together in a new sequence (skipping out the numerous red flash frames, of course) just to get a clean export out. Pitiful.
I can see reports of this happening over a year ago - why hasn't it been fixed? I think it's pretty scandalous that this hasn't been sorted - Premiere is advertised as being able to handle these camera formats natively...well, it can't right now for me if using the native camera files results in issues like this.
Has anyone found any other work arounds that I haven't noted above?

Hi Mark,
According to the "about Premiere Pro" window, I am on 8.2.0 (65) build.
I have had the same issue exporting out of both Premiere and Adobe Media Encoder - the build of AME is 8.2.0.54.
Adam

Similar Messages

  • Red flash frame

    Hello,
    As instructed in this thread, I've started a new thread regarding this problem.
    I work as an editor at a channel with Premiere CC 7.2.1 installed as our NLE. We have several 27" iMacs, 21" iMacs and about a dozen MacbookPro's.
    We have experienced the red flash frame several times. It has appeared on MXF and ProRes exports. In one case, (using a MacBook Pro) it was generated on a ProRes export, but not on the low res proxy (unsure of format, will update as soon as I know) that is generated when we export to Sienna.
    Red frames have also been introduced on MXF exports from iMac's (i7 27"), via ethernet to an Isilon.
    I've taken the advice on the previous thread and told an editor to delete her cache and re-export. She did this and the red frames were not on the new export.
    However, we have a high turnaround of news and current affairs content where a red frame may not be spotted. This could happen in a SOT or PKG for news. This file with the red frame could be loaded into ENPS and played out live. As the producer will be viewing the proxy in Sienna, they will not see the red frame as it'll only be on the ProRes, which is in a TX server they do not have access too.
    The added danger is that if that section of programming is repeated, it will not be TX'd live from in house, it will be TX'd by a third party. Who (I assume) will pick up the red frame and hit us with a fine.
    So, Adobe, is there a fix coming? Or is there anything we can do to ensure this does not happen?

    To add, the low res proxy is an MPEG movie at 640 x 360, .mov suffix. No red frames appear on this.

  • Has anyone solved or worked around the After Effects CC red flash frame glitch?

    I can't find any mention on any forums of the After Effects CC red flash frame glitch later than Feb. 2014. I just installed 12.2 (which was my first CC version) on my macpro and started getting the red flash frames randomly, but with increasing frequency, in my projects. I have never had this problem before on any previous computer or version for AE. The forums I've read have referenced ProRes source footage, outputs to ProRes, and lens blur. My project uses all of these things.
    If there is a universally accepted solution/work around, I haven't seen it definitively. Do I not use ProRes source footage? Do I not render to ProRes 4444? Do I not use the lens blur effect? Do I give up and go back to CS6?

    Hi Keith,
    I have the "same" issue with the red frames in AFX CC
    I have seen them first, as I resized a prores4444 HD to a smaller format and saw the redframes in the preview window.
    Setup in AFX: I created a comp from the HD Prores4444 footage and put this comp in a comp with resolution of 960x540.
    The output format was again prores4444.
    I shuttled through the clips in the small comp and I saw the red frames too.
    When I switched to the HD comp at the same position everything was fine.
    I "solved" the problem by flushing the cache, twice. Because after the first purge I was only able to render the first clip. The second one had the red frame problematic again.
    Maybe It has something to do with hardware accelerated layers.
    I'm using a MacPro running OSX 10.8.5 with a Nvidia GTX680.
    Cheers
    Michael

  • MPEG Streamclip "Red Flashing Frames"

    I am having a problem with mpeg streamclip. I keep getting lots of red flashing frames. These happen when i am playing a dvd or even a .mov footage. I have re-installed also. I am running 10.6.5 on intel chip. Any help would be greatly appreciated or if there is a different forum, please let me know.

    I think it's a system glitch because it started happening to me just recently in Final Cut Pro. When I play a clip in the viewer window, it flashes solid red like every half second. There aren't actually any red frames in the clip and once its placed on the timeline it plays fine.
    More evidence that it's a glitch is that it'll sometimes go away on its own, sometimes (like now) go away if I pause the clip, go to another program and come back a few seconds later. Other times I have to quit and relaunch Final Cut to solve it.
    The only consistent thing I've noticed is that it never happens when I first launch the program. It seems to happen after I've been working in it for at least a few minutes.
    Message was edited by: Tonya Goodnow

  • Flash Frames on h.264 Export

    We are exporting an edit for web using the h.264 codec. The edit plays through fine on the timeline but each time we export there are a couple flash frames in the edit. These flash frames usually occur within a second of an upcoming cut and will flash a frame of the next shot we are going to prematurely.
    My initial thought is that it has to do with the Key Frame settings on the export or is perhaps due to bad render files. If anyone has experienced this and could point me in the direction of what the issue is that would be much appreciated.
    Tom

    If you are exporting to h.264 directly from the FCP timeline, try exporting the sequence as "current settings" then do the conversion in Compressor.
    x

  • Black flash frames introduced upon QT export

    I'm having an issue where upon exporting a QT of my sequence, it introduces one-frame black flash frames in between every cut, both in the QT and in the sequence. This is a standard DV NTSC 48kHz sequence. Running FCP 6.0.5. Any ideas?

    Is this in your timeline too? Zoom in between two cuts to see if there is a gap between clips.

  • Flash frame in nested sequence won't go away

    When I open up the sequence to play it, it's fine. When the sequence itself is played, It flashes over the first part of her sentence, then cuts in as she's saying a particular word.
    I dont show that there's anything to be rendered. I've done everything i can think of, including exporting and hoping that would fix it, closing out fcp and reloading the project, etc.
    Anyone ever run into this?

    Are you saying that your nested sequence is starting at a later point than the inpoint of the first clip contained within it? A nested sequence can be trimmed just like a regular clip, so you may just need to drag its in-point to the left (or perform a slip-edit).
    If this is not the problem, you could certainly have a phantom render file (this happens most often with nested sequences). You can usually kill it by forcing FCP to re-render that section of the timeline. There are a billion ways to do this–my favorite is selecting a clip (or range of clips) located on the section of your timeline where the phantom is hanging out, then hit Ctrl-B twice to toggle their visibility on and off. A fresh re-render of that timeline section should confirm that your phantom has finally been released to render file heaven.
    Zap
    Dual 2 GHz PowerPC G5 Mac OS X (10.3.6)

  • 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

  • How do I get a lip sync flash frame sequence to encode properly

    I built a flash frame sequ
    ence in Premiere.  It is 2 seconds long with the
    first two frame white and the remaining time black
    frames. This is repeated for 1 minute.  If I encode it in non-compressed AVI it is correct.  If I use
    MPEG2 or H.264 to build a transport stream, I see two white frames
    as I would expect,then black frames for the rest of the sequence.  Over 15 seconds, I will start to see three frames, gray, white and gray again.  Eventually, the white or gray frame starts two frames later than it should.  I built this as a 720P/60 sequence with non-drop frame timecode.  I have tried all I frames and the same issue occurs.  The GOP structure does not seem to have an effect.  There is no audio in this stream.  It as if it cannot handle the quick and short transistion from white to black.  There are some advanced settings for MPEG 2 but I cannot see where they are explained in the Premier help document.  I need this stream to measure latency on a piece of video equipment.
    Thanks
    Ralph

    Bill,
    Your answer gave me a hint to what was happening.  I'm fairly new to Premier and took for granted that the preset I chose at the begining of the program would carry through to the sequence, wrong!  I found another discussion that talked about resetting the properties of a sequence.  I expanded the project box a little and saw that it said my sequence was 59.94 frame rate not 60.  I followed the instructions on the other discussion.  File, new sequence, general, editing mode, and frame rate.  The frame rate was set to 59.94 not 60.  I reset it to 60, closed all the menues and deleted the original 59.94 sequence.  The new sequence I just created shows a 60 Hz frame rate.  I exported my lip sync project as an MPEG 2 transport stream and it was correct according to our MPEG analyzer.
    Thanks again for the help.
    Ralph

  • Final Cut Pro X Image Sequence Export missing frames per second option?

    I am using the trial version of Final Cut Pro X.  I can export an image sequence but it will only allow me to do so at 30 frames per second -every single frame! 
    So a 10 min movie takes half an hour to export 20,000+ frames that no one on earth has time to look thru.
    In my old Final Cut Express I was able to choose 1 or 2 frames per second, which was just right.
    What am I missing?
    Do I need to buy Quicktime Pro or Compressor to allow me to export image sequences without exporting every frame?
    Why would Apple even have an image sequence export if it only allows you to export every frame, or it that only in the trial version?
    Thank you

    I found a free option for you, if you don't already have Compressor 4.
    In FCPX create your movie. Then SHARE as a Master File.
    Get MPEG Streamclip, which is a free app available here.
    http://www.squared5.com/svideo/mpeg-streamclip-mac.html
    Drag your Master File into MPEG Streamclip.
    In MPEG Streamclip, select FILE/EXPORT TO OTHER FORMATS.
    In FORMAT: choose IMAGE SEQUENCE
    In OPTIONS, choose your frame rate.

  • Changing Frame Padding On Image Sequence Exports, Media Encoder

    Hello Adobe World,
    I am using dynamic link from After Effects to Media Encoder and I am trying to export an image sequence with a specific numbering system for input into software code. Is there any way to change the frame padding or change the numbering system for Image sequence exports?
    We are trying to speed up our workflow by Batch rendering from AME. AE does let us set our frame numbering and gives us an option for creating sub-folders (it's surprising the AE is much more organized in it's export options that AME). We need to be able to render more than one thing at a time and need to keep working in AE while the files are rendering. I have not found a workable background rendering plug-in for CC14. We could use AME if there is a way to fix the Number system.  We are working on a PC Windows 8. I can provide more system specs if it is necessary.
    Side note: in AE we can use [#] to set the numbering value and in AME it does not work.
    Thank you for your help!
    Still looking for an answer on this.... it's been 2 months.... Adobe team? Anyone?

    Change it to this?

  • Red frames on the movie exported

    Hi, I exported a project to MPEG2 blu-ray (source XMF files, camera Canon XF100), and I have several red frames within the movie. It's almost unusable. I have tried to do media cache cleaning, re-rendered the effects, but still without success. I work on Macbook Pro with OSx Yosemite. Premiere is 2014.2 v8.1 Caravan build 8.2.0.
    Could someone have experienced this issue?
    Does Adobe have a fix?
    In the meanwhile, I prefer downgrade to CS6, that is rock solid. The problem is the waste of time to start from zero, because the project isn't down-compatible. This is a crazy way by Adobe to handle a downgrade!
    Bye

    Hi, I still have the issue. I'm using Premiere Pro 2014.2 v8.1 Caravan 8.2.0 (65) build, on Macbook Pro, half 2012, Yosemite 10.10.2. Several red frames in the output exported (MPEG2-bluray) from MXF source (Canon XF100). After several export try, the red frames still remain, but they are located in different positions. I confirm that the same clip exported using Premiere CS6 (and also using Premiere CC 2014.0 v8.0) are OK, without red frames!!! The big issue for me is that the project cannot be opened by previous Premiere releases, and I lost weeks of work!!!
    Adobe, any news? I'm available to give you all the information you ask to test the case.

  • Won't start -- five red-flashe​s sequence

    My PlayBook worked just fine until last evening. Battery life was good; with no start-up or play issues. Original model; has worked well for nearly 3 years. Has latest OS. Never been dropped or abused in any way.
    Last night it wouldn't wake up. I did a hard reboot (power button for 15 seconds) and then it seemed to start, but when the GUI came up the screen was insensitive: no reaction to touch anywhere. I then did a hard reset (both volume buttons plus power button), and now all I can get is a five-red-flashes sequence: flash pause flash flash flash pause flash -- longer pause, then repeat.
    I had the BlackBerry charger plugged in overnight...  no change, still get the five-red-flashes. Tried another hard reset, same result.
    Any help would be appreciated! Thanks.
    Solved!
    Go to Solution.

    Yasminm wrote:
    Hello... I started to upI date my OS yesterday when I got the prompt of a new OS - I did over wifi on the phone, the phone died and I couldn't turn it on anymore and their was the rapid fast red light that keeps happening. I put the phone on the charger and still today that light is going on and the phone still doesn't turn on. I tried to update the OS via PC today and it got to 98% and said it can't go further. Please help!
    you do realize this is the playbook area
    Click here to Backup the data on your BlackBerry Device! It's important, and FREE!
    Click "Accept as Solution" if your problem is solved. To give thanks, click thumbs up
    Click to search the Knowledge Base at BTSC and click to Read The Fabulous Manuals
    BESAdmin's, please make a signature with your BES environment info.
    SIM Free BlackBerry Unlocking FAQ
    Follow me on Twitter @knottyrope
    Want to thank me? Buy my KnottyRope App here
    BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V

  • Who can help - my Playbook just flashes 1 + 4 in sequence red

    Playbook flashes 5 times,1 red flash than 4 red flashes
    restart with power button doesn't work (pressing button for 20 seconds
    pressing power button  and + and -  buttons doesn't work as well
    connecting to desktop software doesn´t `t work as the PC doesn`t  "see " my playbook.....
    Any ideas? Many thanks in advance!!!!!!!!!!!!!!!!!!!!!

    Follow directions in the other thread where you've already posted, to deep charge the PlayBook.
    Please don't double post. Thanks!
    1. If any post helps you please click the below the post(s) that helped you.
    2. Please resolve your thread by marking the post "Solution?" which solved it for you!
    3. Install free BlackBerry Protect today for backups of contacts and data.
    4. Guide to Unlocking your BlackBerry & Unlock Codes
    Join our BBM Channels (Beta)
    BlackBerry Support Forums Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • Red Flashes in MXF video

    Hi I am having major problems with red frames appearing at random in video i edit that is from my Canon XF300 camera. This problem has appeared since the last upgrade. I have never had this problem before and have been testing old video from before the upgrade and new video shot recently with the same problem. I need a solution to this problem as I run a business and cannot send my customers video with red flash in it. I have been tying to find a way to contact Adobe but there seems to be no direct way of communicating.
    I have been monitoring this for some time now and have tried a number of solutions my self like updating to the latest Canon XF utility to no avail.
    Here is a list of errors that have occurred over the last few weeks from different projects.
    MXF Errors Prem CC
    MXF read error in '/Volumes/CEMacTravel/Pysch SP At Deakln 10-
    Nov-2014/XF300 Video Clips/20141110170959/AA016802.MXF" at frame
    -1.
    MXF read error in '/Volumes/CEMacTravel/Pysch SP At Deakln 10-
    Nov-2014/XF300 Video Clips/20141110170959/AA016802.MXF" at frame
    -1.
    19-Feb-2015
    MXF read error in '/Volumes/CEMacEdit 01/Pysch SP At Deakln O3-
    Dec-2014/Video Files/XF300 Video Clips/20141203 171415]
    AA020403.MXF" at frame -1.
    MXF read error in "/Volumes/CEMacEdit 01/Pysch SP At Deakln O3-
    Dec-20l4/Vldeo Files/XF300 Video Clips/20141203 171415]
    AA020403.MXF" at frame -1.
    MXF read error in '/Volumes/CEMacEdit 01/Pysch SP At Deakln O3-
    Dec-2014/Video Files/XF300 Video Clips/20141203 171415]
    AA020403.MXF" at frame -1.
    MXF read error in "/Volumes/CEMacEdit 01/Pysch SP At Deakln O3-
    Dec-20l4/Vldeo Files/XF300 Video Clips/20141203 171415]
    AA020403.MXF" at frame -1.
    MXF read error in "/Volumes/CEMacEdit 01/Pysch SP At Deakln O3-
    Dec-2014/Video Files/XF300 Video Clips/20141203 171415]
    AA020403.MXF" at frame -1.
    MXF read error in "/Volumes/CEMacEdit 01/Pysch SP At Deakln O3-
    Dec-20l4/Video Files/XF300 Video Clips/20141203 171415]
    AA020403.MXF" at frame -1.
    MXF read error in '/Volumes/CEMacEdit 01/Pysch SP At Deakln O3-
    Feb-2015/XF300 Video/20150203165521/AAO22-101.MXF“ at frame -1.
    MXF read error in '/Volumes/CEMacEdit 01/Pysch SP At Deakln O3-
    Feb-2015/XF300 Video/20150203165521/AAO22-101.MXF“ at frame -1.
    MXF read error in "/Volumes/CEMacEdit 01/Pysch SP At Deakln O3-
    Feb-2015/XF300 Video/20150203165521/AAO22-101.MXF" at frame -1.
    MXF read error in "/Volumes/CEMacEdit 01/Pysch SP At Deakln O3-
    Feb-2015/XF300 Video/20150203165521/AAO22-101.MXF" at frame -1.
    MXF read error in '/Volumes/CEMacEdit 01/Pysch SP At Deakln O3-
    Feb-2015/XF300 Video/20150203165521/AAO21801.MXF" at frame -1.
    MXF read error in "/Volumes/CEMacEdit 01/Pysch SP At Deakln O3-
    Feb-2015/XF300 Video/20150203165521/AAO21801.MXF" at frame -1.
    MXF read error in '/Volumes/CEMacEdit 01/Pysch SP At Deakln OS-
    Feb-2015/XF300 Video/XF300-01/20150206070552/AA024601.MXF" at
    frame -1.
    MXF read error in '/Volumes/CEMacEdit 01/Pysch SP At Deakln OS-
    Feb-2015/XF300 Video/XF300-01/20150206070552/AA024601.MXF" at
    frame -1.
    03-Mar-2015
    MXF read error in "/Volumes/CEVideo-01/Cabrini Q&A 03-Mar-2015/Video
    Files/XF30O Video/20150303155505/AA025805.MXF" at frame -1.
    MXF read error in '/Volumes/CEVideo-01/Cabrini Q&A 03-Mar-2015/Video
    Files/XF30O Video/20150303155505/AA025805.MXF" at frame -1.
    05-Mar-2015
    MXF read error in "/Volumes/CEVideo-Olffoorak College/2015/Toorak
    Talks International Womens Day 04—Mar-2015/Video & Audio Files/XF3OO
    Video/20150304193907/AAO25902.MXF" at frame -1.
    MXF read error in '/Volumes/CEVideo-Olffoorak College/2015/Toorak
    Talks International Womens Day 04—Mar-2015/Video & Audio Files/XF3OO
    Video/20150304193907/AAO25902.MXF" at frame -1.
    I am running Premiere Pro CC V 8.1 Caravan
    Thank you.
    Regards, Cliff Elliott

    not sure of any solutions, but here are some of the other threads here with that same problem.
    RED FRAMES with MXF files in latest Premiere CC2014 update 8.1.0 (81)
    MXF XDCAM OP1a Red Frames in Media Encoder
    RED FRAME in source_Clip or Program_sequence of a media 720p MXF whit AFD(active format descriptor)
    Premiere CC 7.1 - Red frames in playback and export
    Red Frames and Freezed Frames with XDCam and C300 Files on export an edit
    MXF files show up as Red on timeline and in export

Maybe you are looking for