AE 12.1.068 Update-Random Red Frame Still Happens-but fixed in PPro v7.2

OS 10.8.4
AE 12.1.068
Updated AE today and still have the random red frame when rendering.....source file ProRes422. This appears to be fixed in Premiere v7.2 tho.
Anyone else still see this after update?

The update for After Effects CC with the fix for the ProRes red frame issue has not been released yet.
http://blogs.adobe.com/aftereffects/2013/12/after-effects-update-coming-soon.html
The Premiere Pro CC (7.2) update has the fix and it was released today.
http://blogs.adobe.com/premierepro/2013/12/pprocc-dec13-release.html

Similar Messages

Random red frames appearing in CS3

I've been using PP CS3 for a few weeks now and I have encountered a strange problem that I didn't see in PP2: random red frames appearing in the project.
Sometimes the red frames are visible when reviewing the project on the timeline (before rendering), and sometimes they show up only after exporting the project to AVI or to flash via Adobe Media Encoder. I'm using MPEG files from Sony hard-drive cameras.
At first I thought it was an issue with my new laptop, but the problem is also occurring on my desktop computer. Both computers have duo-core 2.2 ghz processors and 512mb dedicated memory video cards and 2 mb of system memory.
I am quite disheartened because I feel I wasted nearly $300 on an upgrade to CS3. I have Googled this problem extensively and haven't found a viable solution. Can anyone help? Thanks.

Not counting HD material, my general understanding is that Premiere is designed to work with SD material where each video frame is complete, not the type of file where 1 frame is complete, and several following frames are simply code which describe changes from the preceeding frame (ie-DV AVI Type 2 files... and not the Type 1 files produced by Windows Movie Maker, and certainly not the AVI files using the divX codec)
Read here to see
Why NOT to try and edit an MPEG
Whatever Premiere does with MPG on the timeline is simply an afterthought... not a design feature (again, this is MY understanding, from reading this forum, and is not based on any inside knowledge of Adobe programming)
If you simply must edit MPG files, you might look at different products
Edit MPEG with
Premiere Elements
or
WOMBLE
or direct from DVD with
Movie Edit Pro
Otherwise, do as suggested and convert the files to DV-AVI Type 2

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

I got some extensions before i update, after i update, the extension is still on but i cant find the extensions in the add-ons manager

some of my extensions is flagfox, greasemonkey, easy youtube downloader and some other which i cannot remember

It is possible that there is a problem with the file(s) that store the extensions registry.
Delete the files extensions.* (e.g. extensions.sqlite, extensions.ini, extensions.cache) and compatibility.ini in the Firefox profile folder to reset the extensions registry.
*https://support.mozilla.org/kb/Profiles
New files will be created when required.
See "Corrupt extension files":
*http://kb.mozillazine.org/Unable_to_install_themes_or_extensions
*https://support.mozilla.org/kb/Unable+to+install+add-ons
If you see disabled, not compatible, extensions in "Tools > Add-ons > Extensions" then click the Tools button at the left side of the Search Bar (or click the "Find Updates" button in older Firefox versions) to do a compatibility check or see if there is a compatibility update available.

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.

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

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

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 7.2 (7.2.0 or 7.2.1) when playing .mxf files

I have an iMac (mid-2011) with the 6970M card (officially not supported but capable of OpenCL) and a new MacBook Pro with the GT 650M card (officially blessed by Adobe, which is why I bought the computer). In 7.2 (either 7.2.0 or 7.2.1) red frames have popped up in seemingly random places when I play .mxf files. When I rolled back to 7.1 on my iMac, the red frames disappeared. I have checked this issue on your forum and tried deleting both the cache and the preview files; neither have worked. Unfortunately for me, my major job for the last half year entails working strictly with .mxf files.
I am wondering if you are planning any fix for this issue, which seems quite major as it is occurring on two different machines with two different video cards. If it weren't for the fact that the problem continues into exporting, I'd live with it, but the export issue makes it unusable in a professional environment at present.

Hi Peter,
Thanks for getting back to me!
the 5k media is 5120 x 2700 and are red r3d files, at a 8:1 redcode compression. Also 5120 x 2560 is the same.
I have a Blackmagic Ultrastudio 4k (1st generation) feeding a sdi signal to a flanders Scientific monitor, and also a Panasonic HDTV via HDMI.
The quality looks the same across the Program monitor, flanders monitor and the HDTV.
i have been editing in 1080p sequences - mainly the red r3d 1080p, but have also used the blackmagic sequnce settings plus many more and am observing the same issue.
As a test i rendered out a short clip at the 5120 x 2700 at full res to prores, imported the prores clip back into premier and resized into a 1080p sequence, playback res set to either 1/4, 1/2 or even full the clip enlages full size in the program monitor to full size but as soon as i pause playback it looks normal. so i dont think its a r3d issue but more a resolution scaling issue on playback. Purley for testing purposes i also tried a 1080p clip in a very low res sequnce at 640 x 360 and obsereved the same issue. 1080p clip in 1280x720 and 1024x576 seemed fine. This issue is a bit different to the above problem of 1/4 res not looking as good as it did but i think the problem is related.
so it seems that either my system has an issue or a strange bug in the update, DaVinci Resolve is working as normal so i can only assume its a bug ??
Thanks for your help with this,
Tim

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

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

Quicktime export contains random grey frames

Lately, doing a straight Quicktime export (not Quicktime conversion) is resulting in movies with random grey frames in them, lasting about 12 frames or so each. This is HD footage, shot on the Panasonic DVX-100. This only seems to happen when exporting certain sequences, but I haven't been able to establish a pattern as to why it's happening on certain exports but not on others. It's all footage shot, ingested, and edited on sequences with the same exact settings.
It's only been happening since upgrading to QT 7.5, but the other computer in the office also upgraded, and it hasn't encountered this problem, and can export the same sequences I'm having problems with just fine.
Has anyone else experienced this, or offer a solution?

for the record this was not my first post, I forgot my account info. I'm normally very nice but studio x was just puffing his chest and belittling a good question
This is a Final Cut issue. If it were only a drive/scsi issue the errors would also be there in the animation codec as well. The bad frames ONLY occur when doing a quicktime export [DVCPRO HD 720](referenced, render all frames, and self contained). I'm not dismissing the fact that there very well may be a drive causing problems (G-SPEED XL12).
The bad frames do not occur any other time. I render plenty of things in the exact same codec over the network to the raid from AE and Motion and never ever have a problem.
One thing I am doing differently now is long form projects. The projects having issues are a one hour show and a two hour+ show. I don't have this problem with commercials or other small packages. It also doesn't matter if it's a random 10 sec section exported or the whole program.
This is what I'm working with:
HVX200 and other mixed footage
FCP and QT last updated in early july (no internet connection)
G-SPEED XL12
Fibre channel to one station that also acts as a file server
gigabit to one station from the file server
trunked gigabit to another station from the server (seperate NIC)
All three stations exhibit the same problem including the station connected via Fibre Channel
Other people are having the same problem as I've found by searching. The earliest report of this specific issue I've found so far was stated around Jan of this year. But there are more reports from this summer.

RED FRAMES ON PREMIERE PRO 8.1 CARAVAN ON PROJECTS THAT WERE FINE BEFORE

I am having this RED FRAMES issue now, never heard of this problem until now. And its happening inside projects that had been ok since a few months back when I finish them. I just went in to export again some of the sequences and now the red frames are all over like a plague. Its Canon footage from an XF300. Ive deleted media cache files, digital rebellion house clean, and now that I want to restart premiere it keeps on crashing while loading the media files, I relaunch again and it loads some more files a bit further until if finally stops crashing after 3 -4 times. I tried then the solution that somebody stated: offline clips, delete media cache, save project, close project, link again, and the red frames were gone from the timeline, but they did show up in the exported movie!! I need to deliver this to client this Monday!! Is there any fix to this? I been using this project for a few months exporting movies with no problem until now, but I haven't changed anything in the project. What caused it? What should I do to fix this asap. Please help! Im running of Premiere Pro 8.1 Caravan OSX 10.9.2 I need to deliver movie to client asap im pulling my hair.

Hi Somu cena,
Welcome to Adobe forums.
You can install the 8.2 update directly. Please check what's changed and fixed in both the updates from the below links.
Premiere Pro CC 2014.1 Release | Premiere Pro work area
Premiere Pro CC (2014.2) Release | Premiere Pro work area
Regards,
Vinay

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.

AE 12.1.068 Update-Random Red Frame Still Happens-but fixed in PPro v7.2

Similar Messages

Maybe you are looking for