70D bounce flash

Hi,
Recently I upgraded my 650D to the 70D and I noticed that the pictures are a lot darker (underexposed) when bouncing the flash. I have tested this with several other cameras, the 600D, 650D and the 700D using the 430EXII and 580EX all with the 18-135 STM. All but the 70D resulted in acceptable exposure.
Is there a setting I am missing? I used both the [A+] and P setting.

What the OP is seeing is a fairly well documented problem at this point.  I believe the problem is a bug/defect with most (if not all) 70D's.  I'm hoping Canon will be able to address this problem via a firmware update.
The problem has been documented in several threads:
http://www.dpreview.com/forums/thread/3591509
http://photography-on-the.net/forum/showthread.php?t=1347702
http://www.dpreview.com/forums/post/52625732
In two of those threads I've posted some results of testing I did measuring the flash output with a light sensor and oscilloscope.  I believe those results are fairly conclusive that there is a defect/bug with the 70D.
I'll repost my results from that testing here for anyone interested...
Test setup:
Used tripod in fixed location
Results taken from 70D and Xsi
In all cases, only the body was swapped out. Used same lens/flash between camera bodies
All shots taken in Manual mode, 1/100 shutter, f5.6, iso-800
I did not touch ANY settings during the whole shoot (except for FEC on the 70D on one shot per focal length...see more explanation below)
I enabled an option on my scope to capture at 56Mpts memory depth. With this increased depth, I was able to capture enough data in a single capture to show both the pre-flash and also the real flash and still be able to zoom into each flash event with enough fidelity left to show an accurate measurement.
Attached image explanation:
For the three attached images, there are three rows each.
Top row is 70D, second row is Xsi, third row is 70D...same config but I took multiple shots adjusting the FEC until the flash output was nearly identical to the flash output from the Xsi.
First column is a scope capture showing the pre-flash, followed by the real flash.
Second column is still from the same capture of both flashes in column 1, but zoomed into the pre-flash
Third column is still from the same capture of both flashes in column 1, but zoomed into the 'real' exposing flash
Fourth column is the picture correlating to the scope data captured.
Conclusions so far:
There is almost NO DOUBT a defect/bug with at least some 70D's.
I don't believe there is any timing problems...the under-exposure simply is from the camera telling the flash to output a lower level than it should.
The 50mm data from the 18-135mm vs from the 50mm f1.8 is VERY interesting. With all settings identical and just swapping the lens...exposure between the two lenses should be nearly identical. This right here is one of the reasons I think we can confidently claim that this problem is NOT user error, nor claim the camera is doing what its supposed to and trying to save highlights. The camera is clearly NOT doing what it should be doing when the 18-135mm lens (or other slower max aperture lenses are attached).
The problem is definitely related to max aperture. I really want to test a non-canon slow lens to see if it does the same thing or if its only applicable to canon lenses.
Pre-flash output looks normal for both cameras.
In the first attached image (18-135mm lens @ 135mm), I had to dial in +2-1/3 FEC on the 70D in the third row to match the flash output of the Xsi (resulting in nearly identical exposure).
In the second attached image (18-135mm lens @ 50mm), I had to dial in +2.0 FEC on the 70D in the third row to match the flash output of the Xsi (resulting in nearly identical exposure).
In the third attached image (50mm f1.8 lens @ 50mm), I had to dial in +0.0 FEC on the 70D in the third row to match the flash output of the Xsi (resulting in nearly identical exposure).
Images are fairly large to show all columns/rows/data. I've included links in the summary below so you can download the original size pictures. You probably want to view original size to see all details accurately.
Please let me know if anyone can think of additional testing I can do with a scope to further define the parameters of this defect/bug...
Attached file summary (also links to full resolution pics):
18-135mm lens, @135mm, +2-1/3 FEC needed on 70D in third row to match Xsi
18-135mm lens, @50mm, +2.0 FEC needed on 70D in third row to match Xsi
50mm f1.8 lens, @50mm, +0.0 FEC needed on 70D in third row to match Xsi
Picture #1
Picture #2
Picture #3

Similar Messages

  • Updated my iphone 3gs to the ios4.3.5. Now the mail application doesn't function properly. App doesn't sync mail from server - deleting mail hardly works now. When the phone downloads messages from the mail server, it bounces/flashes between accounts too

    I recently upgraded to Lion and then updated my iphone to iOS 4.3.5. Now my mail app on the phone seems all messed up. When I check mail, it pulls down mail from the server but I have to go into each individual account to make that happen but even then the view automatically bounces from one mail account to another but never to the Microsoft Exchange server. It also doesn't let me delete mail

    I have wasted much time trying different combinations to have push and gmail "send mail as". I guess I have tried so much because it seems like a no brainer.
    If you set up as exchange you can at least add in the extra comma and address, but it disappears when you go to send an email.
    very frustrating indeed. my solution is to use the gmail app for notifications of new email.

  • Lightroom 5.4 won't tether to Canon EOS 70D

    Lightroom 5.4 won't tether to my Canon EOS 70D - Keeps flashing "no camera detected" to "Canon EOS 70D". So it must see the camera, but I can't access it. Adobe shows the 70D was supported in version 5.2. I can transfer images fine from the camera, but not tether it.

    There are people waiting for tethering support for the slightly higher-end Nikon D610 for a similar amount of time.  It’s almost as if Adobe postpones releasing tethering support until they are not busy with other things or there are enough new cameras to warrant the effort and then they catch up.  I’m sure tethering is not easy to get to work, sometimes, and there is both PC and Macs to worry about.
    Another issue, besides having to wait for the manufacturer to release their SDK which usually doesn’t happen for several months after a new camera is for sale, is that sometimes older models of cameras are dropped from support when newer models are added to the SDK, so perhaps Adobe also delays support for new cameras due to people, perhaps Adobe employees or internal beta testers, still using older ones.  Or maybe it is a simple matter of priority and the number of people affected by bugs is more than the number of people affected by not tethering a particular model of camera.

  • Flash Exposure Bracketing T3i

    Hi, I am new to Canon and this is my first post.  I just got the T3i and believe it is not possible to do FEB with the built in flash.  Am I correct on that?  The direction to do that is with an external speedlite flash.  Which Speedlite model does FEB, and works best with the T3i?  Plus I like to use bounce flash too.
    Thanks
    CX

    Copperxray,
    I am sorry, but FEB is not available when using the built-in flash.  You will need to use an external Speedlite flash, such as the Speedlite 600EX-RT or the Speedlite 430EX II.  Both of these allow you to do bounch flash as well.
    If this is a time sensitive-matter, additional support options are available at Contact Us.
    Did this answer your question? Please click the Accept as Solution button so that others may find the answer as well.

  • Downloading Flash Player for Vista

    I've been trying to play MindJolt Games, which I have done in the past. Unfortunately it now keeps asking me to download latest FlashPlayer which I have done - 20 times! Still no joy. My system is Vista.

    Hello,
    Welcome to Adobe Forums.
    Which browser are you using ?
    Do you see bouncing Flash logo here : http://www.adobe.com/software/flash/about
    Thanks,
    Vikram

  • How to fix flash reflecting off of wall in background?

    I'm trying to remove the flash bouncing off of the back wall of an image. When I try brushing over it and lowering its highlights / exposure it just turns a mucky grey. Not sure how to proceed. Help!

    Flash reflecting off the background is one of those gotchas that is difficult to fix. For me, it's even difficult to do it in Photoshop. The real key is to use bounce flash, or angle yourself so that you're not shooting directly against the background. Easy to say after-the-fact, I know. I tried fixing a photo of my daughter and granddaughters that had a glaring reflection from the wall. I tried several different approaches that ended up looking worse than the reflection. But then, I'm not a real "high end" photo finisher when it comes to those types of problems.

  • Canon 5d2 DNG +custom profiles = bad preview in Bridge?

    I'm using DNG Profile Editor (1.0.0.39 Beta 2) to make custom profiles for my new Canon 5D Mark II, and then using DNG Converter (5.2) plus Photoshop CS3 Bridge to process images. All on Windows XP.
    After my 5D2 custom profiles were in place I noticed that the image preview in Bridge CS3 was "bad." The Bridge preview is very blurry and does not update when changes are made to the DNG file via ACR. For example, if I change exposure in ACR and click "Done" or "Open in Photoshop, the change is saved OK in the DNG file but the Bridge preview remains the original blurry image.
    Took a long time to figure this out because I did not immediately associate the problem with the creation of custom profiles. Older 5D2 DNG files previewed OK in Bridge, as did DNG files from my other cameras. I even re-converted some old camera raw files to DNG and they previewed OK in Bridge. There are custom profiles in place for those older cameras.
    I spent a lot of time on the usual suspects - purging cache, reseting preferences. All to no avail. Then I removed all my custom profiles and deleted the index.dat file. Ran DNG converter again to make new DNG files from the 5D2 raw. Now the Bridge preview was OK. Then I restored my custom profiles and converted raw to DNG again, getting bad Bridge previews again. Yet the previous converted files would still preview OK in Bridge.
    My conclusion: The DNG converter is using camera profiles during the conversion, and in the case of 5D Mark II raw files is creating an error. I'm guessing it is putting an embedded jpeg in the DNG file that somehow confuses Bridge.
    I've repeated the tests many times now. I've changed the DNG Converter "jpeg preview" preference to none, medium and full. For the 5D2 files I get bad Bridge previews on all settings. But I get good Bridge previews on my Canon 20D and Canon 1Ds DNG files regardless of any settings. Regardless of the presence or absence of custom profiles, regardless of the jpeg preview size, regardless of the ACR default settings.
    So I'm hoping the Adobe team can take a look at this. Or anyone willing to confirm or deny my tests. I don't have an easy way to post a DNG file, but could email one of my "bad" ones to anyone willing to take a look.

    The lack of response to this post forced me to keep testing. Now I've more closely pinpointed the problem and found an easy work around. First some background.
    ACR camera profiles are stored in two places. The Adobe supplied profiles are in:
    C:\Documents and Settings\All Users\Application Data\Adobe\CameraRaw\CameraProfiles
    and your custom profiles are in:
    C:\Documents and Settings\yourusername\Application Data\Adobe\CameraRaw\CameraProfiles
    Adobe Camera Raw, and it turns out the DNG Converter, both build an Index.dat file in this last folder. Apparently this index is built by scanning both camera profile directory trees and building a list of all the profiles it finds. It then sorts that list alphabetically by the profile name that is embedded in the file, not the Windows file name.
    The "Adobe Standard" profile for a camera has a file name like "Canon EOS 5D Mark II Adobe Standard.dcp", but embedded in that file is the profile name of just "Adobe Standard". That's why only "Adobe Standard" shows up in the drop down list of profiles in ACR. And that's why "Adobe Standard" appears before "Camera Faithful", which appears before "Camera Landscape". It's alphabetical order.
    Now, when you create a custom profile with the DNG Profile Editor, the "Export" function puts "Canon EOS 5D Mark II" on the front of the name. If you are an idiot, like me, you type over all that with something simple like "5D2 Bouce Flash" for the profile name. But wait, "5D2 Bounce Flash" sorts alphabetically before "Adobe Standard" and appears first in the ACR drop down menu. Sounds OK so far.
    But then the magic occurs. The DNG converter uses the camera profiles. It actually accesses that Index.dat file, and if it does not exist, the DNG converter will rebuild it, just like ACR. Why it does that I can't imagine. Seems to me that the DNG converter should be simply converting raw to DNG and passing the EXIF and embedded camera jpeg along as is. What need does it have for camera profiles?
    Anyhow, if that 5D2 profile is first in the list due to its alpahbetical name, the resulting DNG file will confuse Bridge. Bridge will display a fuzzy preview and will never update that preview, or the thumbnail, when you make adjustments in ACR.
    But if you name the 5D2 custom profile such that it sorts alphabetically after "Adobe Standard", then all is OK. The DNG files can be previewed and thumbed OK by Bridge. So I named my custom profile "My 5D2 Bounce Flash", a simple workaround.
    Now I can move on to more important things. Like generating a good custom profile for the 5D2. So far the Adobe Standard profile beats anything I've generated. Especailly if I remove that curious Point Curve which can sometimes muck up the shadows.
    And now that Bridge previews are "OK" I can work on the mystery of why Bridge Previews of 5D2 DNG files do not match the previews of their equivalent TIF or PSD files. If you're curious you can see samples and read more about that here: http://forums.dpreview.com/forums/read.asp?forum=1032&message=30748423

  • White Balance not working

    I'm using Aperture 3.2.2 and when I use the white balance 'pipette' tool to select neutral grey area no changes are applied.  I think I know how this tool works as I have used it in the past.  The image I am trying to adjust I also know needs adjusting as it was shot using bounced flash off an cream surface.  Of course I can manually change the white balance using the temperature and tint sliders but have found better results in the past using the select neutral grey.
    Anyone else having this issue and know of a fix?

    Is it only on certain images that the white balance pipette tool does not work, or is it a general problem?
    If it does not work on any images, delete the Aperture Preference files, as described in
         Aperture 3: Troubleshooting Basics: http://support.apple.com/kb/HT3805
    for sometimes user interface elements do not work, when preference files are corrupted.
    If only some images cannot be adjusted, then try the library "first aid": repairing permissions and library.
    Regards
    Léonie

  • Aperture vs....

    Hello All-
    I recently purchased a Canon 5D Mk II as I quit my job and am going to take a year off to travel and enjoy life. I have been trying to decide whether to edit my photos in LR or Aperture. I have been using both programs for a couple of weeks and a few days ago decided to go with Aperture 3 as I am an Apple loyalist, I use FCP HD, had my 1st Apple computer in 1980, blah, blah, blah....
    So now I shoot some pictures last night where the white balance is horribly screwed up (I shoot in fully Manual mode and save RAW files only). Try as I might to find a neutral gray in the photos I was having a very difficult time. So I decided to open the image in Camera Raw, I do the Auto White Balance and it comes up with a temperature of 2840 degrees. The picture looks significantly better. Then I take the same photo into Photoshop CS4 and use a method I read about online for trying to find neutral where you add a layer at 50% Gray, Blend to difference, Add a threshold, etc....
    I did all that to find a spot in the photo that Photoshop tells me is neutral gray. I go to my image in Aperture and use the eyedropper from the White Balance brick and click it in the area Photoshop showed me was neutral and the picture adjusted to 2795 degrees - pretty close to the Auto setting Camera Raw came up with WITH A SINGLE CLICK.
    Now my question. Why would I use aperture when in LR2, Camera RAW and Photoshop I have all these tools to help me get White Balance corrected? In Aperture I could have just clicked, clicked, clicked and clicked until I got something close and then tweaked it. Fine for ONE image but what if you have 20-30-40 images to go through? Am I missing something in Aperture 3? Surely getting White Balance in Camera Raw and LR2 can't be that much easier than in Aperture 3 can it? White Balance is one of the quickest ways to improve the look/quality of your photograph so why is Aperture making it so much more difficult for me to get it right than these other programs?
    I really want to use Aperture 3 but if I have to take every photo with bad White Balance into Camera Raw and/or Photoshop seems like I am using the wrong program, no? I look forward to reading your help/response(s).
    All the Best....

    I don't know the details of the algorithms used for an auto white balance tool, but basically the program adjusts the color temperature to produce even RGB numbers at a given spot - thus it will work on black (which should be 0,0,0; white 255,255,255; or grey - you get the idea.
    Remember, if it should be grey, and it IS grey, then your white balance is correct. So, if you photograph a grey card, look at it. Is it grey, or does it have a color cast. If it is grey, then clicking on it will produce little change. If it has a color cast, then clicking on it should produce a correction - that is, your grey card will become more grey.
    Click on something that is green, for example, and you will get a wild red/yellow shift, click blue, you will get red, etc.
    See also: Click on the Tint droppers. This tends to be most useful when cleaning up a really bad image, for example, an aged slide. Find something that should be black, something that should be white, and finally something grey. This can go a long way to eliminating color casts etc.
    For what it is worth, the white balance right out of my Nikon D200 rarely needs any work unless it is a hard exposure - bounce flash off a green ceiling with fluorescent lighting. And sometimes in these cases it is simply better to adjust with the Mark One Eyeball. Start will wild swings of the sliders and work your way ever closer. (I was given a nice set of plastic cards, but I confess that I have not used them that much. Again, they are most useful in mixed or otherwise difficult light.)
    Hope this is helpful.

  • Canon 5D Mark II profiling experience?

    I've had very good past experience using the DNG Profile Editor to generate profiles for a Canon 1Ds, 20D, and 40D. Now I have a new 5D Mark II, and the first profiling attempts have been poor. The Adobe Standard and Camera Standard profiles for the 5D Mark II seem much better than my custom profiles.
    My profiles are making much darker blues, much lighter and desaturated reds, and some strange yellows. I'm plagued by blowing snow and dark gray skies now, so finding good light to shoot the MacBeth color checker is a challenge. Thus my initial attempts have been indoors with incadescents, bounce flash, and studio strobes.
    Looking for others with the 5D MarkII who have profiled. What is your experience?

    I have not seen any issues profiling the 5D II.
    Make sure you are not getting flare or non-uniform color casts while shooting the target.

  • NEF Nikon D5100 - displaying too dark in LR

    I just bought a Nikon D5100.
    While importing the NEF files, LR firstly shows the images with the correct exposition (equal to the ones previewed in camera), then two seconds after (after fully rendering the image) LR darkens the images, so that they seem underexposed by 1 or  2 stops.
    I was using LR 3.4, then I updated to 3.5 and later on to 3.6 and in every version the same happened.
    The same pictures viewed in ViewNX2 appear with the correct parameters. So, I believe that LR does not read the camera adjustments?
    The JPG images are also shown with the correct parameters.
    Does anyone know how to solve this problem?
    Thank you.

    Using ExifTool to examine the shooting parameters of each example photos posted, here, it appears that both the Exposure and the Flash were set to Manual mode; hence the term to “operator influenced” because the camera was doing what it was told by the operator rather than using its own metering.  Exposure Compensation only has an effect if camera metering is controlling the exposure.  In M mode, the value is merely being recorded but not utilized.
    The Flash-related info for DSC_0074, paying special attention to the power being only 1%, is:
    Flash                           : On, Return not detected
    Flash Setting                   : Normal
    Flash Type                      : Optional,M
    Flash Exposure Compensation     : 0
    External Flash Exposure Comp    : 0
    Flash Exposure Bracket Value    : 0.0
    Flash Mode                      : Fired, External
    Flash Info Version              : 0104
    Flash Source                    : External
    External Flash Firmware         : 6.01 (Unknown model)
    External Flash Flags            : Fired, Dome Diffuser,
    Flash Commander Mode            : Off
    Flash Control Mode              : Manual
    Flash Output                    : 1%
    Flash Focal Length              : 14 mm
    Flash GN Distance               : n/a
    Flash Color Filter              : None
    And the Flash-related info for DSC_0115 is:
    Flash                           : On, Return not detected
    Flash Setting                   : Normal
    Flash Type                      : Optional,M
    Flash Exposure Compensation     : 0
    External Flash Exposure Comp    : 0
    Flash Exposure Bracket Value    : 0.0
    Flash Mode                      : Fired, External
    Flash Info Version              : 0104
    Flash Source                    : External
    External Flash Firmware         : 6.01 (Unknown model)
    External Flash Flags            : Fired, Bounce Flash
    Flash Commander Mode            : Off
    Flash Control Mode              : Manual
    Flash Output                    : 12%
    Flash Focal Length              : 50 mm
    Flash GN Distance               : n/a
    Flash Color Filter              : None
    For reference, ExifTool can be downloaded from:
    http://www.sno.phy.queensu.ca/~phil/exiftool/
    and can be used by dragging and dropping an image file onto the EXE that is renamed exiftool(-k).exe
    For a friendlier interface, something like ExifGUI can be used:
    http://u88.n24.queensu.ca/~bogdan/
    In summary, if the EXIF information is to be believed, these images are dark because the camera was being told to shoot with settings to dark for the other lighting.  Does this sound right, or did you use the camera and/or the flash in TTL mode, which should have allowed the camera and/or flash to make things bright enough with more motion or focus blur as the shutter became slower or the aperture became wider.

  • Equalizing photos with similar content but different exposures

    PSE7
    Greetings,
    I asked this in the Elements forum with no resoultion.  If it can be done I may have to go out and buy the full photoshop.
    Background:
    I have a group of photos that are very similar.  They are posed graduation photos where the camera and background do not move.  Only the subject , who wear very similar robes, changes.  The exposure of my D-70 with a bounced flash wound up being eratic with some good subject expressions being captured under existing light conditions and dramatically underexposed because the flash didn't fire (took the pixs too fast and the flash didn't recharge fast enough).
    The question:
    Is there a way in photoshop to take a group of very similar photos that vary in exposure, color tone, etc.,
    then select one master photo from the group that has the exposure, color tone, etc. that I want,
    and then batch process all the photographs so that all of the photos are changed to match the exposure, color tone, etc. of the master photo I picked???
    Another way of saying it, How do I make the common background of each photos above identical in one step (or as few as I can)???
    Thanks..

    don't know about Elements but in Photoshop i suppose that you could maybe use Image->Adjustments->Match Color in an action but it's a fake so don't expect miracles from it. Another way would be to just open them all in Camera Raw and apply the Auto setting to them but that won't correct the images based on a base image

  • PSE 8 Tutorials Not Playing

    Attempted to play one of the PSE 8 tutorials by Jan Kibili (sic) under the "help" section of the toolbar.  Title and subject came up but the video would not play.  Logged into Adobe TV and still wouldn't play.  With PSE 9 out, did Adobe delete these tutorials or do I need to update something else on my PC (Windows XP)?
    Marion

    Hi Colin,
    Does the bouncing flash cube video before the advertisement play for you here?
    http://www.adobe.com/software/flash/about/
    What version of flash does it show you have?
    Does the same thing happen in other browsers other than Chrome?
    -Dave

  • I have an iPhone 4S-whenever I take a picture using the flash, all I get is a white blob-pictures without the flash are fine.  I tried using different cases, thinking a bounce off the case might be the problem, but the same thing happens.  Any suggestions

    I have an iphone 4s - whenever I take a picture using the flash, all I get is a white "blob".  Pictures without the flash are fine.  I thought the flash bouncing off the case might be the problem, but when I used different cases I still had the same problem.  Any suggestions?

    I have an iphone 4s - whenever I take a picture using the flash, all I get is a white "blob".  Pictures without the flash are fine.  I thought the flash bouncing off the case might be the problem, but when I used different cases I still had the same problem.  Any suggestions?

  • Canon Flash 430EX 11 to go with my Canon EOS 70D camera with an 18-135mm lens.

    I purchased a Canon Flash 430EX 11 to go with my Canon EOS 70D camera with an 18-135mm lens. The flash displays the icon confirming auto zoom only intermittenly and when it doesn't, twisting the camera zoom does not display on the flash screen.  All batteries are charged and the flash is locked on to the camera.
    Solved!
    Go to Solution.

    I'm not entirely certain I understand your question.  The 430EX II has can be put in a mode where it automatically follows the camera zoom (within limits... 24mm to 105mm) but you can ALSO put it into a mode where you manually control the flash zoom.  If it's in the manual control mode then it will not automatically zoom.
    It is important that the "wide" panel NOT be in-use (if you pull out and flip down the wide-panel then the flash will go to wide angle and will not zoom EVEN if it was in auto mode.)
    Press the Zoom button, then use the - / + buttons to change the zoom.  
    When under manual control there's a black "M" icon which will appear next the word "Zoom".  If the "M" is not present then it's in auto zoom mode.
    Lastly... when you change the zoom on the camera lens, typically nothing will happen on the flash UNTIL you wake the system by doing a half-press of the shutter button.    When the camera wakes up to meter and focus... that's when it adjusts the zoom on the flash head.
    Tim Campbell
    5D II, 5D III, 60Da

Maybe you are looking for