Color fidelity between slides and FCE output

Until the recent past, I have been scanning 35mm slides using a Cannon Canoscan 9900F coupled with Photoshop Elements v 2.0 into FCE v 3.0 on a Mac G-4 with OS 10.4.3. The color fidelity between the slides and final output was reasonably good. Within the past week I have upgraded system software to OS 10.4.8; upgraded Photoshop Elements to v 4.0 and FCE to v3.5.1. Now when I scan slides, the resulting images (both on the desktop and as printed with an Epson stylus 2200) are dark as if the slides were greatly underexposed. The Photoshop Elements correcting or enhancing tools do not solve the problem. I don’t think this is a monitor calibration issue but would welcome any suggestions. Thanks in advance. Jack A

Hi(Bonjour)!
What is the relation with FCE ? It's seem that is more a problem with MAC OS X itself or photoshop or your scanner than FCE.
See MAC OS X forum:
http://discussions.apple.com/category.jspa?categoryID=160
Try to make a new color profile for your monitor.
Michel Boissonneault

Similar Messages

  • Color shift between play and pause

    Hello,
    On CC 7.0 and 7.1, I noticed there is an important color shift between pausing and playing my timeline when using "CineForm Visually Perfect" encoded source material.
    This is especially noticeable on reds.
    Using other codecs, there is no such shift.
    My video card is a Geforce 650M. At first, I thaught it might be related to the video overlay settings of the card, but there are no such settings in the control panel.
    Besides, using Quicktime to play the source produces no shift as well.
    As I am often doing color correction using Premiere, and as I have dropped Avid exactly because I always had this same problem (when using a profiled calibrated screen), I would like to know precisely what is going on. As I'm regularly producing shows for broadcast, it is a real problem not to be sure whether what you see matches the final exported output in all circumstances.
    NB : For the need of searching the cause of this problem I disabled any custom profiling of my screen.
    Thanks ! for any answers.
    Fred

    Sure and thanks. But nevertheless, if you color correct using a calibrated screen, and produce for the web ; or if you do a first pass of color correction before the ultimate pass happens with a "properly calibrated TV", wouldn't you like that your paused frame would look like your playing frame ?

  • Color mismatch between CS4 and Canon PIXMA PRO6500

    Hi there! I am trying to research if anyone else is having a problem with color mismatch between CS4 and their printer. Last night I printed a .tiff image out of CS4 to my Canon PRO6500 printer and the sky came out purple / pink! It was supposed to be a stormy grey color. I have the color management turned off on the printer settings. I have CS4 manages color turned on and the correct ICC profile selected for the paper I am using. When I do a soft proof in CS4 the image looks fine, but when I print I get something completely different, mostly with the sky (purple / pink) color! Just for the heck of it I did a Print Preview under my Page Setup and guess what, the sky actually shows purple / pink! So I have no idea what's going on. I checked all my setting, ink cartridges, tried different paper with the appropriate ICC profile and no dice. Still have a goofy looking sky! I thought PROOFING the image is supposed to show you how the printed image is going to look? apparently it doesn't because it's not. The Print Preview has an accurate representation of the print but I have no idea where the pink / purple sky is coming from. They are supposed to be stormy clouds as I said. I appreciate any help anyone can provide .
    Sabciu

    I have the color management turned off on the printer settings.
    But do you have a measured color profile based on a sample print? Most likely not, so this is not doing anything in your favor. The current profile may present the defaults for a given printer, but not the actual density based on your other printer settings. So by all means, unless you can be sure to obey a full calibration throughout, turn on the printer CM. Also, since it is a Pro model, you may actualyl have to use the dedicated RIP software that was bundled with it to get correct results, not the default windows print engine.
    Mylenium

  • Need help with Color Profiles between Photoshop and iPhoto

    Hey guys, I'm a photographer and have always used Photoshop in comination with iPhoto. I am having great difficulty lately with color profiles randomly changing within albums of pictures. I need all of my images to be in sRGB, but some somehow end up in Adobe RGB. It seems to happen at random. Apple seems to think it's an Adobe problem. Adobe isn't sure what to do. Anybody aware of any known issues between CS5 and iPhoto using OS 10.8.4 with regard to color profiles and how to fix them?

    SRiegel schrieb:
    I don't know inkscape, but this article seems to indicate that is will support cmyk.
    The article also says you need Scribus to then further process the SVG file.
    @shaunamm You need to open the SVGin Illustrator, not place it. But I doubt that you will be able to get the effects in Illustrator.

  • Spot Color mismatches between EPS and PDF files

    Recently I created a file in Illustrator CS6 with several Pantone color swatches. I used the CMYK color mode set to the Coated GRACoL 2006 color space. I saved the file as an EPS and we printed our test samples on our large format printer. After reviewing the print I saw the colors were off. The grey color showed up green.I then opened up the exact same EPS file and simply saved it as a PDF. We ran the PDF on the same printer, using the same material and profile and the color was completely different. This time the grey colors came out grey (correctly). We tested this twice and came up witht he same color differences between the EPS files and the PDF files. Why would an Illustrator file produce 2 different colors if saved as a PDF versus an EPS?
    Also, I sent these files to another prepress person in our company and he printed them on our proofing printer. The EPS printed slightly differently than the PDF. He then opened the PDF file in Acrobat and saved it out of Acrobat as an EPS. After this, he printed the new EPS file created from Acrobat and it printed the exact same as the PDF file (correctly).
    This leads me to believe that the problem is in the way Illustrator saves EPS files. Has anyone else seen this problem?
    Thanks for any and all help with this very perplexing issue.

    I will speak from CS3.
    The current PDF format if 1.7 exported out of Photoshop supports vector elements as independent objects, but you can't edit them correctly out of Acrobat because Photoshop reads the data as a flat file and drops the vector data. Basically the workflow is not finished being developed. Also, Transparency is broken within the PDF file format at this time. It will support Spots though correctly.
    PSD and TIF support Transparency and Spots, but vector objects are rasterized due Acrobat reading the flat version of the file.
    When Photoshop wrote its own PDF format and not the corporate PDF flavor that we now have, PDF's would support Transparency correctly.
    I would assume that Transparency and vector objects would be addressed in the next release, but that is to be seen.
    There is no best practice except don't do it.

  • Color shift between Library and Develop module

    Hi,
    I recently noticed a color shift between in the image when going from the library to the develop module. Yes, I know this is mentioned in the FAQ, but I did not find the solutions given there to be satisfactory.
    Let me explain what happens: I have taken Photos with my Canon EOS 300D, in Jpeg mode with Color Space in the Camera set to AdobeRGB. The photos I am talking about were taken with Tungsten light with auto white balance and have a distinct orange color cast. I use Windows XP and view my Photos on a LCD Display calibrated with the Pantone Huey system. The Lightroom Library Module and Photoshop CS2 both display the original image almost identically (there are no changes applied inside Lightroom or Photoshop, I view the original image in both applications). Photoshop is set to use the Adobe RGB Color space as its working Color space, Softproofing is switched off. However, when I switch to the Develop Module, the colors (especially the orange hues) shift very noticably toward pink. I can only assume that the Colorspace conversion or maybe some implicit soft proof used differs between the modules. So, to restate the problem: If I switch back and forth between Library and Develop, without changing anything and in 1:1 view to avoid errors introduced by different zooming methods, the colors shift quite drastically back and forth.
    I have to say that this is really quite annoying. The whole point for me to use the develop module is to use it to make adjustments to the colors, and for this to work properly I have to see the same colors in both modules and in Photoshop. There is no point in correcting a pink color cast away in Develop that is not even there in either the library module or Photoshop (and that would then have a stronger orange tint because I tried to counter the pink tint in develop).
    So this leads me to the final question: Is it possible to tell Develop to use the exact same color settings as the Library Module? Or is there another way to compensate for the color shift?
    I hope I was clear in what happens and what I tried to do. If it helps I can gladly provide a sample photograph that clearly illustrates the point.
    Thank you in advance for your help,
    Daniel

    Thanks for your comments, Don and Fred. I hope that this issue will be worked on soon.
    Fred, I have set the Preview Quality to High, but it doesn't seem to make any differences concerning the color shift. I have investigated this matter further by now and made the following observations:
    *The color shift is a lot less noticable on my laptop (the laptop screen is also color profiled). On my laptop the change is more of a subtle shift in contrast than in color. This might be caused by the smaller color gammut of my laptop display though.
    *I have uploaded a testimage so that others can check if this shift occurs at their workstations too - after all, it might be a misconfiguration of my color management software, though I doubt that (because Adobe already states that library and develop render different previews). I would be interested if the color shift I describe is noticable at other workstations too. The link to the testimage: http://www.danyx.com/colorshift.jpg (permission to use the image to test the color reproduction is of course granted hereby).
    Thanks for your help, I hope Adobe will listen soon,
    Daniel

  • Color Differences between Lightroom and Premiere Pro

    I have been making color adjustments to movie clips in Photoshop or Lightroom (both of which do a great job), but when I bring the clips into Premiere Pro or Premiere Elements the colors are not the same as what I was seing in the other programs. It is as if the programs are using different color profiles. How do I resolve this problem?

    bryanbrowne1 wrote:
    I have been making color adjustments to movie clips in Photoshop or Lightroom (both of which do a great job), but when I bring the clips into Premiere Pro or Premiere Elements the colors are not the same as what I was seing in the other programs. It is as if the programs are using different color profiles. How do I resolve this problem?
    Photoshop and Lightroom are designed for still photography. Still photographers use a color managed workflow that in general ends in a paper print. Since printers/inks/papers can in general display a wider gamut than computer monitors can display, we use tools manage it, such as soft proofing. The efficient way to control this is through ICC profiles of the printer/ink/paper combinations, of which there are thousands. Thus Photoshop and Lightroom and other still photography tools are esentially required to be color managed.
    PPro and film/video have decidedly different requirements. The video workflow ends in a light source display (projection, HDTV, or web video, all are light sources, where a pigment ink print is a reflective source, which has entirely different characteristics). These end displays are not variable workspace displays. HDTV displays only in REC.709 workspace, its gamut, contrast, etc. are tightly defined. Web video uses the sRGB workspace. Etc.
    I'm just sayin' that still photography and video have very different requirements. Trying to force still photography methods onto a video workflow is bound to be difficult and full of problems, as you have found.
    The answer to your "How do I resolve this problem" question is perhaps to use the still photography tools for still photography, and the video tools for video. A stills workflow for stills, and a video workflow for video.
    A video workflow implies doing color correction and color grading on external monitors that natively support the target work space (Rec.709 in the case of HDTV, Blu-ray, or DVD output [OK, technically DVD uses SDTV's REC.601 work space, but 709 is "close enough" that you can get by in all but the most critical applications]). IOW, use a production monitor, or at least an HDTV (calibrated of course), to judge final output.
    Trying to color correct video on a computer monitor is just asking for trouble. As you well know by now.
    A good place to start learning the video way of things when it comes to color correction and grading is Alexis Van Hurkman's Color Correction Handbook. Highly recommended; it answered questions that I didn't know enough to ask yet. Might for you too, IDK.

  • Color changes between CS2 and CS4 opacity with effects turned on

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

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

  • Color differences between FCP and Motion

    Forgive me if I'm breaking any unwritten rules here as I posted this same topic on the Final Cut forum the other day..so bear with me as I hope to find some insight here from the many experienced (and extremely helpful) Motion users on the motion forum.
    OK...here's my dilemma. I create a graphic/text page in Motion working with the RGB colors from a style guide provided by an agency. I then drop the motion project into the FCP timeline and the colors between the 2 applications are different.
    I'm attaching a link to 2 jpegs that show the different RGB readings with the DigitalColorMeter application.
    http://www.myphotos.yahoo.com/s/218qifk6fseemvbmprlw
    In my Motion project the meter tells me that the dark blue color is RGB-11,44,99
    In my FCP timeline the meter tells me that the dark blue color is RGB-4,30,79
    I gather from some forum research that this may have something to do with gamma levels...my FCP setting has the Imported/StillRGB Video Gamma setting set at Source.
    I'm hoping that someone can explain to me why the DigitalColorMeter readings would be different between Motion and FCP...and what I might do to feel confident that my Motion files would import correctly into my FCP timeline.
    Thanks in advance to any insight....
    Jay

    After some more exploration...turning things on and off, changing sequence/gamma setting, and the like...I now realize what the issue is.
    When the background setting in my canvas/edit window is set to black the colors are accurate between motion and FCP.
    Once I change the background setting in the canvas/edit window to white or checkerboard there is definitely a shift in color/gamma. Not sure why that is...maybe someone can explain

  • Color problems between Lr5 and other software

    I can not see where to make adjustments to get the same tones between Lr and my other software: Photoshop, Irfanview, Windows Viewer ...
    My test conditions:
    My monitor is calibrated
    ... - Export Lr Jpeg quality 85% and also tests 16bit TIFF (sRGB, Adobe rgb and prophoto)
    ... - When exporting, I checked the "add to catalog" to view the same image in Lr.
    Conclusion: Other software gives almost the same tones (some small differences due to the chosen color space) and Lr gives a much warmer picture (Raw or treated Jgeg reimported in the catalog). Will it have a preference of Lr to settle?
    Note: the direct opening of RAW file in Photoshop with Camera Raw (same engine as Lr) without special settings, also gives a duller color different image, that directly Lr.
    What is the solution?

    In general, any difference between Lightroom and other color managed software is indicative of a corrupt monitor profile. No idea about Irfanview, but Lightroom, Photoshop and Windows Photo Viewer should all display identically.
    What they all do is convert from the source/document color space to the target color space, which for display is your monitor profile. The result should be identical - that is in fact the whole point of color management. But since the source space may be different the actual conversion itself may also be different. So one conversion may go bad but not others.
    A difference between Library and Develop will have the same explanation (different source spaces; Library is Adobe RGB while Develop is linear ProPhoto).
    It also happens that different applications react differently to a bad monitor profile. It may work in one application and fail in others.
    Any software that is not color managed will simply display in the native monitor color space, which can be anything under the sun, so you can just ignore and disregard that. It won't be accurate anyway.
    So the solution is to have a valid and healthy monitor profile. Then everything color managed will display identically (save for gamut differences, but in practice that only applies if you have a wide gamut monitor. With a standard monitor any source space will have equal or larger gamut than the monitor).
    Some calibration software has been known to not follow specifications strictly at all times, so check for updated software. Or the profile can simply have become corrupt. It happens. A way to test this is to set sRGB as default monitor profile in the OS - or Adobe RGB if you have a wide gamut monitor - and see if the problem clears.

  • Color Sync Between iPhoto and Photoshop

    iPhoto's retouching tool does a good job for retouching small marks in a photo, but there are times when Photoshop is needed to do rechouching work.
    While making a slideshow I noticed a colorshift when moving an image from iPhoto to Photoshop and then back into the iPhoto. To be more specific there is a loss of saturation as if the color space between the to programs are not sycncronized or embedded profiles are changed when an image moves between the two. The images are five mega pixle jpgs.
    This issues is made more complicated because of color differences between iPhoto's edit window and the slideshow it's self while it is playing.
    Apparently I'm missing something in using these to programs together.
    Photoscene

    Thanks for your help. I did change the value, but have not imported any new pictures yet into iphoto. I did figure out how to get Photoshop to not color shift on save. However I'm not sure this method is a good thing, since the only way to prevent the color shift on saves, is from the photoshop save as dialog box. you must turn off embed color profile. when I do this, there is no longer a color shift. however the color profile is no longer embeded in the picture. are there any negatives for doing it this way?

  • Color discrepancies between iPhoto and Elements...

    Okay, enough ******** about iPhoto ’08. I actually like it, but I have had no problems, so far. Anyway, there is something a little quirky I have been noticing: I do like the new editor in iPhoto, but I still jump between iPhoto and Elements. I have noticed that my on-screen images are generally a little lighter and with much better skin tones while viewing them in Elements. In iPhoto they are a little darker and skin tones are more red. What am I missing? Is there a setting (Color Settings in PSE, Color Sync) I should be paying attention to? It would seem to me that the image should look identical regardless of which editor I am viewing the image in.
    Thanks for your thoughts…

    Old Toad wrote:
    TheGuyintheProj...:
    Try deleting the iPhoto preference file, com.apple.iPhoto.plist, that resides in your User/Library/Preferences folder. If you're still at 10.4.9 update to 10.4.10 via the COMBO updater. Also make sure you're at the latest Quicktime version.
    Next, log into another account, create a library if there is none, import a couple of photos that are showing bad in your primary account and compare. If those photos appear correct there may be some conflicting preference files in your primary account. Here's how you can weed them out if that's the case:
    Trouble Shooting Preferences
    Go to HD/Users/Your_name/Library. Move the Preferences folder (in its entirety) to the Desktop and make a second copy of it so you have Copy A and B. Now try the the process again and determine if problem is fixed.
    If the problem IS fixed, then go to the new Prefs folder that the OS will have created and open it up.
    Open Copy B on the Desktop and select all of the items inside. Drag them into the open new library folder. When the Copy window comes up check the Apply to All check box and then click on the Don't Replace button as seen here. That will keep the new files created and bring back all of the others.
    If the problem is NOT fixed, trash the new Prefs folder and move the intact Copy A folder back to the Library folder .
    Lastly, rebuild the library as follows: launch iPhoto with the Command+Option keys depressed and follow the instructions to rebuild the library. Select the first three options.
    OT
    Old Toad,
    Thank you for the advice. I have done everything you have suggested, except for the updating to 10.4.10. That is not an option. It trashed 5 of my machines and I am just now getting my main machine usable again. Thank God for backups.
    I have taken the worst pictures and viewed them in every photo viewing application that I have including the Finder/Finder Window in column mode, iPhoto 6 and 4, and they are as they should be. This is clearly an iPhoto 7.x issue.
    Thanks again!

  • Color shift between viewer and browser after pro kit update

    hi there,
    i thought i be one of the lucky guys since updating and running 3.0.1 was easy on my system. but after yesterdays pro kit update i experience a weird color shift between the look of pictures in the browser and viewer.
    there is a strong colorshift in orange parts of sundown pictures. they turn magenta in the viewer but stay orange in the browser. the difference can easily be seen in the split screen. even weirder if i export a picture from the vier/split screen the exported files show the magenta tint. if i export them from the browser, they have the "right" orange tint.
    this happens with raw-files from both d200 and d70. also exportet the raw and processed it with ps cs3 and everything was ok. anyone got a clue?
    thanx in advance

    just found the explanation. after my prokit update, all raw-files needed to be reprocessed and then i needed to select the standard apple camera module for the d200. that was quite tricky and i don't understand why something like this happens. why do all files need to be reprocessed and than afterwards you would have to manually select the apple standard converter and why did the viewer look different than the browser and why is there no warning module that tell you all files will have to be reprocessed?

  • No difference between High and Normal output sharpening

    I was going to post a topic about how small is difference between screen output sharpening settings, when some tests revealed that in fact the difference is nil.
    b Can anyone see any difference between Normal and High screen sharpening in applied at export?
    I even stacked the two versions in Photoshop with the Difference blending mode on and a Levels adjustment layer amplifying the difference, and even the histogram was showing that I'be got big plain black rectangle.
    Sharpening for paper seems to work fine.
    Lightroom 2.3 Windows.

    Just took the time to test this on my 'calibration' image and there is indeed no difference in Standard and High sharpening for screen.
    Same result with and without resizing image; with and without jpeg compression; with both tif and jpeg files.
    Lr 2.3 on XP.

  • Color difference between PNG and JPG in Save For Web

    I am working on a website and I while building images for the site I am using a mix of png and jpg images. When I "Save for Web" the same source image creates two different color images when I save them as either png or jpg. How do I make sure the images are saving with identical colors in both png and jpg. Thanks

    >My working space is Adobe RGB but I'm not opening the sRGB PNG into Adobe RGB. I am choosing "Leave as is (don't color manage)" this should preserve the PNG's RGB numbers.
    are you certain it is not being converted when you open it?
    The numbers you quoted are the numbers I get if I open an untagged sRGB image into Adobe RGB (assuming Adobe RGB), and then convert to sRGB.
    If I open my sRGB images, either PNG or JPEG, into sRGB, they always match. I've been working on a web site for the past 3 weeks, doing this regularly.
    If you are working in Adobe RGB with sRGB images that are not tagged, you add a level of complexity that requires you make the right decision at every step. You need to open them without conversion, then assign sRGB, to keep working.
    Or just open the images in Firefox 2, which cannot color manage, and see if the sRGB jpeg and the sRGB PNG match. This is the acid test.

Maybe you are looking for