Thanks for the information. I found out that
=p=require'propcase' set_prop(171,5) works properly. I also realized that Digic II cameras like my S3IS don't have a VIDEO_RESOLUTION prop-thing. My SX40HS with a DIGIC 5 does. I found a hidden underwater white balance mode on my S3IS, and I tried pushing my SX40HS beyond its limits. I discovered, that it can record 1080p at 30fps! You can actually film 1080p at 30fps instead of its default 1080p 24fps! In terms of HD slow motion, that's not going to happen any time soon. I tried 120fps and 240fps at other resolutions, an absolute mess, hahaha! Some worked, but were the same original resolution but had corrupt data at the top of the frame, and some outright crashed the camera. I did manage to find out that you can film at 320x240 in regular mode, which isn't available in the default firmware, as it is used in the 240fps slow motion mode only, so there's that.
But, as I mentioned before, the SX40HS can film 1080p 30fps!!! I might implement a little script people can load within CHDK and engage the hidden mode! Just a warning, It might overheat the camera, I don't know yet, as I've just discovered it, haha! But, I'm going to continue pushing the limits. I want to get to the very bottom of my cameras. I'm still excited about the 1080p 30fps mode. I wonder why they decided to do 24fps instead. The 720p and 480p modes do 30fps, but 1080p is 24fps. It's a bit confusing. But regardless, the camera can do 1080p 30fps. But yeah, HD slow motion isn't going to happen, unless we, meaning I, meaning probably never, hehehe, manage to completely re-write a massive portion of the SX40HS firmware, just to accommodate a larger and specific framebuffer to store all the HD frames, because what I've noticed, what I take away from what I saw when I attempted to do a larger resolution, is essentially, the camera grabs 240 frames per second of 640x480 resolution, and quickly fills up the frame buffer, until it reaches the maximum size of the buffer, and then proceeds to encode the frames into a video file. Since when I changed the resolution, the camera attempted to do 1080p frames at 240 frames per second. Because of this, it just overran the buffer completely, and wrote data into the frame and then encoded the corrupt frames into a video file, with the original low resolution. It's an absolute disaster. This would require a full firmware re-write to accommodate for HD frames. It's not worth it. Perhaps if A.I. becomes advanced enough, I'd be able to just feed the firmware in, and get a full CHDK + Firmware "Merged Frankenstein" that can move stuff around. At the moment, I'm happy that it can at least do 1080p at 30fps. But I will let everyone know if I can engage some hidden features that work, and don't crash the camera.
