November 27, 2014, 06:01:23 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - East Wind Photography

Pages: 1 2 3 [4] 5 6 ... 52
46
EOS Bodies - For Stills / Re: 7D Mark II Reported Issues
« on: November 12, 2014, 07:53:08 AM »
If we are talking issues this happened to me this weekend while shooting high school football... I set up my back AF-ON button in the custom config to be AF-OFF instead. So I "half press" shutter button to acquire focus, lock focus with back button while maintaining half press. I noticed that if I shoot a sequence of frames and pause but still maintain half press, then try to press again there is no response from the 7DII - no pictures taken. This resulted in missed shots! I had to physically lift up the shutter button completely in order to take more shots(with the back button completely pressed the whole time). Now I was also using a 300mm L IS at the time and tried using the dedicated defaulted AF-OFF buttons on the lens (instead of back button on the camera) to do the same situation described, and it worked as expected... So has anyone else experienced this issue?  I would think this has to be a bug and hopefully fixed in the next firmware update?  Or is there something I am doing wrong or a hidden setting to allow what I want.  I know the first generation 7d did not have this problem... I used this technique quite often.

I will check this tonight and see if I can reproduce that.  I wonder if it's specific to the big whites or does the same thing with other lenses?

I believe this was happening to me on the 7DII along with a 70-200 L is II as well.  However there is not a dedicated AF-OFF button on the lens hence why I configure the back button for this purpose. Also I usually configure both the back "AF-ON" button and the "*" to be AF-OFF so as a "miss aligned push" will yield what I want :D  It didn't matter what button here I configured for this technique, the outcome of "no response from 7DII" still occurred.
Also I did send this issue to Canon right before posting here, via the Canon website ;)

Just wanted to describe my findings on this issue that I am having, if anyone else is running into this, or following...  After 5 emails back and forth from Canon, asking to reset everything and take battery out for 5 minutes and try again... they came to the conclusion that this is how it is designed on the 7dII.  Frustrated since this works on the original 7D, I went back to the 7DII and tried again paying close attention as to what I was doing.  It turns out I was wrong about my comment that it works with the "dedicated AF-OFF button" on the 300mm L is lens.  It is the same as with the  70-200 L is II.  Here is what I found:  If you push any "AF-OFF button" configured(either on the lens body or a custom configured back button) BEFORE pushing the shutter button, multiple volleys of frames taken, with a pause in-between, from the "half pressed state" to "shutter release" works.  Now if you press the shutter button first to "half press" and then push any "AF-OFF button" configured, the first initial volleys of frames taken will work, but the second and subsequent presses from the "half pressed state" to shutter release will produce no pictures taken - unresponsive 7DII.  One might think that I am anal about this :o... But it was very frustrating when you are out in the field trying to figure out why the camera won't take pictures, granted in this weird set up state :)  So in the process of figuring out this issue I noticed a new button custom config that I can use on custom back button that solves my issue even better than the original 7D... it is the "*AF-OFF" customization. This locks metering and AF!  So the continual "half press" is not needed anymore....  But if I am am shooting a football game and I am using both the 7dII and 7D,  I am going to get confused while trying to use this technique... But the price you pay for an awesome camera ;)

I've found that sometimes you dont get the resolution you want or expect over the phone or by email.  I had a similar experience a while back but rest assured the report is in and it will work its way up to development where the firmware guys will taks a look at it.  IT could get fixed if its fixable...just have to deal with it for a bit.

47
EOS Bodies - For Stills / Re: 7D Mark II Reported Issues
« on: November 11, 2014, 10:16:15 PM »
Another issue that can slow down AF is the use of Spot AF.  Canon used to warn about that.

Yes I considered that but found the lag in all AF modes.  I was performing a AFMA on my 24 1.2 II last night and I did not see the lag as I did on the 300.  I will try my 70-200 today and my 600 tomorrow (Need to find a vacant football field)

I used the 7d2 today pretty extensively with my 600 F4L and I did not have any AF lag in any of the AF modes or other combos.  I ran into some conditions where the Zone AF would not pick up a heron in flight...just wouldnt get a lock but with center and spot AF I did not have any issues.  Could have been my AF case though I was messing around with tracking sensitivity to ignore some tree limbs that were in my way.  I'll test that more to see if it happens again.

I also tested last night with the 70-200 F2.8L II and saw no lag.

So now I'm scratching my head a bit and now need to go back and reproduce the issue with the 300 2.8L II.

Just to keep it all real, I'm really liking the 7D2.  Getting some really nice images for a crop sensor.  Though DPP is really annoying, I can live with it until the other raw processors get up to speed.

I'll actually add one more thing about ZOne AF.  On the 5D3 the zone AF would lock onto the closest thing within the zone range (great for BIF).  I'm noticing that on the 7D2 that's not always the case.  I'm not sure if it's color or contrast sensitivity that is different but it seems to operate a bit differently than the 5D3.  In one sequence I was tracking an eagle and the zone AF appeared to be locked onto the eagle as the active AF point would track the eagle but the images all focused on the background and not the eagle.  I had a similar issue with a heron.

Zone AF worked fine the other day when I was shooting a soccer game so not sure what is happening.

Other modes seem to work just fine.

Trying to find out of Canon changed the algorithm for zone AF in this model.


48
EOS Bodies - For Stills / Re: 7D Mark II Reported Issues
« on: November 11, 2014, 10:08:46 PM »
Another issue that can slow down AF is the use of Spot AF.  Canon used to warn about that.

Yes I considered that but found the lag in all AF modes.  I was performing a AFMA on my 24 1.2 II last night and I did not see the lag as I did on the 300.  I will try my 70-200 today and my 600 tomorrow (Need to find a vacant football field)

I used the 7d2 today pretty extensively with my 600 F4L and I did not have any AF lag in any of the AF modes or other combos.  I ran into some conditions where the Zone AF would not pick up a heron in flight...just wouldnt get a lock but with center and spot AF I did not have any issues.  Could have been my AF case though I was messing around with tracking sensitivity to ignore some tree limbs that were in my way.  I'll test that more to see if it happens again.

I also tested last night with the 70-200 F2.8L II and saw no lag.

So now I'm scratching my head a bit and now need to go back and reproduce the issue with the 300 2.8L II.

Just to keep it all real, I'm really liking the 7D2.  Getting some really nice images for a crop sensor.  Though DPP is really annoying, I can live with it until the other raw processors get up to speed.


49
EOS Bodies - For Stills / Re: 7D Mark II Reported Issues
« on: November 10, 2014, 08:33:37 PM »
Given the number of ways that the AF buttons and controls can be custom configured it's easy to imagine that Canon could have overlooked some combination of body and lens configs that results in a bug. Hate it when companies use paying customers for Beta testers but that's just what they do. Sounds like reporting and requesting a fix is the best option. If that's the way you want your gear set up you should be able to do it.

As to the larger issue of overall AF effectiveness, I was at a local Bald Eagle hotspot today where hundreds of photographers congregate. I spoke to a number of new 7D2 owners, although I don't specifically recall any of them using the 300 2.8, and all reported to me that they were extremely pleased with the AF functions of the new 7D. Seems as though these issues may result from a fairly specific case. Users I talked to had pretty much all of the other longer tele's as well as 1, 5 and 7 series second bodies. These are a pretty sophisticated group of shooters who aren't afraid to express their opinion. Often even when you aren't particularly interested in their opinion.  ;) However, I can say that on the 7D2's autofocus, sentiment was overwhelmingly positive. As is mine.

Just saying this because with all of the negativity out there, I'd hate to see people get the impression that the 7D2's autofocus isn't effective. I shot a few 20 to 30 frame bursts of flying eagles against complex backgrounds without a single out of focus image and I don't consider myself a particularly advanced BIF shooter.

I'm not trying to minimize your concerns or the seriousness of this issue. In the end, obviously what works for your needs is the only thing that matters.

Most likely we'll here of more issues in the coming weeks as these cameras get into the hands of larger numbers of users. No system of this complexity is ever perfect right out of the gate. Hopefully Canon will get this stuff worked out pretty quickly as they can't really afford to drop the ball on this release. Just my 2 cents, probably worth about what you paid for it. :)

No I agree, I'm not trying to be negative on the AF system.  It is for me very nice and I did not have one game shot that was out of focus except for my error.  I was simply reporting a slight lag in getting an AF lock.. It wasnt hunting it was just a fraction of a second delay before the AF snapped into focus.  Once it locked, the camera went like a bat out of h3ll.

The reason why I started this thread was to share some of the initial issues discovered so that we as a collective can report this issues to Canon so they are aware of a systemic problem or bug.  I havent found anything that would give me pause to return the camera.  THe issue coud very well be my 300mm or its firmware.

I unfortuntely did not have time to test with my other lenses today so will try tomorrow.

50
EOS Bodies - For Stills / Re: 7D Mark II Reported Issues
« on: November 10, 2014, 12:56:04 PM »
"Try turning on the function on that says keep searching when AF impossible.  If the scene is very out of focus apparently the phase difference is larger than the AF sensors can see, so the camera does not know what to do."

I just saw this on another forum...

Yeah I prefer to leave this on so I'm certain this was on when I noticed the issue.  However I will note whether the condition is worse if AF is near or far from actual focus.  I wasnt paying attention to that detail during the game.

51
EOS Bodies - For Stills / Re: 7D Mark II Reported Issues
« on: November 10, 2014, 12:53:12 PM »
If we are talking issues this happened to me this weekend while shooting high school football... I set up my back AF-ON button in the custom config to be AF-OFF instead. So I "half press" shutter button to acquire focus, lock focus with back button while maintaining half press. I noticed that if I shoot a sequence of frames and pause but still maintain half press, then try to press again there is no response from the 7DII - no pictures taken. This resulted in missed shots! I had to physically lift up the shutter button completely in order to take more shots(with the back button completely pressed the whole time). Now I was also using a 300mm L IS at the time and tried using the dedicated defaulted AF-OFF buttons on the lens (instead of back button on the camera) to do the same situation described, and it worked as expected... So has anyone else experienced this issue?  I would think this has to be a bug and hopefully fixed in the next firmware update?  Or is there something I am doing wrong or a hidden setting to allow what I want.  I know the first generation 7d did not have this problem... I used this technique quite often.

I will check this tonight and see if I can reproduce that.  I wonder if it's specific to the big whites or does the same thing with other lenses?


52
EOS Bodies - For Stills / Re: 7D Mark II Reported Issues
« on: November 10, 2014, 12:50:25 PM »
It's important to note here that if you find what you think is a bug, it's nice to get confirmation here that others noticed the same issue.  However you should still report it to Canon with a clear description of how to reproduce it.

They are usually more receptive to fixing things on the first and second firmware update.  After that unless it's a major issue it may not make it in for a while.

53
EOS Bodies - For Stills / Re: 7D Mark II Reported Issues
« on: November 10, 2014, 09:06:26 AM »
Another issue that can slow down AF is the use of Spot AF.  Canon used to warn about that.

Yes I considered that but found the lag in all AF modes.  I was performing a AFMA on my 24 1.2 II last night and I did not see the lag as I did on the 300.  I will try my 70-200 today and my 600 tomorrow (Need to find a vacant football field)


54
EOS Bodies - For Stills / Re: 7D Mark II Reported Issues
« on: November 10, 2014, 09:01:49 AM »
Hi,
    Did you on the GPS?? When the GPS is on, sometime there will be lag on the AF.

   Have a nice day.

No I leave GPS off as that is generally a useless feature to me that sucks battery power even when the camera is turned off.  Not sure why Canon did that.  Maybe have GPS go into sleep mode where it polls every hour instead of on the regular schedule.  Could be something they could fix in firmware.

55
EOS Bodies - For Stills / Re: 7D Mark II Reported Issues
« on: November 09, 2014, 08:07:21 PM »
Thought I would start a thread today for issues noticed with the 7D Mark II.

I will start with one issue I discovered today shooting a Soccer game.  First of all my setup:

7D MKII with 300mm F2.8L IS II [ AFMA +8  :( ]  Ok got that taken care of.  The one issue I noticed is a lag from the time the shutter button is pressed to when the AF locks on.  No hunting just a noticeable lag in acquiring initial focus.  Most may not notice but in sports it can make the difference between getting the shot and not.  This condition does not exist on my 5DIII so it's something specific to the 7DII.

I was using center AF point only (though the condition exists on all of the AF area settings I tried).

Hopefully this is something that can be resolved in a firmware update.  Hopefully someone here may have discovered a setting which minimizes this issue.

You didn't say AI Servo or single shot.
I have been comparing mine to my 1D IV.
Single Shot single point on the big white lenses take longer to confirm. The 1D IV is half again as fast.
It confirms focus similar to the old 7D, it makes focus and for a brief instance reconfirms.
There is no noticeable difference on other lenses.

AI Servo mode I am still working on, I have yet to have a decent lock on a BIF. I have only had a few opportunities to check and I still attribute my failures to lack of proper settings.

At this time I am leaning toward believing the 1D IV is the better AF system.

That does pose an interesting question.  I was using AI Servo during the game.  The AF once it locked was very fast to adapt I rarely had any that were out of focus the entire day that wasnt due to me obviously drifting off target.  The AF is fast but I only have a 5D3 to compare to and so far I would say it's about the same.

The issue is the fraction of a second from when the shutter is half pressed and the lens snaps to focus.  IS and metering kick in instantly but the AF lock lags a fraction of a second.  After it's locked it tracks and performs flawlessly.

I will compare with some other big whites I have and see if it's the same.


56
EOS Bodies - For Stills / Re: 7D Mark II Reported Issues
« on: November 09, 2014, 03:58:44 PM »
Have you checked what settings you have for the Ai Servo 1st Image parameters..setting it to Release Priority will get your first frame in a burst off quickly, alternately, having it set for Focus priority will cause it to take longer before the shutter will release and can delay shooting.  The same settings can be applied to the rest of the images in the burst, in the menu Ai Servo 2nd Image Priority.

These two settings are under the Pink AF menu tab, and the second menu screen, tab 2.  Perhaps set both options to Release and Speed and see if it feels the same.

So this issue is before the shutter fires when you do a half press of the shutter.  Doesn't have anything to do with the priority settings.

57
EOS Bodies - For Stills / Re: 7D Mark II Reported Issues
« on: November 09, 2014, 03:56:28 PM »
I would return the camera and exchange it for another.  It sounds faulty.  See if the new camera has the same issue.

I don't think its faulty though I do need to test with some different lenses to see if it's consistent

58
EOS Bodies - For Stills / 7D Mark II Reported Issues
« on: November 09, 2014, 01:35:59 PM »
Thought I would start a thread today for issues noticed with the 7D Mark II.

I will start with one issue I discovered today shooting a Soccer game.  First of all my setup:

7D MKII with 300mm F2.8L IS II [ AFMA +8  :( ]  Ok got that taken care of.  The one issue I noticed is a lag from the time the shutter button is pressed to when the AF locks on.  No hunting just a noticeable lag in acquiring initial focus.  Most may not notice but in sports it can make the difference between getting the shot and not.  This condition does not exist on my 5DIII so it's something specific to the 7DII.

I was using center AF point only (though the condition exists on all of the AF area settings I tried).

Hopefully this is something that can be resolved in a firmware update.  Hopefully someone here may have discovered a setting which minimizes this issue.


59
Lenses / Re: Introducing the Canon EF 100-400 f/4.5-5.6L IS II
« on: November 08, 2014, 08:22:02 PM »
Crap!  They had to announce this today?  I haven't even paid for the 7d2 yet  ;)
It is next on my purchase list, perhaps in the spring!

Likely not worth the pre-order.  Wait for the test results first.  Most people will just use it a 400 anyway so might as well get the 400 5.6L prime lens.

However I'm not very enchanted with F5.6 lenses as to realize their sharpness, you have to stop them down even more.  Shooting at F7 to F8 really limits what you can shoot and when you can shoot it.

60
EOS Bodies / Re: Focus problems with the Canon 7DII?
« on: November 06, 2014, 11:49:44 PM »
I don't shoot sports, portraits, wildlife and landscapes.

Since you managed to achieve consistent AF using live view and have no need to photograph moving subjects or landscape, I suggest you move to a contrast based AF camera. The A6000 or XT1 or EM1 or GH4 beckons...  ;D
That was a typo, I meant that I shoot only portraits, wildlife and landscapes. I'm not switching brands, I have a big investment in Canon gear.

One other thing.  Many people had simiar issues wwhen the 5diii came out.  Most of the AF issues where due to a lack of understanding how the new advaned AF system works.  Many assumed settings in the older or consumer models are now manual settings in the new models and require one to visit all of the settings to ensure they are set up properly for the task at hand.  Thank god for custom modes on the top dial.  On my 5DIII I have one for birds in flight, one mode for static subjects, and one mode for sports action.  I will likely set up the same for the 7dii once I can get out to do some shooting.

If the complexity of these models is too much then iit may be too much camera for your needs.  I use an EOS-M for shots of my kids as it's quick and easy and does a pretty good job.  No one camera will suit every need until you have mastered all of the settings and fully understand the implications of changing them.

Good luck.  Based on the image posts it looks like AFMA is required.


Pages: 1 2 3 [4] 5 6 ... 52