My images look completely different while I'm working in Bridge and Photoshop (CS6) than they do once they are saved.

They look normal while I'm working on them in Bridge or Photoshop but when I saved them (doesn't matter how I save them - jpeg, png, it's all the same) and view them with any other program or on any other computer the blacks go through the roof and the contrast is way too high. I didn't have this problem at all on CS3 and I'm using the same computer and monitor.

The profile, in this case Adobe RGB, follows the file, that's the whole idea. The profile defines the colors you get with those specific RGB numbers. The only option when you save is to not embed it, which is usually a very bad idea, because then the RGB numbers no longer have a specific meaning. They're just arbitrary numbers.
The working space mainly matters when you create a new file. The document profile, if it already has one, overrides the working space. Put it this way: each file has its own working space, and then you have a backup working space in case the file has none.
(You can change this behavior in color settings > color management policies, but don't. The default is "preserve embedded profiles", and that's the only sensible setting. The other two will quickly send you out swimming with no dry land in sight. So to speak).
All that said, working in Adobe RGB is probably not a good idea until you get a better understanding of the implications. sRGB is the safe choice, it will usually display correctly without any special considerations. So if you have an Adobe RGB file and you want to use the safer sRGB instead, you convert to sRGB, with the menu item Edit > Convert to Profile.
Don't be confused by the fact that you then have sRGB as both document profile and monitor profile. That's coincidental, and just to set up a safe workflow. These two profiles are still separate and serve different purposes. The document profile defines the numbers in the file; the monitor profile describes the behavior of the monitor. But they're similar enough so that you can use it in both places.
So. What do you see now, with sRGB as monitor profile? You must close down Photoshop and relaunch it for the new profile to take effect. Are they similar or still different?

Similar Messages

My Adobe Photoshop looks completely different. How did it change from what I am used to using?

My photoshop elements looks totally different from what I have been using. How can I find the simplier version I am used to?

When did the version change to 10?   I used it in March and it was the one I was used to. It was much simplier. Is there another Adobe Photoshop besides Elements?
==============================
Patti Farley - Albuquerque, NM - US
[email protected]
505 417 5730
==============================
Date: Tue, 7 May 2013 11:22:43 -0700
From: [email protected]
To: [email protected]
Subject: My Adobe Photoshop looks completely different. How did it change from what I am used to using?
    Re: My Adobe Photoshop looks completely different. How did it change from what I am used to using?
    created by 99jon in Photoshop Elements - View the full discussion
Hold down the CtrlShiftAlt keys and simultaneously click on the Edit button on the welcome screen. After a few seconds release the three keys and look behind the welcome screen by closing it. Alternatively hold down the three keys whilst clicking on the desktop icon for the Editor or PhotoshopElementsEditor.exe in the Programs folder. Keep holding down all three keys for a few seconds; then release. You should get the settings option. When you see a pop up box with the words: Delete Adobe Photoshop Elements Settings File? Click on Yes Then wait whilst Elements rebuilds the preferences.
https://lh4.googleusercontent.com/-S6Kjmq-x08U/USJJS91-teI/AAAAAAAABIg/jpqUlTmNez4/s320/Se ttings.jpg
     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/5298329#5298329
     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/5298329#5298329
     To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/5298329#5298329. In the Actions box on the right, click the Stop Email Notifications link.
     Start a new discussion in Photoshop Elements 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.

IWeb site looks completely different when published compared to on iWeb...

For whatever reason, whenever I publish my website (I published it to a "local folder"), it looks completely different and VERY ugly.
This is what it looks like in iWeb right now:
http://i3.photobucket.com/albums/y53/WWEFreak69/Screenshot2011-03-22at34527PM.pn g
This is what it looks like when it's published:
http://i3.photobucket.com/albums/y53/WWEFreak69/Screenshot2011-03-22at33817PM.jp g
There's an obvious difference.
So what am I doing wrong?

For one thing there are many files that did not get uploaded to the server. You can see which by viewing your site in Safari and bringing up the Activity window (Command+Option+A).
The pages where the navbar is down the site appear to have much of the site's objects in the navbar section rather than the body of the page. Go to the iWeb preferences and check the checkbox to show guides and image indicator.
Click to view full size
The design link on the home page is inoperable. Did you intend to have just the text be the link for the hyperlinks on that page or also the image that each text box is on? Makes for a very small link to find.

I bought a Mac Mini for the family but there's something very odd. Windows looks completely different and I'm completely confused. Is this because of Windows 8? How do I get back to my old Windows!

Windows looks completely different and we can't use the computer. We're flumoxed, we did some research and read about this new version of Windows - is this the problem? Is there a way to revert to the older version of Windows? Apple has shot themselves in the foot with this change. Any help would be greatly appreciated.

Macs don't come with Windows. They come with OS X. If you want Windows, you'll need to install it yourself, or return the Mac and buy a PC.

My macbook pro crashed and the hard drive was replaced. How do I restore my backup pre- 9.6 iphoto library to the 9.6.1 iphoto library? They look completely different.

My macbook pro crashed and the hard drive was replaced. How do I restore my backup pre- 9.6 iphoto library to the 9.6.1 iphoto library? They look completely different. When I look at my backed-up iphoto library folder I see lots of files and folders: ALbumData.xml, Attachments folder, etc. The 9.6.1 iphoto library doesn't appear to be a folder at all. Help!

iPhoto 6 and earlier libraries were regular folders with the kind of files your reporting. With the advent of iPhoto 7 the library folder was changed to a package similar to the application packages but have essentially the same files and folders inside. There's no reason to have access to the inside of the iPhoto Library so Apple changed them to packages.
Do you have a backup copy of the iPhoto Library from before the HD crash. If so restore it to the Pictures folder in your Home folder. If you previous version of iPhoto was iPhoto 7 or earlier download and run the iPhoto Library Upgrader 1.1 on your library before trying to open it with iPhoto 9.6.1.

Opening images via Bridge to photoshop CS6

Hi,
We are teaching 3 young 8 year olds Dreamweaver CS6 and Photoshop CS6 (recent installations). We are going fine with Dreamweaver but then we needed to learn how to manipulate images. In particular make new logos for the site and create images for uplaoding from the camera.
We are new to photoshop CS6 but wouldn't expect the issues we are getting right now.
We can't open jpegs completely. We get a transparent background or just a part image. Must be something we are doing wrong I guess. It looks fine in Bridge but really isn't loading well in Photoshop.
Here is where you can see about the laptop we are using : http://brianmellady.com/system.html
Here is a screendump of the issue: http://brianmellady.com/screendump.htm
By the way this is a site http://brianmellady.com which we are using dreamweaver for. We have made a members login page which appears to be working but as you can see unfortunately we badly need to create a logo and make some images for their site which isn't created yet. If I can keep them from games and from Minecraft then we will make progress
It needs to be ready soon so that I can get a domain for them and host it on my Dad's servers.
Regards,
Kristina & Brian

If you are having trouble using Photoshop you will probably get better results if you post in one of the Photoshop forums. While are are available from the page linked below, the General Discussion one at the top is the most popular, though there is the new one for beginners if you think that might be better.
http://forums.adobe.com/community/photoshop

Bridge and Photoshop keep coming to the front while batching

I downloaded the newest updates today and now when I run a batch from Bridge to a photoshop action the bridge and photoshop programs keep coming to the front and will no longer allow me to work on background programs or surf the net while the batch is running.
I am using the latest "patches" as of June 5th 2012, on a Mac Pro running 10.6.8
ANyone got a fix for this?

I may have updated another program as I have the Production Suite. But before I did the update my Bridge was working very well.
As always, when Bridge starts unexpected behavior out of nowhere first thing to try is a reset of preferences by restarting the application while holding down option key and from the menu choose reset preferences.
My videos, mov files are previewing nicely even at 3.5 Gb. But this current challenge of the program not allowing me to work on anything else while I am batching is troubling.
I'm a bit surprised you did not have experienced this before. It is an OS thing that when applications running in the background come to front when finishing a task. Every time PS finishes a batch task the focus comes to front. But normally you would be able to keep on doing what you are doing IF you have the window you are looking at activated. If you have a browser open you should click on this window to activate it. Then the activated window should stay in front. Same in Mail, Finder or any other applications. Even haven multiple windows open of this application, the activated window stays in front while others of the same app are hided by PS. At least it does so at my (same as you) set up.
As Yammer P also suggested, if you have a save command included in the batch action and have set the sort order to date modified or any other setting that changes the sort order in Bridge Content panel when a task (save) is finished it builds a new (updated) thumb and due to sort order replaces itself to top or bottom of the content panel. this also updates the content window and brings it to focus. As said, this is behavior caused by OSX itself.
But again, this should not effect your front activated window and even with the activated window in front it still can be very disturbing...
And I forgot to mention since I did the recent up grades my camera raw files will no longer update in Bridge. Even though they are correct once I open them they are being shown as raw/unrefined images.
This indicates that either your cache has been effected or something happened with your ACR plug in.
Open PS and in the menu Photoshop look under about plugins / camera raw. Inhere should be only one version showing (for CS 5 this should be 6.7 and for CS6 it shows 7.1)
Also select a file that has not been updated and with right mouse click menu choose 'purge cache for selection'
If this rebuilds the thumb correctly choose the menu tools/cache/ purge cache for folder.

JPG images not displayed correctly in Bridge and Photoshop (Mac OS)

(Note: I have copied the content of this query from the Creative Suites forum where I originally opened it.)
I am using CS4 under OSX 10.4.11 on a PowerMac G5 Quad with 23" Apple cinema display. Images which have been captured as JPG are displayed fine by Preview, but when opened in Bridge, Camera Raw or Photoshop. the colours are all "washed out". The attached screen capture should give an idea of the difference, with the upper being Camera Raw (image settings) and the lower being Preview. My monitor has been calibrated and I'm using sRGB IEC61966-2.1 colour space in Camera Raw and Photoshop. The colours displayed by Preview are pretty close to "real life". I find it virtually impossible to adjust the colours in Photoshop to get back to anything similar.
After opening the image in Photoshop without adjustment, and Save As JPEG with embedded color profile, Preview displays the new image the same as Photoshop. Save As JPEG without embedded color profile, and Preview displays this copy just like the original. It seems that Photoshop is making different (incorrect) assumptions about what color space to use when there is no embedded color profile. Shouldn't it assume sRGB like virtually everything else (http://en.wikipedia.org/wiki/SRGB)? Or is its interpretation of sRGB incorrect? How can I fix this?
Re: JPG images not displayed correctly in Bridge and Photoshop

xxxxyyyyz wrote:
…If there is someone out there who has experience of obtaining decent colour management in CS4 on a Power PC, I would really like to know how you achieved it.
That would be yours truly, and I hasten to reply because I may have some insights that can help you too.
Just get it it out of the way, here's my setup:
Photoshop 11.0.2 ("CS4"); VersionCue disabled and uninstalled.—2.5 GHz Power Mac (PPC) G5-Quad; 16GB RAM; mutant, flashed 550MHz nVidia GeForce 7800GTX 1,700MHz 512MB VRAM; ATTO ExpressPCI UL5D LP SCSI card; Mac OS X Tiger 10.4.11 and Leopard 10.5.8 boot drives; Spotblight, Dashboard and Time Machine permanently disabled; dual 22" CRT monitors; USB wireless 'n' available but connected to the Internet via wired Ethernet; 1 FW flatbed scanner; 2 SCSI scanners (one tabloid-size transparency scanner and a film scanner); various internal & external HDs; FW Epson 2200 and Ethernet Samsung ML-2850ND printers; 2 X Back-UPS RS 1500 XS units.
I can unambiguously and in good faith represent to you that my color management, from capture to print, is as spot-on as anyone with any kind of setup can hope to achieve. Unequivocally and without qualifications.
Now, first things first: Forget about trying to synchronize color management across the point applications lumped together only by Adobe marketing fiat into a variety of meaningless "creative suites". Concentrate on Photoshop. Do not try to use Bridge to synchronize anything.
The "suites" are a totally artificial construct created by Adobe bean counters and marketing types. The point applications (i.e. the individual programs clumsily bundled together, e.g. Photoshop, Illustrator, InDesign, etc.) are developed independently by separate engineering teams that are not only not in the same building, but in different cities, different states of the American Union, and even in different countries. They have very little communication among them, if any, as evidenced by repeated posts in these forums by Photoshop engineering staff urging us, the end users, to let the other teams know in their own forums that a given problem exists and is actually affecting our work.
Enough said about the cause of the problem. The end result is that Color Management is at very, very different levels of progress and sophistication in each individual point application, with only Photoshop fully entitled to be considered state of the art.
Secondly, a disclaimer: I have been hanging on to my CRT monitors and take care of them as Jascha Heifetz used to take care of his Stradivarius. I don't know what I will do if I manage to outlive the usefulness and accuracy of my CRTs (unlikely at this point). I have despaired in futile efforts to bring the luminosity of any LCD monitor down to where I would feel comfortable calibrating and profiling it. I believe my monitors are the foundation of my color management efforts.
Especially if you have one of the extreme wide-gamut LCD or LED monitors, you'll face an uphill battle.
Be careful to avoid any version 4 icc profiles, whether canned or generated by your calibration software. Stick to version2 icc profiles. Ask the manufacturer of your calibration software/hardware if in doubt.
Here are some not-too-recent, but thoroughly representative screen shots of the calibration results I obtain with my monitors, which I calibrate and profile often and regularly (I validate the calibration at least several times per month).
In a nutshell, my color management practices and settings mirror those described by Bruce Fraser, Jeff Schewe, Andrew Rodney and Gary Ballard's site. I have learned from all of them.
My working color space is ProPhoto RGB. I choose to work with PSD and PSB files. As a long-time, rabid JPEG hater, I only rarely deal with JPEGs, using them sporadically to illustrate a point in this forum or elsewhere in the web. My main output consists of prints.
I only deal with tagged image files (files with an embedded color profile) and often recommend beating up with a baseball bat any moron that hands you an untagged file—figuratively of course, but I find the expression gets my point across unambiguously.
Following is a screen shot of some of my pertinent settings:
Note that I have never bought into the "suite" concept myself. I do have and routinely use Adobe Illustrator 10.x, InDesign 2.x and Acrobat Professional 8.x, but they are all older, independent versions of each point application, licensed at different times.
Be further advised, that the answer to many problems offered by Adobe engineers often is not to install VersionCue, or uninstall it, or at least disable it.
Also, as outlined at the beginning of this post, concentrate on Photoshop, not on synchronizing applications that can't really communicate with each other, despite the claims of Adobe marketing hacks to the contrary.
One big caveat, do not fall into this trap:
xxxxyyyyz wrote:
…I believe my problem has nothing to do with my monitor profile, for several reasons, but…
…It seems extremely unlikely to me that…
You either want to learn, or you don't. You either want to solve your problems, or you don't.
When you start arguing instead of studying, questioning advice instead of following it and detecting where you went wrong, you're on the right track to nowhere. That attitude will get you there fast. Remember you are the one with the problem, and only you can acquire the discipline to learn how to solve it.
Go ahead and ask me anything that is not clear, just don't argue with me please, and don't tell me why you think Fraser, Rodney, Ballard and I are wrong. You see, I am not experiencing any problem that needs fixing. I have an interest in helping you, but not in hearing about your speculations, theories or conclusions.
Good luck.
Wo Tai Lao Le
我太老了

Recently upgraded to a Canon Mark 3 and now having issues with my RAW files in Bridge and Photoshop. I am operating with CS4. Photoshop produces an error " Could not complete your request because photoshop does not recognize this type of file"

Recently upgraded to a Canon Mark 3 and now having issues with my RAW files in Bridge and Photoshop. I have operating with CS4. Photoshop produces and error " Could not complete your request because photoshop does not recognize this type of file"

Assuming you mean 5D Mark III, Photoshop CS4 cannot directly open raw files from your camera.
Generally speaking, Adobe stopped updating older versions to be able to read raw files from newer cameras when they released a new major version of Photoshop. Photoshop CS4 is no longer receiving Camera Raw updates.
You can double check this yourself:
First you need to determine whether Adobe has released support for your new camera in your version of Photoshop. To do that, look at these two pages. You'll want to find out the earliest version of Camera Raw that can support your camera, then what version of Photoshop can run that version of Camera Raw.
Camera Raw plug-in | Supported cameras
Camera Raw-compatible Adobe applications
If you find your camera is supported by your version of Photoshop, you need to download the latest update for Camera Raw. There's more information on how to do that here:
Keeping Photoshop Up-To-Date
If your version of Photoshop cannot support your camera, you can download and install the latest version of the free Adobe DNG Converter, which can take your raw files as input and put out DNG format files, which your version of Photoshop can open.
Photoshop Help | Digital Negative (DNG)
The DNG converter DOES work, but if you want maximal quality from your raw files (not to mention the convenience and ease of use of directly opening your raw files) you'll want the latest version of Photoshop. Adobe has made substantial improvements in raw conversion quality in recent years.
-Noel

HT201077 After updating my iPhone4s to the lastest update my photostream stopped updated onto my comuter. From my phone it looks like pictures have been moved into the photostream folder... but they are not showing up on my computer. Help!

After updating my iPhone4s to the lastest update my photostream stopped updated onto my comuter. From my phone it looks like pictures have been moved into the photostream folder... but they are not showing up on my computer. Help!
I have signed out then back into the cloud. I have comfirmed location of the photostream folder. I have have even restored settings on my phone. any ideas on what I can do to get it working again? or do I have to accept defect, and manually save my photos?

There's a whole lot to read in your post, and frankly I have not read it all.
Having said that, this troubleshooting guide should help:
http://support.apple.com/kb/TS1538
In particular, pay attention to the mobile device support sections near the bottom, assuming you have already done the items above it.

Why are my images suddenly darker in camera raw and photoshop C4 than when I open them in bridge?

Why are my images suddenly darker in camera raw and photoshop C4 than when I open them in bridge?

"Catalog"? Are you referencing Ps Elements perhaps?
Wrong forum. We do not do Elements here.
Here's the link to the Elements forum:
Photoshop Elements

I am using CC v17.1 on a PC. I have recently taken over design responsibilities from someone who used a Mac. I need to use the Cygnet Round font, but it looks completely different on my PC than it did on the Mac.

I am wondering if fonts look different on a PC than a Mac. The font I am using is Cygnet Round, and it is completely different on my PC. I am at a loss....
Any help would be greatly appreciated!

Hi John, I am using Adobe Illustrator CC Version 17.1.

Pictures look completely different in Aperture

I shoot with a Pentax K200D with RAW+JPEG using the PEF format for RAW files. I then use Apple Aperture to edit the files, but I recently noticed that pictures converted to jpeg using aperture looke very different from the PEF files when viewed side by side.

Like RWB I am a bit confused by your query, but my guess is that you may at some point be comparing files derived from RAW PEF captures against captured JPEGs. In addition to being compressed, captured JPEGs have typically been heavily adjusted in-camera for color, sharpness, etc. Prior to editing, files derived from RAW captures will appear flat in comparison to such files.
-Allen Wicks

HT1338 my mac book pro is constantly "looking for networks" while connected using my home network and other wifi systems. how can i stop it?

Why is my Mac Book constantly "looking for networks" while i am using wifi?

If it is constantly searching for networks every five seconds or so, then it is the bluetooth - wifi problem discussed on other threads. I find that system preferences > network and clicking at the bottom on the 'Show wi-fi status in menu bar' button to switch it off, and then back onto the menu bar, solves the problem. Sometimes on waking I lose wi-fi completely and have to reload, but that's infrequent.
Hopefully Apple will come up with a solution soon.

Completely different objects in Exchange management consoles 2010 and 2013

HI scripting guys,
First, apologies for the non-specific title. This is not the first incompatibility I am finding (e.g. scripts perfectly working in exchange console 2010 do not work in 2013).
Here is my current problem. I spent a good amount of time, but shame on me could not solve it.
I run the following line:
Get-MailboxPermission $mailbox |select @{Name="Access";Expression={([string]::join(',', $_.AccessRights))}}
and get what I want in EMC 2010:
Access
FullAccess, SendAs, ReadPermission
FullAccess, DeleteItem
FullAccess, DeleteItem
However in EMC 2013 I get the following instead:
Access
System.Collections.ArrayList
System.Collections.ArrayList
System.Collections.ArrayList
Which is a clear sign that at some point the objects are different.
Edit: Just before sending this, I added out-string this way:
Get-MailboxPermission $mailbox |select @{Name="Access";Expression={([string]::join(',', ($_.AccessRights|out-string)))}}
which made the script to work in both consoles but introducing the nasty ellipsis:
Access
FullAccess, SendAs, ReadPermission...
FullAccess, DeleteItem...
FullAccess, DeleteItem...
Piping the above to "format-table -wrap -autosize" is not a solution. It helps with the ellipsis but introduces blank lines:
Access
FullAccess, SendAs, ReadPermission
FullAccess, DeleteItem
FullAccess, DeleteItem
I would greatly appreciate if you can help me with this !
Thank you !

one day later, mission accomplished.
joining strings is not necessary and should be removed in that line in ems 2013 because each "row" is a single string. In contrast in ems 2010 the permissions for each user are an array of strings which need to be joined first in order to user
"replace" further. For example in ems 2013 my actual line now looks like this:
Get-MailboxPermission $mailbox |Select @{Name="User";Expression={$_.User.tostring().replace("UVIC\","")}},@{Name="Access";Expression={$_.AccessRights.replace("Full","Full ").replace("Delete","Delete
")}}| sort user| format-table -auto
and the output looks for example like this:
Access
Full Access, Delete Item
Full Access
Full Access
Which is what I wanted to accomplish in the first place.
=============================================
Now since I could not find ANYTHING online about incompatibilities between Exchange management shell 2010 and Exchange management shell 2013 , let me share one more:
it is about "send on behalf" permissions:
after:
$MBox = Get-Mailbox $MailboxName
$SoB=$Mbox.grantsendonbehalfto
things get different to list the users who has Send on behalf permissions for EMS 2013 and EMS 2010
in 2010:
foreach($S in $SoB){$S.name}
while in 2013:
foreach($S in $SoB){$S}
again in EMS 2013 the things are simpler - $S is just a string

My images look completely different while I'm working in Bridge and Photoshop (CS6) than they do once they are saved.

Similar Messages

Maybe you are looking for