Gamma 1.8?

When would you want to view your graphics under View > Gamma 1.8? Do new computers still use this Gamma setting or is this a setting that was only used by older Macs?
Thanks.

I think you're on the right track. Here's what Fireworks Help has to say on the subject:
http://help.adobe.com/en_US/fireworks/cs/using/WS4c25cfbb1410b0021e63e3d1152b00cace-7fe0.h tml#WS660F659B-4CE0-4718-9B59-8ACACF9EFEA5
My copy of Fireworks 8 for Mac (circa CS2) has a Windows Gamma view option. I'm guessing that the Windows version had a Mac Gamma option. If the two gammas converged with the release of Mac OS 10.6, then the Windows/Mac dichotomy would no longer be applicable, so a single "Gamma 1.8" option was probably considered the best choice, in lieu of removing the menu item altogether.

Similar Messages

Momentary gamma shifts in PS-CS6 composed image h.264 video

Before I finalize a bug report, wonder what others are seeing?
Having discovered the problem in a more complex scenario, I've narrowed down to a simple set of jpg images placed sequentially in a video group, and exported as an h.264 video from Photoshop PS6. All is on Windows 7 Professional SP1, all software involved completely up-to-date.
I first noticed the gamma shift using the 'High Quality' preset. It occurs with variations on Vimeo 29.97 and Youtube 29.97 presets. The gamma problem does not occur on HD 720p or 1080p 29.97 presets.
When I view the resulting video through Quicktime, I see a gamma shift for a moment on the first image, making it look washed out. After another moment, the gamma goes back to normal. On other players such as Windows Media or VLC, no such shift is visible.
Interestingly, the shift comes at 1 second when exporting to the Vimeo 29.97 preset, or 'High Quality', while at 3 seconds on Youtube 29.97. Similarly, the shift back occurs at 2 seconds, or 6 seconds for Youtube.
What the gamma shift looks like sounds like the now age-old Apple Quicktime fault on h.264. -- except it occurs only for one or a few seconds, then reverts to proper gamma, instead of continuing..
With the simple setup of single image (jpg) sequence, it occurs only on the first image. With a more complex scenario, some actual videos included, I've seen it occur on every jpg -- or on some -- in a sequence.
This is very repeatable here - 100%. Anyone else who's noticed it? I'm on the CS6 trial, and still thinking whether to purchase, or go on the Creative Cloud.
Regards,
Clive

We're seeing a worse issue when exporting in H.264 and playing in QuickTime 10.0 (Mac OS 10.6). We are using a custom size video to fit a spot on our website (398x498). When exported and played in QuickTime 10.0 the white inverts throughout the video (back and forth). The same issue is not seen when viewed in VLC or QuickTime 10.1.
This is how the video should look:
And this is how they are appearing:
But like I said, the issue is very specific to QuickTime 10.0 on Mac 10.6. VLC, Flash, Chrome, FireFox all play it correctly.

How to change document gamma (or create a "false profile")

Although there has been much recent criticism of the notion of "false profiles," generally associated with the person who espouses it, I would like to be able to convert a document which is in, e.g., Adobe RGB with a gamma of 2.2 to one of the same colorspace but a gamma of, say, 1.5. Although I can do this via the color settings dialogue, creating a new setting with the name, e.g., "gamma 1.5," and although at the time of creation of the new setting the document does indeed become lighter, nonetheless the setting does not "stick." That is, if I leave that document and later try to apply that same setting via edit>convert to profile, nothing happens. I'd greatly appreciate someone giving me some pointers on how to establish a setting such that it appears and is functional in the edit>convert to profile list. I'm working in CS2 in OS10.5.6. Many thanks

retiredpatman wrote:
I would like to be able to convert a document which is in, e.g., Adobe RGB with a gamma of 2.2 to one of the same colorspace but a gamma of, say, 1.5.
The Red, Green and Blue tone response curves are kept separately in the .icm file. You can see that if you open an .icm file in Apple's ColorSync Utility.app. In the case of AdobeRGB1998.icm you'll find that each of those curves has an identical Gamma of 2.199, but they're stored and display separately.
You would need access to a profile generating application to change that, and you'd need to know what you're doing.

FCP "Export - QuickTime Movie" gamma shift

Above is an example of what happens when I do a direct export in Final Cut Pro, using the Export -> QuickTime Movie function. As you can see, the image is significantly brighter and the colors are a little more washed out (this image isn't particularly colorful, but trust me, it washes them out). I always thought the Export -> QuickTime Movie meant the image would not be compressed--that it was a straight export using the sequence settings.
The image you see above was shot natively in ProRes 422 (HQ) using an Arriflex Alexa. It has never been transcoded. The bottom image is what it looks like using Export -> QuickTime Movie. Totally unacceptable for a piece of professional software, if you ask me.
I can't express how infuriating this is, to have everything looking perfect in FCP and then exporting only to have it look like garbage. I've been able to play with gamma correction a bit and have gotten it PRETTY close to the original look, but this seems like a horrible workaround.
Anyone else know why this is happening? Is there a fix for this?
I'm working with FCP 6.0.6 and QuickTime 10.1.

Sure thing, Meg.
Here's a source clip with "approximate" gamma correction:
"Approximate" gamma correction makes the image look flatter within Final Cut Pro than it actually is.
Now, the very same clip and frame, but with gamma set to "Accurate" :
Now, things are switched. The exported image looks flatter than the source clip within FCP.
Here's another tidbit of info--the frame from my first post was professionally color graded and exported as a self-contained movie--so there were no filters, FCP or otherwise, being applied there. But the difference is just night-and-day to me.

CS4 - Is there a way to adjust gamma for second monitor or send to overlay?

One thing that is evident when I edit in Premiere CS4 using the AVCHD 1080i 60 template is that the preview in the second monitor, which in my case is my TV set connected using a DVI to HDMI cable, is that the output is too dark compared to what it should be. Darker areas of the frame sometimes even get crushed into black when the same footage, when played directly from the camcorder, or even burned to blu-ray and played, is noticeably brighter and at the right black levels.
This doesn't happen when editing in Vegas Pro 8, or when the untouched footage is played through other video player, including Windows 7 Media Center.
A workaround for this problem can be to go to the graphics card control panel, in my case ATI Catalyst, and adjust the gamma for the second monitor, with the problem being that when you're done editing in Premiere you have to go back to the normal gamma. At one point I had setup two profiles in Catalyst with shortcuts and it worked well, but one day Catalyst simply lost the profiles and noticing how buggy it was I wasn't going to keep creating profiles so that Catalyst would delete them.
So my question is, since it's not in the preferences, is there some settings file or registry address that I can tweak to make Premiere display a brighter gamma of my choice?
And this may be a dead end, but is there a way to send the output of the second monitor to the overlay so that it can take advantage of the graphic's card video capabilities and display video smoothly? It's nice to have a preview of the timeline, but it's rather annoying if I have to go to the Catalyst control panel and adjust gamma before editing and after editing and that motion is jerky and not interlaced when I'm editing interlaced content.

You need the VESA mount option. That way your minimum angle would be completely vertical and you could open it to a negative 10 degrees.
Hope this helps.
Pete
I am not an HP employee, But I did stay at a Holiday Inn Express last night.
TouchSmart IQ526t CTO Intel 2.26 Ghz 4 gig ram 750 gig HDD Vista Premium 64 bit

AE CC and the Rest of Adobe Apps - ProRes Quicktime Render Gamma Problem Back AGAIN

Hi ---
With this version I am back to square one with AE NOT being able to render out correct gamma exporting to PR4444 -
Scenario (And this matter NOT whether I use Color Management or Not)
1) I open a Clip in AE or PPRO (In this case a TIFF Sequence RAW'ed from Lightroom)
2) I switch back and forth between Lightroom and AE and the images are identical in color and gamma
3) I export to PR4444 and open in Quicktime Player or FCPx and the Gamma is off.
4) If I re-import the exported file into AE - AE reads the file with a diff. gamma and the result appears to be identical with source
But it is no good that the result only looks the way it was intended in AE ! --- The poeople on the web are not viewing the movie in AE but with other players.
If i open that same tiff sequence in the quicktime player pro and export to PR4444 the results are 100% identical.
I find it highly frustrating that a company so higly regarded with so amazing software is NOT able to render out an image correctly...
This problem has been around since forever and I find it higly disturbing that this issue has not yet been addressed.
As of now I have no choice that to ditch AE and PPRO.... I WANT the images I work with to look the way they do in the app while color grading... What point is there in CG'ing images to perfection
if adobe cant even render out the results....
As I stated it does NOT matter whether I am color managing or not... Results are lighter in gamma when viewed in anything else than AE or PPRO !!!!!!
The amount to correct back is approx. a gamma of 0.9
BTW --- When in 32 bit how come I cannot set a gamma of 0.905 why is the gamma limited to two digits after the comma... 32 bit has MUCH more to offer !!!!

Thanks Todd,
I have tried those tips before. Unfortunately, I haven't had great success with them in this case.
When I reserve the 16GB of RAM for other apps and RAM preview a comp containing multiple Prores 4444 footage layers, it plays back and retains the cache as expected. However, the 2nd RAM preview of another comp in the same project containing multiple Prores 4444 footage layers stays stuck in "Initializing Background Processes." A check with Activity Monitor usually shows aeselflink processes that are hung up.
This has been my experience until I came upon the work-around of precomping Prores files.
To demonstrate, here's a screen shot of the stuck process with the memory settings I used -
I rebooted the system and tried 2 more times with the same result.
If I simply precomp the Prores 4444 footage layers as demonstrated in the video, I get smooth RAM preview caching and performance. This works even if I allocated less RAM to other applications in the Memory and Multiprocessing preferences (hence the 6GB setting from earlier). With the work-around, AE runs smooth with no hiccups and RAM previews behave as expected.

How to disable Adobe Gamma in Windows 7?

I have a new PC running Windows 7 and a new monitor. I want to color-calibrate the monitor using Spyder3, as I've done in the past with Windows XP. I cannot, however, locate Adobe Gamma in the msconfig "Startup" folder on Windows 7 to de-activate it. Has it been eliminated? Can I run the calibration program without taking this step? Many thanks in advance.

I'm loading CS5 (upgraded from CS3). It's the computer OS that I've had to remove it from before - and it doesn't appear in the Startup folder, unlike in Windows XP's system. (Or in the Control Panel, although there is a "Color Management" folder that lists color profiles I've downloaded from Epson when I downloaded my printer drivers for Windows 7).
So I guess Windows 7 doesn't include it, and I am free to do my calibration. Adobe's tech support phone line is closed for the weekend so I am turning to you forum experts. There must be someone out there who has encountered this in setting up a new computer system and loading PS onto it. Thanks for the input from both you and John.

QuickTime 7.1.6 Gamma/Color Shift Is Demonstrable

You can easily see the undesirable behavior of gamma/color shifting when playing H.264 codec movies in Apple's QuickTime Player.
Download any Apple HD (1920x?) QuickTime Trailer. Open and switch view to Double Size. The movie will immediately become darker with a pronounced gamma and color shift.
Reopening the movie switches back to the correct gamma and color.
I reported this bug, and since it's so easy to demonstrate, Apple should be able to fix it once and for all.
PowerBook G4 17 Mac OS X (10.4.9) QuickTime 7.1.6
PowerBook G4 17

I think you may find some will argue with you. DV and H264 at normal size look too bright and washed out for a lot of people, and are not the correct amount of darkness they should be. Fortuately when they're compressed to MPEG-2, if that's where you headed, they get the contrast back again.
Playing the move doubled up is one of many work arounds to the problem. But the problem isn't the one you think it is. You're right about the fact that it should be fixed once and for all.

Safari 4 Color and Gamma STILL Washes Out -- NOT Solved 7/4/2009

OK, just bringing this back to the top:
http://discussions.apple.com/thread.jspa?threadID=2032159&start=0&tstart=0 is listed as 'Solved', but that was totally premature. The alleged fixes range from the usual repair permissions, trash Safari prefs, reboot, etc., but it's all temporary, at best.
A CLEAN install of the OS to a virgin partition, followed by permissions, repair, combo updater, apply all related Safari, repair permissions, delete, shutdown and reboot leaves you with the same issue as soon as you sleep displays, go to screen saver, use FUS, and come back in with Safari 4 already running, you will get the screen wash as further described here:
http://gallery.me.com/frederico/100070
Posted Elsewhere:
Gamma settings within Safari 4 windows since upgrade will "degrade" (read: darken and stratify) when scrolling the window contents, using either scroll wheel, arrow keys, or mouse on scroll bar. Text also becomes progressively fuzzy and its opacity decreases until the entire window is black.
Moving another application window in front, or minimizing and maximizing the errant window, moving or resizing it in any manner, or using the 'Force Repaint' command will restore the appearance immediately. I can capture screenshots of it, but cannot use your included screenshot command, as the mere act of dropping down the report slider forces repaint.
Quitting Safari, rebooting machine, or just logging out will "cure" the problem for a short time, but it returns fairly quickly. I do not believe I have any third party plugins causing the issue; I removed several and the problem still crept back; each user account, including a freshly created test account sees this error.
This can fairly regularly be triggered by sleeping the displays or entering locked screensaver, logging in, and going to several sites such as Daring Fireball, Mac OS X Hints, and anything displaying PNG and Flash combos.
Perhaps related: I updated to 10.5.7 at the same time, and when I restarted, noticed that the gamma profile on my center screen (of five LCDs) was severely washed out. Switching back and forth between any other color profile in Displays and back to my calibrated profile will cure the wash -- until I log out and back in. Each user account, including a freshly created test account sees this error.
Have also clean installed OS X 10.5.4 and updated to a10.5.7 using combo updater; then installed and updated Safari 4. Problem follows Main screen (menubar host) on each of five LCD displays on three ATi video cards on Mac Pro Quad 2008.
Getting ready to restore back to Safari 3 and 10.5.6 from clone; this behavior is becoming tedious.
Screenshots and additional details on request; <Edited by Host>
http://gallery.me.com/frederico/100070
More info and more users seeing the same thing here
http://www.macosxhints.com/article.php?story=2009062403534417
http://www.macosxhints.com/article.php?story=2009062403534417#comments
Hardware Overview:
Model Name: Mac Pro
Model Identifier: MacPro3,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 2.8 GHz
Number Of Processors: 2
Total Number Of Cores: 8
L2 Cache (per processor): 12 MB
Memory: 6 GB
Bus Speed: 1.6 GHz
Boot ROM Version: MP31.006C.B05
System Version: Mac OS X 10.5.7 (9J61)
Kernel Version: Darwin 9.7.0
Boot Volume: system
Boot Mode: Normal
ATI Radeon HD 2600 XT:
Chipset Model: ATI Radeon HD 2600
Type: Display
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x16
VRAM (Total): 256 MB
Vendor: ATI (0x1002)
Device ID: 0x9588
Revision ID: 0x0000
ROM Revision: 113-B1480A-252
EFI Driver Version: 01.00.252
Displays:
CMC 22 W:
Resolution: 1680 x 1050 @ 60 Hz
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
CMC 22 W:
Resolution: 1680 x 1050 @ 60 Hz
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
ATI Radeon HD 2600 XT:
Chipset Model: ATI Radeon HD 2600
Type: Display
Bus: PCIe
Slot: Slot-2
PCIe Lane Width: x16
VRAM (Total): 256 MB
Vendor: ATI (0x1002)
Device ID: 0x9588
Revision ID: 0x0000
ROM Revision: 113-B1480A-252
EFI Driver Version: 01.00.252
Displays:
CMC 22 W:
Resolution: 1680 x 1050 @ 60 Hz
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
CMC 22 W:
Resolution: 1680 x 1050 @ 60 Hz
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
ATI Radeon HD 2600 XT:
Chipset Model: ATI Radeon HD 2600
Type: Display
Bus: PCIe
Slot: Slot-3
PCIe Lane Width: x16
VRAM (Total): 256 MB
Vendor: ATI (0x1002)
Device ID: 0x9588
Revision ID: 0x0000
ROM Revision: 113-B1480A-252
EFI Driver Version: 01.00.252
Displays:
CMC 19AW:
Resolution: 1440 x 900 @ 60 Hz
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
Display Connector:
Status: No Display Connected

Now THAT is interesting. I typically do not have two Safari windows open and active on the same screen; I usually have three or more Safari windows open, but each is on its own screen, using tabs within each.
I think it's fascinating to see that the content is only affected in one window on the same page.
Can you elaborate as to your trigger? Is it FUS? Screensaver? Other?
The suggestion in either this thread or the other to switch the window momentarily to another screen to clear the problem until the next FUS or screensaver event is my current favorite fix. I have hotkeys assigned to move a window from one screen to another, anyway, so when I return to a user session from login to see Safari schizing out, a quick screen-swap toggle clears the issues until I allow a screensaver (but not always) or engage FUS (always) and see the issue return.
Do you have multiple screens? Can you reliably resolve the issue by swapping and returning, rather than being forced to quit Safari?
One thing to note about the screen swap, is that when this issue is occurring, there is a tremendous lag (a solid second or so) before the window is actually moved to the other screen, and a comparable lag when returning. IOW, there is an observable and HUGE processor spike as well as a memory-use spike (seen in Activity Monitor, top, and iStat Menus) as it deals with moving the visual display (be it plain text or graphic or video content) when this bug is active, but the same action two seconds later, or the same action in any other program, nets near-instant screen movement in response to the global hotkey action.
So, whatever it is that is borked between Safari and Core Video is not just an interpretation/ColorSync/disply error; it seems also to be leaking memory and having runaway processor cycles, as well.
There are times when Safari, with less than ten or twenty tabs open starts eating pretty close to 2GB of RAM, and will dominate a single processor to near 100%, *without* any windows actually containing very much in the way of images, and certainly no Flash or even QT.
I know this sounds a bit arrogant and spoiled, but thank God I have 8 cores and 8GB of RAM; I cannot imagine how this bug might feel on a single core machine with less than 2GB of RAM.

Fluctuating gamma on TV connected via S-video adapter

I have a television (generic CRT) connected to my Powerbook G4 through the S-video adapter and an RCA cable.
Periodically (and I think with increasing frequency), it looks like the gamma setting for the TV fluctuates when it is displaying the line in from the Powerbook. It gets darker and darker... and then it gets lighter and lighter... and then it gets darker and darker... etc. It's a slow cycle, but I haven't been able to find any way of breaking it (restarting the computer, reconnecting the cables, re-detecting the displays, turning mirroring on and off) and it appears to happen whether the display is mirrored or part of a multiple display arrangement.
The one correlation I might have seen is between the temperature of the computer and the fluctuation: hotter -> fluctuation is more likely (no faster or more extreme, just more likely to happen). I think. Of course, the Powerbook spends so much time raging hot that it's hard to tell if this is coincidence or actually meaningful.
Has anyone else experienced this or something like it? Since it's sporadic, I have to hope that there is a fix ("always reboot before connecting the TV" would be a fine fix... if it worked), rather than marking it down as dying hardware.
Thanks for any help folks can offer!

It was indeed Macrovision copy protection. And, if anyone happens to pull this up on a similar search, it's worth noting that not all video players bother to transmit the Macrovision "protection" signal (this occurred to me as a I read this. With DVDs, 'tain't the hardware -- it's in the software!)
Try something more flexible than Apple's DVD Player: VLC.
AlBook G4/1.25GHz, Windtunnel G4/400MHz, and more.. Mac OS X (10.4.10)

Best rgb and gamma settings for external monitor with mountain lion

Hi,
I'm using an LG LED 22 inch monitor with my MBP mid 2010 via minidisplay to hdmi. on OS X side the settings have been default. On the LED side the settings , if set to preset RGB it tends to fade the whites a lot. when i set to user definied and let the preset rgb be at it is, the colors are quote decent. currently they are on R 50, G 58 and B 59 and Gamma 1. Which is the best RGB and Gamma value for OS X Mountain Lion?

Welcome to the forum.
First off, you need to go and buy a hardware monitor calibrator, such as an OptixXR or similar. This will build a custom monitor profile for your specific screen. Without this starting point you can forget ANY attempt at accurate colour matching.
Never (and I mean never) use a working space such as sRGB or Adobe98 as your monitor profile, that's not what they are designed for. Working spaces control what colours are possible in the image, monitor profiles control how those colours are shown on screen. Aperture uses it's own working space so you don't have to worry about that too much.
To answer the rest far too briefly, I'd suggest setting the proofing profile to sRGB and of course use sRGB for the export preset. The gamma setting you will have to adjust depending on how dark the Lightjet prints look compared to your screen. You will have to do test-strips to start with.
Your images looking crap on flickr on Windows machines is partly because Windows web browsers generally do NO colour correction, and only partly to do with the different gamma.
Ian

Final Cut Pro monitor gamma question... again!

Very confused here: can anyone tell me for sure what gamma my Cinema Display needs to be set to for work with FCP7 / Snow Leopard? I can only find contradictory information and nothing clear and conclusive from Apple.
My problem: following the latest advice, I've been using a Cinema Display calibrated to 2.2 (dual monitors on a Macbook Pro). I can export an edited file which matches FCP's canvas when viewed in QuickTime.
However, if I send to Compressor from FCP, the preview in Compressor is darker and more contrasty than FCP's canvas.
If I upload a video that looks OK in QuickTime to MobileMe it becomes dark and contrasty too.
If I convert my exported file that looked OK in QuickTime to H.264 in Mpeg Streamclip I, once again, get a version that is darker and more contrasty than in FCP or QuickTime.
I'm pulling my hair out over this, not least because it's becoming a fantastic waste of time. I would like to be concentrating on editing rather than trying to sort this out!
I had assumed that using a suite of Apple applications on an Apple computer would mean seamless and easy integration...

But the problem here is not simply viewing. I am also creating and then viewing and I think this is where the problem lies. A video uploaded to MobileMe is transformed in the process and it's during the transformation (whatever that might be) that the change in appearance occurs. I view a video in FCP's canvas but then it is exported before being viewed in QuickTime. Gamma levels may be set, colour profiles embedded and / or read, applications may make assumptions about viewing conditions or which of the two monitors I'm using is the principal one, who knows what... I think it's here that the problem lies...

I want to change the settings (brightness, contrast, gamma) for my internal cam on Macbook pro. I find having to but a third party software (iglasses, webcam settings) to control basic settings as unnecessary and exploitative. Does anyone have a solution?

I want to change the settings (brightness, contrast, gamma) for my internal cam on Macbook pro. I find having to but a third party software (iglasses, webcam settings) to control basic settings as unnecessary and exploitative. Does anyone have a solution?

It is not about payment of $19.95 (Igalsses) or $7.99(webcam settings). This is a very basic setting that should be available in the system settings. The automatic setting of the internal cam does not work great on low lighting as everyone is aware.
i am just amazed how users take in lying down and suggest solutions such as paying for a 3rd party paid app or improving the lighting in your room.

Convert RGB to Gray Gamma 1.2 and count number of color pages

I'm working with a printer for theses and dissertations. I receive the PDF files from our graduate students and pass them along. I'm responsible for checking that the document meets the needs of the printer and billing the students appropriately. I'm using Adobe Acrobat X Pro, and am fairly savvy with the pre-flight profiles (creating and running), but I'm not a designer or printer.
Recently, the printer informed me that our students creating PDF files from Word are actually creating what they consider color documents because black is an RGB color from a Word document. I did see in Word that I can use the "High Quality Print" conversion setting to make the text black from the start, but I'm dealing with the final PDF file more often.
They gave me instructions on how to use the "Convert Colors" command to convert the document (or specific pages) to the Gray Gamma 2.2 profile so those pages would be in black and white - see screenshot:
I then submit the document to their web page, where it tells me the count of color pages. I have two problems:
1. For some documents, even after I convert all pages to the profile above, their preflight tool (they use pit stop through their web site, I think ), tells me that some pages are still in color.
2. I can't seem to find a consistent way to count color pages in Acrobat. I've created a pre-flight profile (seee screenshot below), but my results never match theirs (unless it's a raw PDF file and every page is in color). Am I missing an option? I don't really know what spot colors are, so maybe that's an issue?
What I want to be able to do is:
1. Provide consistent instructions to our students on how to fix their documents (perhaps create a pre-flight profile or droplet for them to put their PDF file into).
AND
2. Count the color pages in their document accurately. The printer bills per the page, and there is a differential between color and black and white printing.
Any help would be appreciated.

To detect a "color" page you only need to look at the first two items (CMY plates or more than 0 spot plates). If an object is in RGB it'll separate onto all four plates when printed.
First question - are you sure that the reports coming back from the printer are correct? If they flag a page as color and you don't, what does that page actually contain? Are there any non-printing items (hidden text, items behind something else, etc.) which won't drop an extra plate when physically printed, but which the print shop might be detecting? You're testing the file from the point of view of the paper passing through the machine, they might just be scanning all the objects and ignoring whether they're visible or not. Open one of the questionable pages using the Output Preview tool (on the Tools > Print Production panel) and look at which plates are used.
FYI, spot color is a purpose-mixed ink (not a 'process' color made from CMYK) which appears on its own plate. Usually it's something like a Pantone color, but it might represent something applied by a different part of the production process entirely - lacquer, foil, embossing, etc. With wet ink printing a spot color was literally taken from another bucket and run on a fifth roller, but in digital printing they're usually converted back to process by the printer hardware. The difference is in how accurately that conversion takes place - so they're common for things like company logos. It's unlikely you'll have any in the type of files you're talking about unless a student has picked one by mistake when writing their document in InDesign. Word doesn't like spots and they're not in JPG/PNG/GIF images.

How do you change default gamma assigned to new displays

Is there a way the change the default gamma assigned to a newly detected display not already in the database?
Thank you,
Nally

In System Prefernces > Displays > Calibrate. Make sure that the desired display is attached then follow through the options. Be sure to click on "Expert Mode" in the bottom left of that window.

Contrast / Gamma Different in Canvas and Desktop Preview

*The Confusion:*
The contrast of my video differs between the Canvas Window and Desktop Preview.
I assume the two are using different gamma settings. But I can't figure out what's going on, to know what those settings are and how to assess the final display picture.
*Screen Grabs:*
Here's a screen grab of the canvas, with the image at 100%. The screen grab does not show the full frame.
- - - http://epokhecutmedia.com/images/gamma-ts-canvas.png
Here's a full screen grab of image in Desktop Preview.
- - - http://epokhecutmedia.com/images/gamma-ts-preview.png
*What I've done:*
I've gone through every gamma setting I know of and can't match the Canvas and Desktop Preview or make sense of the difference.
Also, If I toggle between Display calibrations of 1.8 and 2.2 using the Display preferences in System Preferences, values in both the Canvas and Desktop Preview shift and still do not match.
*Another seemingly related thing:*
My Canvas window display jumps between different contrasts (possibly gamma values) automatically while I'm working.
For example,
- - - I'll have video frozen. I'll play it and the image with brighten across the mids with playback. However, after freezing it again it keeps the brighter value.
- - - When I'm using filter, such as the 3-Way Color Corrector, when I click to drag a slider, the image with darken across the mids. Sometimes, as I drag, the canvas will erratically jump back and forth between the two values.
*Why this is a problem:*
I can't do basic exposure correction, because I don't know which is the accurate value to work with.
edit by: FordPrefectRevisited, Screen Grabs added

If I may re-open this thread, let me ask the question FordPrefect only alluded to:
Given that I should be using a pro-level HD broadcast monitor to view everything, given that every piece of footage is different in the particulars, and given that the Canvas Window image is almost always different than any other playback system (Finder, QT, VLC Players, etc.), are there general exposure/gamma changes y'all make to account for the visual difference between the Canvas Window and other playback systems? If you're anything like me, you don't start from SCRATCH on every single edit... You have a few go-to filters with a few go-to settings, and then make minor adjustments according to the needs of the footage.
For instance, in order to get the exported image close in exposure to the ideal Canvas Window image, I usually go: Effects - Video Filters - Quicktime - Brightness and Contrast - and then adjust the Brightness to 0.85 and it seems to get close.
You guys have anything like that? Thanks for any help!

Gamma 1.8?

Similar Messages

Maybe you are looking for