White Balance Effect

CS6 Production Premium Suite
Win7x64
Nvidia GForce GTX 470
Intel i7 930 @2.8GHz
12 GB memory
Canon XA10
Does Premiere have a White Balance effect like Camera Raw which adjusts the white balance Kelvin?
If not, why not since Camera Raw has one.
Is there a third party that does?
Thanks in advance.

I use an Expo Disc to manually set the white balance for the Canon XA10. However, the lighting was suddenly changed while shooting. Unfortunately, the XA10 greys white balance changes while shooting. The speaker would have gone ballistic if I asked her to stop for a moment to change to auto white balance. So I was forced to shoot with a manual white balance setting that looked great before the lighting change but looked awful afterward. Hence, the need to make white balance adjustments in post production.

Similar Messages

Help requested with White Balance

This may come as a surprise to many, but here I am requesting your help, instead of giving it.
I have filled out a feature request with the following content, already some time ago:
Would it not be nice to be able to extract the WB settings in K from the metadata and be able in post to change it to what you should have done during the shoot.
Say your WB is set to 5600 K, you can extract that from the metadata and with the White Balance effect you can enter a desired setting of say 6100 K. During the shoot you can do that with the Canon XF series, but if you have forgotten to use a warm card instead of the white balance card, this would be a great effect to have. Or in the situation where you simply want a shot to be slightly cooler or warmer, this would be a great feature.
Interface similar to the scale slider and fully keyframeable. The program monitor should reflect changes in color temperature immediately. Simple, easy to understand, like using a set of Warm Cards after the shoot.
Retrieval of the color temperatures should not be difficult. It is contained in the metadata:
It works both with AWB and manual for the XF series. If the camera does not record these data, the effect should be greyed out.
I request your help to get this feature implemented, since it is pretty simple to implement, is a great help to have when doing multicam work, to fine tune different cameras or to change the atmosphere of a shot. It is far easier than the color correction effects we already have.
If you agree with me, please fill out a similar feature request. The more requests made, the greater the chance of it being implemented.
See Feature Request Form

Harm, I've seen instances of multi-cam shoot cameras that were identical models, using a clone of the settings which still resulted in differences in color. I've seen this blamed on the chips and the chip manufacturing process. I've also seen multicam footage from analog cameras that were supposedly balanced before shooting that resulted in shifts. And then, you have a situation where the atmospherics can alter the color, such as when one camera is close to the action, and the distant camera is shooting through fog or haze that has light shooting through it.
So again, while you can get in the ballpark with certain regimes, when it comes time to finish, you have to trust your eyes.
So, for my situation, it's not something that rises to the level of something I'd use enough to warrant a feature request.
My biggest issue today is that I'd love to see Pr offering bottom-up rendering, the way Avid MC offers it with its Render All option vs. Smart Rendering, which is top down. I don't like that I have to re-render entire sequences just because I made a little change to an upper layer clip. That, to me, warrants a concerted campaign or pitchfork mob.
But, I'll make a pact with you. If you'll request bottom up rendering, I'll request WB metadata support, OK?

Video white balance levels not showing, so video effects and color editing won't work

I've watched white balance tutorials, and I tried clicking the dropper onto the viewer to change the color. But, in the gray box above it there are normally red green and blue lines, but I have nothing there. I think this is preventing any edits to my color balance, can anyone help?

Well, no offense, but you seriously should read the C4D help. That's normal specular shading behavior and it is uniform acroos the plane because you obviously haven't defined any scene lights and use the default viewport light. Read up on how to create materials and adjust there properties and then learn the fine art of scene lighting as well as how to use object buffers to isolate objects with multipass renders.
Mylenium

Can you remove the camera white balance setting in Aperture

I have a Canon 7D and use Aperture for processing and storing my images.
With the Canon I shoot both video and still and frequently adjust the white balance in the camera. I make a frequent mistake in leaving the wrong white balance setting on - eg when taking video indoors in the evening I set the white balance to indoors (the Canon seems poor at white balance decision making on video) and then I forget I'm not using auto white balance and switch to taking a photo with flash. The result is a horrible blue photo - which if I don't spot the problem at the time seems very hard to correct afterwards.
I use the Aperture white balance adjustments frequently but unless there is a patch or white or grey I an use the dropper on, I find this particular situation seems to be right off the scale of what I can fix in Aperture. I end up with sliders at the extremes of the scales and no intuitive sense of what numbers to type in manually to try and get realistic colour - so I often end up discarding these photos even if the shot itself is something I'd like to use.
So my question is given I'm importing RAW, is there a way to show the phoo without the (wrong) white balance setting I applied in the camera, to let me choose white balance from scratch?
Or if not, do you have any advice about how to adjust from this very bluey unrealistic colour of image?

Kirkby - thanks for the quick reply.
Didn't know you could drag inside a value field - that's helpful.
But being able to get different numbers on the slider isn't the root of my problem.
In a specific example I have two photos - one taken with white balance set to flash and the photo was with flash, where after a bit of tweaking to get the colour I want the temp slider is at 5000K (and tint 0). The second photo has my shooting error with interior lighting white balance but taken with flash. The two shots were taken from almost the same point of the same view (but different people in frame). The shot with the white balance error comes off camera horribly blue coloured. I can fiddle with the two sliders - I take temperature to 20000K and tint to 40 to do the best with it I can, and with those settings one of the two faces is approaching flesh colour but the wall behind the subjects (which is a light blue in reality) is now appearing light yellow in places. I just can't get a good looking colour effect no matter ow extreme the slider settings.
I may have phrased my question badly - as I totally agree you can't show a raw without a colour setting - so maybe I'm better asking to be able to use a different colour setting on the raw data rather than having to start with adjustments on top of my white balance mistake.
Given the two shots were in the same place against the same background and the same lighting (both with flash) it seems to me I ought to be able to get a similar colour effect on both and I just can't. To illustrate here are the two photos (the one on the left was shot with flash wb and in Aperture I'm viewing it with 5000K and 0 tint, the one on the right was shot with indoor wb and in Aperture I'm viewing it with 20000K and 40 tint and it looks terrible!)
https://www.box.com/shared/qle3t6ovyhrd1egez3vc

White balance

What is the best way to correct white balance shifts post production.
If shooting underwater, there is either a big jump to very blue, or to red.
Will I have to select different underwatercolour ranges and correct them each, or is there an easier way?
Is it best to use 3 way colour corrector, or other effects, or a combo?
I also have Adobe after effects 6.5, is there something in there recommended, as superior?

Underwater footage is fascinating stuff but it will not necessarily respond to conventional color correction. Unless properly lit, filtered or balanced the colors simply do not exist; there's no color data to correct.
The #1 advice form the kenstone.net articles: Shooting underwater successfully requires knowing what you're doing long before diving.
http://www.kenstone.net/fcphomepage/lighting_below_thewaves.html
The loss of color is deceiving. The human brain compensates for much of the color loss and even at depths below 30 feet, your eyes will still see some red. But a fact which we must understand is that the camera is really dumb. It has no brain, so therefore it will not compensate. To overcome this problem, artificial light sources must be used.< </div>
When working in water with a greenish tinge, as in the west coast of our continent from Seattle north to Vancouver Island, a magenta filter will produce good results. For blue caribbean waters, I always prefer my red color correction filter. < </div>
POST PRODUCTION FILTERS. As in topside video work, occasionally we misjudge the lighting conditions and must attempt a repair within Final Cut Pro. There are a few filters in the browser which I have discovered work well with underwater video footage. The Proc Amp filter can be used to put some vibrancy into an otherwise washed out shot. The RGB Balance filter is another which if used sparingly can save an otherwise interesting piece of footage from the cutting room floor.
But these filters are definitely no substitute for getting it right in the first place. The best angle of attack is to concentrate on the basic principals of lighting so that your footage can go untouched from the camera to the timeline.<
bogiesan

White balance field to metadata panel

There's a lot of info available in the metadata/EXIF panel but the preset/program used for white balance is missing, eg. Auto, Cloudy, Tungsten, Custom, etc. Interestingly though, LR can read the actual values in the Develop module, unless I'm wrong and it is actually working it out, not reading it.

Is there any way to get detailed info of White Balance setting in Bridge Metadata ? I'm getting only "custom" ; my instructor in College needs more detailed data in my contact sheets.
Thanks for any imput
You can't get this info in a contact sheet, neither is it easy to get other then look at the camera setting you have used to shoot the files. Maybe it is somewhere hidden deep down in the exif data but I can't find it with exact numbers.
Shooting Raw those WB figures are irrelevant because you can set color temperature and tint to whatever you like. Shooting jpeg your options are limited because of the fact the Raw data is already processed and changing temperature and tint effects the whole image.
Try shoot a Raw and jpeg together from the same scene. One with daylight and one with artificial light conditions. (personally I have set my WB in camera fixed at 5500 but with auto settings you can also see the difference) Try to correct the jpeg and the Raw file in ACR and see what I mean.
And to be honest, if your instructor at College would like to have this he also should tell you why he wants it and how you can deliver it...

How to set White Balance details in Metadata Bridge Cs6 shooting with MarkIII 5D ?

Is there any way to get detailed info of White Balance setting in Bridge Metadata ? I'm getting only "custom" ; my instructor in College needs more detailed data in my contact sheets.
Thanks for any imput

Is there any way to get detailed info of White Balance setting in Bridge Metadata ? I'm getting only "custom" ; my instructor in College needs more detailed data in my contact sheets.
Thanks for any imput
You can't get this info in a contact sheet, neither is it easy to get other then look at the camera setting you have used to shoot the files. Maybe it is somewhere hidden deep down in the exif data but I can't find it with exact numbers.
Shooting Raw those WB figures are irrelevant because you can set color temperature and tint to whatever you like. Shooting jpeg your options are limited because of the fact the Raw data is already processed and changing temperature and tint effects the whole image.
Try shoot a Raw and jpeg together from the same scene. One with daylight and one with artificial light conditions. (personally I have set my WB in camera fixed at 5500 but with auto settings you can also see the difference) Try to correct the jpeg and the Raw file in ACR and see what I mean.
And to be honest, if your instructor at College would like to have this he also should tell you why he wants it and how you can deliver it...

Bridge CS5 applies wrong white balance during thumbnail extraction (raw files only)

Hello to all Adobe Wizards,
Hobbiest photographer here. I use a Canon T2i and I have been shooting raw with auto white balance.
After I upload the CR2 files to Bridge, Bridge begins thumbnail extraction. This is when the problem begins: I watch Bridge extracting thumbnail photo after photo, turning them into wrong white balance one by one. After Bridge is done, I open one of these photos in Camera Raw, it shows the photo in "custom white balance". I was able to change it back to "As Shot". But every photo in Bridge now has custom white balance and is difficult to view in Bridge. This screenshot shows what my Bridge looks like after thumbnail extraction....
Yesterday, just out of curiosity, I took some photos with different white balance settings on the camera. I uploaded them to Bridge and Bridge over-wrote all the white balance settings. I then imported the same photos (from the same files) to iPhoto, they show up with correct write balance. Please see the second screenshot.
The third screenshot shows a unedited photo I opened from Bridge to Camera Raw, and the same photo as it appears in iPhoto, both unedited.
Again, this only happens to CR2 files. All tif, jpeg files are fine.
Any ideas?
Thanks!
-Wolfie

Any ideas?
First of all, shooting Raw has the benefit of changing the color temperature (Whit Balance) to what ever you like from whatever you shot in camera.
To me it seems you once have saved a custom white balance as default setting and this is been applied to every new file because you told Bridge to do so. The easiest way to get out of this is open a raw file in ACR and in the basic tab at the right side you see a small icon for sub menu (next to the word basic). Click on it and from the row choose 'Reset Camera Raw defaults' at the bottom.
Also decide whether you want to stay in 16 bit mode (as you are now as shown in the blue line under the preview). If you want to chance it back to 8 bit just click on that blue line and choose your options from that menu. You only have to do this once for the files from that same camera, ACR remembers the settings for you.
Using 16 bit mode has advantages when using critical color corrections (but then you also should change the color mode to ProPhoto in my opinion). The disadvantage is that 16 bit doubles the file size compared to 8 bit
Having set the ACR defaults should effect your thumbs immediately by building new thumbs and previews but if not you must choose purge cache for folder from the menu tools / cache/ purge cache for folder. Now the new settings will be applied.
It may take some time so let Bridge do its work properly before starting other jobs in Bridge (see the activity bar bottom left to check if Bridge is still caching).

White Balance Selector Tool operation

The WB selector tool still appears as though it only selects one pixel in the the "Pick a Target Neutral" array display window, the one with the x over it (regardles of whether you scale the matrix to 16x16 or 5x5 with the scale slider. It does not appear to allow averaging of adjacent pixels to reduce the effect of random noisy pixels messing up the wb. This has already been brought up in previous threads and the LR team apparently dismisses the concern. Reminder to Adobe Labs: we don't all shoot with relatively noiseless Nikon D3/ D700s. Our cameras do produce significant color noise even at relatively low ISOs. So when we attempt to find a neutral patch or pick a spot on a neutral whibal card with the color picker tool, we see a random array of various shades of gray, some a little more purple, some a little more green in the tool's selection window. Depending on which pixel we place the X on, we get a different white balance. EVEN THOUGH WE ARE HOVERING OVER WHAT IS SUPPOSED TO BE AN EVENLY LIT NEUTRAL BALANCE CARD! Could you guys please talk with your Photoshop colleagues and figure out how to give us a 5x5 or NxN pixel averaging white balance picker. Or maybe you confirm that I am wrong and in fact this tool already DOES average all the pixels I see in the "Pick a Target Neutral" pixel array display? This would be far more useful an option than the ability to put a decorative flourish at the bottom of a menu panel! Thanks.

In addition to the point being made above in regards to a 3x3 or 5x5 pixel eye dropper for the selection of your color balance(color temperature), it would be great to have an eye dropper to select & set your black, white & mid grey(18%) point inside of lightroom to not only neutralize any color cast but also to set your tonal values with a x-rite color checker or similar reference.

White Balance color temperature for custom temperature shots

Hello,
I would like to understand why LR and Photoshop too are always show wrong color temperature "As Shot"?
Let say I shoot with 6000K, set manually (Canon 40D, RAW)
Canon itself says it's 6000K in the slide info, fine.
Both Adobe apps says it's 5750K!
What's going on there?
Second question - I know the light was EXACTLY 6000K, but the slide has some green in it. Picking white balance in LR gives me 5900K (which is close to the truth) and +31 Tint, which makes slide neutral.
Of course I can correct Tint manually before the shot by WB Shift in Camera, so the question is: what is the best way - to find more or less appropriate WB shift in the camera, or use WB correction in LR after all?
Thanks
UPD. My suggestion is - Adobe doesn't read custom temperature from RAW file, it's just guessing! Is that right?

The white balance value you see in Lightroom is profile specific. It reads your custom white balance and translates it so that neutrals stay neutral, which is exactly what you want. If it wouldn't do this, your neutrals would shift in color.
The best way to get a correct white balance is to shoot a white balance (grey) card or use one of those filters on your camera to measure it. You can either set it in camera from the grey card or do it with the dropper in Lightroom and sync over the series. The effect will be the same.
P.S. unless you shoot a white balance card, you do not know that the color temp of your light is exactly 6000K. That is quite impossible to know. It might be approximately that under certain standardized conditions but you cannot be sure, no matter what you're told by the manufacturer.

Can Bridge report in-camera settings for White Balance?

No matter what settings I choose in Bridge Preferences, I cannot get it to tell me what was the White Balance (WB) setting of the camera when raw images were shot.
This seems an odd omission because Camera Raw is passed this information and displays images correctly, although it doesn't report what WB value it was given, only that what you are viewing, prior to any editing, is the default "As Shot".
I'm referring to raw files shot on my Canon 300D, Nikon D700 and Canon 5D Mark II.
Currently I'm using PsCS6 (13.0.1.2 x64), Bridge CS6 (5.0.2.4 x64) and ACR 8.1 on a Windows 7 x64 8GB system, but the same omission existed on the same Windows system with ACR 7.x in CS6 and all releases of PsCS5, Bridge CS5 and ACR 6.6 and 6.7.
On the opening dialog of Bridge Preferences, at the bottom you can choose whether or not you wish to 'Hide Empty Fields'. Selecting or unselecting this option does not have any effect upon Bridge's inability to report WB when, from within Bridge, you select File Info from the File menu or by hitting Ctrl + I.
The only locations in Bridge Preferences I can find that need selection (and which I have selected) for Bridge to supply WB information upon invoking File Info are here:
Preferences\Metadata\Camera Data (Exif)\White Balance; and
Preferences\Metadata\Camera Raw\White Balance
I have also selected Preferences\Metadata\File Properties\Supports XMP, and yet Bridge fails to give the in-camera WB in the Camera Data tab of File Info.
I have been able to locate references to WB in the following tabs of File Info:
File Info\Advanced, where there appears, under the sub-tab 'Exif Properties (http://ns.adobe.com/exif/1.0)', an entry such as 'exif:White Balance:1'; and
File Info\Raw Data an entry such as '<exif:White Balance >1< /exif:White Balance>'.
However, these are just code numbers, not names like 'Cloudy' or 'Shade', and they are not only inconsistent (both showing the code 1 for an unedited image I know was shot with Auto WB and another unedited image I know was shot with Flash WB) but also it would appear that the codes may refer to the WB as modified by ACR - because an image I know had its in-camera WB of Auto altered in ACR shows a code of 'Custom' rather than 0, 1 or some other number.
So what am I missing? Does anyone know how to make Bridge Preferences display the in-camera setting for WB, and if so, under which tab of File Info do you look for the answer once you have set up Preferences properly?
Message was edited by: Andrew_Hart
Just corrected my current Photoshop version

I'm afraid that you just haven't addressed the question that I asked in my original post.
I still like to think I have but if you for whatever reason need this info showing in the metadata you probably be better of trying to alter it your self or find a way to address Paul personally (maybe via a private message).
I have not heard from him for a long time and a small google search provided me with this forum post, hope it helps you, maybe you can also persuaded Paul to come back, he is very missed!
http://www.ps-scripts.com/bb/viewtopic.php?f=2&t=5508

Premiere Elements 13 Eyedropper for white balance, gray, and black NOT WORKING. Help!

I'm using Premiere Elements 13.1 on an iMac, and trying to adjust the white balance on a clip with ZERO success. The main reason for this is that I cannot utilize the "eyedropper" selector; I know what should appear white, gray, and black, but cannot select those items.
In the Three-Way Color Corrector there are Eyedroppers to use to specify areas of known color range. I have tried without success to select ANY of the eyedroppers...
I have clicked on it - NOTHING
I have held the left mouse on it and attempted to drag it onto the frame - NOTHING
I have right-clicked it - NOTHING
The eyedroppers are not greyed out and they do respond when clicked. I have hit Reset button galore. I have restarted the program.
I have held my mouth funny - NOTHING :-)
When my cursor is hovering over the tool, it changes to an eyedropper. If I click, nothing happens when the cursor is moved - the cursor changes right back into its regular arrow shape. The cursor does nothing to the image if an item is clicked....there is no change to anything on the monitor.
I am a longtime Photoshop user but new to Premiere Elements. This dropper seems to work nothing like the PS ones. In fact, it doesn't work at all...so far.
Can someone please tell me what I need to do to simply select the eyedropper and take it onto the image and select the white (or gray or black)??? Before I go bananas (may be too late)? THANK YOU!

Still not working. I think the root cause of the problem is the mechanics of using the tool itself; I hope this screen shot shows up below ...
Here I have APPLIED EFFECTS open, and have selected Midtones (Greys) to be expanded so that the eyedropper and other details appear:
Now, just below where it has a box and "Impacted frame area in white" (which I know is a checkbox allowing the area effected to be seen), there is a little color box and an eyedropper.
What EXACTLY do I do to select (activate) the eyedropper and subsequently tell the program what I feel should be grey in the selected clip?
As mentioned before, I can click it and the cursor briefly changes to the same shape as the eyedropper. But as soon as I move the cursor a fraction, it changes back to an arrow (normal cursor) shape. Even then, going to the area I need to select in the image, and then clicking it, does exactly nothing to the appearance of the image shown -- even if the colors start way off. No correction at all. It is as if the tool does nothing. The color wheels below all this DO work however - it's just the eyedropper that doesn't do anything. This just cannot be Adobe's intention. I am convinced there must be some flaw in how I am selecting the tool itself. And the user guide - needless to say - is worthless in explaining the mechanics.
So very frustrating. This appears to be the only thing wrong with the program - nothing else seems amiss.
NOTE: To add insult to injury, this promised white/gray/black balance feature and the three-way-color corrector is the SOLE REASON I purchased the software. Funny.

Custom white balance from Canon 5D Mark 3 erased from RAW files when developed in Lightroom 4.2?

Hi Everybody!
Got a bit of a problem...I set custom white balance for a lot of my photos (I'm a nightclub photographer) as sometimes the colours are so saturated the image becomes unusable. Unfortunately in Lightroom 4 the photos import with the correct WB I have set but when I click on them to develop the settings are changed and the image looks completely awful. I try and adjust the image back to the way I have taken it but it never looks the same....why is Lighroom not recognising the WB settings I set within my 5D?
Any pointers?
Cheers!
Sarah

All Raw images can be expected to change appearance significantly after the initial display of the in-camera embedded JPG preview, has been replaced with a true LR-generated conversion preview.
This is because all in-camera image settings and processing options (except WB) are disregarded by Lightroom. Lightroom just works to its own processing default, and this is in your control to get as you want it.
Even the in-camera WB, is only used provided LR is set to "as-shot" WB at the top of the Basic panel. If LR's default gets changed to a fixed WB of some kind, then that is what every image will show initially thereafter.
Even with the right WB transferred and used, first LR renditions can still look very different than the camera rendition; two people picking up the same violin might make very different noises with it. One of the biggest effects for that, is when proprietary in-camera "dynamic range boost" (or however else named) functions have been used. These work by deliberate underexposure of the basic capture, and Adobe software tends not to then apply the right corrective for that.
Even without these special functions in play, it is still usual for Adobe factory default processing - combined with camera programmed metering - to produce images which appear a little on the dark side, but which nonetheless have good scope for brightening without losing highlight detail. An image that looks generally bright enough in this context, will usually turn out to have blown highlights. If the camera has any kind of a low-noise sensor, the shadows will tolerate brightening even better than the highlights will.
And if your customised LR default has applied some brightening and that turns out to be too much in a given case, it can simply be turned back down for that image with no harm done. Or you might prefer to under-correct with your default; up to you.

Why does my infrared custom white balance not load into Lightroom or CameraRaw?

The preview shows the correct WB, but the full render removes WB and any monochromatic color profiles.
Correct WB that I want. As seen from back of camera
Once the full preview loads. DO NOT WANT.
White balance is at 2000, the coolest it can go. I cannot recreate the custom WB that is in camera. I can make all of the B&W, but I want the custom WB so I can do a proper channel mix in PS.
Thank you for any help.

You can use the DNG Profile Editor to add a negative bias to the WB settings in an existing camera profile and save it as a new profile (for IR) so you can adjust the effective WB lower than 2000K:
http://stevencastle.wordpress.com/2010/07/17/processing-infrared-shots-in-adobe-camera-raw /
It still won’t pick up what the camera did, but you can adjust things lower, at least.
If this one page doesn’t make sense Google for (DNG Profile Editor IR white balance)

Bug Fix for White Balance Issue (When ?)

Dear Apple:
When can users expect a patch for the bug that "crept" into Aperture late in the development cycle that seriously effects the white balance tool?
This bug is obviously a major concern and issue for most professional-level photographers; and, quite frankly, prevents Aperture from being used in a professional capacity with regard to RAW decoding.
Cheers

Excuse me, John:
But, quite frankly I don't think you are in any position to tell the users of this form how they should feel. Most users, who happen to be high-end prosumers or professionals such as myself, have paid a great deal of money on a piece of software that was supposed to live up to certain, basic expectations. Unfortunately, that software did not. As such it cannot be used in a professional environment.
Subsequently, an update was provided to address all the concerns that users expressed. Unfortunately, that update created a major issue with regard to the white balance of RAW images. Yet again, this expensive piece of software is nearly useless in a professional environment.
Let me ask you this: "if you were a gardner and paid several hundred dollars for a lawn mower, only to discover that it cut your clients' grass unevenly, would you continue to use it? Would you continue to be patient after taking it into the repair shop only to have it still screw up your lawns? Would you not be on the phone with the repair shop constantly until it was fixed?"
Unfortunately, Aperture is a good idea that has a flawed implementation and that NEEDS to be addressed! So, I will continue to ask Joe and Steve and the others at Apple when will this piece of software actually live up to the expectations set forth by the company that produced it!

White Balance Effect

Similar Messages

Maybe you are looking for