Red frames and MXF decode error

Hi there,
I have Premiere Pro CC and running Mac OSX 10.9.5. I have one long 32 minute long C300 MXF clip in my timeline which seems to be fine until around the 26 minute mark, where the entire frame goes red. The audio still works, but I can't see anything. I have tried to convert the clip to ProRes in Media Encoder also, but the same issue happens.
In the report log from Media Encoder I get the following message repeated many times:
MXF decode error in "[FOOTAGE LOCATION]/Card 1/CONTENTS/CLIPS001/E51151/E5115107.MXF" at frame 47650. Frame 47618 was substituted.
And then occasionally it says:
MXF read error in "[FOOTAGE LOCATION]/Card 1/CONTENTS/CLIPS001/E51151/E5115107.MXF" at frame 239.
Any advice about this??
Thanks,
Simon

Similar Messages

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 error

When I tried to render my sequence I got an error message. In Premiere I saw "MXF decode error".
It only happens on the spots where I used opacity and transitions.
Deleted cache and all the usual things I could do, but nothing helps.
Cheers

Try to convert your MXF files into other format like MPEG. Or just find go for another edit software like FCP X, the 10.1.4 can support MXF files natively and as well as 4K . But if you just get used to this Adobe premiere , here are some free converters for you : Handbrake, ffMPEG(_this one I am not very recommended, it will mess all your original video and database), MPEG Stream clip, any video converter. I used now is this MXF Converter from pav, and the quality is good.

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

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

With Half-Sized Frame and SP/LP error, am I getting lower quality?

Seven years ago, I recorded some videos with my Canon ZR miniDV camcorder. I want to preserve the quality of these videos by archiving them on my Mac. The read head on this camcorder is broken. So, I'm borrowing my brother's Sony Digital Handycam DCR-PC110 NTSC to play these miniDV video tapes.
When I use iMovie 6 to import, I get this message:
"The camera is sending half-sized frames, which iMovie can’t accept. Check your camera’s record mode (this is the setting that affects recording quality, which determines the total recording time on a tape). The mode must be set to “SP” or “LP.” If that doesn't help, try removing all the cables and batteries from the camera, wait a minute, replace them, and then reset the date, time, and record mode."
The recording mode is already set to "SP". However, I still cannot import. Every time I try to play the video, it shows a fraction of a second of the video and then it stops. If I disconnect the camera from the Mac, I can play the video without a problem. It seems that iMovie 6 will not allow me to play this video.
Does anybody know what the problem is?
With my brother's miniDV tapes, I don't get this problem on his Sony Digital Handycam.
From some research, I read that it might have something to do with playing a PAL recording instead of NTSC. However, my cameras are NTSC. I've never (consciously or remember to) use PAL. iMovie 6 is set to 29.97 bps frame rate, which is supposedly NTSC.
I tried the suggestion from this posting:
https://discussions.apple.com/message/1808010#1808010
Which is:
- I disconnected the camera from the Mac.
- Started up iMovie 6.
- Started playing my miniDV tape.
- Connected the firewire from the camera to the Mac
Now, I can play and import the miniDV video on iMovie 6. However, I'm curious as to whether iMovie is inputting NTSC and saving into PAL, or vice versa. Therefore, I'm concerned about the possibility of losing quality. Would anybody know if I will be losing quality?

"..the last 43 minutes of clips, cannot play well on my Canon camcorder.."
Run through the tapes to see how many total minutes of material you have on these tapes. A miniDV tape records a maximum of 63 mins at Standard Play rate, and up to about 90 mins at LP (Long Play) rate.
If you have more than 63 mins of material on these tapes, then the recording was made at LP rate.
At LP rate, the tape moves at 2/3 the speed of SP, which means that the video tracks recorded on the tape are very narrow. This means that when those tapes are played in a different camcorder the heads may read the tape properly, because there's no margin for error on these very narrow tracks. When replaying an LP tape, the camcorder's heads may not properly align with the recorded track, giving the 'half frame' error you mentioned.
No camera manufacturer guarantees that any LP material will play correctly on any camcorder other than the one on which it was recorded (because of these narrow LP tracks). [Sony created the professional 'DVCAM' speed - one-and-a-half-times normal SP speed, so two-thirds the recording time - to provide -w-i-d-e-r- tracks than normal, and thus ensure that professional DV recordings can be played back and edited on equipment other than the camcorder which was used
for shooting the material.]
The only solution for LP tapes is to try importing from as many different camcorders as possible till you find one which will do the job. (I had to do exactly the same thing last week, and found that various other Sony 'consumer-grade' camcorders - the material was recorded on a Sony - couldn't 'lock onto' the LP track, but professional or 'prosumer' (more expensive) Canon (XLH1) and Sony (FX1) camcorders could play the old LP material.)
Before trying to play old tapes, whether SP or LP, always wind them fast-forward all the way to the end, then rewind them - at least once - to make sure that the tape layers don't stick together, and to ease the stresses in the tape. You should also do this once a year to every recorded tape, to avoid stresses, pinching, and 'print-through' (seepage of magnetism from one layer of tape to others).
P.S: Have you tried cleaning the 'broken' head on your old Canon? Dip a cotton bud in methylated spirits - or, better still, carbon tetrachloride 'dry cleaning' fluid - and slowly turn the head drum, and wipe up and down it, over and over again ..making sure NOT to catch cotton wool in the sharp narrow gap between each of the (two) heads, which are each halfway round the head (at 180 degrees to each other). Wipe carefully, then examine the cotton bud and see if there are any brown stains on it ..if so, you've cleaned old muck off the head. Repeat with a new cotton bud until there are no more stains on it. Leave the head drum to dry for 10 minutes, playing gentle (half) heat from a hair-dryer on it, but don't melt the plastic camcorder - so that the fluid evaporates and doesn't stick any tape to the head! - then try importing again.
P.P.S: "..It seems that iMovie 6 will not allow me to play this video.." iMovie's tolerance for damaged digital video frames is far tighter than any camcorder's: a camcorder will often replace 'damaged' frames with detail from the undamaged frame before, so doesn't give a clear idea of how damaged the video data may be. If it won't import, it's damaged, possibly through head misalignment, or through a weak or dissipated signal. (Earlier versions, such as iMovie 2.1.2, were more tolerant of 'dodgy' video, and could import material which later versions, e.g; iMHD6, won't allow accept.)

Red frames and sound out of sync in HDV

I'm fairly new to capturing HDV. I'm trying to capture from a Sony A1E into PPCS6. I'm choosing capture format HDV and Preset HDV 1080i25 (50i). I'm in England on the PAL system.
I'm able to capture, but the resulting footage always has the sound a good few frames out of sync. This can of course easily be dealt with. But more worryingly, I frequently get 1 or 2 or 3 frames of solid bold red. Clearly something is not right. Can anyone please advise? I'm about to do a big project which will entail digitising about six hours of footage, so I do need to get on top of this. Thanks.

The dropped frames can result from bad tape,
dirty or misaligned heads in the deck, etc.
Could anyone possibly be kind enough to run quickly through the settings that I should be using on both camera and project?
HDV settings on the camera,
and a Sequence that matches your footage...
1440x1080 (1.3333)
Do this:
Or, right-click a media file and select 'New Sequence From Clip".
How do I choose the right sequence settings?
http://www.video2brain.com/en/lessons/how-do-i-choose-the-right-sequence-settings

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.

Red Flashes in MXF video

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

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

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

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.

How to detect red frame in a series of images using web cam?

hey i am a new use of lab view(8.2 n 8.6).kindly ca any1 help me out in red color detection in a series of frames being capture by a usb web cam.i have done the grabbing thing but dont knw what to do now.plz help me out. basically i hve to do the following things:
1 )the camera is continuously making video
2)the moment a red color or red frame comes across the camera the camera is programmed such that it will capture that red frame. and display that captured frame
plz hep me out.i need serious help.
i am attaching a vi that is grabbing the images and then xtracting the red color info n thn displyaing its intensities rows and coumn wise on a graph.here i have used a guassian surface to locate the red color.
Solved!
Go to Solution.
Attachments:
giving intensity of red color.vi ‏78 KB

hey,i have made the code plz chk it and do rep soon as ma project sbmission date is very near =((
i am snaping an image from the web cam then comparing it with the red colored jpg image made in paint.
the jpg image is converted to give input image to imaq match vi.but after the comparison it gives the same output.
on the front pannel the snapped image is displayed,the red colored image that is converted in to its respective pixels is displayed and the image that is obtained after cheking the image in the draw fails vi...the pic converted to pixels is all the time displayed.and the pass/fail icon always denotes one pass led on..plz chk the code =((.
also can u provide me some guide line for using thr hough transform for the red color detection in lab view..i dont have to import the matlab code..i have to purely make it using the lb view libraries.
also one more request pl rep me regularly as i really need your golden piece of advice for ma success.
thnx
Attachments:
picture to image(BY ME).vi ‏102 KB
untitled.JPG ‏3 KB

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.

MXF frame read errors and general render errors since update to CC

Hi there folks,
Being a Creative Cloud member for a while now I share the benefits of immediate updates of CC products. However, I also get to deal with the downsides, it seems.
Since I updated to CC versions of the entire Adobe Collection I experienced unprecedented trouble with After Effects. I'll mention the most pertinent errors:
- I used to render short compositions to uncompressed HD Quicktime, functioning as a master render for future sorts of output for my clients or just to have optimum quality before further conversions. For some reason AE CC has been generating all sorts of video dropouts lately, especially when audio render is set to 'auto'. Furthermore I noticed that the only audio res that I can choose in case of an uncompressed QT render is 8000 Hz. This is new in AE CC, I don't understand the reason for this modification since the previous AE versions never had this limitation.
I must mention the fact that other output formats and codecs also suffer from dropouts, be it less frequently than QT uncompressed.
- Imported MXF files from my customers which I incorporate in AE compositions are also full of dropouts. Every dropout shows up as a single frame (two fields) of red or black. Premiere Pro encounters the same problem and reports the dropouts as frames with a read or decode error. I checked some older MXF files in previous AE projects that have been rendered and delivered perfectly in the past, but these old MXFs now appear to have the same issue. I tested the older and the new MXF on another PC that wasn't updated to CC versions and found no dropouts at all. Something must have changed in the updated codecs that belong to the CC version. All MXFs play fine in VLC player on all systems, so it's not the video source being faulty. Anyone recognize this?
I do get notifications of CC product updates, but is there a way to just update the codecs? Maybe there is a better codec for MXF.
Any help is truy appreciated!

Like often, it's better to wait a little until there's enough people experiencing the same problem. So everyone here: thanks for responding to my post! In the end it seems to have helped, considering the update of Adobe. I am still a little precautious, because some MXFs give no red frames at all (input side I'm talking about) and others still do, but then the strange thing is that scrubbing the MXFs forth and back a bit results in having less red frames to none at all in the end. The red frames now disappear and then re-appear on different points in time of the MXF file, whereas I always found them being bound to specific and unchanging points, especially on the first frame of a scene change for instance.
Anyway, Adobe Media Encoder is not suffering from this problem, so there is a workaround, converting the footage before using it in AE and Premiere. That's good enough for now. But the problem hasn't vanished yet. Another problem that I had with rendering uncompressed HD Quicktime videos that always generated dropouts has all of a sudden magically disappeared. Thanks Adobe. I see progress.

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 and MXF decode error

Similar Messages

Maybe you are looking for