SX280 / 275 / 270 porting - page 16 - DryOS Development - CHDK Forum

SX280 / 275 / 270 porting

  • 365 Replies
  • 239928 Views
Re: SX280 / 275 / 270 porting
« Reply #150 on: 19 / January / 2015, 00:03:59 »
Advertisements
Is there away to turn preview off on SX280 while shooting? set_lcd_display(0) doesn't work. There is no view finder on this camera.

*

Offline srsa_4c

  • ******
  • 4451
Re: SX280 / 275 / 270 porting
« Reply #151 on: 19 / January / 2015, 10:35:48 »
Is there away to turn preview off on SX280 while shooting? set_lcd_display(0) doesn't work.
That script command does work, both in playback and shooting mode. What script are you trying to use? Try setting "display time" to 'off' under "review image after shooting" in the Canon menu.
I did not test the reliability of that command in "Eco" mode though.

Re: SX280 / 275 / 270 porting
« Reply #152 on: 19 / January / 2015, 11:44:17 »
try setting "display time" to 'off' under "review image after shooting" in the Canon menu.
That was of a great help to me, thanks. I set Review to "quick". I must say that I was trying to resolve a bigger problem. print() does not display a string in the console until the last iteration of the script. I am printing the number of shots taken by the intervalometer, but it gets displayed only briefly after the last iteration. I was thinking Priview blocks it, but this is something else. Other intervalometers that rely on shoot() print messages fine, but this one I am trying to adopt to my needs uses press() and it doesn't want to display messages. Any ideas?
Code: [Select]
--[[
@title Fast Intervalometer
@param n number of shots
@default n 5
@param t interval between shots in seconds
@default t 2
@param d start delay seconds
@default d 1

--]]
counter=0
-- restore
function restore()
    set_aflock(0)
end

set_console_layout(10, 0, 40, 14)
print("Fast Shooter Started...")
-- switch to shooting mode if necessary
if ( get_mode() == false ) then
  sleep(1000)
  set_record(1)
  while ( get_mode() == false) do
      sleep(100)
  end
end
-- programmable delay to let you get in the picture too
sleep(d+1000)
-- lock in the exposure and focus
press("shoot_half")
repeat
    sleep(50)
until get_shooting() == true
set_aflock(1)

-- fire away with interval
for i=1, n, 1 do
   z = get_tick_count()
   ecnt=get_exp_count()
   press("shoot_full_only")
   repeat
      sleep(20)
   until(get_exp_count()~=ecnt)
   release("shoot_full_only")
   currenttime=get_tick_count()
   print("shot", i)
   sleepfor=t*1000 - (currenttime-z)
   if (sleepfor>0) then sleep(sleepfor) end

end

-- done
restore()
print("...done")

*

Offline srsa_4c

  • ******
  • 4451
Re: SX280 / 275 / 270 porting
« Reply #153 on: 19 / January / 2015, 14:50:37 »
I am printing the number of shots taken by the intervalometer, but it gets displayed only briefly after the last iteration.
"print" prints to the CHDK console. The console is only visible for a limited time (3 seconds) by default. You can find the console settings in Miscellaneous stuff -> Console. This version of CHDK won't allow you to specify more than 30 seconds before it hides the console. However, there's a workaround, see here.

Re: SX280 / 275 / 270 porting
« Reply #154 on: 19 / January / 2015, 17:00:14 »
Quote
print() does not display a string in the console until the last iteration of the script.
The problem is not that the console is displayed briefly after the script completed, but the console is not displayed at all while the script runs. I don't see messages added after each iteration until the last iteration when all messages are displayed. Even with 10sec delays the console is not displayed.

*

Offline srsa_4c

  • ******
  • 4451
Re: SX280 / 275 / 270 porting
« Reply #155 on: 19 / January / 2015, 17:24:37 »
The problem is not that the console is displayed briefly after the script completed, but the console is not displayed at all while the script runs. I don't see messages added after each iteration until the last iteration when all messages are displayed. Even with 10sec delays the console is not displayed.
I tried the script on a different camera and it does exactly the same, CHDK doesn't display anything during the script run. Not sure about the cause, I'm not much into scripting...
Try playing with the console related script commands from here: http://chdk.wikia.com/wiki/CHDK_Scripting_Cross_Reference_Page but it could be that none of those will help.

Re: SX280 / 275 / 270 porting
« Reply #156 on: 20 / January / 2015, 13:01:45 »
In what circumstances get_focus() returns -1? 

*

Offline srsa_4c

  • ******
  • 4451
Re: SX280 / 275 / 270 porting
« Reply #157 on: 20 / January / 2015, 17:18:37 »
In what circumstances get_focus() returns -1?
That's "infinity".
You can easily get it at wide angle, reported focus distances become more accurate toward the tele end of zoom.
You may also get it in playback mode if you try.

The problem is not that the console is displayed briefly after the script completed, but the console is not displayed at all while the script runs.
This issue is probably connected to the fact that the script keeps the camera in half-shoot, but I still don't know why the CHDK display disappears. Or, could it be the AF-lock?
« Last Edit: 20 / January / 2015, 17:30:51 by srsa_4c »

Re: SX280 / 275 / 270 porting
« Reply #158 on: 21 / January / 2015, 08:02:46 »
That's "infinity".
You can easily get it at wide angle, reported focus distances become more accurate toward the tele end of zoom.
Isn't infinity 65530?

Re: SX280 / 275 / 270 porting
« Reply #159 on: 21 / January / 2015, 10:12:38 »
Hi
First of all thank you for the great work you are carrying on: extending the capabilities of my camera gave me
motivation to improve my knowledges about photography.
About 6 months ago, I made use of 'Override Tv' function: if I well remember, I used a 40 sec. exposure time, but it seemed to me that there were malfunctions.
As I was using an older version of the prealpha, I didn't write anything here because newer versions meanwhile were produced.
Nowadays I am running 'sx280hs-102c-prealpha7_1.3.0-3449-full' chdk software on my camera; with this version i used again the 'Override Tv' function shooting in moonlight with a Tv period of 2 min. but the real shooting time was of about 140 sec.
Anyone else has this problem?
Another little trouble is that CHDK menu, when moving and rotating my camera, blinks (more or less as if it was badly linked to the device that sets the camera orientation).
Again, I am asking if it's a problem affecting only the hardware I am owning.
Thank you again for your work.
« Last Edit: 21 / January / 2015, 10:15:12 by Ubicano »
Please, pardon me for possible mistakes: I'm not a native English speaker.
Corrections will be appreciated.

 

Related Topics


SimplePortal © 2008-2014, SimplePortal