Automatic Playback button press - SD4000 - page 3 - Script Writing

waterwingz

12092

Re: Automatic Playback button press - SD4000

« Reply #20 on: 17 / June / 2017, 16:55:47 »

Advertisements

Jog dial.

Logged

Ported : A1200 SD940 G10 Powershot N G16

reyalp

13438

Re: Automatic Playback button press - SD4000

« Reply #21 on: 17 / June / 2017, 17:12:17 »

Quote from: Robert1975 on 17 / June / 2017, 16:51:45

I thought it's the only IXUS without separate buttons? It's very minimalist.

On many cameras, the directional buttons are also a wheel (jog dial) you can turn. A few also have the touch feature, which in the Canon firmware just displays icons or hints on the screen to tell you what clicking in that direction would do.

Looking at the code further, there is actually stuff to handle the touch part as well, so from your report that's probably OK.

Just to be clear, in CHDK
* Clicking up/down the top or bottom of the wheel without turning should move up or down the CHDK menu
* Turning the wheel without clicking the top/bottom should also move up or down
* The Canon settings normally controlled by clicking or turning the wheel should not be affected when the CHDK menu is open.
* Some CHDK ports have display update problems, where you will see an old copy of the menu when the canon firmware updates the screen. This can make it seem like the buttons aren't behaving correctly, or is moving up and down by itself. This should not occur in playback mode.

Logged

Don't forget what the H stands for.

Robert1975

Re: Automatic Playback button press - SD4000

« Reply #22 on: 17 / June / 2017, 17:16:13 »

Quote from: waterwingz on 17 / June / 2017, 16:46:51

But as reyalp has repeated said, there are bugs in the port that we can fix. I know you somehow just don't want to believe that.

I'm not pessimistic. But I was usually right about things

I knew it was pointless to try anything about manual focusing on this cam.
I thought NR caused the hangs, but it was DFS - quite similar... Fortunately, reyalp mentioned this!

I'm still using the old build - it's the safest bet for me, particularly with DFS off

Logged

Robert1975

Re: Automatic Playback button press - SD4000

« Reply #23 on: 17 / June / 2017, 17:23:27 »

Quote from: reyalp on 17 / June / 2017, 17:12:17

Just to be clear, in CHDK
* Clicking up/down the top or bottom of the wheel without turning should move up or down the CHDK menu
* Turning the wheel without clicking the top/bottom should also move up or down
* The Canon settings normally controlled by clicking or turning the wheel should not be affected when the CHDK menu is open.
* Some CHDK ports have display update problems, where you will see an old copy of the menu when the canon firmware updates the screen. This can make it seem like the buttons aren't behaving correctly, or is moving up and down by itself. This should not occur in playback mode.

Yes, it works that way.
But for example, turning the wheel in CHDK in Beta I tested today affects the aperture - quite annoying, shouldn't happen...
That's why I stick with the old build, it's great now that we eliminated the hangs.

Any ideas about partitioned cards?

Logged

reyalp

13438

Re: Automatic Playback button press - SD4000

« Reply #24 on: 17 / June / 2017, 17:55:14 »

Quote from: Robert1975 on 17 / June / 2017, 17:23:27

Yes, it works that way.
But for example, turning the wheel in CHDK in Beta I tested today affects the aperture - quite annoying, shouldn't happen...

So you are saying that in the build I posted, when you turn the wheel with the CHDK menu open, the Av value changes? This is what I meant should not happen in

Quote

* The Canon settings normally controlled by clicking or turning the wheel should not be affected when the CHDK menu is open.

Does this happen as soon as you move the wheel, or only after you leave alt mode?

In the build you are currently using, does this really not happen, or does the fact that using the alt button leaves the camera in playback prevent it? You could test this by changing the alt key option.

Quote

That's why I stick with the old build, it's great now that we eliminated the hangs.

It's great that this works for you, but I would like to fix the problems in the port for the rest of the community. The behavior of the playback button was clearly incorrect. I fixed that. If that fix uncovered other problems, I would like to fix those problems.

Quote

Any ideas about partitioned cards?

The relevant code appears to be there, but I haven't looked at it further. One thing at a time...

Logged

Don't forget what the H stands for.

waterwingz

12092

Re: Automatic Playback button press - SD4000

« Reply #25 on: 17 / June / 2017, 18:01:27 »

Quote from: Robert1975 on 17 / June / 2017, 17:16:13

I knew it was pointless to try anything about manual focusing on this cam.

For the record, I don't agree. You were certain your "camera hangs" were memory management related. Not so. And you were certain the uBASIC is_key function does not work on your camera when it appears you had simple scripting errors in your code.

Getting MF to work takes a bit of work on the part of the person doing a camera port. AFAIK, none of that has been done on the SD4000 - running the MF test script is only the start of the process.

Quote from: Robert1975 on 17 / June / 2017, 17:23:27

Any ideas about partitioned cards?

Quote from: Robert1975 on 17 / June / 2017, 16:45:19

It could be limitation imposed by original firmware, I think it's possible.

Do you want to help to debug this or is your mind made up? (as you are "was usually right about things").

Logged

Ported : A1200 SD940 G10 Powershot N G16

Robert1975

Re: Automatic Playback button press - SD4000

« Reply #26 on: 17 / June / 2017, 18:49:13 »

Yep, Av value changes while turning the wheel in CHDK menu. It's like Alt and Rec are somehow mixed.
It never happened in the old build - and I did try it multiple times with Up+Left keys for Alt.

Unfortunately, every time you fixed something, another thing broke...

@waterwingz - I still believe it's memory issue (CPU as well), it cannot hold both CHDK/DNG and process slow shutter speed shots. Reading about memory management got me to NR idea, however, it was DFS. Disabling it completely freed up memory and CPU. Isn't that obvious? There are issues with is_key - trust me. And the script, well, there are bugs and issues within the language itself. Check out this document http://images2.wikia.nocookie.net/__cb20100806022158/chdk/images/e/e5/UBASIC_User_Guide_D0_5.pdf Page 21, NESTED IF. This applies to my problem. I was very close to the solution with the first version of the loop, even with the "wrong syntax" (the script was actually running without errors reported), but the machine definitely has some issues with keys and buttons.

Of course, I will help as much as I can, but I really have some other important things to do (as well as shoot some pictures with my "secret weapon"). Sorry guys.

Logged

reyalp

13438

Re: Automatic Playback button press - SD4000

« Reply #27 on: 19 / June / 2017, 13:47:42 »

Quote from: Robert1975 on 17 / June / 2017, 18:49:13

Yep, Av value changes while turning the wheel in CHDK menu. It's like Alt and Rec are somehow mixed.
It never happened in the old build - and I did try it multiple times with Up+Left keys for Alt.

So you were able to enter alt mode, while still in record mode, and turning the jog dial did not affect the canon UI? And when you left alt mode, you were still in record mode?

Quote

@waterwingz - I still believe it's memory issue (CPU as well), it cannot hold both CHDK/DNG and process slow shutter speed shots.

This is not correct. DFS hangs the camera because the camera takes a second exposure identical to the first with the shutter closed.

Shooting with CHDK DNG doesn't actually use noticeably more memory than shooting without, because it writes directly from the raw buffer to the card. Shooting DNG does use substantially more CPU time than without, but this is completely independent of the exposure length.

I've been the lead developer of CHDK for the last ~8 years or so, and waterwingz has been hacking the code for almost as long, so do we have some idea of what we are talking about here

Logged

Don't forget what the H stands for.