I'd like to test it, but can not made SD card bootable. I have tried STICK, that find my test100e.zip file, but after that it crashed and did not do anything. I can not install CHDK with the firmware update mode either, because I did not find the firmware update option in the menu of the camera.How to install CHDK for SX 700? thank you
I have made some test:
- Menu is flickering in shooting mode (1 by sec), but if you do not press shutter button after starting the camera and you are in playback mode, it is not flickering
- the text in the upper left corner (red characters) are bit covered on the right side
- Grid works, but can not change its colour (not really a need)
- Auto ISO is great!!!!- DNG Crop Size: Active/Full/JPEG gives the same picture area (might be not a problem)
- every second DNG file is corrupt (even with 10 second of gap), size normal, but in its upper area (about 70-80%) is only noise with bluish color
- every games loads, in Mastermind the rows are covering each other (did not try to finish any of the games)
well, something happened, it is not flickering any more, but after restarting it flickers again
I spent some time review the code on github. Very good work, especially for a first time port on a digic 6 camera
Some comments:stubs_min.S + lib.ccurrent_viewport_buffer and viewport_buffers are FAKEDEF. If these aren't found, vid_get_viewport_live_fb in lib.c should just return 0 without referring to them. The rest of CHDK will then fall back to vid_get_viewport_fb. Getting these values correct will allow fast motion detection to work, and reduce latency in chdkptp live view.
lib.chook_raw_image_addr just returns the first raw buffer. If the camera actually uses multiple raw buffers, the image will sometimes contain the wrong data. If you tested using a static scene, it might not be obvious. raw_buffers and active_raw_buffer are listed as "found" in stubs_min.S, so it may just be a matter of hooking them up.The camera is probably more likely to use multiple buffers when shooting in continuous mode.
main.cNUM_FL looks like it is ~2x the expected value. I had this mistake in an earlier version of the sx710 code. It should be the maximum zoom_pos value you get at full optical zoom. If it's too high, set_zoom(get_zoom_steps()) will crash.screen_opened / screen_rotated are only for cameras with articulated LCD.
platform_camera.hCAM_HOTSHOE_OVERRIDE should not be defined, camera doesn't have a hotshoe.Have focus overrides been tested? The CAM_SD_OVER_IN* defines should be set based on testing.If you use a color matrix from a cam with MATRIX1 and MATRIX2, it's probably a good idea to use both (I had just one in the sx710 port for a while, but I think the results with fully copy of sx60hs are better)CAM_HAS_SPORTS_MODE should be defined if MODE_SPORTS is in the modemap*ACTIVE_AREA can be found using the procedure at the end of https://app.assembla.com/spaces/chdkptp/wiki/DNG_Processing
platform_kbd.hThe BATTCOVER and HOTSHOE flags aren't relevant to this port.
kbd.cKEY_FRAMING_ASSIST is commented out. From pictures it looks like this camera has one, so it should be found and included.
stubs_entry.S + shooting.Some modes are listed as "In firmware but not in current modemap"If you can't find them through the canon UI, you can try setting them using set_capture_mode_canon()Some might be internal modes that just crash or aren't settable.
notes.txtShould be updated to reflect status of this port.
Quote from: mastodon on 31 / December / 2017, 17:38:41- Menu is flickering in shooting mode (1 by sec), but if you do not press shutter button after starting the camera and you are in playback mode, it is not flickering I could be wrong but I believe this is a common issue to Digic 6 camera CHDK ports.
Quote Grid works, but can not change its colour (not really a need)Thanks for checking this feature out. I had not tested this. On my camera, the grid feature does not seem to be working properly. I will check it out.
Grid works, but can not change its colour (not really a need)
Quote- DNG Crop Size: Active/Full/JPEG gives the same picture area (might be not a problem)I will check this out. There are likely settings I need to change.
- DNG Crop Size: Active/Full/JPEG gives the same picture area (might be not a problem)
#define CAM_RAW_ROWPIX xxxx #define CAM_RAW_ROWS yyyy #define CAM_JPEG_WIDTH wwww #define CAM_JPEG_HEIGHT zzzz #define CAM_ACTIVE_AREA_X1 nn #define CAM_ACTIVE_AREA_Y1 mm #define CAM_ACTIVE_AREA_X2 iiii #define CAM_ACTIVE_AREA_Y2 kkkk
Quote- every second DNG file is corrupt (even with 10 second of gap), size normal, but in its upper area (about 70-80%) is only noise with bluish colorI am not having this problem. I shot 10 dngs in a row both on the camera as well as with chdkptp. There were no issues with any of them. Can you describe a little bit more your situation? What program are you using to view the DNG files. Maybe a different card.
lib.chook_raw_image_addr just returns the first raw buffer. If the camera actually uses multiple raw buffers, the image will sometimes contain the wrong data. If you tested using a static scene, it might not be obvious.
You can use CAPTSEQ_DEBUG_LOG with chdkptp dlstart / dlgetcam to see whether your raw_buffers/active_raw_buffer give reasonable looking results.
01017710: UI:Capture Sequence Start: m:31 arb:1 rb:0x45782700 i:066101020380: UI:Capture Sequence Start: m:43 arb:0 rb:0x43f83ae0 i:0662
Started by LogicSmith
General Discussion and Assistance
Started by KevB
« 1 2 ... 31 32 »
Started by sylikc
« 1 2 ... 68 69 »
General Discussion and Assistance
Started by antwtna
Started by Angel9999l5
General Help and Assistance on using CHDK stable releases