Since update to 3.5 issues with white balance

since update to Aperture 3.5 tonight the white balance in all of my pictures is completely wrong (way too cool with a greenish tint).
After setting the white balance with the eyedropper it reads on a Whibal grey card
R: 117
G: 188
B: 156
Any suggestions? Thanks a lot !

I cannot replicate this issue. Upon import of new images (RAW) I tested the White Correction using the eye dropper. No issue at all, despite reports here to the contrary.
In the previous round of this issue, it seems to have only impacted people who did not directly download new photos into Aperture, but rather were using some third party software to first do some processing of them.
The previous issue required some sort of fix not only from Apple, but also an update of the aforementioned third party software (Nik apps in that case.)
Ernie

Similar Messages

Issues with White Balance and other camera setting...

I have found a glitch with the camera on the Lumia 800: When you try to change a different white balance setting- (try it with incandescent so you can see the difference) as well as changing the scene (ie to portrait mode) it will flip back to auto white balance, although it will say that it is still incandescent. If you change the scene first and then the white balance and save those settings, it will take one picture like that and then revert back to auto white balance again for the next shot, but again it will tell you that it is still incandescent. (You can clearly see the white balance difference between the 2 shots, even though the camera settings say they should be the same). The whole point of saving settings is so that you can take multple shots with the same settings. I have spent hours on the phone to Nokia trying to explain this to them and they have assured me that it will be fixed in the next update. I took the phone back to the Orange shop and we tried 3 different handsets and they all had the same problem.
I also have the same problem with video autofocus that lots of people have mentioned. Has anyone found a solution yet? The main reason I got this phone (only last week) was for the camera so I am diappointed. I am a photographer so I am really fussy about cameras! They have said in the Orange shop that I can change the Lumia for another phone, such as a Galaxy S2, which is also an awesome phone. The thing is, I really love the Lumia otherwise. I really like the fact that I don't have an iPhone anymore, for a start!!
Does anyone think the network you are on makes a difference? It's just that several people have suggested that there could be a conflict with the Orange software and the Nokia/Windows software. Does anyone else have this problem who is not with Orange?

Thanks for all of your valuable suggestions.
The problem was compounded when there were drastic shifts in the levels of ambient light also occuring at the same time.
Happy Holidays to everyone.
Bruce

After the recent update I am having issues with Flash based games freezing and not responding.

After the recent update I am having issues with flash based programs not running or loading correctly. The programs will not load or take an extremely long time to load compared to jsut a few days ago. This happens across the board on anything flash based. Also, once they do load they will freeze, stop responding or need to be constantly refreshed to come back alive which is short lived at best. I went thru the help and did all the file deleting, cache clearing, disabling hardware acceleration, removing then reinstalling flash, and even removing and reinstalling my browsers. None of this has helped at all. I am using Chrome and it is up to date and I checked my Flash player and it is up to date. I am running windows 7 64bit.

Here's what you're up against guys,
Adobe writes the base code for Flash Player, and then hands it off to Google, who adapt it to a PPAPI plug-in (it's NPAPI when Adobe writes it). It's then "PepperFlash" and Google embeds it in their Chrome browser. While Google is pushing a "webwide" move to PPAPI Flash Content, a reinvention of the wheel so to speak, not everyone "got the memo", and Google is slowly making it so that PepperFlash will block NPAPI Flash content from running properly, and you have to disable PepperFlash to force the NPAPI plug-in to work, which sometimes fixes it, sometimes not. I have a feeling this is only going to get worse. HTML5 will eventually resolve the video end but game developers need to come up with something that won't require a plug-in.
And to the first post: Since PepperFlash is embedded in Chrome by Google, you can uninstall and reinstall Flash Player from here until your hard drive literally seizes up.... guess what? It has NO EFFECT at all on the PepperFlash plug-in in Chrome because it's a separate file in a separate folder and the uninstaller & installers don't have anything to do with it.

Has anyone received an update on apple tv issue with HD movies and what they are doing about it

Has anyone received an update on apple tv issue with HD movies and what they are doing about it

Whatever the rep told you, it is complete nonsense. There is clearly a problem at your end, the Apple TV 3 is capable of more than the Apple TV 2, and you clearly have the Apple TV 2 working perfectly. Since the Apple TV 2 is able to download from the Internet properly, then my suspicion would be your problem lies on your local network. Interference is a common problem on local networks.
Interference can be caused by other networks in the neighbourhood or from household electrical items.
You can download and install iStumbler (NetStumbler for windows users) to help you see which channels are used by neighbouring networks so that you can avoid them, but iStumbler will not see household items.
Refer to your router manual for instructions on changing your wifi channel or adjusting your multicast rate.
There are other types of problems that can affect networks, but this is by far the most common, hence worth mentioning first. Networks that have inherent issues can be seen to work differently with different versions of the same software. You might also try moving the Apple TV away from other electrical equipment.

Since updating Firefox I have problems with playing Zynga games

since updating Firefox I have problems with the Zynga games I am playing. The functions often stop working so I have to reboot the game. Also there are often a lot of items missing on my screen so I can't play at all

I have this problem, as well, since the upgrade to 4.0.1. After the upgrade, I found several 'Recovered Files' in my Trash. On taking a look, they all had to do with the Crowdstar app. Happy Aquarium, I believe, but there are several folders of them. Some of them could have to do with Zynga's FarmVille.
However, after repeated problems, I installed Chrome 10. to see if the Facebook apps. would work. They did, without problems. That tells me the folders in Trash shouldn't have anything to do with whether they operate or not but it has something to do with something Firefox has done, or not done, with this upgrade. Frankly, I'm baffled and more than a little annoyed. :/
However, thinking back to the upgrade, it happened suddenly while I was on the phone with AppleCare on another matter. It was they who suggested I needed to upgrade my browser and I did it immediately, on-the-spot. It wasn't what you would call a 'clean install' because I was on the phone but also online with AppleCare. The process went so fast, I remember there were things about the installation that didn't quite seem right and I do remember that the earlier version of Firefox was not removed prior to the upgrade. Is there any chance something could be out-of whack because of this? If so, I need to know how to save my passwords, bookmarks, profile, and any other critical info that would need to be transferred.

The panel with White Balance, contrast, exposure, whites, blacks, etc. has disappeared from my Develop screen

The panel with White Balance, Exposure, Contrast, Tone, Whites, Blacks, etc has disappeared from my Develop screen. The control panel on the right side now starts with Tone Curve and I can't find a way to revert back to the screen with the other adjustments. I need to know how to correct this problem.
This is what I'm working with now:

Right click 'Tone Curve' (the title/words) and enable 'Basic'.
Do you see it?

SSL patch update has caused many issues with my iPhone 5c

Since the patch update completed, my iPhone is acting ridiculous. I cannot use safari. Every time I try to search something, it tells me it cannot connect to server. I also cannot delete voicemails. Once I delete, the phone freezes and the voicemail is not deleted. It comes back from deleted messages. When I hit the phone toggle button, it opens up my recent call list but it opens to the calls from Thursday, the day I did the update. It also deleted every text message that I had sent that day from my text history. I have shut the phone down, what other options do I have?

I have actually talked to a couple people that I know that have the 5c and it seems like it is a hit or miss. Some people have problems with the blue ones, im having issues with the white one, some people have no issues att all. COnsider your son luck that he has no problems. I have had problems with 3 different whote 5c over the coarse of 4 months now and contuining to have problems.

Anyone else having issues with white iphone4 home button?

so i have come across this stuff here and there but i am pointing more towards people from India..
You all know how Pathetic apple is at India because of not having major share holding...
My White iPhone 4 purchased in july on the same date as launch in India has issues with the home button.. It sometimes becomes unresponsive.. Stays like that for 5-15 seconds as it varies and then starts working..
I don't understand if it is hardware or software issue.. Sometimes for weeks it doesn't happen and then it could happen way too much... i went to the iStore guys and they told me to restore it as its a software issue..
I wanted to know if any of you faced that and what did you do? did you get a replacement? since it happens occasionally i cant show the store guys that it is happening so they won't replace.

My experience with home button:
Mine did not work sometimes also; but I found this was due to "how" i was pressing the button. There must have been some dust under it because if you pressed it in a certain place; the button would press in but this would not register until you pressed really quite hard.
Pressing in any other place and the click seemed to register.
Try it and see if it is the same for you? Can you press your button in a place and it doesnt register (mine was at the top of the white square on the button)...
I had mine replaced under warranty from my Apple Store.

Does the 10.6.4 update fix the freezing issues with the i5 & i7 MBP's

Since I am on the fence about buying a new 15" MBP I would be interested to know what effect the new update has on the latest MBP's and the freezing issues some are experiencing.

The "freezes" that are mentioned in other threads here appear to be due to a wide variety of different issues. Looking at the relevant posts I'd reckon about one in thirty of them at the most are due to an unusual issue with a few of the current MBPs. The other 29 are simply the regular array of things that cause freezes on any computer - out of date software, corrupted directory structures, the migration of already corrupted software from older computers, duplicate or corrupted fonts, badly written third party software, the occasional shonky HD or RAM module, etc etc etc.
THis is a non-issue from what I can see. Some people may well benefit from updating to 10.6.4 , but probably only because it replaces some files that have been corrupted for other reasons in the past.
I certainly wouldn't be putting off getting a new MBP on the basis of the stuff here. Sure, some people will experience "freezes", but there doesn't really seem to me to be anything out of the ordinary being reported here with respect to the new MBPs. There are a thousand and one things that can lead to "freezes". In a few cases it probably is due to a hardware problem with one component or another. In the vast majority, however, it will simply be because of the common old "thousand and one shocks that silicon chips, magnetic storage and software developers are heir too"!
Cheers
Rod

Overprint issue with white type.

We have been creating Digital PDF successfully for over 10 years. This is a problem that comes along once in a great blue moon.
Please read complete text before forming an opinion or answering the questions. The focus of these questions are on Digital AD's from outside vendors/customers.
We create our publications using Quark 6.5 on Windows XP
(We are locked into this version because of some other proprietary software tied into Quark, so upgrading Quark is not an option for us).
We compose a page of some type, some MAC EPS Illustrator 5.1 files and at least one Digital AD (PDF's which are from our advertisers/customer that we pre-flight) on to the page.
Print the page to a postscript file, distill postscript file with Acrobat Distiller Ver. 7 on PC's into a PDF file with Crops and Registration Marks.
We got a PDF (Digital AD) from a customer that was created in InDesign CS6 on a Mac. There is some white type in the AD ( See Photo Below)
The Last "E" in Engineered is selected in each screen shot.
The Top one is the AD untouched before Pre-flighting it. The White Type "E" letter is set to knock out and is still type (not converted to outlines).
(Pitstop is showing this in the dialog box on the right)
In the Bottom screen shot the type has been converted to outlines and is set to overprint.
First problem is white type should never overprint. Unless you specifically set it to in the original program.
This type was originally set to knockout and then when it was distilled from a Postscript file from Quark into a PDF with "Preserve Overprint Settings" check in (Distiller Settings) the type is converted to outlines and the type was set to overprint.
(If I turn off "Preserve Overprint Settings" and re-distill the postscript file the type doesn't convert to outlines or change to overprint.... it remains a knockout.)
Second Problem is catching this while using preflight tools. I have Pitstop tools to show Overprinting and Acrobat has a Output Preview/Color Warnings/Show Overprinting feature too.
Using Pitstops Overprint does show it in the inspector window, but not a Pitstop report.
Acrobat's Show Overprinting does NOT show that the type has been set to overprint.
So our workflow now is to flag any white type and check it throughout the whole pre-press process to make sure the type holds the knockout function.
Below is a scan of how the type ran when it was printed on sheet feed printing press paper.
Talk about overprinting... this is not what it looked like in the above pictures.
I am aware of this problem from Illustrator. It's an order of operations when dealing with white type.
If you set type, change the color to something other than 100% black and then convert it to outlines... it will knockout.
If you set type, convert to outlines and THEN change the color from black to white, it will hold the overprint from being black type.
It doesn't always do this every time, but it does happen enough that I have to double and triple check my white type.
Questions:
Does anyone have this problem in their workflow (White Type Overprinting) and do you have a solution to better catch this when you have to process 50+ AD's each week?
Obviously anything with white type will be looked at much closer now that this AD got through. It would be nice if these settings would hold through the whole preflight to printed piece process.
Any Words of Wisdom would be appreciated too.

You can set Pitstop up to catch this and even fix it.
In the preflight profile, under 'Text', select 'White Text' and add it to the list of checks, you can also enable the fix as well so it's just resolved.
I'm using PitStop 11 update 2, but it's in earlier versions as well.
If you need futher information you can always drop me a mail. I am the Product Manager for PitStop, [email protected]

Raw Update 2.3 + Nikon D90 = Wrong White Balance Temperature

Hi folks. Wonder if someone has had a similar issue and/or has any insights.
Here's the background:
- Aperture 2.1.2 on OS 10.4.11
- Downloaded/installed Raw Update 2.3
- Imported ~800 NEFs from a D90
- On ~15-20 NEFs, pictures show up blue (white balance at ~2500)
- The affected NEFs are semi-randomly distributed among the ~800
Here's why it's weird:
- NEF displays correctly in Nikon View (the thumbnail and full picture)
- NEF displays correctly in the Finder (the thumbnail)
- NEF displays correctly in the preview and thumbnail *in Aperture* but only until the preview and thumbnail processing completes at which point they turn blue (this is why it's especially weird)
- Peeking into the Aperture package, the NEF thumbnail shows up correctly but the preview and thumbnail files show up blue.
If I delete the NEFs from Aperture, close down, and repeat I get the exact same problem on the exact same NEFs. This leads me to believe that there's something specific to the NEFs but it must also be linked to Aperture and more specifically, it's thumbnail/preview process since they show up fine in Nikon View, the finder and Aperture before the thumbnail/preview processing takes place.
Obviously I can't downgrade to Raw Converter 2.1 or 2.2 since my files are from a D90, and I shoot in raw (not raw + jpeg) only so have been limping along with Nikon's software.
Any ideas out there?
Thanks!
Message was edited by: rbhansen57

Hi,
I simply can't see the NEFs.
OS X 10.5.5
Aperture 2.1.2
Nikon D90
Import runs fine, and the thumbs are there, but when opening a NEF a big thumb (7x4.5cm on the 24" screen) is displayed in the middle for a second, and then it turns into a dark red message "Unsupported Image Format".
It's general - no NEFs work for me.
I import directly into Aperture - do you import via the Nikon Software?
Previously I had an Olympus E400 - the RAWs worked fine in Aperture (directly imported).
My strange observations are:
With the Olympus E400 (10MB) the size of the JPG files were 6-7MB and the RAW files (called .ORF) were 21MB.
With the Nikon D90 (12.3MB) the size of the JPGs are around 6.5MB (4288x2848 pixels), but the size of the NEFs are just around 11MB (I did expect over 21MB) and the pixels are 256x170 (although the picture says 4288x2848 on the camera itself).
I'm new to this support site - do Apple supporters take time to read our questions and join these discussions?

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?

Real Problems With White Balance Tool

I attempted to white balance an image I took using the White Balance eyedropper tool, and selecing an area on a Grey Balance Target. Well, Aperture is doing a horrible job of white balancing the image. With Aperture, I exported the image to Photoshop and white balanced it using levels.
You can see the side by side images here along with the corresponding RGB values. The image on the left, is the one that Aperture "thinks" is white balanced. Since there doesn't seem to be a way to check RGB values within Aperture I can't say what they really are, other than to use OS X's Digital Color Meter, which shows exactly what Photoshop is telling me...the image has a definite blue cast to it.
http://www.johnburdick.us/WhiteBalance.jpg
I don't know if I'm doing something wrong, or if Aperture's white balance function is not working as advertised..
Any suggestions? Has anyone else had these issues?
PowerMac G5 Dual 2.3 4.5Gb RAM Mac OS X (10.4.2)
PowerMac G5 Dual 2.3 Mac OS X (10.4.2)

Apple are being deliberately deceptive on this issue.
I have been to a couple of demo's at their store and watched the demonstrator use the same wedding photo each time to highlight the power of the white balance eye-dropper. I think this is the only photo on the face of the earth to give a half-way decent result from the eye-dropper (and even then it's still a little blue).
When I cornered the demonstrator on this specific issue he tried to use another image (one of the Tibet portraits) and the results were horrible and he was forced to concede that this tool was lousy.
I simply don't believe the software developers weren't aware of the shortcomings of this and yet they still decided to release and insult their customers with it.
But this is a minor issue compared with the overall quality of the images coming out of the RAW adjustments.
I can't understand why photographers are still fighting to make this application work. Sure, as a image selection/management tool it's very nice but beyond that it's garbage.
I've returned my copy to the Apple Store where I purchased it and received a full refund thankfully.

Lightroom 4: Massive BUG with White Balance / Quick Develop. Totally Unreliable!

I just recently updated from LR3 and just now found a massive bug concerning the white balance adjustments in the quick develop module.
After a studio shooting and especially after weddings I use the "make warmer" adjustment in the quick develop panel to give all (a few thousand NEFs) a nicer look all at once.
The great thing about this is - like all quick developments - that it increases the color temperature relative to each image's starting white balance.
Yesterday I wanted to edit my first wedding in LR4 and like in LR3 applied one click "make warmer" to all images at once (previously WB was "as shot").
While I browsed through the images to rate them I noticed some of them were very "pinkish".
After closer inspection it came out that a lot of images (50%-60%) had the following custom WB set: 5316, Tint: +10.
It is always this exact combination no matter what the "as shot" WB was.
That setting of course applies way too much magenta to a lot of images.
After resetting the WB of single images to "as shot" and selecting "make warmer" once again the images look fine and get appropriate WB values.
But every time I select more than one image to apply "make warmer" a lot of them get the strange value of 5316 and +10.
Sometimes it's even just the first few images of the selection that get correct values and all the following ones get the off value. It appears to be totally random.
I tried completely resetting all images prior to "make warmer", setting them to different camera profiles first and even switched them to Process 2010 again. But absolutely no luck! :-(
The "make warmer" tool gives me totally unusable results.
I find it strange, that I couldn't find anything about that on the net.
PLEASE fix this ASAP.
To apply WB to thousands of images individually is a real pain.
I would be glad to support you fixing the issue.
My setup:
Nikon D700
Nikon D300s
(Both cameras affected, I only shoot NEF)
Win7 x64
LR4.1 as well as LR4.2 RC

@ssprengel
I get your point but that is exactly my problem.
Not only is there no pattern but also once I reset a file that got 5316+10 to "as shot" and select "make warmer" for it again it does get the correct value! As long as I select it as a single file without others.
So just to simplify my findings and explain what I have been doing all night:
- SELECT 5 files in Library View (all freshly imported, no settings altered, WB "as shot")
File 1: 5700 / -8
File 2: 5500 / -8
File 3: 5550 / -8
File 4: 5450 / -6
File 5: 5500 / -7
- CLICK "make warmer" once
Result:
File 1: 6089 / -8
File 2: 5867 / -8
File 3: 5316 / +10
File 4: 5316 / +10
File 5: 5316 / +10
1 and 2 are okay!
- SELECT 3-5
- RESET THEM
Result:
File 3: 5550 / -8
File 4: 5450 / -6
File 5: 5500 / -7
- CLICK "make warmer" again
Result:
File 3: 5316 / +10
File 4: 5812 / -6
File 5: 5867 / -7
File 4 and 5 are okay!
- SELECT File 3 again
- RESET IT
- CLICK "make warmer"
Result:
File 3: 5923 / -8
now File 3 is okay, too.
It is completely random!
But that is no way to work, of course.
I have two weddings from last week and am going nuts already.

FF_5 - Issue with Account Balance option while processing BAI file

Hi All,
We are getting a runtime error while trying to process the same bank file again through transaction FF_5 with 'Account balance' option checked. And the message says 'The ABAP/4 Open SQL array insert results in duplicate database records.' with the command 'Insert_FEBPI'. This happens only when we have combination of uploaded and not uploaded statements in the bank file.
I could find a OSS note for the same issue but that was for the file format MT942. We are using BAI file format. Can some one please help me in this regard.
Thanks in advance!
Regards,
Jalendhar

This is standard SAP functionality. If there are no applicable notes, then you should open an OSS message.
Rob

Since update to 3.5 issues with white balance

Similar Messages

Maybe you are looking for