The test script starts. After a while the screen freezes. No measured results will be displayed. With grid option the camera tries to draw a grid. After a few seconds freezes the LCD. The AF LED will not be activated.
The MD_Tune.bas script will enable the extra AF LED test code as needed (controlled with the new 'md_af_on_time' script function.
Maybe a silly question, but did you try disabling the canon firmware AF assist?
It probably doesn't like something messing with the AF LED with the shutter half pressed.Can you test this with a script to see if it's the problem?
rem AF Test@title AF Testdo press "shoot_half" sleep 5000 rem Turn ON AF LED set_led 1 0 sleep 1000 rem Turn OFF AF LED set_led 1 1 release "shoot_half"until 0
I've done some tests.AF assist LED on or off makes no difference. MD_tune crashes as described. A shutter half pressed test was ok, whether AF assist LED on or off. set_led(10,1) works fine.The crashes produce random results. Some times the camera switches to playback mode. Then I can see some script console and md test result fracments. Some times the live view is destroyed (only horizontal lines). The script console will never be displayed. I think there is a issue with the viewport.msl
Some test with A810 100b, I'm seeing the similar problems reported by msl:- If grid parameter > 0, camera crashes. Sometimes I can see the grid, sometimes camera crashes before drawing grid.- If grid parameter == 0, script starts, but when motion detected, AF LED turn on and camera crashes.I tried using *vid_get_viewport_live_fb() implementation using viewport_buffers[] but I got the same results.Quote from: reyalp on 16 / February / 2013, 19:57:25Maybe a silly question, but did you try disabling the canon firmware AF assist?I'm using Program Mode. In canon menu I setup: AF Frame = Center, AF-Point Zoom = Off, Servo AF =Off.Quote from: philmoz on 16 / February / 2013, 19:06:35It probably doesn't like something messing with the AF LED with the shutter half pressed.Can you test this with a script to see if it's the problem?This script runs without problems:Code: [Select]rem AF Test@title AF Testdo press "shoot_half" sleep 5000 rem Turn ON AF LED set_led 1 0 sleep 1000 rem Turn OFF AF LED set_led 1 1 release "shoot_half"until 0
What happens if you set 'AF on delay' and 'AF on time' both to 0 in the MD_Tune.bas script?
Quote from: philmoz on 17 / February / 2013, 17:20:24What happens if you set 'AF on delay' and 'AF on time' both to 0 in the MD_Tune.bas script?'AF on delay' has no influence. 'AF on time' = 0 => The script runs without problems like a normal md script (also with grids & cell values). 'AF on time' > 0 => described problems (destroyed bitmap overlay & live view -> frozen display -> crash)msl
Quote from: msl on 17 / February / 2013, 18:07:46Quote from: philmoz on 17 / February / 2013, 17:20:24What happens if you set 'AF on delay' and 'AF on time' both to 0 in the MD_Tune.bas script?'AF on delay' has no influence. 'AF on time' = 0 => The script runs without problems like a normal md script (also with grids & cell values). 'AF on time' > 0 => described problems (destroyed bitmap overlay & live view -> frozen display -> crash)mslCan you comment out each of the code sections that tests 'camera_info.perf.md_af_tuning' and see which one is causing the problem.Phil.
The buffer used to store and display the on-screen stats was too small - so I suspect some memory was being corrupted.
Started by Barney Fife « 1 2 » Completed and Working Scripts
Started by knorke Creative Uses of CHDK
Started by mrShrimp LUA Scripting
Started by mellow-yellow Script Writing
Started by Kestrel1978 General Help and Assistance on using CHDK stable releases
