Jump to content

A-6000 firmware issue ???


Recommended Posts

I'm really hoping Sony assigned someone to regularly check

this forum. This glitch involves something that they would not

ever have thought to check, but in real use, it's a problem. 

  

The MR [memory recall] mode on the A-6000 is very useful.

 

Like many users, I use "back button AF' meaning I've moved

the AF activation OFF of the shutter button and assigned it

to a button on the rear of the body [AEL in my case].

  

Like many users, I go thru batteries like madness. Yes, you

can shoot hundreds of frames on one battery, if you avoid

using going into the menus, checking sharpness with the

playback magnifiers, etc etc.

   

THE GLITCH:  

  

If you change a battery while in MR mode, upon inserting a

new one and switching on the camera, the "AF by shutter

button" will reactivate itself. 

    

DETAILS: 

   

I've checked my procedure very thoroughly. The glitch is

tied to the mode dial "MR" setting when powering up after

a battery swap. IOW, even if the dead battery is removed in

MR mode, and a new one is inserted, IF you switch OUT of

MR mode before power up, the "AF by shutter button" will

NOT reactivate itself. Switching back into MR mode at this  

point is OK, it will not reactivate AF by shutter button. It's

all about the mode dial setting at the moment of powering

on the camera [and only after a battery swap out].

    

Using rear button AF is not rare amongst users, nor is it

rare to go thru batteries quickly. No problem with those

two user habits in combination. But two's company and

three's a crowd. Add a 3rd user habit that happens to be

favoring the MR mode, and now you hit the glitch. I don't

really know if MR mode is popular or I'm one of very few

using it ... so I don't know how much the glitch matters in

The Big Picture to Sony. But clearly this is not something

Sony would have ignored had it been encountered during

development. But it's perfectly understandable that they

never happened to test the result of this sequence of user

operations as it impacts the many custom functions a user

might have engaged. But back button AF is a commonly  

engaged custom function, so I hope this gets addressed. 

  

 

`

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...