X100 Color Balance/Display Issues

I have an X100 which has display problems. It is hard to describe, but it is as though the display is on high contrast and lower than true (32-bit color), and the color balance is heavily biased towards red. Restarting the computer and trying different display settings and calibration don't work. My drivers are up to date. What is going on here?

Hello,
In the settings for your video driver is an option called "Vari-Bright" which, as I understand it, dynamically changes contrast in order to improve battery life. Try disabling it and seeing if tha tmakes any difference.
Regards,
Aryeh Goretsky
I am a volunteer and neither a Lenovo nor a Microsoft employee. • Dexter is a good dog • Dexter je dobrý pes
S230u (3347-4HU) • X220 (4286-CTO) • W510 (4318-CTO) • W530 (2441-4R3) • X100e (3508-CTO) • X120e (0596-CTO) • T61p (6459-CTO) • T43p (2678-H7U) • T42 (2378-R4U) • T23 (2648-LU7)
Deutsche Community Comunidad en Español Русскоязычное Сообщество

Similar Messages

Balance display issue

I cannot locate the Balance Display option using the directions Menu -> Settings & Tools -> Display Settings -> Balance Display.
My Display Settings menu does not include a Balance Display option.
I asked customer service about this and they had nothing useful to offer. Their suggestion was that I go to a Verizon store and have someone help me find it! lol
I have a basic Verizon Samsung Gusto flip phone, if that matters....
Any advice? Thanks....

cjshahmeran wrote:
I cannot locate the Balance Display option using the directions Menu -> Settings & Tools -> Display Settings -> Balance Display.
My Display Settings menu does not include a Balance Display option.
I asked customer service about this and they had nothing useful to offer. Their suggestion was that I go to a Verizon store and have someone help me find it! lol
I have a basic Verizon Samsung Gusto flip phone, if that matters....
Any advice? Thanks....
I just looked through the Samsung Gusto manual, and there is no mention of a "Balance Display" option. Why do you think it should be there?

Color display issues in Fireworks

I have been having problems with how colors are displaying in Fireworks CS4. Some colors appear to be extremely desaturated and was
hed out, yet when exported or viewed in another application, they appear vivid and vibrant.
Similarly, some jpeg files, when opened in Fireworks, appear overly saturated and vibrant as compared to the original.
This is a new issue which seemed to develop spontaneously in the past month or so (it used to work fine). I have tried to find some
way of adjusting the color display or calibrating the program, but have come up empty handed. This is becoming a big problem for m
e since I rely heavily on Fireworks for creating website layouts. A color palate that looks perfect in Fireworks then looks garish
and terrible in the other adobe programs or in my safari browser.
The only changes I have made to my system are to install any mac or adobe updates that come through.
Can you suggest anything which might be causing this problem and how I might resolve it?
Operating System: Mac OS X (v10.6)
Illustrator CS4

Is your system Gamma setting correct? Did you adjust your view/ monitor profile accordingly?
Mylenium

Color/Display issues

Hello! I have a MacBook that just recently was having some display issues (brightness problems, hard to read, hard on the eyes!) however it wasn't all the time. I could restart the computer and my old display was good and I'd have no problems. So yesterday I was transferring my apps to an older iMac using the firewall cable. When it was done and I restarted the computer the messed up display has transferred to the iMac! Now I can't view any of my computers for more then 30 minutes because it's so hard on my eyes. Any suggestions?

Sounds like hardware issues. Try posting in the Computing Hardware>MacBook forums:
http://discussions.apple.com/category.jspa?categoryID=218
or stop down to an Apple store or AASP and have it looked at.

How can I convert from color balance in FCE to color balance in FCPX?

Let me start off by saying that I've been having an issue with a project in Final Cut Express - a project I'd put a lot of time into and thought I was finished with. Before continuing on, I encourage you to take a look at my other thread: https://discussions.apple.com/message/18702933?ac_cid=op123456#18702933
Realizing that there may be no one who can walk me through fixing my project as is, I decided to download a trial version of Final Cut Pro X and see if I could replicate my project there and have more success (after all, it was only a matter of time before I switched anyway).
So, in my original project in FCE, I keyed a lot of frames with different color balances. I downloaded the Ripple Training color balance effect to do just that, but the sliders are set up differently. In FCE, they range from -1 to 1. In FCPX, they range from 0 to 1. I'm wondering how I can conveniently convert the values from FCE to FCPX. Being terrible at math has made this much harder.
Just by drawing a diagram, like the following, I can figure out the basics:
FCE
[-1]-----[-.5]-----[0]-----[.5]-----[1]
is equal to:
FCPX
[0]-----[.25]-----[.5]-----[.75]-----[1]
Since I have very specific numbers, not all of which can be easily converted using a basic diagram like the one above, I definitely need some help here. For example, one of the values in FCE is .77. What would that be equal to in FCPX? It's probably something simple, but like I said, I'm stupid when it comes to math.
Thanks to anyone who can provide me with some help here, although I still hope that I'll end up having no reason to redo everything in FCPX.

Well, the "math answer" is .885…but I'm afraid that's not likely to be of much help. FCPX and FCE have absolutely nothing in common, including filters land color correction. So even if you sent the time comverting all your numeric values, I'm guessing you'll wind up with a mess and be very frustrated with all the time wasted in the workaround.
If I read your original FCE thread correctly, I if it were my project., I'd do a test on a short clip in X to see whether yoi can the effects and quality you expect. If you can, great. Build you project from scratch and learn a new NLE at the same time.
Good luck.
Russ

The cumulative balance displayed in FS10N does not match the sum of the det

Hello,
The cumulative balance displayed in FS10N does not match the sum of the details. For example, we have a GL disbursement account that has a ***. Balance of 8 million. The debit is 2 million and the credit is 10 million. But, when you drill down on the ***. Bal. for the current period, the sum of the details is 9 million. According to our users, the 2 balances should equal. I did a search in this forum and found 1 post stating they had the same issue and the answer was to run f.16. Has anyone experienced this and if so, how did you handle it? I'm not sure how f.16 functions. Do we have to run it for each consecutive year? I'm not a FI specialist. I'm responsible for data archiving and the users think it's related to archiving. However, we have a test system that was resynced with production prior to when archiving was done and it shows that this issue is pre-existing.
Thank you very much in advance,
Lourdes

Hello,
There is a possibility that you have activate line item display for some of the accounts at a later stage. Meaning that earlier postings were not be shown for the earlier postings but only totals will be made available. Therefore, obviously there is bound to be difference between line item report and totals report.
You need to identify which accounts are being changed with line item display at a later stage.
In case if you forget to keep GL Line item display for an account, but the posting are already made the following steps you would required to get the line item display retrospectively.
1. Note that you are NOT required to make the balance of that GL account to ZERO. Please do not confuse with Open Item Management.
2. Put the check box line item display for the account in FS00. Make sure you are entering right company code.
3. Block the account for posting in COA Segment and Company Code Segment in FS00
4. Go to SA38 and run program RFSEPA01 (Give correct GL Account and Company Code)
5. Now, remove the block you kept on the GL Account in FS00.
This will reset the line item display retrospectively.
Hope this will solve your problem.
Regards,
Ravi

Colors are displayed not correct

Hi!
I use lightroom 3.4.1 on Windows Vista 64bit with a Iiyama PRO LITE E2407 HDS monitor and a ATI Raedon HD3600. The colors of some images that I imported from my Canon EOS 500d into lightroom are "strange".
If I display the same image with another program, e.g. XNVIEW or windows-live-photo-gallery the colors looks totally different. You can see the differece here:
(http://wipux2.wifo.uni-mannheim.de/~kesnw/download/HPB/Farbwiedergabe_Lightroom_vs_XNView. PNG - larger)
The ugly colors appear on both, RAW images and JPG images.
Where can I influence the colors?
Thanks,
Peter

"The default in Lightroom is ProPhoto RGB color space."
You can set the choice of color space that's passed to CS5 in Edit menu, Preferences, External editing. That can be anything you want. So I'm assuming you've set ProPhoto RGB.You’re the expert here. I just installed the product and the default was ProPhoto RGB. I was just expressing my experience with the default install
"Right click a file and select "Edit In" CS5."
So LR passes the file to CS5 in ProPhoto, if you've set that in the preferences
Once again I just installed Lihtroom with defaults. Unless a user is made aware of the ramifications of default settings they will not necessarily discover it on their own
"Do all your edits in CS5 and then "Save As" JPG."
If you don't alter the colour space in CS5 (Edit menu, Convert to Profile...) then it will still be in ProPhoto, so that's how it will be saved in CS5. So this is not clearly described when using both products.
"Use a broswer or any other 3rd party viewer and you will see the colors are washed out."
Only if your browser color management isn't working. Either you don't have appropriate profile for the monitor, or you're not using a colour-managed program to display the image, in which case the colours look very washed out. If you have a calibrated and profiled monitor, and use a colour-managed program to view the image, then it doesn't matter what is the colour space of the image, colour management will sort it out and it will display correctly. The assumption is that JPG will be used on color profiled display is not consistent with the default save options. Why would a “save as” color space be deferent from the export to JPG file? They are both sRBG files and not consistent or clear to the end-user.
"In CS5 use the "File/Save for Web & Devices" and save a JPG version the colors are more accurate in the JPG"
Yep, because save-for-web converts to sRGB. Normal monitors are approximately sRGB, so even if colour management isn't working (no monitor profile, or using unmanaged software) then when you display an sRGB image on a normal monitor, colours will be approximately (though not necessarily exactly) right. Yes. So the “Save As” option does state sRGB and does not distinguish any color spaces or differences in the menu. So until you post or email the files, a user will ot see the effects of the settings. Have you tried this?
"If you then change the default in Lightroom to sRGB and run through the same sequence you get a better color match in the (step 2) “File/Save As” JPG."
Again, I assume you mean changing the Edit menu, Preferences, External Editing and change the colour space used with CS5. If you set that to sRGB then, without having to do a conversion in CS5, the image is already sRGB, so if you save it then it will still be in sRGB, and it will display correctly on a monitor without a profile or using unmanaged software. Yes, but the “Save As” does not distinguish between sRGB or ProPhoto. For example if I used a 3rd party asset management product to export the file to CS5 and used “Save As” in CS5 it would create a JPG file viewable in a unmanaged monitor/software/display more accurately. I have been a long time Photoshop user, but new to LR. These issues or lack of understanding on my part only occurred after I installed LR 3. I'm assuming Adobe would like to have both LR and CS5 to work seamlessly together or is that a bad assumption?

Color mis-display in IE 7

Hi to match my clients logo I have used a lot of the color
#A59689 (light brown) looks fine in safari and firefox mac but IE7
and firefox PC the color is displaying as grey (both the images
that contain that color and the css placed #A59689)
see: www.joltconsulting.com.au
Is there away to fix this? I can't seem to see a color close
to this in the "websafe" range but I have seen many websites that
use similar colors seemingly successfully.
thanks
thanks - shontelle

> It's good to use web safe or
http://www.morecrayons.com/palettes/webSmart/
> colors when you can, but the majority of people's
monitors should be able
> to
> display 24-bit color. That being said...
Only if you're still in 1999. Websafe colors are completely
obsolete. It's
been more than a decade since the last 8-bit color graphics
card was
produced. So, it's not a monitor issue at all.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"bsoliman" <[email protected]> wrote in
message
news:fp9mtc$rbu$[email protected]..
> It also looks fine on WinXP IE6/7 & Firefox.
>
> It's good to use web safe or
http://www.morecrayons.com/palettes/webSmart/
> colors when you can, but the majority of people's
monitors should be able
> to
> display 24-bit color. That being said...
>
> As the previous poster mentioned, it could simply be a
bad monitor, but
> then
> again no two monitors will display things exactly the
same, not even if
> they're
> the same brand & model. There are simply too many
variables at play: the
> quality & age of the monitor and video card, whether
or not the monitor is
> color calibrated, the technology (LCD or CRT),
individual user settings,
> ambient light, etc. Also keep in mind the differences in
>
http://www.creativepro.com/story/feature/7584.html?origin=story
between
> Macs &
> PCs.
>
> B.
>

EMac Still Humming Along - Display Issues Though ... Any Help?

I have a strange display issue to run by the forum here:
Obviously my 2002 eMac is going to be suffering some display issues
with the age the Mac is and all ... but besides the slightly "softer" screen focus
(due to aging tube), I only have one other constant issue with the display.
I know the brightness and contrast are not what they used to be when the eMac
was newer, but here is the issue I am having. At least once a day now (after a few hours
of use), I seem to be constantly adjusting the "brightness" and "contrast" setting to get the
screen to a very usable brighter white field color. Normally now, the screen will get kind
of "dim gray" and less "contrast white" ... without any brightness or contrast range left for
me to adjust (the brightness and contrast settings in the system preferences/display pane
are usually maxed out).
To kind of fix this, what I've noticed lately, is that if I open the system preferences pane
and go to the "display" settings, lower both brightness and contrast down to the lowest settings,
then close out of system preferences .... then open system preferences again, and adjust the brightness and contrast up to slightly higher than the normal middle settings .... the screen brightness and contast are better and I have more "adjustment range.
Here's my question: What would be making the "brightness" and "contrast" settings come back to
a more "normal state" by performing the above sequence? I once thought the screen display was
getting older and as a result, dimming normally. But now I am thinking that it may be more of a "software" issue that isn't keeping the brightness or contrast settings in hold.
I pretty much perform all the basic maintenance procedures on a regular basis (ie: Permissions,
repair, disc repair/check, DiscWarrior directory repair/check, etc.), so am I missing anything
important here?
Any thoughts or ideas what is happening here, or how to make the "brightness" and "contrast"
hold their settings longer?
Any assistance is appreciated. Thanks

One other thing to look at is the setting in System Preferences, Universal Access, *Enhance Contrast* slider to make sure it is set to normal before you make the adjustment in Display.
Have you ever tried calibrating your screen? It can also be done under Display?
Generally an increasingly darker display is hardware related caused by heat, as well as the aging of the tube as you have indicated.
I used to like cleaning out the dust from the interior of the eMac periodically using a large soft artist's brush to dust and a running vacuum cleaner to suck up the dust as it flew. Most dust accumulates on the fan blades and it always seemed to run quieter afterwards, though 'quieter' is a relative term on an eMac.
The only tricky bit to this operation is the micro plug that connects to the power button. It is very small and fiddly to reattach.
Only consider the above course of action if your are naturally happy with opening electrical equipment and realize it must be completely disconnected from any power outlet before you even start. Otherwise don't do it if you feel unsure.
Your problem is unusual in your saying that it appears to be software related, from opening and closing your Sys. Prefs dialogue. It makes me wonder if anything is corrupting that file, and the settings it contains? It is peculiar.
I wonder if deleting that particular file would help. With System Preferences closed, in Finder locate,
~/Library/Preferences/com.apple.systempreferences.plist
and drag it to the trash.
It will be recreated next time your open Sys. Prefs.
I doubt if that will be the fix, but you might as well try it. As an experiment, instead of doing your described technique, instead try trashing that .plist and see if it achieves the same.
Lastly when was the last time you replaced your PRAM battery? It is a cheap thing to do, and I mention it only because the PRAM chip does control some video settings and removing a possible aberrant voltage from the equation is a one more thing you can do.
references:
eMac: How to Replace the Backup Battery
Resetting the PRAM and NVRAM

Color Balance Adj Layer Characteristics Changed from CS4- CS5?

Maybe some guru with better connections to Adobe knows the answer to this. (or maybe I just forgot).
I just discovered (and I don't think it is pilot error) that the characteristic behavior of the Color Balance Adjustment Layer is different in CS5 than it was in CS4/CS3. (Much stronger in CS4/CS3).
In addition, there is also an associated behavior that is like a buried legacy mode that is not made visible to the user. Here is what I mean.
If I create an image in CS4 with a single Color Balance Adj Layer, I get an adjusted image.
If I open that same PSD file in CS5, the same image is displayed.
If I use the same base image, yet create the Color Balance Adj Layer from within CS5, the adjusted image is different than the prior two.   So the Color Adjustment Layer acts like it has a hidden legacy mode where the characteristics are one type if created in CS4/CS3 yet a different characteristic if created in CS5.
My mind might be slipping (or my cold has the better of me) because I do not remember this as a documented change and I searched the internet for "What's new in CS5" etc etc. I don't remember anything on other forums about this either.
I guess the good news is, the new characteristic of the Color Balance Adjustment Layer is better behaved with a transfer curve with less clipping for highlights and shadows. Very similar to the better behavior of the change of the Brightness/Contrast Adjustment Layer going from CS2 to CS3.
Here are some comparison images.
This is the Layer Stack Used with Base Image of simple B to W gradient with CB Layer on top with just the highlights pegged to red. This is the exact same Layer Stack for all of the images shown:
Here is the first image. This was created in PS CS4 and displayed from CS4 with the conditions show above:
This is the same image from above that was saved as PSD with profile and them imported to PS CS5 with same profile. There was no change:
This next image is using the same base gradient, yet then creating the CB Layer from within PS CS5 with the same parameters, only the Red pegged for the Highlights:
Does someone have an easy answer for this. Can someone duplicate this and confirm the change from CS4 to CS5. A test by someone else would either confirm I am off base with pilot error or there is something to this.
And yes, all the images were sRGB and kept in sRGB for creation/display. All Screenshot images were the images brought up side by side on the same color managed monitor.   All Edit > Color Settings were identical.
Thanks in advance for any help
John

OK, Chris, but before I perform my act of self flaggelation for the benefit for all and my extra embarrassment, let me add in some useful information about the Color Balance Adj Layer that could be helpful.
I was working with another individual who wanted a better understanding the color balance adj layer, what is was exactly doing, how the shadows, midtones, and highlights interacted, and the differences with preserve luminosity checked or not, and also why the preserve luminosity was so hard to predict (e.g. did not really preserve luminoisty).
Without going into the deails of all of that, the tidbit I will leave as far as penance for my stupid original post above is that the Color Balance Adj Layer with the Preserve Luminosity box checked does a reasonable job or preserving luminoisty for the midtone adjustments yet definitely does not for the shadow and highlight adjustments.
An easy workaround for this is to just set the Color Balance Adj Layer Blend to Color which preserves Luminosity of the image presented from lower layers while maintaining the Color as best it can from using the CB Adj Layer (It holds the Hue and does its best to keep the same Saturation yet the Luminoisty from the presented image from lower layers takes prescendence). This does a much better job at preserving Luminosity than using the checkbox option.    I usually use this approach and keep the Preserve Luminiosity box turned off.
The error that I made was during the fairly involved exchange with this other individual, at some point I accidentally set the Layer Mask for the CB Adj Layer to 50% gray and did not notice that it had changed from the default white. Much further down the line, when this other individual could not exactly recreate my results, he mentioned working in CS3. Thinking this odd, I pulled up CS3, created the image from scratch (without the erroneous mask change to 50% gray) so therefore I duplicated his results and did not realize the error was in my original Layer Stack. To make a long story short, I went and checked for differences in all system settings, profiles, Color Settings, opacity settings, Blend settings, Layer Style settings (and their options) etc, etc and overlooked a change in the Mask gray level.       When I quickly flashed back and forth between the two documents/stack it finally popped out at me. Mea Culpa.

Triple Display issue Mac Pro 4.1, GTX660, GT120.

Hi guys.
I have a mac pro 4.1 with a GTX 660 and a stock GT 120.
The 660 has 2 x DVI, 1x HDMI, 1x Displayport
The GT 120 has 1x MiniDp 1x DVI.
I have both NVIDIA drivers and stock drivers.
I've recently received a Dell U3011 2560 x 1600 to compliment my 2 20 inch 1600 x 1200 monitors.
I plan to have the 20's flank the u3011 in portrait on either side to create a PLP setup.
The problem is that I can't get them all to work together.
Most of the time the monitor on the left isn't recognised (in system information it is described as color LCD display) and displays a resolution of 480 x 640. The other two monitors will work fine.
If I fiddle with the video outputs on 660 and 120 (mix them up, use adapters etc) I can get all three monitors to display their correct resolution, But if the computer sleeps or is restarted it goes back to low resolution on one monitor and doesn't display an image at all and goes to sleep.
The U3011 is always recognised at its correct resolution via displayport.
Other two are connected to DVI1 on the 660 and the DVI on GT120
Currently both 20's are recognised as 'vga display' or 'color LCD', no resolution options are available, just what it defaults to (640 x 480)
What it is at the moment:
What it was before I had the 30 and was using a 24:
I'm pretty sure its not a monitor issue, as the issues vary between monitors (depending on which is plugged in where)
I'd prefer to resolve this issue by running everything off the 660, allowing me to remove the GT120.
Any help would be much appreciated.
Cheers.

I'm pretty sure its not a monitor issue, as the issues vary between monitors
I'm pretty sure this is a display and adapter and interface problem, especially when the name(s) of your display(s) show up wrong after sleep.
The Mac uses one display driver that is highly parameterized. The parameters to be used are set by sending a query to the display for its name and capabilities. This query is sent on the secondary digital data channel, and is sometimes referred to as EDID data.
Currently both 20's are recognised as 'vga display' or 'color LCD', no resolution options are available, just what it defaults to (640 x 480)
When the name of the display is not correctly reflected in the name of its Display Preferences pane, that is a direct indication the display-adapter-cable-display part of the chain "dropped the ball" in resounding to the Mac's query for capabilities.
Adapters that do not pass the EDID data through, and displays that do not answer when queried for their name and capabilities are the primary source of problems. For example, TV sets that are not "paying attention" to the secondary data channel, and therefore do not answer the query, drive Mac users crazy.
The query is sent in response to four different events:
• System Startup
• wake form sleep
• cable insertion at the Mac-end (not necessarily at the Display-end)
• The use of the Option-Detect_Displays button in Displays Preferences window

Shape colors not displaying properly: reds look orange

I'll keep this short: I created a red rectangle, but it shows up as orange. You can see in the screenshot the difference between the color in the color picker and layers pain versus the color in the main viewer. This orange color carries through to FCPX, although the thumbnail always displays the correct shade of red. Help? Thank you.

Thanks for the reply. The issue is the same regardless of whether I go through the inspector or the system color picker. I have also since found that the same problem occurs within FCP X for anything I try to make red—text, backgrounds, whatever (other colors seem to display fine). However, I also discovered that when I export, the red displays properly in the exported video. Since I know the hex value for the red I need, this is no longer an issue for me since I don't really need the color to display right until the final product. Still, it would be nice to understand what's going on here.
The computer I'm on is a work computer, a 2010 27" iMac, but all software is up to date. I have a newer iMac at home so I'll check that to see if I can replicate the problem.

Why doesn't my Color Balance tool work anymore?

I've been working in Photoshop CS6 for two years and have never had issues with a tool not working. This past week I've noticed the Color Balance adjustment won't work at all. I've tried restarting my computer but that didn't help. I've searched for answers on my own but can't find anything. It seems very odd to me and I really don't know what is going on. Maybe someone knows something I don't know? It's putting my work behind. The only thing I can think of is I recently had my laptop cleaned out so it runs like new again. After that I reinstalled Photoshop CS6. This problem didn't start until I reinstalled it. I'm hoping I didn't do something wrong when installing it. Everything else works just fine.

I pressed the Reset New in CS6 button and it's working now. Crossing my fingers it keeps working!

MJPEG source color/balance/contrast etc all no good. Someone please help ;(

Hi all,
I'm having an issue and worst of all I don't know if it's Adobe with their 6.0.2 update or my own itchy fingers. But something got screwed up and I can't get it back to where it was. In a nutshell the MJPEG footage in PPro is all out of whack with respect to color balance/brightness/contrast all that sort.
I don't really have a good frame-for-frame comparison I could show so what I did was generate a Bars video in Premiere, then video capped the clip playing in monitor using Bandicam. Portion captured using Xvid looks fine, just like the MJPEG used to look before. One captured using MJPEG is fubar. Not the clip itself, that still is fine and dandy, just looks bad in Premiere. And not only in Source/Program monitor, it exports "washed out" as well. (tried H.264, AVI, the lot)
Here's a composite of the difference:
"M-JPEG IN PREMIERE" is how the footage now looks imported and viewed in Monitor (also exports looking...bad)
"M-JPEG IN M-PLAYER" is what same MJPEG clip looks like playing in WMP (and used to look like in Premiere before this mess)
"XVID IN PREMIERE" is how the Xvid footage looks imported and viewed in Premire
"XVID IN M-PLAYER" is what Xvid looks like playing same clip in WMP
If you look at the "M-JPEG IN PREMIERE", this is totally wrong and it used to look just like the other 3, IOW, no difference.
Also, any video effect (accel, YUV or not) applied to MJPEG source in Timeline crashes PPro on Exit or Save. Every. Time.
Ok, so what I've done to possibly screw things up:
1 For some strange reason I decided to put a 3rd party MJPEG codec on my machine. Not sure why, things seemed to work fine. But, spilled milk. So I used MainConcept because I was happy with their stuff in the past. Noticed no effect on my PPro goings so out it went. Maybe because it was 32-bit codec and I'm on x64 machine.
2 The same happened with Morgan MJPEG x64 v3, didn't seem to make any difference either, out it went.
3 Then window popped up telling me PPro has a 6.0.2 update. Why not, the thing is crashing constantly maybe it got fixed. So after the update is applied I go into my project, it is a total useless mess (not the issue here though) but all of the sudden I view a clip and notice the scene is a complete washout. There was some Luma Correction applied to it to bring it out of the dark somewhat and now it was just horrible. So I checked rest of the project and few others and yup, everything (either with effects or straight up) is just ... wrong, washed out, bland, too bright and all that.
Now, as much as I'd like to hold Adobe responsible for that, I don't believe in coincidences so I'm thinking me mucking about with those codecs is the issue because only MJPEG footage appears to exhibit those problems. Question is, is this something that can be "fixed"? And I don't mean by color correction in post, not gonna happen. I really hope some smart people here can surprise me with a "Hell yea" because otherwise I am facing complete reinstall of the system (since I know for a fact it was OK before) and that will take several days if not a week or two. Not looking forward to this, obviously.
What I've tried:
Just about everything I could think of and few things that did not make sense, too. Different preview formats, MPE GPU/SW, new project, import old project, clean cache/previews, export to various formats; Look thru registry and some codec sniffers to see if there's anything left over from those other 2, all "seems" in order; Uninstalled PPro completely, reinstalled 6.0 from my original media.
No go, things look the same (bad) in Premiere. Again, this is something that "happened", it was never like that before and it's not some monitor calibration issue. So either I did it (likely) or 6.0.2 update installed something that is otherwise not removed by uninstaller and persists after complete reinstall reverting back to 6.0.
Machine specs:
i7 with Win 7 x64 GTX 680 and gobs of RAM,
Please help and TIA for any. I'm in real deep S if I don't get that solved.

When you uninstalled Premiere Pro did you use the adobe creative suite cleaner tool? If not you can try the uninstall again and try using the cleaner tool and the steps listed on this page...
http://www.adobe.com/support/contact/cscleanertool.html
That link is the download link and also the instructions on how to use it.
You could also try to install the BMD MJPEG codec although I know when I had it on my system before my reinstalled windows back when Premiere was still at version 6.0 it made any timeline that had BMD's MJPEG codec in it constantly crash. But it might work.
http://www.blackmagicdesign.com/support/detail?sid=3945&pid=4041&leg=false&os=win
This link will allow you download their desktop video program and installing that program will install the BMD MJPEG codec on your system.
Also have you checked how the files look in another media player like VLC?

Output display issue in only a particular user account.

Let me start off by noting that I recently switched to mac from windows. Last night I was browsing around the system just getting a feel for the environment when the color / display changed and looked something like a display one would see from booting up in safe mode on a windows machine. I went on to restart and log back into the user account where I was having the display issue, but that did not work. I ran the tech tool deluxe suite to try and find the problem, maybe the video ram? That test came back with no issues to report. I went into the administrator account and found that the display there was normal, and then checked the problem account once more to find that my problem was not solved. Luckily I did not have a lot of information on the problem account so I went onto delete the problem account and recreated a new one. This solved my display issues. Does anyone have any idea why this would have happened or what I can do to prevent it from happening? Should I contact Apple because I am not sure if this may be a hardware/software issue/defect? Thanks.

If you open the Universal Access pane in System Preferences and select "White on Black" in the Seeing tab does that replicate the problem? I'm not familiar with Safe mode on a Windows machine.

X100 Color Balance/Display Issues

Similar Messages

Maybe you are looking for