Remaining RAW+JPG shots + filespace icon/text- done :D - page 15 - General Discussion and Assistance - CHDK Forum

Remaining RAW+JPG shots + filespace icon/text- done :D

  • 175 Replies
  • 63876 Views
*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Calculation of remaining shots with RAW - done :D
« Reply #140 on: 17 / February / 2008, 09:30:59 »
Advertisements
edit: attached s3is build for barney.
Edit: Hmm... what are the chances ... that it could have a horizontal/vertical toggle? Might look really nice sitting up along the right side, or lower-right side of the frame. :)
this can and will be done. but i think we first have to make a feature-freeze so we can bugfix, comment code and finally get it into trunk, this way we spare the hassle with the tons of diffs that float around in this thread :D
by the way, the icon is fixed at 100 width (or height in vertical mode), how about a 2nd toggle that lets you choose between whole screenwidth/height,half & quarter? this way you'd have size/visibility vs. accuracy.

Quote from: Wilson
The realtime filespace counter gave me an idea; would it be possible to display the estimated remaining record time while recording in video mode, based on your current video settings?
we are discussing this already in detail in this very thread, just read back a couple of pages/posts.
this will be a bit tricky, as this time there is no (ASM) address we can refer to for getting the current remaining time, and also we dont know how big a video in filesize will be, because its not always 1 minute long etc. we will have to make an estimate, thats right. but that will be better than nothing. i say: we can do it (after feature freeze :D).

Quote
Should 1/3EV-selectable tv override be committed to official trunk or not? Poll?
Could both methods co-exist? That is, can a menu entry be dynamic: shown or not, depending on a variable?
Of course entries for both could be visible all time, and one has priority over the other... but.
this is about the "human readable" shutter speeds in extra photo operations, right? i like it. but its not so accurate to some people maybe, so yes, there should be a switch somewhere.

Quote
A620. Tryed enabling filespace icon again now (yesterday's build) and as soon as I did that, something got wrong (even in photo mode). Can't go into alt mode anymore, can't switch off the camera, except by opening batery tray, but even after switching it on again, it's the same. I will have to return a copy of cfg file from PC again, can't find other way out from this
i can help you out: just delete the cfg file and do NOT overwrite it with an old one. chdk creates its own this way.
problem exists because i added some new menu entries, and in official trunk there some additions as well. i think you tried a build from me and after that a newer build. my builds are based on older official sources, so now chdk gets in trouble because of the config file.  just delete it.

jucifer: hopefully i will have time this evening to take a look.

*

Offline vit40

  • ****
  • 276
Re: Calculation of remaining shots with RAW - done :D
« Reply #141 on: 17 / February / 2008, 10:12:20 »
Possible. On that SD card, I had Allbest builds up to #31, and then several builds with RAW/filespace indicators. Of course, I left cfg file there, so I didn't have to configure all options again

---

Edit: tryed erasing cfg file and, after 5-6 min configuring, it worked. This also solved a problem with some strange characters that remained in misc part of OSD

Of course, I wasn't happy until I crashed the camera again. A have a histogram in upper right corner of the LCD (it's usually sky at that place, so it's best position for me) and got to idea to place filespace indicator at the same place. Half press hides the indicator and shows the histogram at the same place. Went to OSD editor and moved an icon up, up ... until it went partially of the screen (by pixel or two) and camera froze the same way. I was lucky this time - opening the battery doors helped, indicator was placed slightly lower (default position I think) and everything worked (including things I configured previously). I moved the indiactor to the bottom, it seems to be the better place (upper right corner isn't good anyway, because it overlaps the Canon symbols there). Maybe vertical design at the lower right (or left ?) corner, as someone suggested, would also be good
« Last Edit: 17 / February / 2008, 10:49:35 by vit40 »

*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Calculation of remaining shots with RAW - done :D
« Reply #142 on: 17 / February / 2008, 10:43:08 »
note2: to avoid interaction problems I'm forced to wait until your/Jucifer's mods are committed.
huh? committed to where?

I guess your last post formulates better what I meant:

Quote
this can and will be done. but i think we first have to make a feature-freeze so we can bugfix, comment code and finally get it into trunk, this way we spare the hassle with the tons of diffs that float around in this thread Big Grin

... the trouble is, you can feature-freeze, but until committed you will still have to keep adapting your code to new trunks,
    while at the same time commenting and debugging  :haha

*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Calculation of remaining shots with RAW - done :D
« Reply #143 on: 17 / February / 2008, 12:06:17 »
Possible. On that SD card, I had Allbest builds up to #31, and then several builds with RAW/filespace indicators. Of course, I left cfg file there, so I didn't have to configure all options again

---

Edit: tryed erasing cfg file and, after 5-6 min configuring, it worked. This also solved a problem with some strange characters that remained in misc part of OSD

Of course, I wasn't happy until I crashed the camera again. A have a histogram in upper right corner of the LCD (it's usually sky at that place, so it's best position for me) and got to idea to place filespace indicator at the same place. Half press hides the indicator and shows the histogram at the same place. Went to OSD editor and moved an icon up, up ... until it went partially of the screen (by pixel or two) and camera froze the same way. I was lucky this time - opening the battery doors helped, indicator was placed slightly lower (default position I think) and everything worked (including things I configured previously). I moved the indiactor to the bottom, it seems to be the better place (upper right corner isn't good anyway, because it overlaps the Canon symbols there). Maybe vertical design at the lower right (or left ?) corner, as someone suggested, would also be good


i tried to reproduce that error, but everything works fine here. strange! i'm on a 620 as well. maybe it has something to do with your overall configuration. can you attach the cfg file with your settings here? and please tell in which build exactly (from which post!)  this problem occurs.

Quote
the trouble is, you can feature-freeze, but until committed you will still have to keep adapting your code to new trunks,
    while at the same time commenting and debugging
yeah, that really is a problem.we should commit our patches very soon.


*

Offline vit40

  • ****
  • 276
Re: Calculation of remaining shots with RAW - done :D
« Reply #144 on: 17 / February / 2008, 12:38:12 »
Ok:    zSHARE - chdk.cfg

Filespace icon is in lower right corner. If I enter OSD layout editor and press "up" about 25 times, icon will cross the upper screeen boundary and I can't do anything except open the battery door. I did as you said, erased cfg file from SD and started from default. I suppose this and yesterday's error have the same/similar reason - y coord of the icon negative

I'm not sure if it's worth to trace the possible bug ...

Build #237, Feb 16 2008, 14:20

*

Offline Jucifer

  • *****
  • 251
  • [A710IS]
Re: Calculation of remaining shots with RAW - done :D
« Reply #145 on: 17 / February / 2008, 12:50:06 »
I reproduced the remaining space-icon bug. It causes camera to lock when moved all the way to the top of the screen.


And now for something completely different:
Sorry, yet another patch. ;)

Would someone able to write to the trunk like to check the diff and commit it? GrAnd? EWAVR? Allbest? Me? (Tried, couldn't. :I) Or better yet, how can I do it? :]


Code: [Select]
- Changed RAW indicator to PhyrePhox's remaining RAWs -calc (chdk.setepontos.com/index.php/topic,468.0.html).
- Raised used-definable parameters in script menu to 26.
- Motion detection's immediate shoot is now more "shoot_full" than "shoot". (Sorry, can't remember whose version, but from chdk.setepontos.com.)
- Changed keys for setting focus (in manual focus) to infinity/hyperfocal to up/down for all cameras.
- There are lines for changing the tv override selection to 1/3EV-selectable (commented with "for 1/3EV-mod")
« Last Edit: 17 / February / 2008, 13:00:02 by Jucifer »

Re: Calculation of remaining shots with RAW - done :D
« Reply #146 on: 17 / February / 2008, 17:00:23 »
Deleted
« Last Edit: 22 / April / 2008, 11:10:39 by Barney Fife »
[acseven/admin commented out: please refrain from more direct offensive language to any user. FW complaints to me] I felt it imperative to withdraw my TOTAL participation. Nobody has my permission, nor the right, to reinstate MY posts. Make-do with my quoted text in others' replies only. Bye

*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Calculation of remaining shots with RAW - done :D
« Reply #147 on: 17 / February / 2008, 17:08:34 »
problem found, when you tuck the icon to the top screen some values got negative in my function. i rewrote some stuff and fixed the problem. you now can use the icon on the top screen without the cam getting stuck.
also i changed a minor issue with the RAW indicator, now you can tuck it directly on the right screen side, above the canon jpeg value. previously i was concerned about the "DISK FULL!" error being drawn into nirvana, but i circumvented that. you can now shove the RAW icon to the left or right side without any sideeffects.

*yay*

jucifer you forgot some of the changes made (warning color, space icons & text etc).
can i ask you some favour? can you incorporate my last changes into your diff please?
i think it is better we put our new stuff behind #302's latest additions, especially in gui_lang.c & the language files, as the chance is pretty high that more people used a #302 build than our build. know what i mean?

Here's the feature list:
Quote
- Changed RAW indicator to PhyrePhox's remaining RAWs -calc (chdk.setepontos.com/index.php/topic,468.0.html) (plus new menu entry to toggle it - enabled by default when RAW is enabled as well).
- Raised used-definable parameters in script menu to 26.
- Motion detection's immediate shoot is now more "shoot_full" than "shoot". (Sorry, can't remember whose version, but from chdk.setepontos.com.)
- Changed keys for setting focus (in manual focus) to infinity/hyperfocal to up/down for all cameras.
- There are lines for changing the tv override selection to 1/3EV-selectable (commented with "for 1/3EV-mod")
- New "Filespace Icon" and Filespace Text (Percent & Megabyte) with new menu entries in OSD menu (icon and MB text enabled by default)
- new conf.osd_color_warn (used in RAW icon, filespace & battery icon) can be set in visual settings menu (red & transparent by default)
- disabled battery & filespace & raw icons to be shown in shutter half_press mode
- updated english lang file
- updated all platform's lib.c file with function char camera_jpeg_count_str()
new files: core/gui_space.c & gui_space.h

by the way people: when our source is added to official trunk, you might want to delete your cfg file before updating.
« Last Edit: 17 / February / 2008, 18:50:10 by PhyrePhoX »


*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Calculation of remaining shots with RAW - done :D
« Reply #148 on: 17 / February / 2008, 17:13:57 »
Just a quick comment to support the idea of including a toggle for shutter-speed selection style. 1/3EV and .0000X decimal method. Both can have their uses. I'd hate to see the decimal method disappear in favor of the 1/3EV method, but if I had to choose I suppose I'd go with the 1/3EV (with regret :) )

Cool idea on that selectable-size space-left icon idea. When posting I even thought how nice it might be as a thin line along one border. Until you actually use them for a while you really can't tell what is best for your own needs. A wonderful idea for those that just needs a quick reminder on their screen, or are highly concerned when doing video clips, extended intervalometer events, or whatever and need to see how fast their space is disappearing on various settings. Wonderful ideas, all.

My only problem is that I don't have the right colors I'd like to use. :) I wish there were tons more hues in even more transparent colors, but I've always wished for that. (There's so many duplicate colors too, but I suppose it was done that way for simplicity in the code.)

Maybe that's for a future tweak, instead of selecting a color from a palette (or when you press [SET] on a palette color), it gives you additional options to select the transparency level or tweak the hue.


we will have to make a switch then. this should be no big problem (we dealt with way nastier things throughout this thread here :D), but first it's gotta get into trunk. the space icon will also be done, toggable in size & orientation - though when we'll have the new "remaining time in video rec mode" function you probably wont need a big icon anymore :D.
the color thingy *could* be done, but also probably raise the bar of complexity for newbies, i guess. add it to your suggestions poll :)


edit: as i consider this feature pretty much done i created another thread regarding the remaining time in video:
Calculation of remaining time in video record mode
this thread here should be about bugs & feature requests regarding remaining RAW & filespace stuff in the future :)
« Last Edit: 17 / February / 2008, 18:48:30 by PhyrePhoX »

*

Offline wontolla

  • ****
  • 413
  • S3 & G9 & A720
Re: Calculation of remaining shots with RAW - done :D
« Reply #149 on: 18 / February / 2008, 06:52:24 »
My God PhyrePhox, you are a programming machine. All you had to do is leave the icon to me and go party this weekend but nooooooooo...you just can't go and dance without beeing programming in your head and have to come back home asap to test it.

I haven't seen your icon yet (I don't want my chief to catch me playing with the camera instead of working) I'll try it in the evening. Here is mine:

The bar can certainly can be thinner, but it is good to have black lines and white as well so you can see it both in a light or in a dark background. It can be placed in the very edge of the screen.

I also made an SD card shape icon. 25 pixels wide so every level corresponds to 4% of the memory.

Dude, I log in here monday morning and there are 4 more pages in this thread. At least I'm not the only one been told by people to turn off the computer and get a life. This CHDK thing grows faster than any money-supported company project. Guys work 8 days a week for the joy of it!

P.S. No offence gentlemen, it's my monday rant ya know. Thanks for all your effort.

Code: (c) [Select]
//BAR SHAPE
static void gui_space_draw_icon () {
    coord x;
    int perc = get_space_perc();
    color cl = (GetFreeCardSpaceKb()/1024<=15)?conf.osd_color_warn:(conf.space_color&0xFF);
    int h = 100; //indicator height (must be at least 6)
    int w = 6;   //indicator width  (must be at least 6)
   
    // memory icon
    draw_rect(conf.space_icon_pos.x,      conf.space_icon_pos.y,       conf.space_icon_pos.x+h,     conf.space_icon_pos.y+w,     COLOR_BLACK);
    draw_rect(conf.space_icon_pos.x+1,    conf.space_icon_pos.y+1,     conf.space_icon_pos.x+h-1,   conf.space_icon_pos.y+w-1,   COLOR_WHITE);

    // memory fill
    x=conf.space_icon_pos.x+(perc*h/100);
    if (x<=conf.space_icon_pos.x) x=conf.space_icon_pos.x+1;
    if (x>conf.space_icon_pos.x+h+1) x=conf.space_icon_pos.x+h+1;
    draw_filled_rect(conf.space_icon_pos.x+2, conf.space_icon_pos.y+2, x-1, conf.space_icon_pos.y+w-2, MAKE_COLOR(COLOR_TRANSPARENT, COLOR_BLACK));
    draw_filled_rect(x, conf.space_icon_pos.y+2, conf.space_icon_pos.x+h-2, conf.space_icon_pos.y+w-2, MAKE_COLOR(cl, cl));   
}


Code: (c) [Select]
//CARD SHAPE
static void gui_space_draw_icon () {
    coord x;
    int perc = get_space_perc();
    color cl = (GetFreeCardSpaceKb()/1024<=15)?conf.osd_color_warn:(conf.space_color&0xFF);
    int i;
   
    // memory icon
    draw_line(conf.space_icon_pos.x+5,      conf.space_icon_pos.y,       conf.space_icon_pos.x+27,     conf.space_icon_pos.y,       COLOR_BLACK);  // top
    draw_line(conf.space_icon_pos.x+6,      conf.space_icon_pos.y+1,     conf.space_icon_pos.x+26,     conf.space_icon_pos.y+1,     COLOR_WHITE);  // top
    draw_line(conf.space_icon_pos.x,        conf.space_icon_pos.y+5,     conf.space_icon_pos.x,        conf.space_icon_pos.y+18,    COLOR_BLACK);  // left
    draw_line(conf.space_icon_pos.x+1,      conf.space_icon_pos.y+6,     conf.space_icon_pos.x+1,      conf.space_icon_pos.y+17,    COLOR_WHITE);  // left
    draw_line(conf.space_icon_pos.x,        conf.space_icon_pos.y+18,    conf.space_icon_pos.x+27,     conf.space_icon_pos.y+18,    COLOR_BLACK);  // bottom
    draw_line(conf.space_icon_pos.x+1,      conf.space_icon_pos.y+17,    conf.space_icon_pos.x+26,     conf.space_icon_pos.y+17,    COLOR_WHITE);  // bottom
    draw_line(conf.space_icon_pos.x+27,     conf.space_icon_pos.y,       conf.space_icon_pos.x+27,     conf.space_icon_pos.y+18,    COLOR_BLACK);  // right
    draw_line(conf.space_icon_pos.x+26,     conf.space_icon_pos.y+1,     conf.space_icon_pos.x+26,     conf.space_icon_pos.y+17,    COLOR_WHITE);  // right
    draw_line(conf.space_icon_pos.x+5,      conf.space_icon_pos.y,       conf.space_icon_pos.x,        conf.space_icon_pos.y+5,     COLOR_BLACK);  // edge
    draw_line(conf.space_icon_pos.x+5,      conf.space_icon_pos.y+1,     conf.space_icon_pos.x+1,      conf.space_icon_pos.y+5,     COLOR_WHITE);  // edge
    draw_line(conf.space_icon_pos.x+6,      conf.space_icon_pos.y+1,     conf.space_icon_pos.x+1,      conf.space_icon_pos.y+6,     COLOR_WHITE);  // edge

    // memory fill
    x=2+(perc*24/100);
    if (x>5) draw_line(conf.space_icon_pos.x+6,      conf.space_icon_pos.y+2,     conf.space_icon_pos.x+x,      conf.space_icon_pos.y+2,     COLOR_BLACK);
    if (x>2) draw_line(conf.space_icon_pos.x+x+1,    conf.space_icon_pos.y+2,     conf.space_icon_pos.x+25,     conf.space_icon_pos.y+2,     COLOR_WHITE);
    else     draw_line(conf.space_icon_pos.x+4,      conf.space_icon_pos.y+2,     conf.space_icon_pos.x+25,     conf.space_icon_pos.y+2,     COLOR_WHITE);   
    for(i=3;i<7;i++){
        if (x>7-i) draw_pixel(conf.space_icon_pos.x+8-i,     conf.space_icon_pos.y+i,     COLOR_BLACK);
        if (x>7-i) draw_pixel(conf.space_icon_pos.x+x,       conf.space_icon_pos.y+i,     COLOR_BLACK);
        draw_line(conf.space_icon_pos.x+x+1,                 conf.space_icon_pos.y+i,     conf.space_icon_pos.x+25,     conf.space_icon_pos.y+i,     COLOR_WHITE);
    }
    for(i=7;i<16;i++){
        if (x>1) draw_pixel(conf.space_icon_pos.x+2,         conf.space_icon_pos.y+i,     COLOR_BLACK);
        if (x>1) draw_pixel(conf.space_icon_pos.x+x,         conf.space_icon_pos.y+i,     COLOR_BLACK);
        draw_line(conf.space_icon_pos.x+x+1,                 conf.space_icon_pos.y+i,     conf.space_icon_pos.x+25,     conf.space_icon_pos.y+i,     COLOR_WHITE);
    }
    if (x>1) draw_line(conf.space_icon_pos.x+2,      conf.space_icon_pos.y+16,    conf.space_icon_pos.x+x,      conf.space_icon_pos.y+16,    COLOR_BLACK);
    draw_line(conf.space_icon_pos.x+x+1,             conf.space_icon_pos.y+16,    conf.space_icon_pos.x+25,     conf.space_icon_pos.y+16,    COLOR_WHITE);
}

 

Related Topics