Using Illustrator CS6, how to preserve drawn colors when Save For Web to PNG?

Using Illustrator CS6 on Mac OSX 10.9.1:
step 1. I open a new file for Web profile.
step 2. I verify that File > Document Color Mode is RGB.
step 3. I draw a square and set it's color to 0,103,197 (decimal).
step 4. I click File > Save For Web
step 5. In the popup that opens, I set to PNG-24, and verify the option Convert To sRGB is not selected.
step 6. Using the Mac's DigitalColorMeter, I observe the color is 0,109,191 in the Save For Web popup. If I save it, then open the saved PNG file, it's color is also 0,109,191.
How to do this so the colors don't change?
step 7. I close Save For Web popup.
step 8. I verify Edit > Color Settings for Working Spaces is set to Monitor RGB, and that the Color Management Policies for RGB is off.
step 9. I verify Edit > Assign Profile is set to Don't Color Manage This Document.
step 10. I verify View > Proof Colors is off.
Can anyone provide a set of Illustrator CS6 settings that let me save a PNG image with the same colors it's drawn in so I can use that PNG image in a website?
I must be missing something obvious, because anyone working in web design must do this day in and day out, please let me know what procedure people follow to achieve this.
UPDATE:
Using the above procedure DOES preserve the colors when embedding the PNG image in a webpage viewed in Firefox and Chome, but NOT for Safari. Also, the colors are not preserved in Mac's Preview software, as well as Microsoft Office 2011 for Mac.
I'm pretty new to all this. Hoping someone can provide some perspective on what typical procedure people use for web development when working with colors in Illustrator CS6.

Using Illustrator CS6 on Mac OSX 10.9.1:
step 1. I open a new file for Web profile.
step 2. I verify that File > Document Color Mode is RGB.
step 3. I draw a square and set it's color to 0,103,197 (decimal).
step 4. I click File > Save For Web
step 5. In the popup that opens, I set to PNG-24, and verify the option Convert To sRGB is not selected.
step 6. Using the Mac's DigitalColorMeter, I observe the color is 0,109,191 in the Save For Web popup. If I save it, then open the saved PNG file, it's color is also 0,109,191.
How to do this so the colors don't change?
step 7. I close Save For Web popup.
step 8. I verify Edit > Color Settings for Working Spaces is set to Monitor RGB, and that the Color Management Policies for RGB is off.
step 9. I verify Edit > Assign Profile is set to Don't Color Manage This Document.
step 10. I verify View > Proof Colors is off.
Can anyone provide a set of Illustrator CS6 settings that let me save a PNG image with the same colors it's drawn in so I can use that PNG image in a website?
I must be missing something obvious, because anyone working in web design must do this day in and day out, please let me know what procedure people follow to achieve this.
UPDATE:
Using the above procedure DOES preserve the colors when embedding the PNG image in a webpage viewed in Firefox and Chome, but NOT for Safari. Also, the colors are not preserved in Mac's Preview software, as well as Microsoft Office 2011 for Mac.
I'm pretty new to all this. Hoping someone can provide some perspective on what typical procedure people use for web development when working with colors in Illustrator CS6.

Similar Messages

  • Illustrator crashes when save for web

    Mac OS X 10.8.4
    Illustrator CS 6
    Everytime I try to do save for web in Illustrator CS6 it gets hung up and I end up having to force quit the program. I have uninstalled and re-installed the software and it works once but then goes back to doing the same thing. I also noticed that now the program is getting hung up when I  try to undo a move or text and again I will have to force quit the program. Any suggestions are greatly appreciated

    Sorry about that here is what i get
    Date/Time:  
    2013-06-13 10:36:15 -0500
    OS Version: 
    10.8.4 (Build 12E55)
    Architecture:
    x86_64
    Report Version:  11
    Command:    
    Illustrator
    Path:       
    /Applications/Adobe Illustrator CS6/Adobe Illustrator.app/Contents/MacOS/Adobe Illustrator
    Version:    
    723 (16.0.0)
    Parent:     
    launchd [144]
    PID:        
    2006
    Event:      
    hang
    Duration:   
    1.12s
    Steps:      
    12 (100ms sampling interval)
    Hardware model:  iMac12,2
    Active cpus:
    4
    Free pages: 
    6968 pages (-2870)
    Pageins:    
    15 pages
    Pageouts:   
    0 pages
    Process:    
    Adobe Illustrator [2006]
    Path:       
    /Applications/Adobe Illustrator CS6/Adobe Illustrator.app/Contents/MacOS/Adobe Illustrator
    Architecture:
    x86_64
    Parent:     
    launchd [144]
    UID:        
    501
    Task size:  
    193628 pages (+6)
    CPU Time:   
    0.001s
      Thread 0x12d6a
    DispatchQueue 1     
    priority 47   
      12 ??? (Adobe Illustrator + 1454936) [0x100163358]
    12 ??? (Adobe Illustrator + 7310260) [0x1006f8bb4]
    12 ??? (Adobe Illustrator + 7376353) [0x100708de1]
    12 ??? (Adobe Illustrator + 7772760) [0x100769a58]
    12 exo::app::OS_AppBase::RunEventLoop() + 55 (exo) [0x108e71747]
    12 -[NSApplication run] + 517 (AppKit) [0x7fff9513d1a3]
    12 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128 (AppKit) [0x7fff95145df2]
    12 _DPSNextEvent + 2073 (AppKit) [0x7fff95146a9f]
    12 _NSHandleCarbonMenuEvent + 245 (AppKit) [0x7fff952248c6]
    12 _HandleMenuSelection2 + 565 (HIToolbox) [0x7fff93e4dec8]
    12 MenuSelectCore(MenuData*, Point, double, unsigned int, OpaqueMenuRef**, unsigned short*) + 605 (HIToolbox) [0x7fff93e4e8bb]
    12 FinishMenuSelection(SelectionData*, MenuResult*, MenuResult*) + 94 (HIToolbox) [0x7fff93e7285f]
    12 SendMenuItemSelectedEvent + 254 (HIToolbox) [0x7fff93e729d3]
    12 SendMenuCommandWithContextAndModifiers + 59 (HIToolbox) [0x7fff93e72a21]
    12 SendHICommandEvent(unsigned int, HICommand const*, unsigned int, unsigned int, unsigned char, void const*, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef**) + 443 (HIToolbox) [0x7fff93ecdca9]
    12 SendEventToEventTarget + 40 (HIToolbox) [0x7fff93e96fc9]
    12 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 410 (HIToolbox) [0x7fff93e811e9]
    12 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1206 (HIToolbox) [0x7fff93e81d1a]
    12 NSSLMMenuEventHandler + 342 (AppKit) [0x7fff95365165]
    12 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 135 (AppKit) [0x7fff95059097]
    12 -[NSMenu _internalPerformActionForItemAtIndex:] + 36 (AppKit) [0x7fff9505920f]
    12 -[DVAMacMenu performActionForItemAtIndex:] + 61 (dvaui) [0x10862293d]
    12 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 133 (AppKit) [0x7fff9536c05a]
    12 -[NSMenuItem _corePerformAction] + 406 (AppKit) [0x7fff9536c36c]
    12 -[NSApplication sendAction:to:from:] + 342 (AppKit) [0x7fff95236959]
    12 -[ExoMacApplication handleMenuCommand:] + 187 (exo) [0x108e73e9b]
    12 void dvacore::config::ExecuteTopLevelFunction<void>(boost::function0<void>, bool*) + 93 (dvacore) [0x107ef497d]
    12 void dvacore::config::ErrorManager::ExecuteFunctionWithTopLevelExceptionHandler<void>(boost::f unction0<void>, bool*) + 250 (dvacore) [0x107ef0e9a]
    12 ??? (Adobe Illustrator + 7781211) [0x10076bb5b]
    12 int dvacore::config::ErrorManager::ExecuteFunction<void>(boost::function0<void>*, void*) + 123 (dvacore) [0x107ef1e0b]
    12 exo::app::OS_AppBase::DispatchMenuCommand(int) + 119 (exo) [0x108e72417]
    12 exo::uisupport::CommandHandlerBase::CallCommandChain(int) + 62 (exo) [0x108ee7ffe]
    12 exo::uisupport::CommandHandler::DoCallMyCommandChain(int) + 36 (exo) [0x108ee85f4]
    12 exo::uisupport::CommandHandler::HandleCommand(int) + 259 (exo) [0x108ee85a3]
    12 ??? (Adobe Illustrator + 7773972) [0x100769f14]
    12 ??? (Adobe Illustrator + 4782547) [0x10048f9d3]
    12 ??? (Adobe Illustrator + 11859237) [0x100b4f525]
    12 ??? (Adobe Illustrator + 9860322) [0x1009674e2]
    12 std::_Rb_tree<SPSUAS, std::pair<SPSUAS const, int>, std::_Select1st<std::pair<SPSUAS const, int> >, std::less<SPSUAS>, std::allocator<std::pair<SPSUAS const, int> > >::erase(SPSUAS const&) + 13900 (Adobe Illustrator) [0x100c951ac]
    12 std::_Rb_tree<SPSUAS, std::pair<SPSUAS const, int>, std::_Select1st<std::pair<SPSUAS const, int> >, std::less<SPSUAS>, std::allocator<std::pair<SPSUAS const, int> > >::erase(SPSUAS const&) + 1228 (Adobe Illustrator) [0x100c9202c]
    12 std::_Rb_tree<SPSUAS, std::pair<SPSUAS const, int>, std::_Select1st<std::pair<SPSUAS const, int> >, std::less<SPSUAS>, std::allocator<std::pair<SPSUAS const, int> > >::erase(SPSUAS const&) + 24282 (Adobe Illustrator) [0x100c97a3a]
    12 ??? (Adobe Illustrator + 9941771) [0x10097b30b]
    12 ??? (Adobe Illustrator + 10209243) [0x1009bc7db]
    12 ??? (Adobe Illustrator + 10207557) [0x1009bc145]
    12 std::_Rb_tree<SPSUAS, std::pair<SPSUAS const, int>, std::_Select1st<std::pair<SPSUAS const, int> >, std::less<SPSUAS>, std::allocator<std::pair<SPSUAS const, int> > >::erase(SPSUAS const&) + 13900 (Adobe Illustrator) [0x100c951ac]
    12 std::_Rb_tree<SPSUAS, std::pair<SPSUAS const, int>, std::_Select1st<std::pair<SPSUAS const, int> >, std::less<SPSUAS>, std::allocator<std::pair<SPSUAS const, int> > >::erase(SPSUAS const&) + 1228 (Adobe Illustrator) [0x100c9202c]
    12 std::_Rb_tree<SPSUAS, std::pair<SPSUAS const, int>, std::_Select1st<std::pair<SPSUAS const, int> >, std::less<SPSUAS>, std::allocator<std::pair<SPSUAS const, int> > >::erase(SPSUAS const&) + 24282 (Adobe Illustrator) [0x100c97a3a]
    12 PluginMain + 744254 (Save4Web) [0x13a8bbeee]
    12 PluginMain + 10078 (Save4Web) [0x13a808b0e]
    12 PluginMain + 6324 (Save4Web) [0x13a807c64]
    12 PluginMain + 314709 (Save4Web) [0x13a853105]
    12 ??? (Save4Web + 104750) [0x13a7f392e]
    12 dvaui::ui::OS_Dialog::RunModal() + 175 (dvaui) [0x1085dd88f]
    12 dvaui::ui::OS_Dialog::ModalLoop() + 177 (dvaui) [0x1085ddbe1]
    12 -[NSApplication runModalSession:] + 49 (AppKit) [0x7fff95390d8e]
    12 -[NSApplication _realDoModalLoop:peek:] + 485 (AppKit) [0x7fff95390659]
    12 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128 (AppKit) [0x7fff95145df2]
    12 _DPSNextEvent + 685 (AppKit) [0x7fff95146533]
    12 BlockUntilNextEventMatchingListInMode + 62 (HIToolbox) [0x7fff93ea8ae3]
    12 ReceiveNextEventCommon + 166 (HIToolbox) [0x7fff93ea8b94]
    12 RunCurrentEventLoopInMode + 209 (HIToolbox) [0x7fff93ea8eb4]
    12 CFRunLoopRunSpecific + 290 (CoreFoundation) [0x7fff94dd00e2]
    12 __CFRunLoopRun + 1529 (CoreFoundation) [0x7fff94dd0ad9]
    12 __CFRunLoopDoTimer + 557 (CoreFoundation) [0x7fff94deb31d]
    12 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20 (CoreFoundation) [0x7fff94deb804]
    12 __NSFireTimer + 96 (Foundation) [0x7fff98dce463]
    12 -[DVAMacNodeTimer fire:] + 118 (dvaui) [0x1085e9476]
    12 void dvacore::config::ExecuteTopLevelFunction<void>(boost::function0<void>, bool*) + 93 (dvacore) [0x107ef497d]
    12 void dvacore::config::ErrorManager::ExecuteFunctionWithTopLevelExceptionHandler<void>(boost::f unction0<void>, bool*) + 250 (dvacore) [0x107ef0e9a]
    12 ??? (Adobe Illustrator + 7781211) [0x10076bb5b]
    12 int dvacore::config::ErrorManager::ExecuteFunction<void>(boost::function0<void>*, void*) + 123 (dvacore) [0x107ef1e0b]
    12 dvaui::ui::OS_NodeTimerData::HandleOSTimerEvent() + 142 (dvaui) [0x1085f395e]
    12 ??? (Adobe Illustrator + 7781211) [0x10076bb5b]
    12 dvaui::ui::OS_NodeTimerData::CallDispatchPossibleTimer(dvaui::ui::OS_NodeTimerData*, dvaui::ui::UI_NodeTimerData*) + 28 (dvaui) [0x1085f209c]
    12 dvaui::ui::UI_Node::UI_DispatchPossibleTimer(dvaui::ui::UI_NodeTimerData*) + 233 (dvaui) [0x10855eb59]
    12 dvaui::ui::UI_SubView::UI_DoTimerNotify(int) + 9 (dvaadameve) [0x10727f4a9]
    12 dvaui::ui::UI_Node::UI_DoTimerNotify(int) + 77 (dvaui) [0x10856272d]
    12 PluginMain + 345462 (Save4Web) [0x13a85a926]
    12 PluginMain + 314653 (Save4Web) [0x13a8530cd]
    12 PluginMain + 321486 (Save4Web) [0x13a854b7e]
    12 PluginMain + 542620 (Save4Web) [0x13a88ab4c]
    12 ??? (Save4Web + 145331) [0x13a7fd7b3]
    12 PluginMain + 3980831 (Save4Web) [0x13abd21cf]
    12 PluginMain + 89934 (Save4Web) [0x13a81c2fe]
    12 ??? (Save4Web + 172283) [0x13a8040fb]
    12 ??? (Save4Web + 152309) [0x13a7ff2f5]
    12 PluginMain + 26658 (Rasterize) [0x110c2e5d2]
    12 PluginMain + 15450 (Rasterize) [0x110c2ba0a]
    12 ??? (Adobe Illustrator + 10385365) [0x1009e77d5]
    12 ??? (Adobe Illustrator + 10501460) [0x100a03d54]
    12 ??? (Adobe Illustrator + 8703269) [0x10084cd25]
    12 ??? (Adobe Illustrator + 10509595) [0x100a05d1b]
    12 ??? (Adobe Illustrator + 10505172) [0x100a04bd4]
    12 ??? (Adobe Illustrator + 10285293) [0x1009cf0ed]
    12 ??? (Adobe Illustrator + 11105157) [0x100a97385]
    12 std::_Rb_tree<SPSUAS, std::pair<SPSUAS const, int>, std::_Select1st<std::pair<SPSUAS const, int> >, std::less<SPSUAS>, std::allocator<std::pair<SPSUAS const, int> > >::erase(SPSUAS const&) + 15393 (Adobe Illustrator) [0x100c95781]
    12 std::_Rb_tree<SPSUAS, std::pair<SPSUAS const, int>, std::_Select1st<std::pair<SPSUAS const, int> >, std::less<SPSUAS>, std::allocator<std::pair<SPSUAS const, int> > >::erase(SPSUAS const&) + 13900 (Adobe Illustrator) [0x100c951ac]
    12 std::_Rb_tree<SPSUAS, std::pair<SPSUAS const, int>, std::_Select1st<std::pair<SPSUAS const, int> >, std::less<SPSUAS>, std::allocator<std::pair<SPSUAS const, int> > >::erase(SPSUAS const&) + 1228 (Adobe Illustrator) [0x100c9202c]
    12 std::_Rb_tree<SPSUAS, std::pair<SPSUAS const, int>, std::_Select1st<std::pair<SPSUAS const, int> >, std::less<SPSUAS>, std::allocator<std::pair<SPSUAS const, int> > >::erase(SPSUAS const&) + 24282 (Adobe Illustrator) [0x100c97a3a]
    12 PluginMain + 280 (BNPlugin) [0x1283b57e8]
    12 PluginMain + 29301 (BNPlugin) [0x1283bc945]
    12 PluginMain + 9949 (BNPlugin) [0x1283b7dad]
    12 PluginMain + 36051 (BNPlugin) [0x1283be3a3]
    12 PSLShutdown + 388 (AdobePSL) [0x1042c58f4]
    12 PSLGetPreferences + 11343 (AdobePSL) [0x1042c540f]
    12 PSLCreateStringUTF8 + 460233 (AdobePSL) [0x104348ce9]
    12 PSLCreateStringUTF8 + 464882 (AdobePSL) [0x104349f12]
    12 PSLSetImageGuides + 1436569 (AdobePSL) [0x1044b0959]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 3318833 (AdobePSL) [0x104036ae1]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 3354840 (AdobePSL) [0x10403f788]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 3353884 (AdobePSL) [0x10403f3cc]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 3353361 (AdobePSL) [0x10403f1c1]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 3346950 (AdobePSL) [0x10403d8b6]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 3342002 (AdobePSL) [0x10403c562]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 5349535 (AdobePSL) [0x10422674f]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 5347308 (AdobePSL) [0x104225e9c]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 5349248 (AdobePSL) [0x104226630]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 5349000 (AdobePSL) [0x104226538]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 5348873 (AdobePSL) [0x1042264b9]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 5514742 (AdobePSL) [0x10424eca6]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 5514524 (AdobePSL) [0x10424ebcc]
    12 ??? (AdobePSL + 118211) [0x103cf6dc3]
    12 ??? (AdobePSL + 117947) [0x103cf6cbb]
    12 ??? (AdobePSL + 117606) [0x103cf6b66]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 569177 (AdobePSL) [0x103d97609]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 580792 (AdobePSL) [0x103d9a368]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 5501139 (AdobePSL) [0x10424b783]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 579476 (AdobePSL) [0x103d99e44]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 585837 (AdobePSL) [0x103d9b71d]
    12 __psynch_mutexwait + 10 (libsystem_kernel.dylib) [0x7fff9275a122]
    *12 psynch_mtxcontinue + 0 (mach_kernel) [0xffffff80005b4550]
      Thread 0x12d78
    DispatchQueue 2     
    priority 49   
      12 _dispatch_mgr_thread + 54 (libdispatch.dylib) [0x7fff8e4d89ee]
    12 kevent + 10 (libsystem_kernel.dylib) [0x7fff9275ad16]
    *12 ??? (mach_kernel + 3471808) [0xffffff800054f9c0]
      Thread 0x12d80
    priority 47   
      12 thread_start + 13 (libsystem_c.dylib) [0x7fff8dd091e1]
    12 _pthread_start + 327 (libsystem_c.dylib) [0x7fff8dd1c7a2]
    12 PrivateMPEntryPoint + 58 (CarbonCore) [0x7fff903067e0]
    12 ??? (AdobeACE + 230874) [0x102a325da]
    12 ??? (AdobeACE + 234185) [0x102a332c9]
    12 MPWaitOnQueue + 252 (CarbonCore) [0x7fff90291a98]
    12 TSWaitOnConditionTimedRelative + 132 (CarbonCore) [0x7fff9032f3e7]
    12 TSWaitOnCondition + 108 (CarbonCore) [0x7fff9032f210]
    12 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff9275a0fa]
    *12 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b5bb0]
      Thread 0x12d81
    priority 47   
      12 thread_start + 13 (libsystem_c.dylib) [0x7fff8dd091e1]
    12 _pthread_start + 327 (libsystem_c.dylib) [0x7fff8dd1c7a2]
    12 PrivateMPEntryPoint + 58 (CarbonCore) [0x7fff903067e0]
    12 ??? (AdobeACE + 230874) [0x102a325da]
    12 ??? (AdobeACE + 234185) [0x102a332c9]
    12 MPWaitOnQueue + 252 (CarbonCore) [0x7fff90291a98]
    12 TSWaitOnConditionTimedRelative + 132 (CarbonCore) [0x7fff9032f3e7]
    12 TSWaitOnCondition + 108 (CarbonCore) [0x7fff9032f210]
    12 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff9275a0fa]
    *12 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b5bb0]
      Thread 0x12d82
    priority 47   
      12 thread_start + 13 (libsystem_c.dylib) [0x7fff8dd091e1]
    12 _pthread_start + 327 (libsystem_c.dylib) [0x7fff8dd1c7a2]
    12 PrivateMPEntryPoint + 58 (CarbonCore) [0x7fff903067e0]
    12 ??? (AdobeACE + 230874) [0x102a325da]
    12 ??? (AdobeACE + 234185) [0x102a332c9]
    12 MPWaitOnQueue + 252 (CarbonCore) [0x7fff90291a98]
    12 TSWaitOnConditionTimedRelative + 132 (CarbonCore) [0x7fff9032f3e7]
    12 TSWaitOnCondition + 108 (CarbonCore) [0x7fff9032f210]
    12 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff9275a0fa]
    *12 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b5bb0]
      Thread 0x12d8f
    priority 47   
      12 thread_start + 13 (libsystem_c.dylib) [0x7fff8dd091e1]
    12 _pthread_start + 327 (libsystem_c.dylib) [0x7fff8dd1c7a2]
    12 AGMInitialize + 3288447 (AdobeAGM) [0x102ee9d8b]
    12 AGMInitialize + 3259120 (AdobeAGM) [0x102ee2afc]
    12 AGMInitialize + 3255535 (AdobeAGM) [0x102ee1cfb]
    12 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff9275a0fa]
    *12 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b5bb0]
      Thread 0x12d9b
    priority 47   
      12 thread_start + 13 (libsystem_c.dylib) [0x7fff8dd091e1]
    12 _pthread_start + 327 (libsystem_c.dylib) [0x7fff8dd1c7a2]
    12 APXGetHostAPI + 2516713 (adbeapeengine) [0x117f9ae79]
    12 APXGetHostAPI + 2516410 (adbeapeengine) [0x117f9ad4a]
    12 APXGetHostAPI + 2516289 (adbeapeengine) [0x117f9acd1]
    12 APXGetHostAPI + 83761 (adbeapeengine) [0x117d48ec1]
    12 APXGetHostAPI + 2516093 (adbeapeengine) [0x117f9ac0d]
    12 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff9275a0fa]
    *12 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b5bb0]
      Thread 0x12d9c
    priority 47   
      12 thread_start + 13 (libsystem_c.dylib) [0x7fff8dd091e1]
    12 _pthread_start + 327 (libsystem_c.dylib) [0x7fff8dd1c7a2]
    12 APXGetHostAPI + 2516713 (adbeapeengine) [0x117f9ae79]
    12 APXGetHostAPI + 2516410 (adbeapeengine) [0x117f9ad4a]
    12 APXGetHostAPI + 2516289 (adbeapeengine) [0x117f9acd1]
    12 APXGetHostAPI + 83761 (adbeapeengine) [0x117d48ec1]
    12 APXGetHostAPI + 2516093 (adbeapeengine) [0x117f9ac0d]
    12 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff9275a0fa]
    *12 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b5bb0]
      Thread 0x12d9d
    priority 47   
      12 thread_start + 13 (libsystem_c.dylib) [0x7fff8dd091e1]
    12 _pthread_start + 327 (libsystem_c.dylib) [0x7fff8dd1c7a2]
    12 APXGetHostAPI + 2516713 (adbeapeengine) [0x117f9ae79]
    12 APXGetHostAPI + 2516410 (adbeapeengine) [0x117f9ad4a]
    12 APXGetHostAPI + 2516289 (adbeapeengine) [0x117f9acd1]
    12 APXGetHostAPI + 83761 (adbeapeengine) [0x117d48ec1]
    12 APXGetHostAPI + 2516093 (adbeapeengine) [0x117f9ac0d]
    12 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff9275a0fa]
    *12 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b5bb0]
      Thread 0x12d9e
    priority 47   
      12 thread_start + 13 (libsystem_c.dylib) [0x7fff8dd091e1]
    12 _pthread_start + 327 (libsystem_c.dylib) [0x7fff8dd1c7a2]
    12 APXGetHostAPI + 2516713 (adbeapeengine) [0x117f9ae79]
    12 APXGetHostAPI + 2516410 (adbeapeengine) [0x117f9ad4a]
    12 APXGetHostAPI + 2516289 (adbeapeengine) [0x117f9acd1]
    12 APXGetHostAPI + 83761 (adbeapeengine) [0x117d48ec1]
    12 APXGetHostAPI + 2516093 (adbeapeengine) [0x117f9ac0d]
    12 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff9275a0fa]
    *12 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b5bb0]
      Thread 0x12da0
    priority 63   
      12 t

  • How to file auto number in save for web ?

    Hi All,
    how to file auto number in save for web ?
    I have make an action script in Photoshop cs5 that
    change the image resolution and SaveForWeb...
    (but at this point user need to supply the file name)
    so, How to write the code/action such that when the
    action button is click the image will save into the file
    file2eMail_001,file2eMail_002,file2eMail_003,file2eMail_004
    or to any unused number ?
    thank for any help!

    You could also ask over in the Photoshop Scripting Forum, I’m pretty certain stuff like progressively numbered copies has been addressed there previously.

  • How differs soft proofing in View - Proof Colors and Save for Web - Preview?

    Hi, I'm currently confused with one inconsistency. My working space is Adobe RGB and I use calibrated monitor. After I finish my work on image I go to View -> Proof Colors -> Internet Standard RGB. Image looks terribly with the overall violet/purple hue. Then I open Save for Web dialogue, I check Convert to RGB and from Preview options I select again Internet Standard RGB. Now the previewed image looks as expected. The same results I get if I manually convert image to sRGB before soft proofing and saving for web. So... what's the difference between preview in Proof Colours and in Save for Web? Thank you for your opinions.

    Hi 21, thank you for your input. All what you say makes perfect sense, it is exactly how it should work and how I expected it works. My problem was, that while testing this theory in practice, I have come to different results. I expected, that if I stick to the theory (meaning keeping in mind all rules you perfectly described) I should get the same result in both soft proof and save for web preview. But... it was not the case. Save for web preview offered expected results while soft proof was completely out of any assumptions and colours were totally over-saturated with violet/purple hue. Also, Edit -> Assign Profile -> sRGB gave another result then Soft Proof -> Custom -> assign sRGB (preserve numbers), but the same as save for web preview.  What troubled me was why this is so.
    Today I've made tests on hardware calibrated monitor and... everything works exactly as you describe and as I expected.
    Then I went back to another monitor which is software calibrated (both monitors are calibrated with X-Rite i1 Display Pro). And again... I received strange results described above. So I did the last thing I thought and disabled colour calibration on that monitor. And suddenly... both soft proof and save for web preview gave the same result.
    Probable conclusion: soft proof and save for web preview (together with Edit -> Assign Profile) are programmed to use different algorithm which is evident on standard gamut monitors with software calibration. Question can be closed.
    Gene and 21, thank you for your effort.

  • Photoshop CS3 color management "Save for Web" problem

    This problem is getting the best of me.......
    After spending 3 full days researching this problem, I am no closer to finding an answer than when I started. I still cannot produce a usable image through the "Save for Web" feature of Photoshop CS3. I have read web page after web page of "Tips, Tricks and Recommendations" from dozens of experts, some from this forum, and still I have no solution... I am exhausted and frustrated to say the least. Here's the simple facts that I know at this point.
    I have a web design project that was started in PS CS1. All artwork was created in photoshop and exported to JPG format by using "Save for Web". Every image displays correctly in these browsers (Safari, Camino, FireFox and even Internet Explorer on a PC).
    I have recently upgraded to PS CS3 and now cannot get any newly JPG'd image to display correctly. My original settings in CS1 were of no concern to me at the time, because it always just worked, and so I do not know what they were. I have opened a few of my previous images in CS3 and found that sRGB-2.1 displays them more or less accurately. I am using sRGB 2.1 working space. Upon openning these previous image files, I get the "Missing Profile" message and of course I select "Leave as is. Do Not color manage". CS3 assumes sRGB-2.1 working space, opens the file, and all is well.
    The problem is when I go to "Save for Web", the saturation goes up, and the colors change. The opposite of what most people are reporting. Here's another important point... new artwork created in CS3 does exactly the same thing, so it's not because of the older CS1 files.
    I have tried every combination of "uncompensated color", "Convert to sRGB", "ICC Profile", etc. while saving. I have Converted to sRGB before saving, and my monitor is calibrated correctly.
    I have tried setting the "Save for Web" page on 2-up and the "original" on the left is already color shifted before I even hit the "Save" button. Of course, the "Optimized" image on the right looks perfect because I am cheating by selecting the "Use Document Color Profile" item. Why do they even have this feature if doesn't work, or misleads you?
    Does anyone have any ideas what could be happening here? Why is this all so screwed up?
    CS1 worked fine out of the box.
    Final note: I do have an image file I could send along that demonstrates how it is possible to display an image exactly the same in all 4 of the browsers I mentioned with no color differences. It is untagged RGB and somehow it just works.
    I am very frustrated with all of this and any suggestions will be appreciated
    Thanks,
    Pete

    >> First of all... I'm using an Adobe RGB image master... I open it and get the Profile Mismatch Screen... I choose Use Enbedded profile... all looks well. Next I go to Proof Setup > Monitor RGB... again all looks well, no change that I can tell.
    This has further confused the issue on several points, not the least of which version PS you are doing this with?
    >> AdobeRGB> Convert to Profile > Working Space sRGB-2.1... all still looks well... but now, when I go to Proof Setup > Monitor RGB... I see the insane oversaturated look that is driving me nuts.
    That is your strongest clue...it sounds like you have a bad system or bad monitor profile. To rule out the monitor profile: Set sRGB as your monitor profile in System Prefs> Displays> Color.
    >> Adobe RGB image master... I open it and get the Profile Mismatch Screen... I choose Use Enbedded profile... all looks well. Next I go to Proof Setup > Monitor RGB... again all looks well
    That doesn't make sense, stripping an embedded AdobeRGB profile should desaturate the color in Softproof MonitorRGB, especially the reds -- you have something wacky going on there.
    At this point I think you need to review the links and get a grip about how color management and profiles work...
    BTW, forget about setting ColorSync in PS COlor Settings, use Adobe ACE.
    MO,
    I think SFW is fixed under CS3 :) By default it Converts to sRGB and strips the profile.

  • CS6 crashing when "save for web"

    On a MacBook Pro, OSx 10.6.8. Using CS6 on .tifs, resizing the file to 600px wide - approx. 750k file - try to save for web, 80 percent quality and I get the folder screen, but it's open to "documents". Then I get spinning beachball, then CS crashes. Shuts down.
    I've tried restarting, no luck. I've had this happen before and I don't remember how it got worked out. I perform this function all the time and there's nothing new in my workflow. I read in another thread about metatag conflicts, and I do process the raws in Capture One before retouching in CS6, but I've done that before without any problem.
    Any ideas? I'm stumped.

    Timothy Kolk wrote:
    I ended up having to delete Save for Web 8.0 and 12.0 prefs as well.
    What made you think you needed to do that?  Did Save For Web also stop working in Photoshop CS or CS5?
    If so, that kind of says something else on your computer is wrong other than in Photoshop, doesn't it?
    -Noel

  • I also have a color problem when Save For Web

    Using Photoshop CS4 and I also have a problem when I use the "Save for Web & Devices" My colors also get bleached. I found a thread with the same problem but on Windows.
    As I have a Macbook Pro I can not change my monitor settings. In the SFW I check "Convert to sRGB" but it make no difference. I also tried to convert in the menu before using SFW. So I need some help here.
    Here is a screen shot on my screen: http://www.scancyp.com/dump.jpg

    Magooi wrote:
    Also I was wondering why?
    You need to calibrate and profile your monitor regularly and often
    First:  Because monitors can and do drift.  In CRTs all kinds of electronic components and the phosphors themselves age; in LEDs and LCDs the back-light illuminants do; etc.
    Second:  Monitor profile files can and occasionally do get corrupted.
    I validate the calibration of my monitors practically on a daily basis.
    If you don't have an accurately profiled monitor at all times, your work is wasted.
    Magooi wrote:
    But it's a whole science to calibrate the monitor without a hardware calibration kit. I had a look at SuperCal as you suggested, but I am afraid it's gona be too complicated for me as I think it's hard enough to calibrate with the Apple calibration tool.
    Even the cheapest hardware calibrator puck will give you superior results than any eyeball calibrator.  That said, SuperCal is a tad better than Apple's  built-in eyeball calibrator, though nowhere as good as a hardware calibrators.
    Personally, I detest laptop screens and categorically do not consider a MacBook Pro a suitable machine for serious color work.  For this reason, I cannot in good conscience insist on your buying a hardware calibrator.
    Laptop screens can be nearly impossible to calibrate accurately.
    Magooi wrote:
    I have made a new screen shot with my results so far. Upper left is Photoshop original. To the right the SFW and lower left the preview result. The SFW result still don't give me the colors I want, but as I said: closer then before.
    Screen shots from an uncalibrated or inaccurately calibrated monitor are worthless, always.  They do not help at all, especially when they are partial snippets that don't show the whole picture.
    This time around they are even worse, as I cannot see whether you rectified your Preview setting in the Save For web dialog box to "Use Document Profile", as I told you earlier:
    You have to start by changing that setting in the Save For Web dialog box to "Use Document Profile".
    Is your original document in a device independent color space (i.e. was your working colorspace set to such a device-independent color space like Adobe RGB or sRGB when you created the original) and is it properly tagged (does it have such a device independent profile embedded)?  If the answer to any of that is no, all your work is wasted.
    If your working space is set to your Monitor Profile, then your work is a useless mess.  If the original is in your Monitor Profile, it's no good either.  Same goes for the Preview setting in the Save For Web dialog box, if it's set to Monitor Profile, it's useless.
    If you view any untagged image (any image without a device-independent profile embedded) in any Apple application, be aware that any such Apple application, From the Finder, through Preview, Aperture and iPhoto to Safari, will throw your monitor profile at your image (assuming it's really in your Monitor Profile) and it will display your image in the wrong colors, as all Apple applications stupidly assume that all untagged images were created by some fool who didn't know better.
    Magooi wrote:
    But now my main questions is:
    Why the Original in the Photoshop SFW don't look like the original? And then why the Optimized in the SFW also don't look like the the preview? (Specially look at he shadows of the palm tree that shows in the Optimized but not in the preview)
    I have no idea what all your other color settings throughout the whole application and in the Save For Web box are, what else may be messed up on your machine, or how badly inaccurate your monitor profile is.  Again, your  screenshot is not helpful and never will be—unless you had an accurately profiled monitor, which you will never be sure you have on your laptop, ever.
    Magooi wrote:
    And again, should I invest in SuperCal? It seems also to be very old.
    SuperCal is better than Apple's calibrator, regardless of whatever its age may be at this point.  Last time I checked, SuperCal was free.  If they want to charge for it now, don't buy it.  It's not worth it for a laptop screen.
    On a side note, if you think SuperCal is "too complicated" for you, I doubt you're ready for Photoshop anyway, even with a better machine.  Sorry, no offense meant, but it wouldn't be fair to you if I didn't tell you exactly how I feel.

  • Illustrator CS5 15.0.2 crash when Save for Web and Devices (Mac)

    Hi baffled with this.
    When Saving for Web and Devices in Illustrator CS5 (15.0.2), the application now freezes and has to be force quit.
    HOWEVER if I delete the Users/~/Library/Preferences/Adobe Illustrator CS5 Settings/en_GB folder all works well until I quit the application, then the freeze will happen again. I had this happen before so under the advice of Adobe I created a new user and all was fine for that user so I transferred everything across... a laborious task.
    So my question now is why now?... what has triggered this AGAIN?...
    Hope you can help... anyone.
    Running:
    Mac OS X 10.6.6
    Mac Pro tower.
    Note:
    have uninstalled, reinstalled, updated 15.0.1 - 15.0.2
    have deleted all font caches
    have deleted everything... that could be related...
    HOWEVER have narrowed it down to the 'Adobe Illustrator Prefs' file in the Users/~/Library/Preferences/Adobe Illustrator CS5 Settings/en_GB folder
    Please too note this is not the folder permissions issue, am aware of that and have thoroughly checked all permissions, ran disk utility and disk warrior.
    thanks

    If you use cocktail I suggest you get rid of it it can cause serious problems if you select the wrong settings, instead download ONYXwhich is free and will not harm your system or corrupt anything by deleting something you actually need.
    I hit the wrong setting using cocktail and it locked me out of all of the hard drives installed or connected to my Mac it is very dangerous. And I cannot imagine a reason for a setting that would protect your hard drives from yourself to the point of not recognizing your own password.
    I know it cost money and has advanced settings but having the ability to kill your system is crazy.
    Also to repair your permissions use the disk utility or ONYX as the permissions can become changed when installing software or if cocktail changes it locking you out of folders etc.

  • Color Trouble - Save for Web

    Hi,
    When I save for web and devices in Illustator and then open the html document in Dreamweaver, the colors of my document appear VERY washed out. In AI I have the RGB set to sRGB and the color mode set to RGB.
    Could someone suggest what might be happening here?
    Thanks!!

    When you import a file you want to import an RGB file with a RGBs profile and you want to know that so that you can change it. If you have color management turned off you will not know what happened and it will not match.
    Unless you take the time to make everything match then it will not work.
    So any place image or file should be RGBs the document should be RGB and the color settings should be RGBs. If you place an image that is Adobe RGB 1998 and the your settings in AI is RGBs then there will be a change in the color and this is expected but not a wanted result. By embedding you are forced to go back convert the profile to RGBs in Photoshop then replacing it in Illustrator, this allows you to correct any difference there is so you can know what it looks like when place in Illustrator otherwise Illustrator will convert it to RGBs when save for the web but without any adjustments.
    So yes I say they are wrong.

  • Problem: Color Management/Save for Web on Wide Gamut Monitor

    Hi,
    I've got a problem with color management - I thought I understood it, but it seems as if didn't. So I'm trying to kindly ask for help.
    I'm printing, and also trying to save an image for Web.
    My setup:
    - Win 7, CS 5
    - Calibrated Wide Gamut Monitor (eizo cg223w)
    - Photoshop set to ProPhoto (I don't want to start a discussion adobergb vs prophoto)
    - Save for Web and Devices, Embed Color Profile, Convert to SRGB
    - Viewing in Firefox 3.6 with Color Management enabled
    Problem:
    Image: http://dl.dropbox.com/u/311345/luchs-1024.jpg
    If I compare the file in Firefox and Photoshop, the Firefox presentation is slightly more saturated - and I have no idea why.
    I thought it should work with the above workflow.
    Here is a screenshot where you can clearly see a difference (Note: the additional over-saturation here is caused by the wide gammut monitor when taking screenshots, in reality its not as dramatic as that): http://imgur.com/MFPbU but you can clearly see the difference.
    I would be very very thankful for any pointers what I'm doing wrong in my workflow!
    Thanks in advance,
    Christoph

    function(){return A.apply(null,[this].concat($A(arguments)))}
    ch_bla wrote:
    - Monitor calibrated
    - Edit under ProPhoto RGB, 16 bit raw files
    - Save for Web and Devices, Embed Color Profile, Convert to SRGB
    Is this the preferred way?
    It's a reasonable and correct way to do it, assuming you want to embed a profile in the images.
    Since at least in some browsers and cases the colors selected within the HTML elements must match image colors, one can sometimes make a case for not embedding any profile at all, but that's really looking backwards.  Browsers are moving forward toward not only managing colors in images but also in the HTML elements themselves.  If you want your images accurately portrayed in as many places as possible you're doing the right thing looking forward.
    Personally I embed the sRGB profile in my web images, as you are doing.  And I check things primarily with IE and Safari.
    Unlike you, I prefer to edit using the sRGB color space, but that's just personal preference.  I find it more convenient to use File - Save As instead of File - Save For Web & Devices, and I get caught by gotchas less often this way.  Your preference ensures you don't lose any colors at the extremes of the gamut while editing and it could easily be argued that that's better, depending on what image products you produce.
    As for the article you mentioned, anyone who would set their preferred working space to Monitor RGB or use Proof Colors in normal editing is asking for trouble, and may not understand color management at all.
    -Noel

  • Photoshop CS6 save for web some colors change?

    I have a picture with large area of color: #fffdfd, when I save it for web (jpg) this color is changed to #fefcfd (in JPG).
    I just can not save as JPG with #fffdfd.
    (was trying uncheck convert to sRGB, do not embed color profile - always #fffdfd changes to #fefcfd when save for web)
    However, color #fefcfd when save for web , does not change.
    Why some colors change and some not? Is it a bug ?
    Window7 64bit, Photoshop CS6

    Save for Web & Devices will strip some color data from the file.
    Browsers aren't color managed. Most file formats on browsers assume they're sRGB. While Photoshop gives you an option of embedding sRGB to the document color space, it also strips off data that is not relevant. This is a common occurence.
    PNG-24 on the other hand will give you the exact color match.
    Also, Save for W&D, JPG quality matters a lot - The same color at Quality 10,20,30,40,50...100 wil give you different color reproductions on the JPG end output.
    If you're concerned that much about an offset of +/- 1 hex value to your RGB colorspace, dont save for web & devices. Do a 'Save As' instead. Then use an image editing/ resizing application such as ResizeMe to resize the quality of your document. This, in most cases will retain colorspace information but just drop the resolution and quality of the image - giving you a lesser filesize.
    On a sidenote, You may also want to read this article on how to best manage color spaces: http://viget.com/inspire/the-mysterious-save-for-web-color-shift

  • PNG changing colors using save for web (CS2)

    Im having a problem with making PNG pictures when using the "save for web" function (this also happens in Image ready)
    I make an image in sRGB color space and chose "save for web" and set the settings, all looks fine and i save it as png8 or png24.
    Then when i view it in a browser the colors af "off" (desaturated) ??
    But if i chose "Save as" in Photoshop, and chose png, and save it that way, the color macth up and looks allright.
    What im a doing wrong ??
    I have made a test with to sets of colors / picture one with "websave" color and one without then save them "using save for web" in gif, jpg with profile, png8 and png24
    The gif and jpg goes well but the png's colors goes "off"
    I also saved the to files using "save as" and here the png's colors looks fine
    (Ther are also some screendums of my color setting, "save for web" setting and my screen profile if that can be of anny help
    http://home19.inet.tele.dk/jgom/pngtest/
    Also! can anybody tell me this ?
    When using "save as" i cant chose what png im saving as ? (8 or 24) What type of png dos PS use when you save it like that ???

    Now I've read up on it, it seems the issue is indeed gamma.
    (I really appreciate the "that's impossible, you must be doing something wrong" comments, by the way. Not "hmm, I don't know," but actually "what you've described in detail isn't happening; you're imagining things." Super helpful.)
    Anyway the real question is: is there a way to stop Photoshop from including gamma data? It's apparently an optional portion of the PNG spec.
    The whole gamma thing is unfortunate, but the *really* unfortunate bit is that Photoshop includes this information at all, particularly in a Save for Web context.
    Most importantly, it seems this has been an issue for some time (Google "PNG Photoshop gamma"), and PNG is usually used for web, so why on Earth hasn't Adobe addressed this? Let's not forget that Photoshop is the industry-leading tool, and the Extended version costs $1000 by itself. The only options I've seen for saving as PNG in PS so far is sRGB conversion, bit depth, transparency, and interlacing. This whole gamma thing seems pretty unacceptable behavior, even by default.
    I'm looking into pngcrush; does anyone have a simpler solution to strip the gamma information? Of course, if there's a way to do this in Photoshop itself, please please let me know.
    Thanks.

  • CS6 "Save for Web" "Convert to sRGB" Issues

    Hello,
    I'm aiming to take RAW photo files, edit them in a wide color space, and when posting them to the web, save them as sRGB.
    My workspace is as follows:
    I open RAW files in Photoshop via ACR as 16-bit ProPhoto smart objects.
    When I finish editing them, I use "Save for Web" with the "Convert to sRGB" and "Embed Color Profile" boxes checked.
    Photoshop and Bridge tell me the profile in photos saved as such is sRGB as expected. When I upload to a site like flickr, however, the metadata says the photo is still in ProPhoto. See an example here: http://www.flickr.com/photos/nrbelex/7950202448/meta/in/photostream
    If I use "Convert to Profile" and change it to sRGB, then upload to flickr, the metadata says the photo is in sRGB, as it should be.
    What am I missing here?
    Thanks!

    Without using Flickr, I'm not seeing any problem with any of the color-managed software I have here.
    The ProPhoto test file I prepared, when Save For Web is used, is saved with sRGB numbers and (since I checked the box) has the sRGB IEC61966-2.1 profile embedded in it.
    Photoshop re-opens the file and correctly judges that it has the sRGB IEC61966-2.1 profile.
    A search through the binary data from the file Saved For Web using a text editor turns up a number of references to sRGB IEC61966-2.1, but none to ProPhoto RGB.
    Your first image above, however, has BOTH references to sRGB IEC61966-2.1 and ProPhoto RGB, the latter appearing in a string of text data that looks like:
    <rdf:Description
    rdf:about=""
    xmlns:xmp="http://ns.adobe.com/xap/1.0/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:aux="http://ns.adobe.com/exif/1.0/aux/"
    xmlns:photoshop="http://ns.adobe.com/photoshop/1.0/"
    xmlns:xmpMM="http://ns.adobe.com/xap/1.0/mm/"
    xmlns:stEvt="http://ns.adobe.com/xap/1.0/sType/ResourceEvent#"
    xmlns:stRef="http://ns.adobe.com/xap/1.0/sType/ResourceRef#"
    xmp:Rating="3"
    xmp:ModifyDate="2012-09-07T12:40:05-05:00"
    xmp:CreateDate="2012-09-06T19:18:56"
    xmp:MetadataDate="2012-09-07T12:40:05-05:00"
    xmp:CreatorTool="Adobe Photoshop CS6 Windows"
    dc:format="image/jpeg"
    aux:SerialNumber="022031001932"
    aux:LensInfo="70/1 200/1 0/0 0/0"
    aux:Lens="EF70-200mm f/2.8L USM"
    aux:LensID="165"
    aux:LensSerialNumber="0000000000"
    aux:ImageNumber="0"
    aux:ApproximateFocusDistance="4294967295/1"
    aux:FlashCompensation="0/1"
    aux:Firmware="1.1.3"
    photoshop:DateCreated="2012-09-06T19:18:56.056"
    photoshop:ColorMode="3"
    photoshop:ICCProfile="ProPhoto RGB"
    xmpMM:DocumentID="xmp.did:0F84D078F91311E19565E271D59D6831"
    xmpMM:OriginalDocumentID="98EDC08C95F6E809F2FB9CADB1F3442D"
    xmpMM:InstanceID="xmp.iid:0F84D077F91311E19565E271D59D6831">
    -Noel

  • IBooks author color shift with "Save for web devices..."

    Hi! I'm a web developer and I'm learning to use iBooks. It's a really easy tool, but there is a problem with color management wich is driving me crazy. This happen when I export images from "Save for web devices..." from Photoshop, then drag it to iBooks author.
    As I do for web development, I do this:
    1) Configure photoshop Color Settings to work with "Color Monitor"
    2) Remove any color management from my document
    3) Proof Setup > Monitor RGB
    4) Disable Proof Colors
    5) Use "Save for web devices..." with ICC profile and sRGB unchecked
    The exported JPG looks fine everywhere... Photoshop, Preview, Safari, Chrome, FF... but looks washed out when I drag it to iBooks Author. Why?
    I solved this issue converting to sRGBIEC61966-2.1 profile and checking ICC profile when  "Save for web devices...", but I'm not confortable with this workaround because I'm not sure about what I'm doing exactly, and I am not sure if this images are gonna look good on any device (I only own an iPad 3).
    Somebody know a best method to deal with this?
    Thanks!

    Hi KT. Thanks for your response. I'm already using this formats. Anyway, the problem occurs within iBooks Author interface. I mean: I can see the color shift (or washed out...) at iBooks Author at my computer screen. Of course, when I test it on iPad it also looks bad.
    It's incredibly strange because the JPGs I'm using looks fine everywhere else except iBooks Author.

  • Save for Web Color Degradation

    Photoshop CS2 - I am doing a Save for Web and have ICC Profiles checked off and also the User Document Color Profile is checked off. However, when the image gets into the browser (or is previewed in GoLive or Dreamweaver) it loses color and actually looks like it does when Uncompensated Color is selected. Any ideas?

    Neil and/or Buko
    Some of the FAQs in bold red at the top of the main page are a little dated. Maybe some should be replaced with the "color looks washed-out when Save for Web" FAQ.

Maybe you are looking for