Cropped zebra or zebra specific OSD - page 4 - Feature Requests - CHDK Forum supplierdeeply

Cropped zebra or zebra specific OSD

  • 90 Replies
  • 40201 Views
*

Offline dzsemx

  • ****
  • 302
  • [SX40HS][A650][A630]
Re: Cropped zebra or zebra specific OSD
« Reply #30 on: 20 / August / 2008, 16:04:55 »
Advertisements
another minor bug...
when using zebra and isoshift on print button, the screen is not updated when pressing print button, because the original FW osd is stored in a buffer...

*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Cropped zebra or zebra specific OSD
« Reply #31 on: 30 / August / 2008, 08:44:32 »
atm we still have the zebra/osd bug in juciphox - screen isnt properly redrawn (or for example text isnt "cleared"). i more or less wasnt involved in this, can someone point me to a fix or tell me how to do it or show me the proper patch (somehow i cannot find it !? didnt search for too long though!).

thanks

*

Offline fudgey

  • *****
  • 1705
  • a570is
Re: Cropped zebra or zebra specific OSD
« Reply #32 on: 30 / August / 2008, 09:05:37 »
I believe I'm using this one

http://chdk.setepontos.com/index.php/topic,1849.msg17451.html#msg17451

but with this modification to gui_osd.c increase blink rates:

Code: [Select]
   
            case ZEBRA_MODE_BLINKED_1:
                f = timer&1;
                break;
            case ZEBRA_MODE_BLINKED_3:
                f = timer&4;
                break;
            case ZEBRA_MODE_BLINKED_2:
            default:
                f = timer&2;
                break;


I mentioned this in http://chdk.setepontos.com/index.php/topic,688.msg20190.html#msg20190.

*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Cropped zebra or zebra specific OSD
« Reply #33 on: 31 / August / 2008, 17:11:55 »
darn, no patch, just the gui_osd attached there. don't have really much time now, maybe someone can supply me with a diff/patch against current version? thanks in advance!


*

Offline fudgey

  • *****
  • 1705
  • a570is
Re: Cropped zebra or zebra specific OSD
« Reply #34 on: 31 / August / 2008, 18:45:11 »
in trunk, gui_osd.c hasn't been changed since rev 396 in May so it's still current to trunk. Attached the diff I used against trunk.

Juciphox is a more complicated since a number of changesets have modified it and 485 in the needs to be reversed... so I grabbed juciphox 484 and made a diff against it, attached as well. I tested it very quickly...it builds on all platforms and seems to work on a570is 1.00e.

*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Cropped zebra or zebra specific OSD
« Reply #35 on: 01 / September / 2008, 18:06:55 »
hm call me an idiot, i fail to apply the diff. tortoise tells me the diff is outdated or at least it was diffed against an outdated gui_osd.c?

*

Offline fudgey

  • *****
  • 1705
  • a570is
Re: Cropped zebra or zebra specific OSD
« Reply #36 on: 01 / September / 2008, 18:15:15 »
hm call me an idiot, i fail to apply the diff. tortoise tells me the diff is outdated or at least it was diffed against an outdated gui_osd.c?

Yes because it's applied against juciphox 484, after which 485 and some newer one have modified it. But since the mod in 485 needs to be reversed (it's the zebraosd fix with the problematic transparency), this is the most recent I was able provide while staying sane myself. I'm really no good with version control and diff/patch tools, never got around to learning them for real.

I believe it should be fine for trunk but I didn't try that yesterday, just checked trunk gui_osd.c hadn't been changed in assembla logs and assumed it would work since it did before.

*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Cropped zebra or zebra specific OSD
« Reply #37 on: 01 / September / 2008, 18:33:15 »
hm, i guess we have to wait for jucifer to fix this then, i have lost track :)
i tried "undoing" the patch, but to no avail.

edit: reverted to "normal" state. i will give it another shot though, but maybe jucifer is faster than me at trying :)
« Last Edit: 01 / September / 2008, 19:52:27 by PhyrePhoX »


*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Cropped zebra or zebra specific OSD
« Reply #38 on: 18 / December / 2008, 16:28:21 »
so, since this was revived somewhere else, we might tackle this problem somehow, sometime.

so, was there a working diff that does not add any bugs?
perhaps some people did not consider some things as bugs (like microsoft: it's not a bug, it's a feature!)? so we might make it an option? via a toggle in conf.c? huh?
who's up for the task? and while ur at it, please open a bugticket for this.

*

Offline fudgey

  • *****
  • 1705
  • a570is
Re: Cropped zebra or zebra specific OSD
« Reply #39 on: 18 / December / 2008, 18:19:25 »
so, since this was revived somewhere else, we might tackle this problem somehow, sometime.

so, was there a working diff that does not add any bugs?
perhaps some people did not consider some things as bugs (like microsoft: it's not a bug, it's a feature!)? so we might make it an option? via a toggle in conf.c? huh?
who's up for the task? and while ur at it, please open a bugticket for this.

Somewhere above may be a working diff or working replacement gui_osd.c (or whatever it was, I can't check right now) to allbest trunk rev xxx. Unless different camera models have different requirements with display buffers or whatever, this is something that lets us remove some of those more cryptic zebra parameters, not add one more. It's just so beautiful and perfect it's hard to describe. ::)

The patch that was tried in Juciphox was incorrect, and did not work well. The reason why I haven't done this is that the C files that this patch/modification changes were significantly changed in Juciphox at the time of developing this zebra improvement, and it got too much for my tiny brain to handle back then.

I think/hope I have a working patched trunk copy of the build I'm using that has the good zebra. The osd/zebra code itself is a bit too puzzly for me to dig into in the little time that I have to put in.

 

Related Topics