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.

Similar Messages

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

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

Another weird media issue - red frames at the end of h.264

Tested with CS6 and CC, bunch of media exported using h.264 wrapped in MOV or MP4, this media plays fine in QT player, Windows Media Player, Media Composer, Sorenson Squezze, CatDV, Flame, Smoke, and any other app I try, but in any CC or CS6 app, the last frame is a red frame, which also takes time to show up if you park right in that frame, and some times crashed the app.
Something else is while any other app not from Adobe reports movies to have for example 300 frames, Adobe apps will report to have 301... I can repeat this on any machine I test.
Can provide a movie for testing too.
V.

here is:
https://www.yousendit.com/download/bWJyS3hjNDJUMFBFdzhUQw
open it with QT player and switch it to show you frames not time, you will see it says 60 frames (0 to 59) and there is no red frame, open it with any CC or CS6 app and you will see 61 frames, last one red. This is not very noticeable in Premiere Pro CC when playing, but if you park on the last frame you will see it, After Effects gets pretty slow and not responding for a few seconds when you park on the last frame.

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.

How to grab the frame of the .mov on the iphone?

Hi,
I want to render the .mov by OpenGL. So I want to know how to grab the .mov's frame. Do you have any suggestion and good reference material? Help.
Thanks very much.
ares

I am sorry, maybe I am not state my question clearly. I mean that I want to grab the video frame of QuickTime's format(*.mov) in iphone. And translate the grabing date to a texture used by OpenGL. I want to do a multi-media player use OpenGL, and cross-platform.
How can I do that?
Thanks very much.
Ares

"An error occurred while trying to add a frame to the movie" (-2014)

Oh c'mon. I just got everything installed. First time i try to use it, and get an error. Anyone help? I tried researchin this but didn't really get concrete answers. Plus, if i try to import livetype file unrendered from fce, fce quits unexpectedly.

Please, any ideas? i have a intel core 2 duo, 10.6.2 macbook, and PCI graphics card. Plenty of memory. Livetype version is 1.2.1. Is this type not compatible?

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

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

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

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.

How to create and export a still frame from a movie in iMovie 09

Disclaimer: Apple does not necessarily endorse any suggestions, solutions, or third-party software products that may be mentioned in the topic below. Apple encourages you to first seek a solution at Apple Support. The following links are provided as is, with no guarantee of the effectiveness or reliability of the information. Apple does not guarantee that these links will be maintained or functional at any given time. Use the information below at your own discretion.
Are you working in iMovie and realize that certain frames in the movie would be perfect as photographs? Here is how to extract them...
*To get a still frame from an Event*, right-click on the frame and select "Add Still Frame to Project". The still will be added to the end of the current project. Right click on the still frame in the project and select "Reveal in Finder". You will see a jpeg file that is highlighted. Drag this jpeg file in the finder to the iPhoto icon on your dock.
*If you want a still from a project*, rather than an event, the process is similar, except you right-click on the frame and select "Add Freeze Frame", and it adds the freeze frame at the end of the clip rather than at the end of the project. Right-click/reveal in Finder, drag JPEG to iPhoto icon in dock.
*If you are not using iPhoto*, and just want to save to your desktop, click Reveal in Finder as above, then COPY, then PASTE to desktop.
Hint: If you do not want to clutter up your iMovie Project with stills at the end that you would have to go back and delete, then create a separate iMovie Project just for your stills, and follow the instructions for capturing stills from an Event.
Note: If you do not have a right mouse button, then control-click will work instead of right-click.
This is the 1st version of this tip. It was submitted on Dec 5, 2009 by AppleMan1958.
Do you want to provide feedback on this User Contributed Tip or contribute your own? If you have achieved Level 2 status, visit the User Tips Library Contributions forum for more information.

First, click iMovie/About and see which version you have.
Versoon 9.0.2 would be iMovie 11.
Follow the instructions [in this post|http://discussions.apple.com/message.jspa?messageID=13065602#13065602]
If you have Version 8.0.6, that is iMovie 09 and you should see the Reveal In Finder option.

Can I copy a single frame from a movie clip and paste it over a bad blank frame in the same clip?

I have two frames in my video clip that are solid green. I would like to copy the last good frame and paste over the green video frames for the movie to play without the green frames popping up. Is thispossible?

You can install an App called MPEG Streamclip or you can simply pull up the clip in full screen and take a screen shot using (command+shift+3) or using (command+shift+4) to click and drag to create a box around what you would like to take a snap shot of.

Imported MPEG has red frames, how do I solve this?

Hi,
I've been playing with Premiere and just create the final movie on something I'm working and I happened to notice that almost at the end, there's a red frame in the video. What's up with that?
I play the original MPEG2 file in Windows Media Player (it was created with muvee Autoproducer and I'm doing editing in Premiere) and there's no red frame at all. But after importing it into Premier, there's a red frame.
Possibly more... How do I find all these red frames and what should I do to fix them?
I don't understand why they are red if the original doesn't have any...

Well, I read something about it that it was some kind of error yes and that I could see it on the events window, however, no errors were reported.
I found another document page at the Adobe site that talked about 3.2.0 update to Premiere (which I though I had, but I didn't) and that this update introduced these red frames and bla bla (but I has having them before the update). Anyway, I did the update, deleted all the cache files, opened the project, the files index was recreated and the red frame gone (at least on the frame I saw it before).
I'm going to produce a new output and then I'll just have to check for those red frames.
Maybe with this update and if the events window is really empty, maybe there are no errors (red frames) at all.
I hope...
Thanks for the input though.

Red Frames in M2V files.

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

Seems like my problem was linked to using VBR 2 pass encoding.
I was advided to used CBR with a bit rate of around 17 and that has worked

Red frames on the movie exported

Similar Messages

Maybe you are looking for