I think it's a good feature. The camera is not stable after we fully press the 
shutter button. Need 1-2 seconds after that to hold the camera stable for 
better picture especially in low light without tripod. 

Thanks,

german translation for r414

For the version updated weekly to the repository, the changeable colour temp in 
the 400plus menu has no effect on the final image.

I have selected white balance, then pushed the DP button to activate custom K 
white balance, but still no affect on the final image.

Sergei's menu version has immediate effect after changing the value in the menu 
without going to WB then pressing DP, yours doesn't eduperez, even with WB + DP 
button.

All the images come out blue regardless of what Kelvin (colour temp) I set.

Each user has different needs, and as we grow the number of available shortcuts 
and actions, not all will fit inside the shortcuts menu; consequently, some of 
them will not be accessible.

Users should be able to select which shortcuts and actions will be visible in 
the shortcuts menu, and what button will trigger each one.

After applying a preset, when the camera is powered-down and back up, the AE 
mode restored corresponds to the AE mode selected in the main dial, not the AE 
mode set by the preset.

Some scripts (Waving, Timer, and Interval) can execute for extended periods of 
time; but the power-saving feature from the camera may kick-in while one of 
these scripts is running, thus turning the camera off.

Power-saving should be (optionally) disabled while a script is running.

According to the manual, C.Fn-05 (AF-assist beam) can have values 0 (emits), 
1(does not emit), and 2 (only external flash emits).

Code should be reviewed.

The following custom functions are defined but unavailable to the user:

#define EVENT_SET_CF_AEB_SEQUENCE         0x32
#define EVENT_SET_CF_SI_INDICATE          0x33
#define EVENT_SET_CF_MENU_POS             0x34
#define EVENT_SET_CF_FPSEL_METHOD         0x36
#define EVENT_SET_CF_LENS_BUTTON          0x40
#define EVENT_SET_CF_ORIGINAL_EVAL        0x41

Some of them have intriguing names, and could be useful; we should experiment 
with some values and decide whether we incorporate them to our menus.

There is currently no prevision in the scripts to interact with the mirror 
lock-up feature: some scripts (Wave, Timer, Intervalometer) could rise the 
mirror several seconds before taking the picture; others (Extended AEB) 
probably should raise the mirror for the entire duration of the execution.

After about a half dozen shots hand waving crashes while instant and no delay.

You might want to rename it from hand "weaving" in the menu as well

Current 400plus has options to control the flash, both during the AF phase and 
the shooting itself. However, the first case can be controlled with CFn.5, and 
the second one by physically raising / lowering the flash.

These unneeded options should be removed.

Only English is currently used in the menu.

Users should be able to select the language used in the menu.

What steps will reproduce the problem?
1. Turn on Camera
2. Press Menu button
3. Press DISP button
4. Press AF (right) button once.
5. 400plus version number incorrectly shown as 400plus ver.: 99999999

What is the expected output? What do you see instead?

Expected output was version number of 400plus software.
Instead saw 400plus ver.: 99999999

What version of the product are you using? On what operating system?
400plus-20110425-0

Please provide any additional information below.
N/a

The DP button has too many tasks assigned (one for each script, plus one to set 
intermediate ISOs), and the user must select one task (in the menu) prior to 
using the button.

The DP button should display a "menu" (just a read-only list of options) of 
shortcuts; each shortcut will be assigned to a button, and the corresponding 
task will be performed immediately. For example:

[DP] => Display shortcut menu => [UP] => Close menu and start "Extended AEB" 
script

The counter for remaining shots in the card from the main display is used as a 
count-down display, during the execution of scripts. However, if a script is 
interrupted, that counter is not restored.

The counter should be restored.

The current menu front-end is hard on the user, as only one row is displayed at 
a time.

The new menu front-end, developed by Sergei, should be integrated.

If the light conditions change during an EAEB, the camera adjusts the base 
exposure accordingly, and thus the compensated exposure values do not 
correspond to what the user expect.

The EAEB script should "lock" the base exposure at the beginning of its 
execution.

I was just using latest revision and I crashed it hand waving with flash on.
I think my main menu is smaller now with a black edge around it on the lcd 
screen.
I dont remember it having a black boarder before.
Or is this just the first time I am noticing it? 

What steps will reproduce the problem?
1. User installs version x of 400plus.
2. User saves some settings and / or presets to the card.
3. User installs version y > x of 400plus.
4. User cannot load settings or presets from the card.

What is the expected output?
User should be able to load configuration files from previous versions, even if 
new parameters have been added to the settings.

What do you see instead?
Camera acts as if no configuration files exist at all.

Please use labels and text to provide additional information.
We should change to a tag-based model for the configuration files (see TIFF 
specification for an example of what I mean): instead of dumping memory areas, 
we should write pairs of {PARAMETER, VALUE} to the files; this way, we can 
later load that file using more recent version, even if new parameters have 
been added.

When using the Developer menu to select "Enter Factory mode" and then exiting 
the "Developer menu", the standard Canon Settings menu displays a new menu 
choice on Tab1 named "Factory menu" which can be accessed without problem.  
After returning to the "Developer menu" and selecting "Exit Factory mode" and 
then exiting the "Developer menu", the standard Canon Settings menu still 
displays the new menu choice named "Factory menu". Did the camera really exit 
from the Factory menu mode or not?  This is confusing... (also see side note 
below under additional info section).

What steps will reproduce the problem?
=====================================================================
see above details

What is the expected output? What do you see instead?
=====================================================================
"Factory menu" should disappear from standard Canon settings menu after 
selecting "Exit factory mode" from "Developer menu".

What version of the product are you using? On what operating system?
=====================================================================
Release 20110425-0

Please provide any additional information below.
=====================================================================
Interesting side note: Although the "Factory menu" is still displayed in the 
standard Canon settings menu after trying to "Exit factory mode".  If you have 
the camera set to "Auto Power off" and let the LCD display power off during 
that interval - upon returning to the standard Canon settings menu - the 
"Factory menu" choice is no longer displayed?  I also noted that when the 
"Factory menu" is available it is always the highlighted default menu choice 
each time you enter the standard Canon settings menu - regardless of what the 
last menu item selected was...

A miror locking bulb mode for hand waving could be useful to many. It would add 
sharpness and ease of control particularly for me I expect when i will be using 
my new 6 inch telescope.
I bet this would be useful for the people doing lightning photography and fire 
works as well.
If it was divided up in to three waves I think the mirror locking one would be 
when something moves away from the sensor, that way you can have a peek in the 
viewer before it locks closed.
I think this would be a quick and easy way to do long exposures.
and you might be able to save some shots that need a quick stop to prevent some 
overexposing light. 

I'm just playing around with the latest released version, 400plus-20110412-0 

Checked out the release count in the INFO menu, then see if it updated, then 
decided to play with the factory menu, battery pull, then reinsert battery 
because no way to exit a factory test, and I checked the INFO menu again and my 
shots were the same as before.

Here's how to replicate the problem.

Check your release count, remember the number, take a shot or two and check the 
count again, remember it.
-Enter factory menu
-Do a factory test
-Flick the power switch to off
-Pull out battery and reinsert
-Turn on camera
-Check INFO screen

The shutter count will be the same as before you took your shots.

Some settings (like (de)activate the mirror lock-up) are used quite frequently; 
however, the user must navigate the menus to change them.

New shortcuts should be defined for these tasks, so they can be easily accessed 
from the shortcuts menu.

I use my camera for my line of work every week, once a week.
The camera acts weird in a few different ways.

I've never had a problem with the older versions as it was only small changes 
such as ISO3200 and spot metering.

However I suspect due to the mass amount of code added and even a fully 
implemented menu in the camera, the camera will behave unexpectedly.

The camera locks up during use. Here and there at random times. 
I've experienced it locking up during shooting, or playback.

Forms of locking up that I've experienced are:
1. In playback mode, the left right buttons do not work, I can go next photo 
with the index finger wheel and select items on the screen with it.

2. Camera completely locks up, will not focus, take a picture, no buttons 
respond.

3. Camera focuses, buttons work, but will not take a shot.

All of the bus I've experienced were solved by a quick battery eject and 
reinsert.

Free space in info screen is displaying wrong value.
On 256 MB CF Card shows 3.4 GB. It is the same on 8 GB CF Card.
If it is confirmed, I guess we should drop this info. It's coming from 
sub_FF83A640() sub...

When scripts make bursts of photographs, and the camera's buffer fills, an 
ERROR 99 is produced.

Current code only checks for the status of the camera, and a new photograph is 
made as soon as it reports to be ready; the status of the buffer is not 
checked, however.

The "ISO in viewfinder" functionality allows the user to change the ISO while 
looking trough the viewfinder; however, it is only available while in P or Tv 
mode.

This functionality should be adapted to Av mode.

Sometimes, having a DOF and hyperfocal calculator on the camera can be handy.

The shortcuts DP button works, but deactivating the shortcut menu, and setting 
it to my preference of ISO change only does not work as well.
The shortcuts menu still appears.

Under the following circumstances, "ISO in viewfinder" changes the shutter 
speed:

1. Put face to viewfinder
   => display switches off.

2. Press-and-hold LEFT or RIGHT buttons
   => ISO is changed, and new value is displayed in viewfinder.

3. Remove face from viewfinder
   => display switches back on.

4. Shutter speed has been changed to ISO value.

Are button combinations posible where we could use the DP button like a shift 
key so we can put extra functions on the other buttons?

Or how about button sequences where the user hits DP first then another button 
to activate a function?

If this can be done it would be a fast way to do things with no need to read a 
menu and a fewer number of button presses.

-JoeNeptune

What steps will reproduce the problem?

1. Turn on camera.
2. Turn mode dial to a basic zone such as Portrait
3. Press Menu button
4. Press DISP. button
5. No. of Actuations, Version #, BodyID not shown on last info line.

What is the expected output? What do you see instead?

Not sure what is expected - the last line displays the original CF free space 
in GB just like it would w/out using 400plus in creative zone.  Is this 
intended?

What version of the product are you using? On what operating system?

400plus automated build - 20110426 - r413

Please provide any additional information below.

If the Extended info could be programmed for basic zones also - this would save 
the user a few steps in determining shutter actuations, version info, etc.

What steps will reproduce the problem?
1. Turn on Camera
2. Press Menu button
3. Press DP button
4. Press WB (down) button 13 times to Developer menu
5. Press SET button to enter Developer menu
6. Press DP button to exit Developer menu
7. DP button does not exit Developer menu to Settings menu

What is the expected output? What do you see instead?

Expected output was to exit Developer menu and return back to Settings menu.  
DP button did not flash blue - No way determined to exit Developer menu back to 
Settings menu w/out starting over.

What version of the product are you using? On what operating system?

400plus-20110425-0

Please provide any additional information below.

FYI: Tried experimenting with the Save presets menu to test the DP button to 
see if Save preset menu could exit back to the Settings menu by pressing DP 
button - it worked correctly as desired.

A few more spelling corrections.

Our camera can do calculate exposures up to 30 seconds; for longer exposures, 
we have the BULB mode, but the exposure time has to be guessed by the user. 
However, sometimes it is possible to calculate a long exposure from a sorter 
one: if the camera suggest an exposure time of 30 seconds at ISO 800, the same 
image can be obtained with an exposure of 4 minutes at ISO 100 (provided the 
aperture is not changed).

Create a new screen where the camera can perform these calculations, and 
suggest an exposure time.

Changes made to wording and text to better reflect the features of 400plus.  
Also made some grammatical changes/updates.

1. User configures AEB using 400plus and saves the new settings.
2. User configures AEB using the standard menus.
3  User switches off and back on the camera.
4. Old AEB configuration is restored from the config file.

Most of the settings that the menu provides are meaningless in AUTO modes.

The menu should not be visible while in AUTO modes, or at least only the 
relevant entries should be accessible.

There are 2 suggestions on how to make the string editor.

1. Highlight current char, then use the Front Dial to change it and left/right 
btns to go to prev/next chars.
2. Use calendar like dialog with virtual keyboard.

Second is better, but I'm not sure there is suitable dialog we can use.

For me it is absolutely great to have ISO changed rapidly via the DP button 
while in shooting-action. 

Perhaps you can bring back this brilliant function and let the user choose to 
either assign a single function to the DP button or use the new SC menue 
instead?

Hi. 
I just wanted to use the EAEB Functionality.
What I did in the 400+
Set AEB to +3
Set EAEB FRames to 7
Set EAEB Stephan to +1
What I would have expected:
to get a Series of Pictures with 0 -3 +3 -2 +2 -1 +1 (maybe in a different 
sequence, but these EV values)
What I got: 0 -2 +2 -5 +6 -3  (Yes only 6 pics)
I might have to say, that I tried to do a night scene HDR - because I guess the 
limitation of 30s max has something to do with it. Nevertheless I cannot 
explain the calculation of the EV Value series. 

Current back-end code for the menu is too repetitive and hard to maintain: 
there are large "switch" structures for each action, and most of the "case" 
statements perform almost the same tasks, only with different data.

A new back-end should be developed, relying on a good data structure, that 
define the menu and the behavior for each item; then, a small generic code 
should handle the menus using that code.

Different situations require different configurations (camera mode, ISO / 
shutter speed / diaphragm aperture, custom functions, 400plus settings, ...); 
but moving from one configuration to another is slow.

Users should be able to keep several complete camera configurations 
independently, and retrieve those configurations easily (from the shortcuts 
menu, for example).

I've had trouble with this before, I thought it was only Sergei's release of 
the 400plus menu.

Having the ISO in Viewfinder set as ON in the 400plus menu, the display needs 
to be ON in order for you to view the ISO change in the viewfinder when you 
look into it, and pushing the left and right buttons.

HOWEVER.

Turning the display OFF prior, when looking into the viewfinder and pressing 
the left and right buttons to change the ISO, the regular metering and AF 
menu's are activated.

Having five presets, named "1", "2", ... is very confusing and hard to use.

Users should be able to rename presets: "Landscape", "Portrait", ...

Having the display on while a script is running is sometimes pointless, and it 
wastes battery.

An option should be added so the display is switched off when a script starts, 
and switched back on when it ends.

Eduperez, your menu version is much more smoother, and has way less lag than 
Sergei's version.

Might I suggest that you change your lower case "yes" and "no"'s to A 
capitalized first letter.
Such as "Yes" and "No".
Example would be "ISO In Viewfinder: Yes"

It looks more professional if it's capitalized.

I personally WANT to use your version, but the nonprofessional look of the 
lower cased letters bug me. Haha

Just a suggestion!

Display the version number of the installed hack somewhere into the menus.

Sergei found out that a call to SendButtonB7 will do the "beep/light warning 
and 2sec. delay" if drive mode is set to "Self-Timer"; this could be used in 
the scripts, to enhance the current 2s delay:

* EAEB / Intervalometer:
If the 2s delay is active, use SendButtonB7 before the first shot.

* Waving:
If the 2s delay is active, use SendButtonB7 before each shot.

I hope someone figures out how to control the shutter timing.
Fine control, most particularly in the range of 1/20sec to 1/40sec, would 
enable some nice shots that couldn't be done with out them.

You could tune it so, for example if leaves were falling you could set it just 
right so you could see both the detail of the leaf and some of the trail from 
its movement.