Red Frames - Version 7.2.1

I know there have been a lot of discussions about red frames in CC, I think I've read them all and tried every solution, here's my situation in case there is something that I missed.
I work with many long (2 hour plus) .mov files with the AVdn codec and after an upgrade to CC on Friday these files now have red frames every 5 minutes or so (maybe more) when opened in anything CC.
I'm using 7.2.1, have tried deleting my media cache, have tried opening, closing, reopening, restarting, exporting, copying, pasting, and nothing works.
Is there a solution that I missed BESIDES the following:
Re-exporting all my files with a different codec and using Media Encoder CS6
Rolling back to a prior version

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

Similar Messages

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

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

Captivate 7 not showing the red frame when recording a slide

I've been using the "Record Additional Slides" button since Captivate 5, and never run into this problem: the red frame that lets you define what you want to capture is not displaying. When I try to record, Captivate captures a portion of the software window, and the desktop. How can I force the red frame to display?
Thank you for your help!
Heloisa
*** By the way, it is happening when I run Captivate from my Apple computer. I just tested running Captitvate on my parallels machine, and the frame does show up.

Hello,
Just to clarify, the problem (no red frame while recording slides) happens only on the Apple version of Captivate. It runs fine on my parallel machine, however I am running a trial version there. My license is for the Apple platform. I'm concerned because my trial period will expire soon. the weird thing is that the Captivate that I have in my machine at home does not present this behavior. Only the one in my work machine.
The project resolution is 930px x 697px
This is the 14th module that I am developing for a training suite.I have never encountered this problem before. It all started after the Maverick's fiasco
So do you think I should uninstall Captivate and start a brand new install? I tried changing the name of the folder but that didn't help much.
Thank you!
Heloisa
*****I just uninstalled and re-installed Captivate 7 7o my apple machine, but the problem persists. ;(

MXF XDCAM OP1a Red Frames in Media Encoder

It was advised in the other thread about red frames to start a new one for this kind of the red-frames-problem.
So my usual workflow is:
Export a masterfile from Premiere via Mediaencoder as XDCAM OP1a 1080p5025fps.
From that I generate various versions for my clientst directly in MediaEncoder. Almost only h264 in all different sizes.
Since the update 3 days ago this doesn't work anymore. The h264 files that are made from the mxf have many red frames and mediaencoder reports errors like:
: MXF read error "\\?\V:\xxxxx-1080p-XDCAMHD50PAL.mxf" frame 383.
In a 3 minute clip 8 of those errors at differnet frames are reported. I suppose that is where the red frames are generated.
Yesterdays update (the Audio Buzz fix) did not change the redframe problem.
So I used my 2nd installation that was not updated for weeks. There everything works as expected.
When I generate the MXF there, it's fine and h264 files are made from it without any problems.
So I have a working MXD XDCAM OP1a 1080p 50 PAL25fps.
That same file in the updated media encoder again gives many "MXF read errors". So it's obviously the Mediaencoder that cannot handle that (working) MXF file.
I hope that helps the developers to get rid of that problem as soon as possible.
__Peter__

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.

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

Red frames in Adobe Premiere after rendering

Hi! I have a big problem since some months. After rendering .MTS files out of my Canon Leghria HFS in Premiere CS6 there appear red frames from time to time. This is also an issue after exporting them in Adobe Media Encoder. I already contacted Adobe concerning this problem but unfortunately nobody could help me there. I am not alone with this problem when - looking in the help forums in internet. But no hint really helped me out yet. Is there someone who knows this issue and can give me a helping hand? Great thanks!!

Try the trial version of this and convert the media. Then let me know if you are still getting the frames.
http://cineform.com/products/gopro-cineform-studio-premium#specs
Eric
ADK

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

C300 Red Frames and other experiences with 2014

Hello,
Just incase it's helpful, I'm sharing my experiences with Premiere 2014, C300 footage and a few other things. First about me. I have a small studio with two new mac mini's and one macbook bro running CC. We recently bought a C300 and upgraded to 2014.
We've only had one project started and finished with C300. Red frames and crashing were a constant problem. We muscled through it. Restart, Disk Permissions repair, PRAM, bow to the east.
Our next c300 project we just started. I only have two interviews so far. In 2014, one interview has red frames in it for about 10 of the 35 minutes. After reading a bunch here I started a new 2014 project, imported that interview via the media browser and still got red frames.
Just for giggles, I opened up the previous version of premiere, CC, on the same machine, started a new project and imported the clip via the media browser. There are NO red frames in the interview. The only difference is the version of Premiere. Same drive, same media, same mac.
Most old projects the I've upgraded to 2014 crash constantly. These consist of ProRes footage from an Atomos Ninja. I've deleted my media cache on all my machines. This problem has been pretty consistent.
For now, I'm going to work in CC. On another thread, I hear there's a 2014 update on the way. We'll see.
Good luck!
J

" ... bow to the east ... "
lol ...
We used to use that phrase a lot when I was younger and a problem that was intermittent popped up in something that we at times seemed to "solve", until ... it wasn't. At times, it does seem rather appropriate mostly jesting comment doesn't it?
Neil

I had completed my iDVD project and burned a disc. It worked great! Then someone messed with the project and put a red frame around the opening screen. Now when I burn the project, it no longer has the opening frame. How can I fix?

I had completed my iDVD project, a Wedding Slideshow with pictures and music, and burned it on a disc. It worked great! Then someone messed with the original project on my computer and clicked around and put a red frame around the opening screen that has the Wedding theme with music. Now when I burn the project to make more DVDs, it burns but no longer has the opening frame. It immediately opens to the iMovie slideshow. How can I fix so I can burn the entire project with opening frames?

As Bengt suggested make a disk image of the successfully burned DVD using Disk Utility. Then you can burn copies any time you need one.
In the future once you have the project as you want it save it as a disk image via the File ➙ Save as Disk Image menu option. This will separate the encoding process from the burn process.
To check the encoding mount the disk image and launch DVD Player and play it. If it plays OK with DVD Player the encoding was good.
You can then burn it to disk with Disk Utility at the slowest speed available to assure the best burn quality. Always use top quality media: Verbatium, Maxell or Taiyo Yuden DVD-R are the most recommended in these forums.
OT

Red frames popping up after upgrade to media encoder cc

I'm having some issues with Media Encoder CC. My workflow is AMA SxS card (footage is in XDCAM HD 1080/50i) into Avid Media Composer 6, edit, and export as XDCAM HD 1080/50i mxf file into a watch folder that Media Encoder picks up and converts to SD mpeg2 (its the way the TV stations want it) that file is then ftp'd using Media Encoder. It used to work fine with Media Encoder CS6, but since I upgraded it keeps giving me red frames (cant read frame errors) usually just before or after there is a cut in the footage. I've resorted to transcoding the footage in Avid to DNxHD 120 after editing and that seems to resolve the issue, but it's just an extra step that adds loads of time to my workflow.
Avid Media Composer 6
Adobe CC
HP EliteBook 8760w
Windows 7 64bit

The whole point is that I dont want to transcode into DNxHD at all, DNxHD is the extra step. The can't read frame errors are also very inconsistent in Media Encoder CC. I might export a file and it gives me a few red frames (can't read frame errors) but if I then take the same file and rename it they sometimes work. I've tried uninstalling and reinstalling but that hasnt helped...

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

Red Frames - Version 7.2.1

Similar Messages

Maybe you are looking for