What you are describing is alternatives to a Tv priority mode.
If I'm outdoors and want to freeze action I ask for 1/1000. If I want better quality still images, I ask for 1/60. Both well within the range of acceptable ISO values usually.
Quote from: waterwingz on 02 / July / 2014, 08:12:21What you are describing is alternatives to a Tv priority mode.Not really. I'm arguing that a straight Tv mode doesn't serve you very well, especially when the only other variable is ISO.
That's better than nothing, but it seems like what you really want is "use a fast shutter speed until the ISO gets really high" in the first case and "use the lowest ISO possible until the shutter speed gets down to 1/60th" in the second. This sounds a lot like "custom auto ISO", except that you'd want a more convenient and comprehensible UI.
In terms of making CHDK overrides adjust the unset parameters, if someone has a specific ISO set in the Canon menu and overrides the shutter, should CHDK mess with the ISO?
Also, what would make the CHDK-nativ-TV... -modes better compared to script solutions:* When I take a picture I like the camera to show it as long as I want until I take the next one. I also like to be able to zoom into this. To check focus for example. It's not possible with CHDKplus (it's possible to show it for some seconds, but not to zoom and not to show it until I want to take the next picture), but possible with enabled overrides in non-<ALT>-mode.
Quote from: oid_maps on 03 / July / 2014, 09:44:53Also, what would make the CHDK-nativ-TV... -modes better compared to script solutions:* When I take a picture I like the camera to show it as long as I want until I take the next one. I also like to be able to zoom into this. To check focus for example. It's not possible with CHDKplus (it's possible to show it for some seconds, but not to zoom and not to show it until I want to take the next picture), but possible with enabled overrides in non-<ALT>-mode.Actually, I think I could expand CHDplus.lua to do this.
Isn't this a bit messy to re-implement functionality which in general is already there?
No doubt there are egotistical people who believe they know what people want and can hard code such things and make everyone happy.
Cannot think of any of the hard-working CHDK developers that applies to. Of course, the CHDK approach is not suitable for everyone :- "The chdk forum is more like a computer science website - very interesting but also very frustrating [for me]."
I agree. But straight Tv mode is something "standard" that photographers understand and expect. Can you imagine the howl if the next G17 or Canon/Nikon DSLR was released without it?
I don't think we fundamentally disagree on anything other than this "needing" to be fixed. I can't think of a possible use case for setting one of Tv,Av,ND or Sv in the CHDK menus and letting the other three "float". Can you?
If we are going to try to make CHDK get the "correct" exposure when some of these are left unset, I think we need to make it clear that is happening and clearly specify when it does what. If we don't, it will be just as confusing as the current behavior and not much more useful.
I think having a shooting control mode like your chdkplus would be a good thing. The current CHDK UI is really not very good for control of day to day shooting. However, IMO this is a fairly large change that needs to be properly thought out. chdkplus is a nice way to prototype.
Whether the final UI ends up as a script or in the C doesn't really matter to me. I think having the basic controls be standard would be good, OTOH, having a special kind of script that can be your shooting UI could provide a lot more flexibility and one (or more) basic ones could be included in the standard distribution.
Started by mattkime
Started by bikechick
Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)
Started by dzsemx
Started by barret
« 1 2 »
General Discussion and Assistance
Started by waterwingz
« 1 2 ... 14 15 »
Completed and Working Scripts