Video Manual Control: ISO, APERTURE & SHUTTER SPEED CONTROL, PLEASE!!!!

[Aket]

Oh my god it would be so good to have these three things to adjust on my powershot. Please someone out there hear my prayers for developing an update in the firmware to have these three things to control.

Someone out there, please!

[kmoreau893]

I second that. It would make video mode on these cameras much more usable. Right now the video features such as zoom and focus are great but having control over shutter and aperture would be excellent. Does anybody have any plans to update this?

[Aket]

Don't forget ISO!

See? People want it! As much as the people who demanded manual exposure on dslrs.

C'mon! Pleaseeee!

[reyalp]

See? People want it! As much as the people who demanded manual exposure on dslrs.

Doesn't matter who wants it, unless they happen to be a programmer with a whole bunch of time and the necessary reverse engineering skills (assuming it's possible at all, which isn't a given.)

Features are generally added because someone who wanted the feature implemented it, not because it would make CHDK more popular with the general public. If you want this feature, you are welcome to dig into the code.

[Aket]

What? SO WHY DOES THIS PART OF THE FORUM EVEN EXIST?

Jeez! I'd even do it myself if I knew some programming, or at least some hint on what should I learn to do it, you might have 7420981 posts but you don't even bring an insight on what to do for help in this situation.

It's even a very basic and helpful feature.

Someone who could help should speak up.

And the ones who encourage nothing to be done like you should shut up.

[reyalp]

What? SO WHY DOES THIS PART OF THE FORUM EVEN EXIST?

So people can make suggestions and discuss ideas. It's not a task list.

Jeez! I'd even do it myself if I knew some programming, or at least some hint on what should I learn to do it,

C and assembler. You're welcome.

And the ones who encourage nothing to be done like you should shut up.

I did not "encourage nothing to be done", I described how the process actually works: Features get implemented because someone with the required skill devotes the required time to it. This is essentially unconnected to how many people request it on the forum.

Exposure control in video is a good idea, and a popular request. I have no objection to it being done, but I don't personally have the time and inclination to work on it. If someone does start work on it, I'll be happy to provide any technical assistance I am able to.

[whim]

@Aket

...or at least some hint on what should I learn to do it

http://chdk.wikia.com/wiki/For_Developers

HTH,

wim

PS You might also want to take a look here http://tools.assembla.com/chdk/log/?action=follow_copy&rev=918&stop_rev=&mode=follow_copy&verbose=on to see that reyalp does 'a little' more than bumping his post count  

[Aket]

I did not "encourage nothing to be done"
[/quote]

You basically said/implied: "You can't ask for features here, and it doesn't matter how many people do also, you would need a lot of time in case you knew programming and if it's even posible to do it and since I'm the only one experienced replying here I don't think there's someone else who can, good luck if you do "

That's pretty discouraging in my book and I think most people's.

But whatever, thanks for the hint. Just checked what you have to know, looks pretty hard.

How many codes would you have to write and where? The assembler gets the codes into the CHDK firmware?

Thanks if you can answer.

[Aket]

@Aket

...or at least some hint on what should I learn to do it

http://chdk.wikia.com/wiki/For_Developers

HTH,

wim

PS You might also want to take a look here http://tools.assembla.com/chdk/log/?action=follow_copy&rev=918&stop_rev=&mode=follow_copy&verbose=on to see that reyalp does 'a little' more than bumping his post count 

I imagined he was a developer but he was very dismissive, thanks anyway, and nice I'll check that out.

[zeno]

Aket - please take the trouble to re-read your posts and the replies. So far you've managed to be unpleasant to two people (note that they are both "Guru Members") who have freely given a great deal of their time to (a) work on CHDK and (b) answer lots of questions politely here. As Reyalp said, this thread is so people can make suggestions - not demands. And no matter how many people ask for something, when they are asking (as you were) for something for nothing, whether they get it depends on the goodwill of people like Reyalp and Whim, not how loudly or aggressively they ask.

And by the way, there's lots of information here and on the Wiki about what you need to know to do development. As you say, "it looks pretty hard".

[Microfunguy]

How many codes would you have to write and where?

What does your question mean, I cannot understand it ?

Do yourself a favour, buy a Panasonic FZ38 or similar, like I have.

[Aket]

Aket - please take the trouble to re-read your posts and the replies. So far you've managed to be unpleasant to two people (note that they are both "Guru Members") who have freely given a great deal of their time to (a) work on CHDK and (b) answer lots of questions politely here. As Reyalp said, this thread is so people can make suggestions - not demands. And no matter how many people ask for something, when they are asking (as you were) for something for nothing, whether they get it depends on the goodwill of people like Reyalp and Whim, not how loudly or aggressively they ask.

And by the way, there's lots of information here and on the Wiki about what you need to know to do development. As you say, "it looks pretty hard".

Got it, sorry I just thought it wasn't so difficult for the guys who know the code, that's why I asked loudly.

How many codes would you have to write and where?

What does your question mean, I cannot understand it ?

Do yourself a favour, buy a Panasonic FZ38 or similar, like I have.

The question is pretty clear and I think we had already too much negativity in here, right? Great suggestion but I already knew of the camera, thanks for helping developing the firmware, but there's a reason we're in Canon forum. Thanks, bye!

[jonny360]

i'd love this feature too! i'm not a programmer but i have cash. so who wants to get paid?
(hows that for offering my help?)

[reyalp]

i'd love this feature too! i'm not a programmer but i have cash. so who wants to get paid?
(hows that for offering my help?)

If you are prepared to offer market value for programmer time, I suggest you just buy a DV system with the features you need. It will likely be significantly cheaper, and you will end up with a system much better suited to producing quality video. Also, as I mentioned before, there's no guarantee that all the requested features can be implemented in CHDK. I would guess that it probably can be done, and might even be fairly simple, but no one knows until they've done the research. Just doing that research is likely to take substantial time.

Again, I'm not trying to discourage people from asking for features, or saying this is a bad idea or is not a worthy feature. Quite the opposite: It's a good idea and quite a few people would obviously like to have it.

What I am trying to do is explain why merely asking for something doesn't have a lot of influence on whether it gets done or not. Think about it this way: If some random stranger asks you to spend hundreds or thousands of dollars worth of time on their project, is the major factor going to be how much they want it, or how interesting/rewarding you find the project ?

edit:
Or maybe you'll get lucky and someone who has already spent the time will tell you how to do it 

[ewavr]

IMO,  manual control of shutter speed and aperture in video can be done using lua script (with event procedures).
1) To turn off auto-exposure and lock ISO, Tv, Av to their current values use ExpCtrlTool.StopConti() function.
2) To change shutter speed, use SetAE_ShutterSpeed() fuction.  Remember that exposure time cannot exceed 1/fps.
3) To change apreture, use MoveIrisToAv() fuction. Sometimes it can crash camera.
4) I don't know how to change ISO. Maybe SetAE_CdsGainValue() function?
5) To turn on auto-exposure back, use ExpCtrlTool.StartConti() fuction.