Gamma changed in snow leopard

My pictures all look darker with the installation of Snow Leopard. Is there an operation that I can do to thousands of pictures as a batch, that will lighten them back to what they used to look like on screen?

Snow Leopard changed the monitor's gamma from 1.8 to 2.2. You can use the System/Display preference pane to recalibrate the screen and change the gamma setting back to 1.8.

Similar Messages

How can I save my keepsake photo albums as PDFs in my album folder. Since I changed from Snow Leopard to Lion last year I have't been able to do this.

How can I save my keepsake photo albums as PDFs in my album folder. Since I changed from Snow Leopard to Lion last year I have't been able to do this.

preview it using this method -http://support.apple.com/kb/HT1040 - and save the resulting PDF
Is this what you are doing?Your description does not sound like you are
LN

Why am i having problems since changing from snow leopard loading maverick

why am i having problems since changing from snow leopard downloading maverick

Yes you solved your own question, use printer handles color, whcih shodul have been the default. If you do want to experiment with Photohsop manages color, try the CMYK profiles, and send a cmyk file. Only exception is if you print to one of the few RGB printers like a lambda.

Renaming a file in Finder changed with Snow Leopard somehow?

I've used an AppleScript for ages to:
1. choose a file (a screenshot)
2. prompt for a new name
3. File is renamed by Finder with new name
4. compose a command to copy it to another server
It seems Finder is not updating the "alias" to the file since I upgraded to Snow Leopard; this very code has worked for the last few versions of OS X:
set screencap to (choose file with prompt "Choose the screen shot: ")
display dialog "Enter new file name: " default answer "foo"
set newname to (the text returned of result as string)
set newnamepng to (newname as string) & ".png"
log "newname is " & newname & " newnamepng is " & newnamepng
log "screencap is " & screencap
tell application "Finder"
set the name of screencap to (newnamepng as string)
end tell
log "the name of screencap is now: " & screencap
set posixscreencap to the POSIX path of screencap
set scpcmd to "scp " & posixscreencap
log scpcmd
Here's what happens when I run it:
tell application "AppleScript Editor"
choose file with prompt "Choose the screen shot: "
--> alias "Einny:Users:swain:Desktop:Screen shot 2010-09-13 at 2.06.44 PM.png"
display dialog "Enter new file name: " default answer "foo"
--> {text returned:"newnameforscreenshot", button returned:"OK"}
end tell
(*newname is newnameforscreenshot newnamepng is newnameforscreenshot.png*)
(*screencap is Einny:Users:swain:Desktop:Screen shot 2010-09-13 at 2.06.44 PM.png*)
tell application "Finder"
set name of alias "Einny:Users:swain:Desktop:Screen shot 2010-09-13 at 2.06.44 PM.png" to "newnameforscreenshot.png"
--> "newnameforscreenshot.png"
end tell
(*the name of screencap is now: Einny:Users:swain:Desktop:Screen shot 2010-09-13 at 2.06.44 PM.png*)
(*scp /Users/swain/Desktop/Screen shot 2010-09-13 at 2.06.44 PM.png*)
For some reason the file alias "screencap" does not get a new name. Any suggestions?

When I run your script, the file name does get changed, it is just that the Finder is not keeping up with the script. There are a few fixes:
1) add a short delay after the rename (delay 1 seems to be enough)
2) use *System Events* instead of the Finder
3) add an update command after setting the name in your FInder tell statement (e.g. update screencap)
Note that an alias will still point to the same file item (even if it does have a different name), but the POSIX path of the alias object does need to be updated before you can use that.

Question about changing a Snow Leopard Server network settings

We have an Xserve running Mac OS X Server 10.6.8, the primary services running on it are afp, smb, dhcp, dns, jabber and the calendar sever.
Right now we have a router connecting two networks together, 192.168.0.0/24 and 192.168.1.0/24. The Xserve has a static IP address in the 192.168.0.0/24 range.
In order to combine two phone systems into one I am required to combine the above networks, this will involve removing the router and changing the subnet mask on every device from 255.255.255.0 to 255.255.254.0, any device that is currently part of the 192.168.1.0/24 network will also need to have it's router setting changed from 192.168.1.1 to 192.168.0.1. That part should all be easy.
However, this is my first experience expanding a network past a standard class C and am wondering if there is anything I need to watch for on my Snow Leopard Sever.
Specifically I wonder about dhcp settings, right now there are two dhcp servers, the Xserve which provides dhcp for 192.168.0.0/24 and the router that provides dhcp for 192.168.1.0/24. Once the router is removed the Xserve will need to provide dhcp for the entire network.
Looking at the Xserve dhcp configuration right now I have one subnet defined providing addresses 192.168.0.5 to 192.168.0.125.
Can I simply click the + to add another subnet and add for instance a range of 192.168.1.5 to 192.168.1.125?
Will it simply give out all of the ip addresses in the first range and then start with the 2nd? Or do I need to find a single range of ip addresses large enough to meet my needs? (e.g. 192.168.1.5 to 192.168.1.225 or something).
Is there anythign else to watch for after making this type of network setting change?
Thanks in advance.

Thank you for your very detailed reply.
I understand the problems that can arise using 192.168.0.x and 192.168.1.x and if this were a new project I would definitely switch to something else, however in this case we have been using these ip ranges for years (they were in use here long before I started) and I don't want to have to redo all of my dns settings at the same time I make these other changes so I'm going to stick with the same ip's we are using at least for now. Anyone here needing vpn access has already dealt with this issue but we have very few vpn users so it has not been a major problem for us to date.
My biggest question is about increasing the size of the dhcp pool. For instance, after I change all the network settings and set up a /23 network is it possible to have a single dhcp pool that includes some ip's in the 192.168.0.x range and others in the 192.168.1.x range? I guess what I am asking is when I am in Server Admin and click on DHCP one of the tabs across the top is "Subnets". Right now there is a single "subnet" configured that provides addresses from 192.168.0.5 to 192.168.0.125.
Ideally I would like one dhcp pool that provides ip's in the range of 192.168.0.5 to 192.168.0.125 and then if all of those are used up, moves to 192.168.1.5 to 192.168.1.125. Can I do that by simply adding another "Subnet" so there are two? Or do I have to find one larger single range? (e.g. 192.168.1.5 to 192.168.1.225?) You may have already answered this indicating I have to have a single larger range but I just want to be sure.
The parts about changing subnet masks, and routers and all that I think I have a pretty good understanding of.
Your last paragraph is something I have been worried about, I do have a feeling that after making this change there will probably be unforseen issues that will need to be resolved, I'm just hoping it is not too many. For the scope of this thread I will just focus on issues that may arise with the Snow Leopard Server however.
Again, thank you for your help.

IDVD Quality Changed after Snow Leopard Upgrade

I created two different iDVD projects (slide shows with music) and burned them to DVDs - great quality, no problems with transitions, or quality of slides displayed. These copies were viewed in a BlueRay player, etc. After I upgraded to Snow Leopard I made two more copies without adding anything to the projects or changing the project settings. Quality is now terrible. The transitions are choppy, and each slide is displayed slightly less bright than it should be, then it jumps to a normal brightness, then goes back to a dimmer setting as the photos change. This did not occur on the originals before the OS upgrade. If I run the project on my MAC it all looks fine. This problem comes up after burning to DVD.
Any ideas?

Hi TJ1955
Welcome to apple discussions. Sorry to hear about the issues with burning to disc you are experiencing at the moment. I'm not sure I can help with this issue without being directly in front of your mac and seeing what's going on. So I'll simply supply you with the apple KB aticle detailing / troubleshooting burn issues to dvd.
http://support.apple.com/kb/HT1583?viewlocale=en_US
If you opt to return to the forum we'll also need more info on the mac model you are currently using and which third party items you have connected to it (if any). Lastly we will need to know how much available hard drive space is remaining on the boot volume (your main startup HD) as well as what type or brand of dvd's you are currently using and if it varied from the original /first burn.
As a final resort you may wish to try the following. Burn your iDvd project to a disc image from the file menu within iDvd (provided you have the available HD space). The disc image acts exactly like a dvd so use apple's dvd player to test for proper playback. Assuming it plays exactly as expected, then burn to Verbatim, Taiyo Yuden, or Maxell Dvd-R at 4x. Please avoid using Memorex while we troubleshoot your issue here. This latter brand of dvd's tends to introduce additional variables into the equation making troubleshooting all that much more complicated. Thereafter, (assuming we resolve the issue) feel free to use whatever brand works best for you and your mac.
Hope this helps but if not come on back.
Message was edited by: SDMacuser

Did Apple Script change - upgraded Snow Leopard Mavericks

I used to use below script to toggle sound output (assigned to function key) in Snow Leopard.
Upgraded to Mavericks few weeks ago and wanted to use that script again, but keep on getting error -1728 as displayed hereafter, anyone out there to tell me what I should do to make it work in Mavericks?
Thx,
Laerg1
Here's the full script:
--This script toggles between two audio outputs in the "Sound" pane in "System Preferences.
--USES GUI SCRIPTING - "ENABLE ASSISTIVE DEVICES" OPTION MUST BE CHECKED IN "UNIVERSAL ACCESS" PREFERENCE PANE
--Adapted from script written by Corey Menscher for toggling outputs using Salling Erickson Clicker
tell application "System Preferences"
    activate
end tell
tell application "System Events"
    tell application process "System Preferences"
        set frontmost to true
        click menu item "Sound" of menu "View" of menu bar 1
        if my wait4window("Sound") is false then return false
        tell window "Sound"
            tell tab group 1
                tell radio button "Output"
                    click
                end tell
                (* You can add your own audio output descriptive text, such as "iMic USB Audio", in the next section. *)
                if (selected of row 2 of table 1 of scroll area 1) then
                    set selected of row 1 of table 1 of scroll area 1 to true
                else
                    set selected of row 2 of table 1 of scroll area 1 to true
                end if
            end tell
        end tell
    end tell
end tell
tell application "System Preferences" to quit
on wait4window(this_title)
    tell application "System Events"
        tell process "System Preferences"
            repeat with i from 1 to 60
                if the name of window 1 is this_title then return true
                delay 1
            end repeat
        end tell
    end tell
    return false
end wait4window

Let's double-check the amount of RAM in that machine. Click the Apple logo in the upper left corner & choose About This Mac. In the window that comes up, what's listed for RAM?
That machine will run Snow Leopard very nicely with 2GB of RAM. For it to run Mavericks, I would upgrade it to at least 4GB or more if it can handle it.
If I was in your position, I would run Snow Leopard for a while and see how well it serves you. If you want to upgrade, my personal opinion would be to go to Mountain Lion, rather than Mavericks, but that is simply because I found that Mavericks slowed one of my machines to a crawl and was not pleased with the performance. Went back to Mountain Lion and it's humming along.
~Lyssa

New refurb Macbook Pro (2010 build)-change to Snow Leopard with TM backup?

During the startup of the new MacBook Pro (Refurbished MacBook Pro 2.66GHz Intel Core i7 that shipped with Lion installed) it asks if I want to use a Time Machine backup to migrate my stuff. If I use a Snow Leopard Time Machine backup will the new computer now run on Snow Leopard? Or will it convert the backup to Lion?

Check this link:
http://pondini.org/TM/14.html
This should put you on the right track.
Ciao.

Is changing from snow leopard to lion a big issue today?

I am considering upgrading to Lion today, is there any big issues or reasons why I shouldn't?
Does anybody have recomendations on a smooth process?
Thanks Jody

I highly advise making a bootable clone of Snow Leopard using Carbon Copy Cloner (better and donationware) or SuperDuper (part free and payware)
http://www.bombich.com/get_ready_for_lion.html
Also if your using TimeMachine, is NOT to hook up to the Snow Leopard TM drive to a Lion machine until your absolutely sure you don't want to revert to Snow Leopard.
Your MacPro should be able to handle Lion well as it's more powerful, but Lion is a slower OS than Snow Leopard and won't run your Rosetta.PPC based software of old.
So you might find out a lot of your software will not work and then want to revert to Snow Leopard rather than pay for Lion upgrade versions of third party software.
And you really need 4GB of RAM for Lion, 2GB is bare minimum and not advised.
As far as a smooth process? All depends how "clean" your Snow Leopard machine is.
Normally MacPro users are professional, and install a lot of third party software to use their machines as tools.
A fresh install of Snow Leopard is advised in that case.
This is the ideal method, a lot more work but results in a pristine machine.
1: Backup personal data off the machine and disconnect.
2: Erase and install 10.6, then to 10.6.8 use same user name as before.
3: Upgrade to 10.7 to 10.7.2
4: Install programs from fresh sources
5: Files from backup.
Note: a lot of third party hardware haven't written software drivers for Lion yet, some are not doing so to force you to buy a new printer, scanner, copier etc.
That's another thing you need to check out first before blindly pushing that update button.

DNS Settings have Changed with Snow Leopard Update

Before I upgraded to SL, I was able to append a DNS server to the list of servers that my MacBook Pro acquired from the DHCP server. This way, I didn't have to manually edit my DNS settings all the time when I was in the office and wanted to access our lab network by name. Now after the upgrade, I have to remove all manually entered DNS servers before it will use the DNS servers given to it by the DHCP server. Is there a way that I can always append my lab DNS server to the list given to me by DHCP?
Thanks,
John

I am on or office wireless network which handles the DHCP lease and DNS addressing, but I am an engineer in the office and access the lab often and we have another DNS server in the lab to handle all of the lab network. The Sales folk don't need access to the lab so the DHCP server doesn't give out the lab dns server... I would like to access the lab via name, not IP, so I need the lab DNS server on my list of servers. If I can't append this to the DHCP list, I have to manually add all three every time I am in the office. I am frequently out at customer/vendor sites and use thier wireless, so I get thier DNS list.
Short answer is I need our lab DNS server on the list and frequently move from network to network... I want it to work the way it was before the "upgrade", which wasn't much of an "upgrade" if it breaks this. I want my Leopard back.
John

STILL CAN'T "CHANGE ALL" SNOW LEOPARD RETARDATION.

APPLE STOP THE RETARDATION!
PLEASE LET PROFESSIONAL USERS HAVE THE OPTION OF OPENING ALL .MOV FILES IN QUICKTIME PRO 7!!!!
YOU KNOW, LIKE WE USED TO BE ABLE TO DO! IN 10.5!!
I'd downgrade if I didn't have to wipe my drive and start over...
And QuickTimeKirk...please don't respond, as you are absolutely wrong if you think 10.6 doesn't override the option of changing the "open with" when you try to change all.
When you're designing and rendering, you don't want to be bothered with changing each of hundreds of renders to open with the PRO version of the software on your machine!

http://www.apple.com/quicktime/feedback
We're all just your fellow users here.
And QuickTimeKirk...please don't respond, as you are absolutely wrong if you think 10.6 doesn't override the option of changing the "open with" when you try to change all.
Kirk is not "absolutely wrong", since it works for some people, including for me, though not for others. As yet I've seen nothing to identify why it fails on some systems.

Has the behavior of 'run script' changed in Snow Leopard?

These work fine:
tell application "Safari"
return URL of front document
end tell
tell application "Safari"
set longURL to URL of front document
return longURL
end tell
This does not:
set getFrontmostURLCommand to "URL of front document"
tell application "Safari"
set longURL to run script getFrontmostURLCommand
end tell
return longURL
Why? It looks like a script interpretation error but I can't figure out what's wrong.
The error returned is:
error "Safari got an error: Can’t get URL of document 1." number -1728 from "URL of front document"

I see. Is there a way to make the application variable? I'm writing a function because getFrontmostURLCommand works with a couple of different browsers and I want it to be run conditionally based on the user's browser. Something like this:
set defaultBrowser to GetDefaultWebBrowser()
on GetDefaultWebBrowser()
set _scpt to "export VERSIONERPERL_PREFER_32BIT=yes; " & -
"perl -MMac::InternetConfig -le " & -
"'print +(GetICHelper \"http\")[1]'"
return do shell script _scpt
end GetDefaultWebBrowser
on defaultGetFrontmostURLCommand(defaultBrowserApplication)
tell application defaultBrowserApplication to set longURL to URL of front document
end defaultGetFrontmostURLCommand
on caminoGetFrontmostURLCommand()
tell application "Camino" to set longURL to URL of current tab of browser window 1
end caminoGetFrontmostURLCommand
if defaultBrowser is in {"Safari", "WebKit", "Opera"} then
defaultGetFrontmostURLCommand(defaultBrowser)
else if defaultBrowser is "Camino" then
caminoGetFrontmostURLCommand()
end if
set the clipboard to longURL

Snow Leopard's Default Gamma & Color Correcting for Pre Press in Photoshop CS4

After searching the forums I thought I would start my own thread on this subject.
I have Photoshop CS4 and InDesign CS4 and I have continued to color correct, for pre press, in OS 10.4.11 Tiger with the 1.8 Default Gamma and 6500 color tempurature, using Apple's display calibration tools in the OS's System Preferances.
I want to switch to Snow Leaopard but with it's Defualt Gamma of 2.2, I'm not able to make my minitor manually adjust to the needed range for brightness and contrast that is needed to begin the calibration process. Is there a way to color correct photos, for pre pre press, in Photoshop with a 2.2 Gamma setting in my display preferances?

I have had success just with Apple's System Preferences for color calibration. I do design and pre press for a number of customers of the various printers I work with. Most of the photos I work with are from digital cameras and are provided by the customer. The only point in the whole process, where the photos get adjusted to have eye pleasing color, when coming off the printing press, is when I work with them.
The printers I work with continue to send their customers to me, for design and pre press, because they like my color work on the photos. I send the pre press files as Press Optimized PDFs to the printer's FTP server and the printer does all the direct to plate separations in-house. I want to continue to be reliable in that area and so the brighter default Gamma built into Snow Leopard seems to complicate things if I ever want to move up from Tiger to Snow Leopard.
I have two 17" Apple CRT displays that cannot adjust into calibration range when I'm booted in Snow Leopard. These CRT displays can only manually adjust in range for calibration under Tiger or Leopard. It sounds like if I purchase an IPS based LCD monitor, made by Apple, Dell, or other brands, I will probably be able to manually adjust the display for Gamma 1.8, under Snow Leopard.
I was posing this question about using Gamma 2.2 because if I could color correct for pre press with the 2.2 setting, I could continue to use my old Apple 17" CRT displays and also any web content I create will preview closer in color, on PCs as they will on my Mac. Maybe my review PDFs will view with similar color on my customers PCs if I work with a 2.2 Gamma setting and instead of 1.8. For now I know I will keep my printers happy if I continue to work with a monitor that has a 1.8 Gamma setting and a 6500 color temperature setting. If that must continue to be the standard for pre press, then I will need to get an IPS based LCD monitor that will allow me to adjust in the 1.8 Gamma range while booted in Snow Leopard.

Snow Leopard Issues Again

Ever since I have installed Snow Leopard my camera profile doesn't seem to be right. My pictures look awesome on the back of my D3 and also in "Photo Mechanic" which I'm told is just a jpg preview of the RAW file, but once I import them into Lightroom they look awful. I was told that the gamma point on Snow Leopard is 2.2 and the default for Leopard was 1.8. Would this affect the import preset to not work properly? Will new camera profiles come out now that Snow Leopard is on the scene? Just wondering. Thanks.
Jim Shields

If you could be more specific about what changes you see, perhaps posting a screen shot or two, we might be able to nail this down better. In my own experience, upgrading to Snow Leopard didn't change anything.

Font errors in some fonts (missing "o") only when printing. Snow Leopard.

In a couple of fonts I use most commonly, the letter "o" (lower case o), does not print. A space appears when the letter should be. It displays fine on the screen. In a QuickView of the font file, the letter is also missing. This just started after I upgraded to Snow Leopard.
1. What is causing this?
2. How can I fix it?
3. Is there a good application that will let me see in innards of the font in detail?
4. How could the display differ from the printed version?
More info:
These fonts were originally purchase a long time ago (about 15 years ago) from Adobe. They are Berkeley and InterState.
The problem occurs in all variations of the fonts.
I have 100s of fonts; so far only these two are affected, but I haven't been able to look at every other font.

What I don't understand is 1) why these fonts worked in Leopard but not Snow Leopard and 2) why these particular fonts.
If you search you will find a large number of posts in these forums about changes in Snow Leopard related to fonts, e.g.
http://discussions.apple.com/thread.jspa?threadID=2154431&start=0&tstart=0

Gamma changed in snow leopard

Similar Messages

Maybe you are looking for