Red frames in Sequence/Exports

Hello. I'm experiencing red frames (some longer than others) within my timeline and on exported files. Sometimes they wont be on the timeline but appear in the export file and vice versa. I'm using XAVC-L codec from my Sony FS7 camera in a AVCHD 1080p timeline. I'm trying to export to H264 .mov files. This happens in both Premiere and by going through Media Encoder.
Specs:
Premiere Pro CC 2014.2 Release 8.2.0 (65) build
(New) Mac Pro Late 2013
2.7 GHz 12-Core Intel Xeon E5
32GB RAM
AMD FirePro D500
OSX 10.9.5

Hi,
Have you tried exporting to a different format? I would suggest so.
You can also try to change the Video Renderer to Mercury Playback Engine software only under File > Project settings > General
Thanks,
Rameez

Similar Messages

Red Frames in Playback and Export

After finding out that others have had this problem and found solutions, I expected the solutions to work, but no luck so far.
I am working with HDV 1080i60 footage in Premiere Pro CC 7.2.1 on OS 10.9.1. When I play my footage through the source window (by double-clicking it in the Project window) or on a sequence timeline, I see intermittent red frames - a lot of them. The red frames persist through export, leaving me with no way to edit this footage except to transcode it to a different format - presumably with an encoder other than Adobe Media Encoder.
Adobe, you have posted possible solutions for other people with this problem, but obviously it persists. What's the nex step?

LFedit, my red frames do not appear only on cross dissolves. They appear during normal playback in the source monitor as well as in the program monitor AND in the small preview area in the project window.
I've seen posts about this problem from the end of 2013, but I'm glad to know I'm not the only still experiencing trouble. I've already submitted a bug request to Adobe. Please do the same, LFedit. The more people report it, the more likely Adobe will pay attention.

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

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

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

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 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

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.

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

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?

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 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 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.

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.

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

Red frames in Sequence/Exports

Similar Messages

Maybe you are looking for