IXUS 100 IS (Europe) / PowerShot SD780 IS - Porting Thread

Microfunguy

OK, thanks.

Maybe he is simply pressing the button for too long.

He did say that it only works if you press for a VERY short time.

As for the function that is the same I think I just didn't need to change anything.

Then why have two identical functions ?

David

HarpoMa

Feel free to delete one. There isn't always a reason sometimes you just think you need it (intention as you say). When I release the code formally I'll probably delete it too. But as it uses a static variable I may choose to change the various variables to ensure use of one doesn't affect the other.

Harpo

Microfunguy

I will enable the relevant code and ask him to check again.

I don't entirely understand kbd_get_held_key() , I will have to study it.

David

Microfunguy

Did you alter the two time values that determine which mode the button is used for or are they 175 and 500 msec ?

Incidentally, I think tick_count only has a resolution of 10 msecs.

David

HarpoMa

Yes my working code that I'm keeping from everyone has the correct timings. I'm hiding it from everyone to allow my build time to rule them all.......

But seriously you have the latest code (minus partition support). I still beleive there is a translation issue to SDM. BUT i will try it at home tonight to verify 100%.

Microfunguy

Interesting problem that may be linked to the kbd_get_held_key code.

With SDM in ALT mode, a brief press of SET turns screen displays on/off.

A longer press turns edge-overlay on/off.

It also crashes the IXUS100 !

Of course, it may have nothing to do with that code.

HarpoMa

Ok. I have compiled my compile here...

DISP (quick) turns on ALT mode. A press of SET then brings up Select script file... (as expected) A press of DISP (quick) then exits ALT mode.
DISP (hold) while in playback executes a normal DISP (canon level) repeats if I repeat

So I consider this a SDM integration issue and not a chdk issue. That said I don't expect my chdk build to currently follow the best standards or such. Maybe my code violates some rules and if it didn't it wouldn't break SDM. However at this point I can't debug SDM and continue my own CHDK work.

Sorry.

Harpo

Microfunguy

So, did you verify this and did you define it ? :-

volatile long *mmio2 = (void*)0xE240; //VERIFY SD780 Used to override long held DISP
// Needs to be #DEFINE

HarpoMa

Yes in my super secret keep from Microfunguy build I have defined and verified everything. I'm keeping for whim and reyalp all my really good stuff.

Lets just end this chain of questions and you can just ask yourself the questions and just assume that my answer will either be "it's not done, it works for me, or it's a SDM thing not a chdk thing". I don't want to be rude but I'm starting to find your questions rude and certainly bordering on accusatory. You have the code you can do as you wish with it but I am not responcible for your ability to code, port, ect.

Except for my super secret build of course.....that version has all the funguy stuff.

Harpo

Microfunguy

Thanks for your 'interesting' reply Jason Harp.

HarpoMa

Your welcome David.

ignasx

Hi Jason, how's the development going ?
I've just played with some Lua, shutter speed and bracketing in continuous mode and everything is nice, but there are some strange things like: menu is disappearing randomly (mentioned), sometimes CHDK fails to load with last time configuration (I can send it to you if this will help you) and histogram is all messed up...
Is it possible to disable CHDK in AUTO mode, when you shoot in auto you don't really need CHDK, so i think, the best way of repairing it is to disable it...
I would really like to help, so i will try to find new bugs...
Good luck with BASIC, Lua and RAW (i need them most).
Thanks HarpoMa !!!

HarpoMa

I've actually been doing stuff on it so I will look at your points of need. I put out a diff of the source yesterday but I'll put out a binary tonight.

If you can detail your issues with BASIC, Lua, and RAW it will give me a list to go off. RAW should work but maybe some small detail needs attention.

Anyways don't be afraid to list any and all issues and i'll just knock them down one-by-one....

Also post #1 always has the update to builds so feel free to reread it often.

Harpo

ignasx

Great I will try the new version up !

At the weekend I will shoot some RAW, test some Scripts and search for bugs (e.g. What causes it not to boot up with my old configuration) and post them...

P.S. I have some ideas of using Image Stabilizer in video mode: We could make stereographic 15fps video, by shooting in 30fps but every frame shifting lenses right or left, I wonder if that shift would be enough. But that's for future development 😀

Keep up the good work 😀

Ignas

reyalp

ignasx
Hi Jason, how's the development going ?
I've just played with some Lua, shutter speed and bracketing in continuous mode and everything is nice, but there are some strange things like: menu is disappearing randomly (mentioned),

This is probably normal: http://chdk.kernreaktor.org/mantis/view.php?id=275

and histogram is all messed up...

Messed up how ? If it displays wrong data, this usually means the live viewport address is wrong. In this case, zebra and edge overlay should also be wrong.

Is it possible to disable CHDK in AUTO mode, when you shoot in auto you don't really need CHDK, so i think, the best way of repairing it is to disable it...

Unless you turn on overrides or raw or something like that, CHDK should have no effect on normal shooting, in auto mode or any other mode. You can set exceptions for raw.

I would really like to help, so i will try to find new bugs...
Good luck with BASIC, Lua and RAW (i need them most).

Be sure you read the sticky threads in the raw forum (or earlier posts on the subject in this thread) before reporting problems with raw 😉

wbloos

I thought it would be interesting to try to compile HarpoMan's ixus100 code.
I installed GrAnd's windows environment and TortoiseSVN.

I checked-out CHDK 853.
I successfully compiled CHDK for another camera.

I renamed HarpoMan's diff.txt file to 'ixus100.diff' and at root directory on the command-line typed :-
patch -p0 < ixus100.diff.

Error messages multiple times :-
"Reversed (or previously applied) patch detected! Assume -R? [n]
Pressed return
Apply anyway[n] yes"
Many other error messages 'hunks failed'and rejects saved.
Hunk#2 succeeded at 244 with fuzz.

No ixus100 subfolder created.
The build for other camera no longer works.

Has anyone else managed to patch this or know what I am doing wrong ?

HarpoMa

Maybe I should just release a full source instead of the patch. Would that work best?

wbloos

Yes, that would be great and make it far easier for me.

Thanks !
Werner

reyalp

You patch is a mess. Please don't include binary files, or files irrelevant to the source.

You also appear to have a bunch of changes that are from the trunk, not your own changes. If you want to track the trunk (which you should), you need to update your working copy, resolve any conflicts, and make the diff against that.

If you are using windows, I highly suggest using tortoise.

HarpoMa

I'm using eclipse but I obviously have not got the team/patch/diff tracking perfect. I'll just put out the source in non-diff and try again later on the diff.

Harpo

« Previous Page Next Page »