Media Export Bug: Red flashes in F55 media

Hi all,
I have been having endless trouble with exporting media via Premiere Pro.
The issue:
I am exporting animation codec via quicktime for use in After Effects. Each and every time (at different points - not consistent) red wash flashes will appear through throughout the export.
This is happening with native Sony F55 files (it is cut with Sony F5 files which do not experience this problem) when the 3 Way Color Corrector is applied. I have gone through countless blogs & videos trying to lock this down, however none with a definitive fix that has worked for me.
Rendering at maximum quality & depth. Sequence settings also at maximum bit depth & quality (yet when I turn any of these features on/off the problem remains).
Bottom line:
I created a work around for my preliminary deliverables. This was sufficient but definitely a step down from my optimal color correction preferences. I am happy to export to any high-quality, AE friendly codec but none have fixed this problem thus far. I need to deliver ASAP and after so much wasted time sourcing the fix myself, I hope someone with similar troubles may be able to point me in the right direction.
See sequence settings screenshot & reference shots to my issue.
Cheers in advance.
Dan

Thanks for getting back to me folks - Yes, I have a problem with Sound every time I try to import my Sony MPEG2 into Premier Pro CS3 - again, not an issue, as I'm recording off a mike to Soundbooth anyway.
I spent some time on the internet, and experimented with a trial 'video cleaner' (on a separate machine so I didn't mess up my production PC. At first they couldn't recognize the Sony MPEG2, and I received a message to download the GPL MPEG-2 decoder - I did, and product worked fine, converting to AVI.
However, simultaneously, I started looking at my video's within Premier- and realized that not every video has this red frame. It's in fact intermittent. (Actually, I see it only on export from Premier - in the sequence preview, the red frame does not present itself).
I don't find that it's always at the end - or the beginning, but shows up randomly somewhere in the video - in every 2nd or third video.
Bottom line Is - I'm sure my issue is related to the MPEG-2 my Sony DCR-DVD505 is producing, because I don't see this when working with original AVI's in premier (negating my PC as a cause).
Other than this Red frame popping up in every 2nd or third video - the results are pristine for my purposes (640X480 or smaller green screens using Ultra) - so for now, I'll just shoot the scene twice (I can use the practice), take the one without the red frame and save my money for new camera in the future.
Thanks!

Similar Messages

How to export my red flash?

I am new to flash building and somehow to managed to create a great flash on my website with help of opencart.
but now i need to export it to use it on my other wbesite
im confused how to export it , where is it stored?
Have a look at my website, the flash script that i want it the Red High Heels Banners that keep changing
Hope to hear from anyone soon
Thank you

Unless you can point to something specific on the page that is made using Flash, there is nothing I can see in that page that uses Flash. I am guessing you have some jquery working for you instead. You'll need to seek out help from the folks in the web design forums for that.

Red flash frames on C300 sequence exports

Still no fix for this widely noted issue, Adobe?
I'm currently trying to get a job completed and the process of getting anything out of Premiere is absolutely painful...
I have tried all the suggested solutions - trashing preferences and media cache files. I saw somewhere that removing any clips that are a different codec to your footage (in this case it's MXF files from a C300) fixed the problem. Tried switching hardware GPU acceleration off. None of these things have worked. I've had to export the sequence several different times and then stitch these exports together in a new sequence (skipping out the numerous red flash frames, of course) just to get a clean export out. Pitiful.
I can see reports of this happening over a year ago - why hasn't it been fixed? I think it's pretty scandalous that this hasn't been sorted - Premiere is advertised as being able to handle these camera formats natively...well, it can't right now for me if using the native camera files results in issues like this.
Has anyone found any other work arounds that I haven't noted above?

Hi Mark,
According to the "about Premiere Pro" window, I am on 8.2.0 (65) build.
I have had the same issue exporting out of both Premiere and Adobe Media Encoder - the build of AME is 8.2.0.54.
Adam

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

Errors and Red Flashes with MXF files

Hi all and Adobe, this is the third time i have posted hear about this and it is now getting very serious as the problem is affecting my income as I run a small one man video production business.
When I encode video that has any MXF file in the timeline, and most of my projects do as I generally am editing two to three camera shoots with one of the cameras being a Canon XF300.
I get many errors, and multiple red flashes in the encoded video.
I run all of my Adobe CC applications on a 2013 iMac 27" 3.5 Intel Core i7 32 gig Ram Nvidia GeForce GTX 780m 4096MB
There is no bottleneck regarding disk drive as I am using a dedicated GRaid 8TB Thunderbolt drive.
I first ran into this problem within a week of upgrading to the latest Premiere Pro CC 8.1 Caravan. I then noticed it when using Media Encoder when encoding both Premiere and After Effects projects Smith MXF files involved.
I at first thought the problem may have been corrupted cache file so deleted them all and re conformed. I even uninstalled Premiere cleaned out all relevant directories then reinstalled.
No matter what I tried the problem will not go away.
I went online and noticed in many forums people complaining about the same problem and coincidently most seem to have the problem appear since the last upgrade.
I then rang support and after a very long wait spoke to a man who advised I need to select Cuda in the GPU settings and delete all previews, so I did this while on the phone to him then started encoding a project and to my delight no errors.
I was so excited I jumped on here to tell another person who had a similar problem the solution.
But then within a day the errors were back and with vengeance, at the end of one of my last encodes yesterday I had an error log window that filled an iMac 27" screen not good.
I then rang support again and as with the previous call a long wait ensured.
After explaining my problem and indicating the discussion I had with the previous support person he indicated that Adobe was aware of this problem and they were trying to fix it.
He suggested a work around and that was to encode only using the Mercury software not any GPU settings.
So off I went and encoded the same project and guess what happened, more errors many errors.
Also please note to be thorough I tried encoding a project from 2013 that has worked perfectly before on previous versions of Premiere but as soon as it is loaded into this version the errors appear.
I also wish to bring to attention the abysmal support mechanism Adobe has established.
There seems to be no way to fast track serious problems.
I and many people like me need this problem solved as we rely on Adobe for our living.
If this continues for much longer I will have to reconsider my investment in the Adobe CC product.
Any assistance would be greatly appreciated.
Regards, Cliff elliott

Over the last couple of hours I tried an experiment using the same project which contains a two camera edits containing video from Canon XF300 and XHA1 cameras.
The experiment was to encode out form the project on three separate Macs.
As I have explained in the first post my main Machine the 2013 iMac gives errors on any setting including GPU selections.
I then tried it on an older iMac a 2010 model 2.93 GHz Intel Core i7 which has an ATI Radeon HD 5750 1024 MB GPU and the same problem occurs.
Next came an old Mac Book Pro 2011 that does not have GPU support. The project rendered without any errors but took about so long compared to the 2013 iMac which is to be expected.
So the problem seems to be related to the relationship between Premiere and the GPU's.
I hope this helps the Adobe engineers sort this out.

Small Bug in Flash 8: loading swf that´s a vectorized image in many layers

Hi! There´s a small bug in flash 8. If you load a swf
that it´s a vectorized image in many layers, when you give it
an action in onLoadInit, like mc.onRelease, the mc don´t
"catch" that action. You can try loading an image (it works), a lot
of swf (it works), but with this kind of swf the actions onRelease,
onPress, etc... don´t work.
The
swf
I´ll make a different vectorized image to make it works
(if there is only one layer it works)

Seems odd it will only run once. Usually if a cache problem
you get the same
results even when you update the movie or server scripts.
If it is
http:// it is not local even if from the browser
cache.
Verify the html is validated.
Check to see if this applies to all swfs. Create a simple
hello world swf
that connects to a JSP script that returns a simple value to
Flash. If that
seems to work, then the problem is in the JSP or
Actionscripting coding.
Check you can load the JSP script repeatedly using a direct
call to it on
the browser line using
http://.
Lon Hosford
www.lonhosford.com
Flash, Actionscript and Flash Media Server examples:
http://flashexamples.hosfordusa.com
May many happy bits flow your way!
"srikanth_s_india" <[email protected]> wrote
in message
news:e6obld$lfb$[email protected]..
> Thanks for the article link.
>
> I can't provide the URL as it is within our application
which requires
> logging
> in. However, one more interesting thing about it is that
it always works
> for
> the first time (in the browser/machine) but not from the
next time.
>
> My doubt is whether it is because of the caching? When
it loads for the
> first
> time, the HTML and SWF files load from our server and
hence are allowed to
> communicate with our JSP. However, when it loads the
subsequent times, it
> probably loads from the cache and hence considered as a
local file and not
> allowed to communicate with our JSP file which is on the
Internet.
>
> Can anybody tell me how to enable a local SWF file to
load SWF files from
> the
> Internet & access URLs from the Internet in Flash 8
pluggin?
>

Mono export bug

strange export bug I experienced this weekend, I think its a metadata issue.
Before the export I had to relink all the material because we had moved all the material from one SAN to another. Exported the show using Premiere, not AME, to Prores. The timeline have two mono audio tracks, each panned left and right. I then used AME to convert the new Prores file to export a MXF version and a h264 version.
All the files came out with only audio in the left channel! But when I check on a different machine the Prores came out with sound in both channels, but the MXF and h264 did not. I then removed all the "Media Cache" and "Media Cache Files", located in the Library/Application Support/Adobe/Common/ folder.
I then reimported the files, and now the Prores came up with audio in both channels but the MXF and h264 was still "corrupted".
Have someone experienced the same? Why would the Prores file, with audio in both channels, produce a single mono track MXF/h264 file? Do people regularly delete the "Media Cache" and "Media Cache Files"? PEBCAK?
Both machines where the new mac pro, 10.9.5, with similar specs, 3,5Ghz 32GB ram dual AMD FirePro D500, with Adobe Premiere 8.2
Any thoughts is appreciated

The Prores was exported with these settings:
Audio Codec: AAC
Sample Rate: 48KHz
Channels: Stereo
Audio Track Layout: 2 Mono Tracks
Channel Layout: Mono
The MXF was exported with these settings:
Audio Codec: Uncompressed
Sample Rate: 48KHz
Channels: 2 Channel
No multichannel

Red flash frame

Hello,
As instructed in this thread, I've started a new thread regarding this problem.
I work as an editor at a channel with Premiere CC 7.2.1 installed as our NLE. We have several 27" iMacs, 21" iMacs and about a dozen MacbookPro's.
We have experienced the red flash frame several times. It has appeared on MXF and ProRes exports. In one case, (using a MacBook Pro) it was generated on a ProRes export, but not on the low res proxy (unsure of format, will update as soon as I know) that is generated when we export to Sienna.
Red frames have also been introduced on MXF exports from iMac's (i7 27"), via ethernet to an Isilon.
I've taken the advice on the previous thread and told an editor to delete her cache and re-export. She did this and the red frames were not on the new export.
However, we have a high turnaround of news and current affairs content where a red frame may not be spotted. This could happen in a SOT or PKG for news. This file with the red frame could be loaded into ENPS and played out live. As the producer will be viewing the proxy in Sienna, they will not see the red frame as it'll only be on the ProRes, which is in a TX server they do not have access too.
The added danger is that if that section of programming is repeated, it will not be TX'd live from in house, it will be TX'd by a third party. Who (I assume) will pick up the red frame and hit us with a fine.
So, Adobe, is there a fix coming? Or is there anything we can do to ensure this does not happen?

To add, the low res proxy is an MPEG movie at 640 x 360, .mov suffix. No red frames appear on this.

How can I fix red flashing tint in new iMovie?

I imported a .mov file into the new imovie version and now I am getting a red flashing tint....how can i fix this??

dasacom,
In addition to what imagecollection said, the Live Rectangle bug is limited to the MAC versions starting with 10.7 and 10.8, but not 10.9 (Mavericks) or 10.10 (Yosemite). Hopefully, the bug will be fixed soon.
So a switch to Mavericks or Yosemite with a reinstallation might be the way to solve it here and now.
To get round it in each case, it is possible to Expand the Live Rectangles to get normal old fashioned rectangles, or to Pathfinder>Unite, or to use the Scale Tool or the Free Transform Tool.
A more permanent way round that is to create normal old fashioned rectangles, after running the free script created by Pawel, see this thread with download link:
https://forums.adobe.com/thread/1587587

Is this a bug in Flash Player or Flex?

Compile and run this code (it is generated when you select New MXML Application) with FlashBuilder4.5:
<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx" minWidth="955" minHeight="600">
<fx:Declarations>

</fx:Declarations>
</s:Application>
If you are using IE, you will see a blue player control panel. But there should be nothing displayed because there is no
visual components in the code above.
If you are using FireFox, there is nothing displayed.
Same behaves for mx:Application.
I think it is a bug with Flash Player or Flex. How can Flex behave differently with different browsers?

This is what I see in IE 9.0.8112.16421, but not in FF.

What's with the "RED FLASHES" when I scroll ?

Using Aurora, when I'm on any web page (except Firefox !) and use the scroll wheel on my mouse, I get a RED FLASH every time I start to scroll. This is potentially dangerous as I have a seizure disorder that can be triggered by light flashes (when coupled with
other stimuli).
The Firefox page scrolls without the flashes - what's up ?
OS XP with latest update.

Try to disable hardware acceleration.
*Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"
If disabling hardware acceleration works then check if there is an update available for your graphics display driver.

Indesign CS6 epub export bug

I am using Indesign CS6 to export a book to epub. Having problems with automatic numbers and bullets as well as spacing issues; however, I've made some adjustments and am getting a pretty decent epub. Here's the issue: When I convert my epub to Mobi using Calibre, I get double bullets and double numbers in my lists. I used this same process to create a Mobi file a few months ago in Indesign 5.5 with no problem. So I took one of my CS6 files, exported it to IDML, opened it in CS5.5 and exported to ePub. I then took that epub and converted it to Mobi using Calibre. No double bullets or numbers. So the issue is coming from Indesign CS6.
Anyone else had this issue. Any other ideas on how to get a clean Mobi file from CS6?

Thanks a million.
Re: Indesign CS6 epub export bug
created by Steve Werner in InDesign - View the full discussion
lotuscott,
You should get the 8.0.1 update for InDesign CS6. It fixes several EPUB bugs including the "space before" problem and the "epub-ruby" (which is I believed intended for Japanese language.
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/4773256#4773256
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4773256#4773256
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4773256#4773256. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in InDesign by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

Has anyone solved or worked around the After Effects CC red flash frame glitch?

I can't find any mention on any forums of the After Effects CC red flash frame glitch later than Feb. 2014. I just installed 12.2 (which was my first CC version) on my macpro and started getting the red flash frames randomly, but with increasing frequency, in my projects. I have never had this problem before on any previous computer or version for AE. The forums I've read have referenced ProRes source footage, outputs to ProRes, and lens blur. My project uses all of these things.
If there is a universally accepted solution/work around, I haven't seen it definitively. Do I not use ProRes source footage? Do I not render to ProRes 4444? Do I not use the lens blur effect? Do I give up and go back to CS6?

Hi Keith,
I have the "same" issue with the red frames in AFX CC
I have seen them first, as I resized a prores4444 HD to a smaller format and saw the redframes in the preview window.
Setup in AFX: I created a comp from the HD Prores4444 footage and put this comp in a comp with resolution of 960x540.
The output format was again prores4444.
I shuttled through the clips in the small comp and I saw the red frames too.
When I switched to the HD comp at the same position everything was fine.
I "solved" the problem by flushing the cache, twice. Because after the first purge I was only able to render the first clip. The second one had the red frame problematic again.
Maybe It has something to do with hardware accelerated layers.
I'm using a MacPro running OSX 10.8.5 with a Nvidia GTX680.
Cheers
Michael

Bug in flash 8 authoring?

I have a fairly big flash project with a number of classes. I
have a problem when changing code in some .as files, the result is
not shown in the published swf. I need to close flash altogether,
reopen the fla, republish, then I see the result of the changed
code in the swf.
Has anyone encountered this bug in flash 8 before?
Thanks,
Paul

Howdy. I'm having a very similar problem. I'm working with 21
languages (including EN) on the strings panel in Flash 8. I've
found that my languages get corrupted -- EN strings get substituted
in for some, not all localized strings in the panel -- when I
publish or test the movie. I was publishing for Flash 7. When I
changed my publishing settings to Flash 8, the problem went away.
Have you gotten any answers to your problem?

Bug in Flash 8 when using Strings Panel?

A problem with the strings panel in Flash 8 I have found is
that, when working with 6 languages, if you save and close down
your Flash file with the Strings panel hidden, and re-open the FLA
and then view the strings panel/view your text on the stage (or
open the xml file) that, in my cae, some EN strings have been
corrupted/mutated to other languages.
This is obviously a bug in Flash which corrupts one of the
XML files if the strings panel is closed. Why does it do this? Its
very annoying having to remember to open the strings panel whenever
I load that specific project, even if I am not going to use it. And
the panel takes up a lot of space as it is so can't leave it open
all the time for other projects.
Any ideas?

Howdy. I'm having a very similar problem. I'm working with 21
languages (including EN) on the strings panel in Flash 8. I've
found that my languages get corrupted -- EN strings get substituted
in for some, not all localized strings in the panel -- when I
publish or test the movie. I was publishing for Flash 7. When I
changed my publishing settings to Flash 8, the problem went away.
Have you gotten any answers to your problem?

Media Export Bug: Red flashes in F55 media

Similar Messages

Maybe you are looking for