Auto Color Effect flickers off and on

I have just tried using auto color under the video adjust effects and the effect seems to flicker off and on in all of my clips. Anyone else had this problem
or is it my computer? I have a new computer with 12 GB of RAM.
Thanks
Doug

Hunt,
I think that explains it. Thanks a lot!!
Doug
In a message dated 9/22/2010 6:49:14 P.M. Eastern Daylight Time,
[email protected] writes:
Doug,
This is the rub on almost all of the "Auto" Effects. Unless the scene is
absolutely constant in lighting, and needing the same exact correction, one
gets a "pulsing," "strobing" or "flicker."
I strongly recommend using the Fast Color Corrector (or one of the other
non-Auto Effects). Same for Auto Levels, etc.
Good luck,
Hunt

Similar Messages

Auto Color Effect Issue

When I put the Auto Color effect onto a clip, it does an extremely good job of correcting colour but the movie clip (1080p from a Canon dSLR) then appears to flicker, even after rendering? Does anybody know what I need to do to correct this?
Thanks.

Most of the "Auto" Effects suffer from what you describe. They really only work so long as everything, the exposure, the lighting, everything, is uniform for the whole Clip.
Most use one of the Color Correction Effects, and not Auto Color, Auto Levels, etc.
About the only way to get the Auto Color to function, when the Clip is not uniform, is to Razor the Clip, when there are change in lighting, or exposure, but that is tedious.
Good luck,
Hunt

All my prints using: Lightroom 5, printer color management turned off, and non-generic ICC profile (e.g. Epson Premium Glossy) have magenta tint or cast

I'm using PC with: Windows 8.1, 64bit, Lightroom 5.4, Epson R3000, 6.75 (latest) driver, color management turned off in printer settings, Lightroom configured to manage color. If I use a generic ICC profile such as Epson sRGB, the prints look OK. But when I use any ICC profile dedicated to my paper and printer combination, such as Epson Premium Glossy, or one created using ColorMunki print profile, the prints all have a medium to heavy magenta tint or cast. The effect can be seen before I even print in the Epson Print Preview. Yet when I soft proof, I don't see this effect. I suspect the problem lies somewhere in the CMM process, but I can't pin it down. Any tips or suggestions are appreciated.

Thank you kindly for your insightful response. As it turns out, the answer is half correct. I've found others who'll say the same thing, that double color management will lead to a very magenta result. I believe this was certainly the case when I first started playing with the settings, Where I went wrong, is that after I corrected my settings by turning off printer manages color and letting Lightroom do the color management, is that the Epson Print Preview was still showing magenta with certain profiles. Not wanting to waste more money on paper and ink, I used the preview to gauge whether I was going to get a normal print or not. Then one day I ignored the print preview's magenta cast as a 'warning' and I went ahead printed the photo anyways. Because I used a profile that I created with ColorMunki Photo, the picture came out perfect (i.e. a very good match to what I was seeing in Lightoom on my monitor). The lesson learned is that for judging the final color correctness, the Epson Print Preview can be way off target and your best bet is to ignore it.

Enable auto color gets turned off

I have dials working just fine. When I update one of them however, all of them turn whie, without the alert colors. When i look inside, I see that all the ranges are now erased, and the "Enable auto colors" box is suddently unchecked. When I try to check it back on, the program crashes.
I have already installed the patch and the new flash program. Can you please help me resolves this problem?
Regards,
Azer

Do you have wifi access at home?
DO the phones connect to wifi?
do the phones have the same usage as Verizon (approximately)

Adobe DNG converter is corrupting NEF files. The color is way off and it's not the camera white balance.

I was using the converter for a few months and it was working fine. Now it will convert the files, but the color is really messed. I know it is not the white balance, because the same files convert fine to TIF files through Nikon's software. I am using this converter for Nikon d610 NEF files. Here's a sample DNG and the same image in TIF. Can anyone help? Thanks!

When you use the DNG Converter to make a DNG from an NEF, the DNG Converter applies the default Camera Raw settings. When I open your DNG it looks fine, but when you open it, it looks off. That is because you've some how set your Camera Raw defaults to have a bunch of customized settings specific to a particular picture, instead of having them all be normal settings. Below you'll see what Photoshop is saying the settings of the DNG-Converted-JPG are, with the non-defaults marked in bold. The main problems are the WB being custom and a bunch of HSL setting changes.
Here is what Photoshop reports that the JPG was created using:
      <rdf:Description rdf:about=""
            xmlns:crs="http://ns.adobe.com/camera-raw-settings/1.0/">
         <crs:RawFileName>hug_8290_0215_1.dng</crs:RawFileName>
         <crs:Version>6.0</crs:Version>
         <crs:ProcessVersion>5.7</crs:ProcessVersion>
         <crs:WhiteBalance>Custom</crs:WhiteBalance>
         <crs:Temperature>5732</crs:Temperature>
         <crs:Tint>+26</crs:Tint>
         <crs:Exposure>0.00</crs:Exposure>
         <crs:Shadows>5</crs:Shadows>
         <crs:Brightness>+50</crs:Brightness>
         <crs:Contrast>+25</crs:Contrast>
         <crs:Saturation>-4</crs:Saturation>
         <crs:Sharpness>90</crs:Sharpness>
         <crs:LuminanceSmoothing>0</crs:LuminanceSmoothing>
         <crs:ColorNoiseReduction>25</crs:ColorNoiseReduction>
         <crs:ChromaticAberrationR>0</crs:ChromaticAberrationR>
         <crs:ChromaticAberrationB>0</crs:ChromaticAberrationB>
         <crs:VignetteAmount>0</crs:VignetteAmount>
         <crs:ShadowTint>0</crs:ShadowTint>
         <crs:RedHue>0</crs:RedHue>
         <crs:RedSaturation>+11</crs:RedSaturation>
         <crs:GreenHue>0</crs:GreenHue>
         <crs:GreenSaturation>0</crs:GreenSaturation>
         <crs:BlueHue>+12</crs:BlueHue>
         <crs:BlueSaturation>+2</crs:BlueSaturation>
         <crs:FillLight>0</crs:FillLight>
         <crs:Vibrance>-6</crs:Vibrance>
         <crs:HighlightRecovery>0</crs:HighlightRecovery>
         <crs:Clarity>0</crs:Clarity>
         <crs:Defringe>0</crs:Defringe>
         <crs:HueAdjustmentRed>0</crs:HueAdjustmentRed>
         <crs:HueAdjustmentOrange>0</crs:HueAdjustmentOrange>
         <crs:HueAdjustmentYellow>+1</crs:HueAdjustmentYellow>
         <crs:HueAdjustmentGreen>+5</crs:HueAdjustmentGreen>
         <crs:HueAdjustmentAqua>0</crs:HueAdjustmentAqua>
         <crs:HueAdjustmentBlue>-9</crs:HueAdjustmentBlue>
         <crs:HueAdjustmentPurple>0</crs:HueAdjustmentPurple>
         <crs:HueAdjustmentMagenta>0</crs:HueAdjustmentMagenta>
         <crs:SaturationAdjustmentRed>-2</crs:SaturationAdjustmentRed>
         <crs:SaturationAdjustmentOrange>+14</crs:SaturationAdjustmentOrange>
         <crs:SaturationAdjustmentYellow>+25</crs:SaturationAdjustmentYellow>
         <crs:SaturationAdjustmentGreen>+26</crs:SaturationAdjustmentGreen>
         <crs:SaturationAdjustmentAqua>0</crs:SaturationAdjustmentAqua>
         <crs:SaturationAdjustmentBlue>+32</crs:SaturationAdjustmentBlue>
         <crs:SaturationAdjustmentPurple>0</crs:SaturationAdjustmentPurple>
         <crs:SaturationAdjustmentMagenta>0</crs:SaturationAdjustmentMagenta>
         <crs:LuminanceAdjustmentRed>+40</crs:LuminanceAdjustmentRed>
         <crs:LuminanceAdjustmentOrange>+13</crs:LuminanceAdjustmentOrange>
         <crs:LuminanceAdjustmentYellow>+3</crs:LuminanceAdjustmentYellow>
         <crs:LuminanceAdjustmentGreen>+15</crs:LuminanceAdjustmentGreen>
         <crs:LuminanceAdjustmentAqua>+3</crs:LuminanceAdjustmentAqua>
         <crs:LuminanceAdjustmentBlue>+4</crs:LuminanceAdjustmentBlue>
         <crs:LuminanceAdjustmentPurple>0</crs:LuminanceAdjustmentPurple>
         <crs:LuminanceAdjustmentMagenta>0</crs:LuminanceAdjustmentMagenta>
         <crs:SplitToningShadowHue>231</crs:SplitToningShadowHue>
         <crs:SplitToningShadowSaturation>32</crs:SplitToningShadowSaturation>
         <crs:SplitToningHighlightHue>45</crs:SplitToningHighlightHue>
         <crs:SplitToningHighlightSaturation>33</crs:SplitToningHighlightSaturation>
         <crs:SplitToningBalance>+74</crs:SplitToningBalance>
         <crs:ParametricShadows>-39</crs:ParametricShadows>
         <crs:ParametricDarks>-7</crs:ParametricDarks>
         <crs:ParametricLights>-15</crs:ParametricLights>
         <crs:ParametricHighlights>+14</crs:ParametricHighlights>
         <crs:ParametricShadowSplit>25</crs:ParametricShadowSplit>
         <crs:ParametricMidtoneSplit>50</crs:ParametricMidtoneSplit>
         <crs:ParametricHighlightSplit>75</crs:ParametricHighlightSplit>
         <crs:SharpenRadius>+1.0</crs:SharpenRadius>
         <crs:SharpenDetail>25</crs:SharpenDetail>
         <crs:SharpenEdgeMasking>0</crs:SharpenEdgeMasking>
         <crs:PostCropVignetteAmount>-24</crs:PostCropVignetteAmount>
         <crs:PostCropVignetteMidpoint>50</crs:PostCropVignetteMidpoint>
         <crs:PostCropVignetteFeather>97</crs:PostCropVignetteFeather>
         <crs:PostCropVignetteRoundness>0</crs:PostCropVignetteRoundness>
         <crs:PostCropVignetteStyle>1</crs:PostCropVignetteStyle>
         <crs:PostCropVignetteHighlightContrast>0</crs:PostCropVignetteHighlightContrast>
         <crs:GrainAmount>0</crs:GrainAmount>
         <crs:ColorNoiseReductionDetail>50</crs:ColorNoiseReductionDetail>
         <crs:ConvertToGrayscale>False</crs:ConvertToGrayscale>
         <crs:ToneCurveName>Medium Contrast</crs:ToneCurveName>
         <crs:CameraProfile>Adobe Standard</crs:CameraProfile>
         <crs:CameraProfileDigest>51B4314CF8312BA027EF3FC60481FB35</crs:CameraProfileDigest>
         <crs:HasSettings>True</crs:HasSettings>
To fix the problem you're gonna need to reset your camera raw defaults:
And then be careful when saving new camera raw defaults with the menu item just above, that your image has the camera raw defaults applied to it, except whatever small change you want to be the new default.

Issues with the Autocomplete pop-up, flashing off and on

I just upgraded to 18.0.1 on my Windows 7 64bit OS. When I start typing in something into an input box or the address bar the pop-up that comes up to show me what I have typed in the past (I'm calling it the autocomplete pop-up) flickers off and on. It comes up for a split second then disappears, but the drop shadow around the box remains there. It flickers on for a split second when I use my arrows or mouse to go through the list, but I don't know what I'm choosing. It is almost like it times out, but the drop shadow around the box remains on.
Any ideas whey this happening.

Try to disable hardware acceleration in Firefox.
*Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"
*https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
*https://hacks.mozilla.org/2010/09/hardware-acceleration/

24" imac with second display that flickers on and off randomly

Hi, I'm a n00b here, I've read a handful of threads before posting this a I cant seem to find a definitive answer.
I have a 24" 2.4Ghz aluminium iMac and I've recently purchased a HP zr24w 24" IPS panel as a second display, connected with an apple miniDVI - DVI connector.
The screen flickers off, to totaly black every time the mac seems to be having a hard time doing something, be it fast scrolling, flash video, but someimes randomly.
I have boot camp installed with winblows vista (for work) the screen does EXACTLY the same thing, all be it less frequently. This for me rules out the Mac OS, i think it must be something video card/driver related.
Was there ever a fix for this? most of the threads seem to just die with no official answer, it would appear that MBP users were ok until the last 10.6.3 update, when the problem seems to have returned, although i think thats a different issue with the same net effect.
I have spoken to apple care and the very helpful girl I spoke to send me some logging software which I've run and sent the logs back, that may help them out someway.
Any help would be GREAT !!
many thanks
Michael

well, some time has passed, here's where I'm at so far.
I tried a friend's samsung 24" screen and all was good with the world, no flickering on and off, no black outs nothing, for days it was all fine. I swapped the HP monitor back on and it went right back to its old ways. I called HP tech support, they decided that the monitor was faulty, i returned it to where I got it from and they have sent me a new one. Which was fine, for about 7 hours!!
So, to recap, the mini-DVI to DVI adapter is fine as it worked on the samsung screen, the HP screen is brand new and exhibiting the exact same issue as the first one (cant be 2 faulty ones surely) The samsung screen was fine.
This leads me to think that there is some compatibility issue between the 24" imac and this particular (hp zr24w) monitor.
I have followed apple support's requests for data logging but they cant find anything wrong there.
I'm out of ideas, any help would be GREATLY appreciated !!!
thanks
Michael

Color changes between CS2 and CS4 opacity with effects turned on

Howdie.
I don't run into issues much with Photoshop, and this one has me stumped.
I needed to drop back to CS2 in order to use a warp mesh plugin. I saved out a small portion of a file that I created in CS4 (Only containing the layer I needed to warp) and then opened that file in CS2, turned off all the effects (drop shadow, inner glow, bevel & emboss), and applied the mesh warp, then saved the file. I went back into CS4 and re-opened it there and copied its layers into the bigger, original file. What is strange is that the colors were a LOT lighter than they should be when compared to the original unwarped layer. So in an attempt to figure out what was wrong, I checked all of my layer opacities, filter settings, layer mixing mode, etc. and everything was exactly the same. I even tried deleting the layer style and copying the layer style from the original layer...no change. I turn off the effects and check the color of the object and it reads the same as the original layer. Both layers have no semi-transparency in the colors. I turn the effects on and it is all whacked out. After a while, I figured out that the problem was that the layer opacity in the effects, although reading the same between both layers (70%), is behaving as if it should be at 90% opacity in the new layer in order to match the original. Its as if the layer worked on in CS2 has brought with it some corrupted info in its definition, that never leaves and affects any Effects you try to apply to it.
Has anyone experienced this one before?

A liitle bit more info here. Apparently, the pixel data for the warped parts screws with the effect, Inner Glow, in the Choke and Size sliders. The sliders simply quit functioning and have an abrupt light/dark toggle effect roughly near about value "7".
The only way I could fix the problem was to do this convoluted solution, since Duplicate Layer does not work.
    1. Clear the effects on the problem layer.
    2. At this point you can either work on the problem layer directly or duplicate it to create a work layer. Doesn't really matter because both layers will get deleted later anyway.
    3. With Channel Mixer, and for EACH color channel CMYK, move all 4 sliders hard left, so that the result is 0/0/0/0 for the CMYK values (Do NOT use Brightness & Contrast in place of Channel Mixer because you will lose any blurred edges. Also, using Channel Mixer does not swell or choke off the pixels along any "floating" shapes' edges).
    4. With the selection tool, create two small selection boxs at two opposite corners of the entire layer. Fill them with any color.
    5. Select the entire layer (CNTL + A on a PC), and copy it to the clipboard.
    6. Create a new Alpha channel and Paste. The little boxs at the opposite corners of the file were needed to precisely position a copy of the layer when we Paste it into the new channel. The contents of the channel must be exactly registered with where the original shapes were in the problem layer.
    7. If you want, you can now delete the boxs in the corners of the channel by filling them with black.
    8. Create a new layer and load the selection (the channel) we just created.
    9. Fill it with the desired color.
    10. Copy the desired effects from the original layer before warping was done and to the new layer we just created.
    11. Delete the old problem layer.
    12. Done.

How can I disable the loading of the Warp Stalibizer and Auto Color Plugins?

I'm having trouble with a project of mine.
My main project file refuses to load because Warp Stabilizer and Auto Color crash when invoked.
I believed it was a file IO problem, but when I removed the external drive where the footage was, it gave me the same errors.
So I'm hoping that disabling the plugin loadin at AFX startup will restore my ability to load the file and retrieve my comps.
the exact error messages are:
'After Effects error: crash while invoking effects plu-gin "Warp Stabilizer".'
and
'After Effects error: crash while invoking effects plu-gin "Auto Color".'
and
'After Effects error: Crash in progress.Last logged message was <5540> <StateBinaryConverter> <5> solveCompleteB = 1'
Then it offers me to save a file and the resulting file has 0 KB...
Anyone can help me with this?
thx in advance

I just moved the plugin files AutoColor.aex and Stabilizer.aex to another location temporalily.
I removed the effects references and replaced the .aex files in their previous location.
Now I can open my project just fine.

Video connector keeps disconnecting (Screen flickers on and off)

Hi,
I bought a HP Pavilion Notebook 14-v054ca two weeks ago. Last week, the screen was flickering on and off, so I took it to the shop. They said the video connector was knocked loose and asked me if I dropped the laptop. The laptop is on my desk 24/7 and I have not dropped it once (I only had it for a week)! I have a warranty, so they replaced my laptop for me. Sadly, all my data was wiped, but hey, things happen.
I digress.
Here I am with my second brand new HP Pavilion Notebook 14. I want to make sure the screen incident doesn't happen again, so I open and close the lid as gently as I can. Guess what. One week later, the video connector disconnected yet again. Is the 14-v054ca just a line of faulty, defective laptops? I hope that is not that case, because I love HP to death. I have an HP desktop and I am extremely satisfied with it. I don't want to trade this laptop in again just to have it happen a third time. It's an utter waste of time, and I lose my data every single time they give me a new one.

Hello, @PongV2
Welcome to the HP Forums.
I see that you've bought two notebooks and both have had an issue with flicker screen. That this was identified from where you purchased it as a loose connector.
To get assistance on this and to see what could be done for you on the issue, I recommend contacting phone support.
Please call our technical support at 800-474-6836. If you live outside the US/Canada Region, please click the link below to get the support number for your region. http://www8.hp.com/us/en/contact-hp/ww-phone-assist.html
Thank you for posting on the HP Forums.
I worked on behalf of HP.

HT4528 the camera on my iPhone 4s color is all weird and the shutter keeps opening and closing trying to fix its self but cant. I rest my phone and turned it off and back on again.. how do i fix this. I only had the phone maybe six months.

The camera on my iPhon 4s is not working correctly. It is colored all strange and the shutter keeps opening and closing trying to fix the problem but it cant. I have already reset my phone and turned it off and on again. How do I fix this??

If resetting the camera app doesn't work you can try restoring your iPhone's software. The entire process takes about an hour to an hour and a half. Make sure you do a backup. Make sure you do a backup.
Backup:
http://support.apple.com/kb/HT1766
Restore:
http://support.apple.com/kb/HT1414

I cannot get the same colors when I print an image using Elements 12 (way off) and iPhoto (Close to Monitor color)

My image colors are over saturated and off in tone when I try to print with Elements 12 but if I take the same image in to iPhoto the colors are much closer to what I see on the monitor. There does not seem to be a way to match the color profile of iPhoto .
Do you have a suggestion?

Epson replied
Thank you for contacting Epson regarding your Epson Stylus Photo R2880.
We have seen an increase in calls of users using 10.7/10.8 with darkness or color issues. We do know this issue is coming from Adobe programs and they are aware of it and have told customers to test this by printing a photo from Apples Preview program, something other than an Adobe program. So if you right click on a jpeg file and select "open with", choose Preview and make settings here and print, the print should come out more like you are used to seeing. If it comes out normal, then this will tell you the program is the issue and you will need to contact Adobe for a fix or an update.
I subsequently did a color test print with Preview from an exported photo from Lightroom 4. I used Color Sync to manage the color with my icc profile to match the paper. The color came out perfectly. I then printed the picture with LR having the application manage the color and the reds remain washed out with an unacceptable print.
So it looks like the problem is with Adobe, not Epson.

The screen color just went off when I connect WD thunderbolt and Viewsonic Screen. What can I do?

I bought Macbook Air with WD Thunderbolt and Viewsonic screen. If I connect the screen to Macbook Air, it works. I connect Hard Drive first and screen connnect to Hard Drive. The color just went off. I have try on RGB and DVI. It has same result. What can I do? Bugs?

It might be best to ask only one question in each post otherwise you may never be able to mark them as solved.
I went to Starbucks this morning and my Wi-Fi on my Verizon Iphone connected, what does this allow me to do?
It should allow you to access the internet, read mail, etc.
My Wi-Fi does not recognize my home network from which I connect wirelessly to my MacBookPro and to my Apple TV using Airport Extreme router, why?
Try restarting your router (remove power for 30 seconds and restart). It may not be properly assigning an IP address to your iPhone.

Auto-save a) crashes AE and b) will not turn off via preferences

I seem to be in an endless loop of AE starting, auto-saving, and crashing.
I reported a bug earlier of AE crashing if auto-save begins during a Warp Track. I thought I could defeat this behavior by turning off auto-save in preferences, but, even with that (the save box is unchecked), auto save starts within a minute of opening a project, and freezes AE (staying at 0% Completed indefinitely).
I've deleted AE preferences, verified that auto-save is off, and the problem continues.
Any suggestions of how to defeat this would be very welcome. Thanks!

Caught in the act. After restarting, fixing permissions, reverting to a early (pre-tracking) version of the project, and verifying that auto-save is still turned off, AE tried to auto-save during a track (this time the stabilize phase) and froze.
One possible new detail - it only attempts to auto-save when the tracking footage window is in the foreground. Is it possible that AE auto-save settings do not affect the tracker when it is in the foreground? I worked several minutes without interruption in another comp before returning to see the track, and apparently triggering the auto-save somehow.
Thanks for any help.

When I start my mac book pro the screen flashes on and off and then a blue color before it open to the log in screen. Sometime a program will shot down buy it's self without me clicking the quit button. Help?!

When I start my mac book pro the screen flashes on and off and then a blue color before it open to the log in screen. Sometime a program will shot down buy it's self without me clicking the quit button. Help?!

If you keep getting a 'red' message it means that the HDD is faulty and will have to be replaced. You will have to format the new HDD in Disk Utility>Erase and then install the OSX and your data from Time Machine.
Ciao.

Auto Color Effect flickers off and on

Similar Messages

Maybe you are looking for