Eos 400d ( Rebel XTI )

guffster

sizzlincok
How come the option for RAW in Auto mode was removed?

I found that quite a nifty option.

Pressing the Av button while shooting from any basic zone (Full Auto, Portrait, Landscape, Close-up, Sports, Night Portrait, Flash Off) should toggle image quality between JPG / RAW. Is this not working for you? Which version of 400plus are you using?

TomBStonE

@sizzlincok

RAw mode in automatique mode working perfectly for me, Pressing the Av button.

- 400plus-20110615-3.src.zip.

scrax

Hi all i'm new here and i'm posting here just to confirm that all worked good with the italian localization, but as already posted in the google.code page (when I submitted the patch) there are some minor corrections that I'm thinking about to optimize it.
First of all Illimitato is too long. I yet don't know if we can use ?

Also for me there are no problem with RAW mode in automatique with Av button.

EDIT: Submitted some corrections to have a more readable localization with more self-explanatory entries.
Updated the wiki UserGuide to match the localized menu.

Ataru, great job with the translation...

I really really like this project, and because it's just a week that I've started using it I need to read a lot of post here before making silly questions, but let me make at least one.
what about Focus Bracketing ?

eduperez

scrax
Hi all i'm new here and i'm posting here just to confirm that all worked good with the italian localization, but as already posted in the google.code page (when I submitted the patch) there are some minor corrections that I'm thinking about to optimize it.
First of all Illimitato is too long. I yet don't know if we can use ?

Also for me there are no problem with RAW mode in automatique with Av button.

Yes, "Illimitato" is one character too long, and it goes out of the screen; I did not catch dat when I did the tests, sorry. Will be fixed in next version, thanks for pointing it out.

scrax

eduperez

Yes, "Illimitato" is one character too long, and it goes out of the screen; I did not catch dat when I did the tests, sorry. Will be fixed in next version, thanks for pointing it out.

Sorry for what? 😀
Thank's to you for your work. (I was editing my previous post and the localizzation while you answered mine.)

sizzlincok

guffster
Pressing the Av button while shooting from any basic zone (Full Auto, Portrait, Landscape, Close-up, Sports, Night Portrait, Flash Off) should toggle image quality between JPG / RAW. Is this not working for you? Which version of 400plus are you using?

Ohhh. It was changed from pressing the DP button to the Aperture button.

Thanks

scrax

Ok tested the italian localization and the new layout is working. I need to short a word because it's a character too long and so the : are not aligned with the other lines. I'll also add the new menu entries added in the developers menu.

EKIT: Submitted new localization patch, updated wiki

TomBStonE

Hello, i'm french,

My english is not perfect, and i have tested to edit "languages.c" for added French Language.

I dont no if is the good action for this.

Someone just help me ?

I'd realy like helped for this project 😀

Thanks

eduperez

TomBStonE
Hello, i'm french,

My english is not perfect, and i have tested to edit "languages.c" for added French Language.

I dont no if is the good action for this.

Someone just help me ?

I'd realy like helped for this project 😀

Thanks

Yes, you just need to edit "languages.c" and follow what others did for the German, Italian, and Spanish translations; then send it to us to incorporate it. Thanks.

scrax

r682 TEST REPORT
Hi all, I've tested last nightly build (r682) and now the Italian localization is complete, clear and works good.
For who want to translate in other languages, I've learned (by editing it) that we can play with the word length to make all the > and : aligned.

LOCALIZATION HINT: WORD LENGHT
We can have a max length of 18 char (> included) in the settings menu (before the : ). Total char length of each line is 28 if I'm not wrong so after the : we have 9 char max (using 10 don't seem to create problem like a wrong length before the : but it's really ugly and unpleasant)
For the italian localization I used 9 char (instead of 8 like in the english version, if remember right) for all the SubMenu ITEM and 8 char for all the SUB-ITEM
Only the Scripts ITEM is 6char because that permitted me to use a more clear and self-explanatory entries of 11 char.
Now I'm looking for a way to keep it easy understandable using 8char for all the SubMenuITEMs, but that is definitely a cosmetic things (I will also add a space in front of the Yes, No and Off entries so to have them aligned with the number we can set).

WRAP AROUND MENU
I've almost read all the topic today and I'll bump an old post because even before reading it was thinking that that need to be the default behavior (like in the Canon's menu)

eduperez

chross
Hi,
great work and improvements so far.
Is it possible to implement cycling menus that wrap around when you reach the top/bottom of the list. So pressing the down arrow when at the bottom will select the topmost entry and vice versa?
Just a little suggestion to improve usability / handling.

Cheers

Looks interesting, I'll note it down; thanks.

NEW SHORTCUT MENU COLORS
And about the new color feature I like it a lot, but the green is for me too bright, It's in general more bright than the selected item and so at first is not so clear (I'll tend to read first the green entries before my eyes moves to the more important, selected one).

My suggestion is to make it more consistent with the settings menu using only one color (green) for the title underline and for the selected line frame. White for the font color and all the unselected items all gray (font anm frame like the settings menu)

EDIT: Localized also the FirmwareHackInstallation page

draekko

Didn't know where else to post this. Its a diff from a checkout from subversion that i got this morning which adds a shortcut for the color temp so i don't have to go to the menu all the time 😐:

Index: menu_shortcuts.c
===================================================================
--- menu_shortcuts.c	(revision 686)
+++ menu_shortcuts.c	(working copy)
@@ -21,6 +21,7 @@
 void menu_shortcuts_script_self_timer   (type_MENUITEM *item);
 
 void menu_shortcuts_apply_iso                (type_MENUITEM *item);
+void menu_shortcuts_apply_color_temp         (type_MENUITEM *item);
 void menu_shortcuts_apply_cf_emit_aux        (type_MENUITEM *item);
 void menu_shortcuts_apply_cf_mirror_up_lock  (type_MENUITEM *item);
 void menu_shortcuts_apply_cf_flash_sync_rear (type_MENUITEM *item);
@@ -28,14 +29,15 @@
 void menu_shortcuts_script (type_TASK script);
 
 type_MENUITEM menu_shortcut_items[] = {
-	MENUITEM_ISO    (LP_WORD(L_ISO),           &sc_cameraMode.iso,                menu_shortcuts_apply_iso),
-	MENUITEM_LAUNCH (LP_WORD(L_EXTENDED_AEB),   menu_shortcuts_script_extended_aeb),
-	MENUITEM_LAUNCH (LP_WORD(L_INTERVALOMETER), menu_shortcuts_script_interval),
-	MENUITEM_LAUNCH (LP_WORD(L_HAND_WAVING),    menu_shortcuts_script_wave),
-	MENUITEM_LAUNCH (LP_WORD(L_SELF_TIMER),     menu_shortcuts_script_self_timer),
-	MENUITEM_AFFLASH(LP_WORD(L_AF_FLASH),      &sc_cameraMode.cf_emit_aux,        menu_shortcuts_apply_cf_emit_aux),
-	MENUITEM_BOOLEAN(LP_WORD(L_MIRROR_LOCKUP), &sc_cameraMode.cf_mirror_up_lock,  menu_shortcuts_apply_cf_mirror_up_lock),
-	MENUITEM_BOOLEAN(LP_WORD(L_FLASH_2ND_CURT),&sc_cameraMode.cf_flash_sync_rear, menu_shortcuts_apply_cf_flash_sync_rear)
+	MENUITEM_ISO        (LP_WORD(L_ISO),           &sc_cameraMode.iso,                menu_shortcuts_apply_iso),
+	MENUITEM_CLRTEMP    (LP_WORD(L_COLOR_TEMP_K),  &sc_cameraMode.color_temp,         menu_shortcuts_apply_color_temp),
+	MENUITEM_LAUNCH     (LP_WORD(L_EXTENDED_AEB),   menu_shortcuts_script_extended_aeb),
+	MENUITEM_LAUNCH     (LP_WORD(L_INTERVALOMETER), menu_shortcuts_script_interval),
+	MENUITEM_LAUNCH     (LP_WORD(L_HAND_WAVING),    menu_shortcuts_script_wave),
+	MENUITEM_LAUNCH     (LP_WORD(L_SELF_TIMER),     menu_shortcuts_script_self_timer),
+	MENUITEM_AFFLASH    (LP_WORD(L_AF_FLASH),      &sc_cameraMode.cf_emit_aux,        menu_shortcuts_apply_cf_emit_aux),
+	MENUITEM_BOOLEAN    (LP_WORD(L_MIRROR_LOCKUP), &sc_cameraMode.cf_mirror_up_lock,  menu_shortcuts_apply_cf_mirror_up_lock),
+	MENUITEM_BOOLEAN    (LP_WORD(L_FLASH_2ND_CURT),&sc_cameraMode.cf_flash_sync_rear, menu_shortcuts_apply_cf_flash_sync_rear)
 };
 
 type_MENU menu_shortcuts = {
@@ -76,6 +78,11 @@
 	send_to_intercom(IC_SET_ISO, 2, *item->parm.menuitem_iso.value);
 }
 
+void menu_shortcuts_apply_color_temp(type_MENUITEM *item) {
+	send_to_intercom(IC_SET_WB,         1, WB_MODE_COLORTEMP);
+	send_to_intercom(IC_SET_COLOR_TEMP, 2, *item->parm.menuitem_int.value);
+}
+
 void menu_shortcuts_apply_cf_emit_aux(type_MENUITEM *item) {
 	send_to_intercom(IC_SET_CF_EMIT_AUX, 1, *item->parm.menuitem_enum.value);
 }

scrax

Nice idea, i think that the appropriate place is the google code page, to be sure that all the dev can see it, here maybe it can be lost in the discussion (so i've also posted it there).
Can you post a compiled bin to test?

0xAF

@scrax, about the colors, it was in "0xAF" branch before i merged it to the trunk. i actually forgot that the colors were set for the shortcuts menu. about the green color, it is some already existing color set in the camera. if i recall correctly, the colors are not free for choice. there was 5-6 combination of colors which we can use, but i'll play a bit with them, i can find some way to make custom sets.

@draekko, thanks for the patch, i'll merge it later. about the place where you should post the patches, please use the google code page and file an issue with the patch, like scrax suggested.

@scrax, i'll merge it later, so you will be able to test it in the next nightly build.

draekko

@Scrax & 0xAF .. ok will do that later or in the AM.

0xAF

@draekko, no need to post it now, it's already in the code, check nightly build >= r687, should be there after couple of hours.
btw did you tested that change ? i mean are you compiling the code to test it ? if yes, what version of gcc is it ?

0xAF

scrax
...
LOCALIZATION HINT: WORD LENGHT
...
EDIT: Localized also the FirmwareHackInstallation page

Scrax,
if you have the time and the will to write another wiki to help the translators (like TomBStonE) would be great.
Instructions how to translate the languages.c file to their language. We could use another translators around.
Actually there is no need of instructions, but the problems and solutions you've faced while translated the file, would be great to have them written down.

I'm looking forward to what TomBStonE is up to.

draekko

@0xAF I used gcc 4.5.2 as per the howto built on ubuntu 10.04. And yes it is on my camera as i type this. Will do an update to my svn checkout to get the latest.

A couple of question is there an easy way to detect that i'm manual mode? Also i tried to turn on debugging but i don't think i'm doing it right doesn't seem to work. Reason i ask is i'd like to figure a way to toggle between picture modes (ie raw -> raw/jpeg -> jpeg Fine -> etc..) when in manual mode using the av button.

This project sure added new life to my aging 400D 😁 thanks.

@scrax Seems its already in the latest build 😉

0xAF

draekko
A couple of question is there an easy way to detect that i'm manual mode? Also i tried to turn on debugging but i don't think i'm doing it right doesn't seem to work. Reason i ask is i'd like to figure a way to toggle between picture modes (ie raw -> raw/jpeg -> jpeg Fine -> etc..) when in manual mode using the av button.

if (cameraMode->ae == AE_MODE_M) { ... }

about the debug mode, i've changed it a bit... go to developers menu
enable "Debug on power on", then choose the logfile mode (Overwrite/New/Append), it's self explaining.
then restart the camera, it will start logging.

draekko

@0XAF ok thanks will tinker with it see what i can come up with 😉 As for debug i did that didn't seem to log anything, no files were created. Will try again later with r687.

scrax

I'm using the last night build and it's ok with the WB in shortcuts menu.
I'll add my finding for the localization in the wiki in the next days now I'm trying to setup my arm tools chain to compile the source by myself. I'm using yagarto on osx as suggested on the MagicLantern dev forum (I'll use it also for the 600D code if possible) and now I need to find something to manage the svn.

with r687 I can see the log file in the card, and every key press activate the CF led (I think, because it's writing it to the log).

NOTE: My old preset don't works with this new build, I had to make them again

« Previous Page Next Page »