Camera Standard beta 2 for D3 showing distinct blue tone on darkish greys.

I have looked today at some hundred or so past D3 NEF virtual images reset to Import default, for which in my case uses Camera Standard beta 1.
I then - without making any other adjustments - applied Camera Standard beta 2. In many cases there was - to my eyes at least - no discernible difference. Particularly in those shots taken in bright sunlight with balanced sky/ground/flesh-tone balance.
However, all the images which contained medium to dark grey areas - roofs/shadows/roadways/etc. - showed a distinct blue/purple cast. The same was true of the few I tried applying other Nikon beta 2 profiles - each to a greater or lesser extent. That said, I didn't spend a lot of time on these; rather concentrating on the Camera Standard as I have been hooked on this since its introduction.
For background, my monitor is well calibrated, and I do not use Nikon Picture Controls other than the default.

Eric:
Eventually managed to send 13.8MB NEF file this morning UK time via YouSendIt. New system to me.
Anyway, I wanted to state publicly that my post was merely a comment on a beta element; and in no way an implied criticism or moan. I am very happy to continue using Camera Standard beta 1 as my default.
Only fly in that ointment might be that, in the future, beta 1s disappear, to be replaced by a new 'final' profile more akin to beta 2.

Similar Messages

New Nikon D3, D300, and D700 "Camera" v3 beta profiles

Hi everyone,
I have posted a zip file containing updated "Camera" color profiles (Camera Standard, Camera Neutral, etc.) for the Nikon D3, Nikon D300, and Nikon D700. The zip file contains a copy of the readme, but I'll post it here for convenience, too:
For lack of a better name, I am calling these "v3" beta profiles.
BETA RELEASE NOTES
Overview
These updated Camera v3 beta profiles for the Nikon D3, Nikon D300, and Nikon D700 are designed to reduce banding and highlight color artifacts. They also address the "too bright" tone curve issues with the previous "v2" version of the D3 and D700 profiles.
IMPORTANT NOTE: When using these v3 beta profiles, if you wish to match the default tonality of Nikon's Picture Controls (e.g., match View NX / Capture NX), you must set the Exposure slider in Camera Raw / Lightroom to -0.5.
Of course, feel free to adjust Exposure to make your image brighter or darker as you like. But in terms of matching Nikon's default tonality, you must set the Exposure slider to -0.5, or the default will be too bright.
For workflow convenience, you can use presets in Camera Raw / Lightroom to take care of both (e.g., simultaneously set the profile to "Camera Standard" and set Exposure to -0.5).
Installation
If you are on Mac OS X, drag the "Camera v3 beta" folder to:
    /Library/Application Support/Adobe/CameraRaw/CameraProfiles
If you are on Windows XP, drag the "Camera v3 beta" folder to:
    C:\Documents and Settings\All Users\Application Data\Adobe\CameraRaw\CameraProfiles
If you are on Windows Vista or Windows 7, drag the "Camera v3 beta" folder to:
    C:\ProgramData\Adobe\CameraRaw\CameraProfiles
Note that the above path on Windows Vista and Windows 7 may be hidden by default. Check your folder settings.
Feedback
The profiles are currently in beta status. Please provide feedback via the online Adobe user-to-user forums here:
http://forums.adobe.com/community/cameraraw
http://forums.adobe.com/community/lightroom
Thank you!

Vit Novak wrote:
It's because ACR assumes that exposure slider at 0 actually means exposure correction of +0.5 EV for this camera model, so with expsure slider at 0, upper 0.5 EV of histogram is clipped
If this bothers you, there is a workaround - convert NEF to DNG, then change BaselineExposure tag in a dng from 0.5 to 0. There are several utilities for this
Or wait for some future version of ACR where this will be solved
The BaselineExposure used by the DNG spec and ACR can complicate ETTR exposure. A uniformly lit surface, when exposed as determined by the standard ISO light meter, should result in 0.18/sqrt(2) or 12.7% saturation of the sensor according to the ISO 12232 saturation standard. This is the standard used by DXO and it allows 0.5 EV highlight headroom. For ETTR exposure, no (or minimum) headroom is desired and mid-gray (18% reflection) is 2.5 stops below 100%.
For example, I exposed a gray card according to the camera light meter reading with the Nikon D3. The resulting 12 bit data number was 497 and the saturation is 497/4095 = 12.1 % saturation, which is very close to the expected value of 12.7%, confirming that the light meter and sensor are properly calibrated. The corresponding pixel value in 8 bit sRGB is 99.8 as shown.
The raw file can be rendered into sRGB with in camera processing or Nikon NX2, which closely approximates in camera processing. With the Standard Picture Control, the camera sRGB value is 150. This is a hot tone curve and the a highlight with 100% reflectance would be clipped. The table below shows the results with ACR and various presets. If one uses the Adobe Standard camera profile, the sRGB value is 162 rather than the expected 99.8 Other combinations are shown. To get the proper value for mid-gray one must use a linear tone curve (sliders on main tab set to zero and a linear point curve) and an exposure correction of -0.5 EV to compensate for the +0.5 EV BaselineExposure. With no exposure correction and a linear TRC, the sRGB value would be 116, very close to the calculated sRGB value of 117 for mid-gray (18%). However, the linear TRC gives a flat appearing image.
The take home point is that if you use Adobe Standard with no exposure compensation with ETTR, your images will appear overexposed and lead to cutting back on the camera expoure. The raw file highlights will have values well under sensor saturation.

New Nikon D3 and D700 "Camera" v2 beta profiles

Over in the Camera Raw forums, I have posted a zip file containing updated "Camera" color profiles (Camera Standard, Camera Neutral, etc.) for the Nikon D3 and Nikon D700, along with some release notes. That thread is here:
http://forums.adobe.com/thread/602274

Here are some sample pics, as requested, processed with Camera Standard original and V2. They show the more contrasty highlight rendering. Switching to "linear" tone curve doesn't quite tone the highlights down enough.
I noticed the steeper tone curve in the V2 profile seems to result in somewhat more desaturated colors too. I tried to show this in the 3rd image, but may be hard to tell. It it as if you took an image in Photoshop and added a slighty S-curve, but only on the luminosity channel (e.g. make adjustment curves layer, set blending mode -> luminosity).

Camera calibration - Adobe/Camera standard?

Hi,
I found my Canon 7D images was not very good regarding colors, red was often near orange. I used "camera standard" as default.
I downloaded software from X-rite and made a new profile with a colorchecker and my images became much much better and I am happy. But then I noticed that the difference between "adobe standard" and my new profile was very small.
So my question is, should not the "camera standard" be much closer to the "correct" profile than the "adobe standard"? I thought the "camera standard" was made for Canon 7D, but that does not seem to be correct. Have I misunderstood something?
- Terje

So my question is, should not the "camera standard" be much closer to the "correct" profile than the "adobe standard"? I thought the "camera standard" was made for Canon 7D, but that does not seem to be correct. Have I misunderstood something?
The camera standard profile is supposed to approximate the jpeg rendering of your camera in its default (standard) settings. So certainly this is not what we would call "correct". It approximates what Canon thinks looks great and is based more on aesthetic considerations than on a desire to get correct color. It basically represents a reverse engineering by Adobe of Canon's "secret sauce". The in-camera jpeg renderings are far from colorimetrically correct. The Adobe standard is based on calibrations using color charts done at Adobe. They are very lightly tweaked for pleasant color (mostly skin) but not by as much as the Canon profiles your camera uses. The Adobe standard profile should be pretty close to correct. When you generate your own profile, you get correct rendering for your specific camera. This compensates for variation between copies of the camera and for color differences in your lenses/filters/lighting conditions. Normally that should not be too far from Adobe Standard. The X-rite software tends to generate a more contrasty profile than Adobe Standard in my experience but the difference in color is not that large.

Camera Raw 8.4 does not show profiles for my Sony A850.

Camera Raw 8.4 does not show the profiles for my Sony A850. The camera profiles are in the directory, Camera Raw recognizes the photo as being from my A850 in the Camera Raw banner, but the only profile available is Adobe Standard. This all used to work OK a few months ago.

I don’t see any of these on either my Windows 7 or Windows 8 computer in that normal ACR profiles location. Both have PS-CC/ACR8.4 so maybe they used to be there and were removed?
However, if they are valid profiles you can probably get them to work by putting them in the user-customer-profiles folder:
%APPDATA%\Adobe\CameraRaw\CameraProfiles
%APPDATA% = C:\Users\yourusername\AppData\Roaming
I have over a dozen custom-created profiles in this folder and both Photoshop and Lightroom see them all.
A few years back it wasn't this way, but more recently Adobe recognizes which profiles are theirs and will ignore any others in the Adobe profile area, but it expects to see others in the user-custom-profile area, so move the .dcp files over there.
Did your A850 profiles come from a third party like these:
Imprescindibles
Maurizio Piraccini Photography: Sony (and Minolta) color profiles for Adobe Camera Raw and Adobe Lightroom - UPDATED 201…
http://pskiss.com/shop/cross-camera-color-profiles/

My Procedure for Camera Profile Betas (1&2) & Presets

I went ahead and installed the Beta 2 profiles without deleting Beta 1. I had presets called:
1. Adobe standard
2. Canon standard
3. Landscape, etc
4. all the others
The preset folder name is appropriately: Profile
I just updated the Beta 1 presets with the Beta 2 presets by right-clicking the original preset and selecting update with current settings. The only current setting I had selected was camera calibration with the Beta needed for the preset.
Now, when I select a preset the new Beta 2 presets are used. I still have available the Beta 1 presets by going to the camera calibration panel.
Hope this helps because I've seen a lot of questions about deleting the old beta 1 etc.

There was no need to install the beta profiles as LR 2.7 comes with its own set of final profiles, so you could get rid of the beta versions.
If you're on a Mac they're located at Library > Application Support > Adobe > CameraRaw > CameraProfiles
In there you should only have two folders labelled "Adobe Standard" and "Camera".
LR automatically recognizes your camera, so all the choices you see in the drop-down menu only apply to that particular model. Besides the Adobe Standard profile you will find other choices that resemble the camera manufacturers' rendering styles for certain camera models. It looks though as if the E-520 is not supported, so you might only see ACR x.x.

D810 RAW conversion in LR 5.6 shows posterization at certain camera profiles: Camera Standard, vivid, monochrome that it does not show with identical photos from a D800. Is this bug already known?

Never had this problem seen before in all my years of LR use. I use a test-chart with a continuous gray bar (from dark to light). Normally use Camera Standard profile to develop all my D800 RAW files with no problem so far. Got a D810 to test this week and did some tests using the same target. Suddenly there are some ugly posterization effects in the gray bar to be seen that can only be eliminated with heavy color-noise reduction or by switching to any other profile but Camera standard, Camera Vivid, Camera monochome.
The following 100% crop shows the effect from a D810:
And this is the same crop from a D800-shot:

OK, after posting there was the right suggestion of other forum threads that took care of the issue:
Nikon D810 & Lightroom 5.6 posterization issue with Camera Profiles
So this thread can be closed.

Nikon NEF red's show to orange as Camera Standard color profile in LR/ACR

I am using a D4s and the red colors in my NEFs in LR 5.5 show more orange. They are not accurate and I am using Camera Standard or Portrait. My screens are calibrated. I see a difference (more true) comparing with Nikon's native program. Even in Capture One the reds are more true. Am I the only one to see this in LR? If I leave the file in Adobe Standard its too saturated and also wrong. Why is it that I notice this more in Nikon files than Canon files in LR/Camera Raw (using 8.5 now)?

I am using a D4s and the red colors in my NEFs in LR 5.5 show more orange. They are not accurate and I am using Camera Standard or Portrait. My screens are calibrated. I see a difference (more true) comparing with Nikon's native program. Even in Capture One the reds are more true. Am I the only one to see this in LR? If I leave the file in Adobe Standard its too saturated and also wrong. Why is it that I notice this more in Nikon files than Canon files in LR/Camera Raw (using 8.5 now)?

Trying to install FF 4 beta 2 for Maemo 5 on my N900 but it still shows as 1.1.

Trying to install FF 4 beta 2 for Maemo 5 on my N900 but it still shows as 1.1. Uninstalled, removed all Mozilla repositories, rebooted, sufed back to firefox.com/m/beta and clicked the install link. The N900 switched over to my app manager and re-installed the beta repository then tried to download/install 1.1.
Has the repository been updated for beta 2?

There's a problem with the Maemo application manager that causes it to always use the version in the Ovi Store, even if you try to install a newer version from a different source. For a possible solution, see http://talk.maemo.org/showthread.php?t=63508

Is camera raw beta 5.4 for 64 bit machines only (PC)?

That is was it seems to be saying when I try and install. If I ignore it and proceed it tells me to close Adobe Bridge, but it's not running.
Hmm!

Thank you for your advice, as you say it was active in the processes. It
has installed OK and works.
General Enquiries: 020 8731 3250
Technical Enquiries: 020 8731 3255
Service and Repair: 020 8731 3270
Sales Enquiries: 020 8731 3260
www.hasselblad.co.uk
This E-mail is from Hasselblad (UK) Limited.
Hasselblad (UK) Limited, is a company registered in England with the
company registration number 1889609. Registered Office: 385 Centennial
Ave, Centennial Park, Elstree, Hertfordshire, WD6 3TJ.
This email and any files transmitted with it are confidential, subject to
copyright, may be subject to legal privilege and are intended solely for
the use of the individual or entity to whom they are addressed.
Any unauthorised dissemination or copying of this email or its
attachments, and any use or disclosure of any information contained in
them, is strictly prohibited and may be illegal. If you have received the
email in error, please notify us immediately by reply email (and delete
the email and any attachments from your system), or telephone +44 (0)20
8731 3250. Any views or opinions expressed by an individual within this
email, does not necessarily reflect the opinions or views of Hasselblad
(UK) Limited.
Internet communications including emails and access and use of web sites
cannot be guaranteed to be secure or error free as information can be
intercepted, corrupted, lost or arrive late. Furthermore, while Hasselblad
(UK) Limited has taken steps to control the spread of viruses on its
systems, it cannot guarantee that this email and any files transmitted
with it are virus free. No liability is accepted for any errors,
omissions, interceptions, corrupted mail, lost communications or late
delivery arising as a result of receiving this message via the Internet or
for any virus that may be contained in it.
From:
ssprengel <[email protected]>
To:
Douglas Fairbank <[email protected]>
Date:
22/05/2009 15:32
Subject:
Is camera raw beta 5.4 for 64 bit machines only (PC)?
Have you checked the Proesses list in TaskManager to see if Bridge.exe is
actually running, invisibly?

"group by" slow for using "count(distinct some_column)" - a better way?

Hi all,
i have an
select
count(distinct some_column),
from [...]
group by [...];
Which is slowed down for the "*count(distinct some_column)*".
The "group by" aggregates base records.
But the base records have 1:n for some #1 event #n records each.
Some of the #n records fall into group by result record (A), some other into group by result record (B).
But each shall only count +1 per event - disregarding how many of the #n record have fallen into that category.
Is there another (faster) way to count for this?
- thanks!
best regards,
Frank
Edited by: user8704911 on Jun 29, 2011 1:30 AM

Hi Dom,
incidentally i went in the direction you proposed:
I replaced the pl/sql collection with the global temporary table.
But the reason for doing this was a different one:
I recognized, that the group by is much faster, if applied on table or global temporary table.
However i first just moved the data from pl/sql collection to global temporary table in order to apply the group by there.
Then the group by is much faster - but the moving of data from pl/sql collection to global temporary table then took away the time.
So it was not the group by, but in general the read-access to the pl/sql collection (btw, around #65,000 records).
Now having completely replaced the pl/sql collection with global temporary table everything is fine.
cheers,
Frank

Camera Profile Beta - will it port?

First, thank you very much to Adobe for creating these new camera profiles per:
http://labs.adobe.com/wiki/index.php/DNG_Profiles#Camera_Profiles_and_DNG_Profile_Editor
For the Fuji S5 and Nikon D80 this makes a major difference.
So, here's the question - if I set my pictures to "Adobe Standard beta 2" profile and in a couple months you go out of "beta" and the profile becomes "Adobe Standard", are the pictures I assigned "Adobe Standard beta 2" going to lose their profile or get messed up.
I assume when this becomes production I will remove and reinstall the production version and/or the production one will replace the beta profiles. In which case will the "fixed" naming of profiles cause me problems?
If the answer is yes, will there be a way to find and replace the broken profiles at some future date with the correct production one (I have a very large catalog)???
Thanks in advance!

In article <[email protected]>,
[email protected] wrote:
>
I actually read that before going ahead and deleting the beta 1 profiles.
"Camera Raw 4.6, 5.1 and Lightroom 2.1 will automatically switch to
using the beta 2 profiles instead."
This statement seems rather clear, but when I checked afterwards the
profile selection was empty on *all images* that had the beta 1 profile
assigned before.
What does that mean? Did the automatic switch not work or is this just a
cosmetic glitch?
Cheers Martin

Live! Cam Voice BETA Drivers and Widows Vista

I have just installed the BETA drivers for Live! Cam Voice and everything seems to have worked except that there appears to be a conflict with Microsoft Genuine Advantage and I am told that "There is a problem with your licence so notifications will no longer appear". The Error is 0xC004D40 described as "The security processor reported a system file mismatch error. I am asked to validate the product online. Validation takes me to Micorosft Genuine Advantage (a misnomer if ever there was one) where I am told that the "copy of Windows did not pass genuine validation. Either an unauthorised change was made to Windows files or a software preogram installed on this computer is not currently compatible with Windows Vista". That would not matter too much if as a by-product. I had not been prevented from updating my installation of Windows Vista, but I was and the only way round that was to start my computer with no programs running and update in such almost clean state. Thus I counsel everyone seeking to use the BETA drivers for Live! Cam Voice to be aware of the problems that they might encounter.

HELLO CREATIVE!!!
CAN YOU MAKE THIS CAMERA USEFUL?
NEED NEW DRIVER!

Camera and ipod shuffle do not show up on desk top when connected

Kodak camera and ipod shuffle do not show up on desk top when connected. Trying to download pictures and adding my music to ipod shuffle, Anyone have any suggestions.

Have you plugged in another USB device to ensure that the USB ports are working?
Suggest you buy (about $10 - $20) a USB memory card reader. Just plug your camera's memory card into it & copy the pic files to your Mac. Quicker & easier than interfacing the camera for pic transfer.
 Cheers, Tom

TS2834 I've been using the mail app that came with my Mac for over a year. Out of the blue, it will not open and keeps saying "Mail cannot open because of a problem" and something about not being compatible ??? Help! I miss my mail

I've been using the mail app that came with my Mac for over a year. Out of the blue, it will not open and keeps giving me an error like "Mail cannot open because of an error and something about it not being compatible. Please help! I miss my mail

Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Click the Clear Display icon in the toolbar. Then try the action that you're having trouble with again. Select any messages that appear in the Console window. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V).
When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Anonymize before posting.

Camera Standard beta 2 for D3 showing distinct blue tone on darkish greys.

Similar Messages

Maybe you are looking for