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

Similar Messages

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

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

TS3274 My iPad mini retina is still having random reboots with blue screen after updating to iOS 8.0.2.i also did reset my iPad.But the problem still persis

My iPad mini retina is still having random reboots with blue screen after updating to iOS 8.0.2.i also did reset my iPad.But the problem still persists

Could you add your problem here: https://discussions.apple.com/thread/6569052? This makes sure the discussion and in one place and we can attract more attention from Apple.

Anyone else still having "up to date" issues?

I am still having issues trying to redeem my free upgrade to lion on an iMac purchased 10th June. I still get "serial number not found" or "ineligible serial number"
I have called apple 3 times and they have basically said they dont know what the problem is and aren't doing anything about it.... they keep saying "were investigating" but methinks not! I know there were issues of this nature on launch day but even Apple admit they have been resolved.
I'm very dissapointed with their customer services' can't do attitude. It may be easier to just pay the £21 in the app store but it's the principle of the matter.
Does anyone still have issues like this? what should I do next?...... wait? call apple again? or just throw all my gear that bears an Apple logo on ebay and be done with it?

you don't need to import that way ...
the option that you chose was actually for "folders into a project" ...
you can't grab just the images from there (folders only), choose the import -> images -> option instead ...

Is anyone else having random file access issues? including "Element not found" error?

I don;t know what the @#$ is going on with this device, but for example:
user A creates a folder in their area(under a share with RW rights)
Everything is great..
They come in on day2, and all of a sudden, they get "Access denied" on the (excel) file
Typically, if I re-apply full rights for them using windows permissions, it "fixes" it.
Today, I went to modify a excel spreasheet that I've been using for a week or so, and boom, access denied
and effective permissions indicate that very thing: no rights.
I attempted to re-apply rights to my home directory, and on that particulat .xls, got a "Element not found" message.
I'm sad that I've had SO much trouble with this device.
I re-sycned with A/D just for kicks, no help.
It syncs with A/D daily
I've had so many of these related permissions issues, we're likel;y scrapping the Lenovo for a windows server, but I figured I'll see if anyone else is dealing with this message..
I'm also open to the fact that it could be our A/D I suppose..

Sorry to reply to such an old topic, but I am having exactly the same issue. Did you ever find a fix? We are reapplying all the parent folder settings every morning to bandaid the situation, but it is becoming a little ridiculous...
We have our settings so that a file administrator has full access to everyone's files, and each individual has full access to their own folder. The folder settings never change, but the files seem to lose the user's access permission periodically after being opened or edited (haven't narrowed down the exact cause, but has never happened to files that haven't been accessed, but doesn't always happen to files that have been accessed). One odd thing that might have something to do with it, the ownership of files keeps defaulting to a generic 63353/UNIX instead of the creator of the file or the owner of the parent folder (which is set the way we want). We are currently experiementing with changing it, but it seems ike if we set the owner to the user, the file administrator randomly loses access, if we set to the file admin, the user randomly loses access. I think we might be can bandaid the situation from the user's perspective with this, but it doesn't seem to fix the initial issue, that the folder permissions won't stay set.

TS4002 I am still having iCloud email pushing issue. apple care seemed to be ignorant of the existence of such problem. help!

Help! I have read the forum and tried out every possible solution suggested there. iCloud mail is not pushing in either my Iphone5 or iPad 1.
Thanks

Yep. Arrived in 2 seconds. You should make an appointment with the Genius bar at a nearby Apple store and have them look at your phone. Sometimes you miss things over the phone that they can see when they physically look at it.
You should also try backing it up and restoring it, unless you have already. If it were me, I would back it up, then restore it as a new iPhone (without using my backup or not sync anything). Then only setup iCloud mail and see if it pushes. If it does, that would indicate that there is something corrupt in your backup that's causing the problem. If that's the case, restore the backup, save as much of your data as you can, then restore it as a new phone again and start over.

Is anyone still having the AME crash issue?

I've been working very efficiently until the last day where Media Encoder just stopped finishing the job. It will get about 50% of the way through a simple .mov to mp4 export and then freeze. I am using a new Imac with an I7 and 20+ gigs of RAM. I have updated both Premiere Pro cs6 and with that Adobe Media Encoder.
I have about 200 edits that I cannot transfer to Final cut Pro with out shooting myself in the face, I am begging for someone to help me out here. Adobe doesn't seem to give a rip and I am at a complete loss.
Sammy

I've been working very efficiently until the last day where Media Encoder just stopped finishing the job. It will get about 50% of the way through a simple .mov to mp4 export and then freeze. I am using a new Imac with an I7 and 20+ gigs of RAM. I have updated both Premiere Pro cs6 and with that Adobe Media Encoder.
I have about 200 edits that I cannot transfer to Final cut Pro with out shooting myself in the face, I am begging for someone to help me out here. Adobe doesn't seem to give a rip and I am at a complete loss.
What version of Premiere Pro? Premiere Cs6 6.0.2 updated yesterday
What operating system? Mac OSX 10.7.4 : 3.4 Ghz 20Gigs of RAM : I7
What kind(s) of source footage? When telling about your source footage, tell us about the codecs, not just the container types. For example, "H.264 in a .mov container", not just "QuickTime". I am using a few different codecs in some of the sequeces. Mainly used is the Apple ProRes 422, Linear PCM, Timecode : sometimes I used a few AVI files as well
If you are getting error message(s), what is the full text of the error message(s)? I do not get error messages the Media Encoder just stops working
What were you doing when the problem occurred? Trying to have exported media converted to h264
Has this ever worked before? This has worked almost all the time except for this last week as I've really need it.
What other software are you running? Premiere CS6 and Media Encoder that is all.
Do you have any third-party effects or codecs installed? No
Tell us about your computer hardware. Be especially certain to tell us about third-party I/O hardware (e.g., AJA, Matrox, Blackmagic, MOTU).
Are you using Mercury Playback Engine GPU Acceleration? I am using the mercury playback engine yes
Does the problem only happen with your final output, with previews, or both? This only happens on the final output

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

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

720p60 P2/HD Dropped Frame Issue

I'm having a dropped frame issue in FCP with some P2 720-60p footage. I can't get it to play through a sequence without freezing and giving me a warning. We've narrowed it down to an apparent processor issue. There are two tracks of audio (a stereo pair), and two tracks of music (again, a stereo pair). When we turn off the music, the sequence plays fine. But when the music goes back on, the sequence chokes. The funny thing is, I just did an HD project shot in 24p/n with several tracks of audio and several tracks of video and, aside from needing to render certain things, it played fine.
Any ideas?
Here are the specs:
P2 footage originated in 720/60p
AUDIO/VIDEO SETTINGS:
Sequence Preset: DVCPro HD 720p60
Video Playback: None (there isn't an output card for this computer).
SEQUENCE SETINGS:
Frame Size: 960x720 (HD 960x720 16:9)
Pixel Aspect Ratio: HD (960x720)
Editing Timebase: 59.94
Compressor: DVCPro HD 720p60
Audio Rate: 48 kHz
Depth: 24
Config: Default
Any ideas here?
Thanks,
Tim Walton
KVIE Public Television

Then it's pointing at a throughput problem between the RAID and the server I'll guess. Trouble shooting that could be interesting. Can you move the media to a local drive?
I'd also be interested to see what AJA's read/write speeds are on that RAID from your station...
Post the gear between your mac and the server etc.. whose RAID is it, How is it formatted? Got a model number of each of the devices involved? Mac Server?
Jerry
You've selected the "Easy setup" for the format you're editing too, right?

HT201406 My phone keeps trying to facetime randomly during phone calls, it will also mute itself and put itself on speaker phone. Anyone else have this problem? I did the factory reset and I am still having issues.

My iphone 4 will randomly try to facetime, mute itself, or put itself on speaker phone during a phone call. I did the factory reset, but I am still having this problem. Does anyone know what may be wrong, or has anyone else had this problem before?

I have the iPhone 4s on Verizon and never had this problem until I recently updated to iOS 7.0.2. I have the same case on it for several months. Yesterday, when I was talking on the phone with someone, it appeared as though I lost the call. But when I looked down at my phone, it was trying to Facetime with someone in my contact list. It happened again today. Different person, but both people have names that start with "A", so they are at the top of my contact list. Very frustrating! So, obviously updating to the latest iOS either did not help or was the cause of the problem.

Mac Pro 6,1 STILL having issues with Open CL (4K scaling and SpeedGrade direct link grades)

I've seen the staff responses to the issues of the new Mac Pro GPU saying that 10.9.4 fixes everything. For me, it has fixed my export issues, so I'm glad. I'm no longer getting lines and artifacts on my renders.
That's great.
However, I'm still having several issues, and they seem to be linked to Adobe and Open CL.
Here's a video that shows what's going on:
mac pro issues july 7 - YouTube
Issue #1
Like most of you probably, I'm doing 1080p exports of most things I'm working on. The first project shows a 1080p timeline with a mix of 4k, 5k, and 720p footage. Because zooming in so much on a 720p file in a 4k timeline looks so crappy, I'm doing 1080p timelines and scaling everything to the size it needs to be. I started in a 4k timeline then switched to 1080p because the 720p footage looked so terrible. However, in the 4k timeline, I didn't have any of the issues I'm showing in this first part of the video.
When I switched to the 1080p timeline, I discovered a weird quirk: When I resize the 4k (or 5k) footage to the size it needs to be (which varies based on the frame I want), it goes back to the 100% view when I'm scrubbing through it. When I pause, the size of the video goes back to the way I set it. I show this in the video. Then I show what was my working solution for the time being: "scale to frame size", which brings all the videos to the size of the sequence frame size and works fine. Later, I turn off OpenCL in premiere and when I scrub through the video, it doesn't zoom back in or only stay at the size I set when stopped. For some reason all of these issues only happen at 50% scale or smaller. It doesn't happen at, say, 60%.
I've tested this with raw R3D files and other 4K (or 5K) clips (even clips exported from After Effects) and the same thing happens. It doesn't seem to happen with 2.5k footage or 1080p footage.
Issue #2
This is the second project you'll see in the video.
After grading in speedgrade (through direct link) I open my project back up in premiere and start playing it back. The video plays back with delays and frame drops. Now normally, this would be expected. But this is 1080p pro res footage, and this is just an effect added, and the yellow bar appears indicating that open CL should be accelerating the playback and it should do so smoothly.
Maybe I was just wrong in assuming that a simple grade from speedgrade would be able to playback smoothly. I turn off the grade, and it plays normally.
But then, when I turn off open cl and leave the grade on, the video plays back without ANY issues.
So to me, it seems I'm still having issues with Open CL and adobe. I've found fixes that make it work temporarily, I don't need that kind of answer. However, I would like this to work. Is there something I'm doing wrong? Something I need to do to get this to work?
Here are my specs:
Mac Pro 6,1 (Late 2013)
3 GHz 8-Core Intel Xeon E5
64 GB 1867 MHz DDR3 ECC
AMD FirePro D700 6144 MB (x2)
OSX 10.9.4
Firmware: 2.20f18
What you're seeing is latest version of Premiere (CC 2014, v8.0.0 [169] Build)
Everything here is ProRes 422, running from a Promise Pegasus2 R4 RAID (drives: 4x Seagate Desktop HDD 4 TB SATA 6Gb/s NCQ 64MB Cache 3.5-Inch Internal Bare Drive ST4000DM000) (that's thunderbolt 2).
I've done everything: I've restarted my computer hundreds of times, I've reset NVRAM and PRAM and done power cycles.
This isn't just some issue that started with 10.9.3 of OSX, the 4k issues happened when I first switched to a 1080p sequence back in February (2014) or so, which means it was an issue even with 10.9.2 and the previous firmware release.
I've reported this issue to adobe.

That crash appears to be casued by the Facebook plug-in.
Create a new account (systempreferences -> accounts or Users & Groups on 10.7 and 10.8), make a new Library in that account, import some shots and see if the problem is repeated there. If it is, then a re-install of the app might be indicated. If it's not, then it's likely the app is okay and the problem is something in the main account.

Getting the error message"your apple ID has been disabled" . I reset my ID password last night and am still having the same issue.

getting the error message"your apple ID has been disabled" . I reset my ID password last night and am still having the same issue.

If you are still unable to access your account after resetting your password, you will need to contact iTunes Store Customer Support via http://www.apple.com/support/itunes/contact/

Still Having Random Red Frame Issues

Similar Messages

Maybe you are looking for