shooting script using Canon basic ? - page 8 - General Discussion and Assistance - CHDK Forum  

shooting script using Canon basic ?

  • 82 Replies
  • 40160 Views
*

Offline c_joerg

  • *****
  • 1231
Re: shooting script using Canon basic ?
« Reply #70 on: 18 / October / 2021, 12:50:46 »
Advertisements
On N,N2 LCDMsg_SetStr is same color in play & rec mode.
On M100 and G9xII never seen in play mode…
The colors vary from cam to cam. 19 is a green on M100, N2.
 ;)  The upperst line could be overwritten by Canon OSD.

I found the problem. If there is no picture on the SD card at all, then I cannot see any text in play mode. As soon as there is a picture on the card, I can also see the text.
M100 100a, M3 121a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

*

Offline Caefix

  • *****
  • 888
  • Sorry, busy deleting test shots...
Re: shooting script using Canon basic ?
« Reply #71 on: 18 / October / 2021, 13:22:17 »
If there is no picture on the SD card at all, then ...
A never expected exception on Your SD-cards... :lol

In short: make sure you don't use a Canon Basic script and CHDK at the same time.
My card with dual boot:
SD-lock open runs CBasic, locked boots CHDK. If the 1st key != "set", CHDK seems undisturbed, else an existing expand.m is executed.
If I use it locked on other cam, it tries to load wrong diskboot.bin...  :-X

Edit2: Tried both together on M100 : How long "wifi" is pressed matters.
Who gets the <ALT> ?? Lucky timing leads to different menues.
At least Cbasic & Ubasic could coexist...  :haha
« Last Edit: 18 / October / 2021, 14:28:59 by Caefix »
All lifetime is a loan from eternity.

*

Offline Caefix

  • *****
  • 888
  • Sorry, busy deleting test shots...
Re: shooting script using Canon basic ?
« Reply #72 on: 20 / October / 2021, 14:08:43 »
Srsa_4c´s great double-script adapted for N2 ...  :xmas
Run extend.m with <wide>, wait until lens opens, switch modes with <wifi> then
the buttons are different, in default to use <on> for "up" and <play> for down to browse the menu. Run entry with <wide>...
Displays also zoomstep && the mysterious DIM PROPCASE_SUBJECT_DIST2=70 ...
All lifetime is a loan from eternity.

*

Offline Caefix

  • *****
  • 888
  • Sorry, busy deleting test shots...
Re: shooting script using Canon basic ?
« Reply #73 on: 21 / October / 2021, 14:30:40 »
... and for Sx600hs.  :xmas
Quote
// Camera info:
//   DRYOS R54 (DRYOS version 2.3, release #0054+p3)
//   Firmware Ver GM1.00F   // Found @ 0xff0a50f4, "GM1.00F" @ 0xff0a5101
//   Firmware build timestamp: Jul 14 2014 08:40:45
//   Canon PowerShot SX600 HS
//   PLATFORMID = 12934# (0x3286) Found @ 0xfff40040
// Port's propset (7) may be set incorrectly
(If == PS7) SD2==0!, SD1=GetZoomLensCurrentPoint()
Code: [Select]
public sub get_zoom(buf)
'    tmp = lens_get_zoom_point() ==> ASSERT!! EvntProc.c Line 222'
    tmp = GetZoomLensCurrentPoint()
        *buf = tmp
end sub
Edit: Replaced PS7 table in camspec*.m with PS6´s. Now sd1=sd2. Seems Propset 6.

Edit2: Tried every button on Ix500hs & E1. Either crashing or not switching.  :(
Seems to need "Wifi" or PressMySmaphoButton.
The script.c Assert is some syntax error like
Code: [Select]
    *set = 0x0000085E:PressSetButton
    system.create w/o ()
    dim x=1 -- Lua comment
    call_event_proc('GetCameraInformationData') ' is comment, not string.

This together gives a loong beep if bug in LoadScript(CAM) before Script.c Assert...

public sub camspec_init()
        BeepDrive(3) ' Loaded fine beep.'
end sub
« Last Edit: 22 / October / 2021, 16:31:07 by Caefix »
All lifetime is a loan from eternity.


Re: shooting script using Canon basic ?
« Reply #74 on: 29 / November / 2021, 12:10:32 »
I cant load the Script on my EOS m100 since the Firmware Update
Firmware Downgrade not possible

*

Offline Caefix

  • *****
  • 888
  • Sorry, busy deleting test shots...
Re: shooting script using Canon basic ?
« Reply #75 on: 30 / November / 2021, 12:19:12 »
If https://chdk.fandom.com/wiki/Canon_Basic/Card_Setup was successfull it should run. :)
All lifetime is a loan from eternity.

*

Offline c_joerg

  • *****
  • 1231
Re: shooting script using Canon basic ?
« Reply #76 on: 04 / October / 2022, 03:22:16 »
I have a G9II and mainly use it for underwater photography. Unfortunately it doesn't have an underwater white balance like my S110. I know it's not that important with RAW (except for the preview image) but with video it has bigger effects that can no longer be corrected.

Is it possible to set underwater white balance with a Canon Basic Script?
I dumped the camera here  https://chdk.setepontos.com/index.php?topic=14244.0

A manual white balance is not possible with my underwater housing.
M100 100a, M3 121a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

*

Offline reyalp

  • ******
  • 13792
Re: shooting script using Canon basic ?
« Reply #77 on: 13 / October / 2022, 01:55:07 »
Is it possible to set underwater white balance with a Canon Basic Script?
It's theoretically possible that the underwater setting remains a valid propcase WB_MODE value that isn't accessible from the UI.

You would want to figure out:
1) What the propcase ID is for WB_MODE on g9x II
2) what the value of WB_MODE accessible from the UI are
3) what the value of WB_MODE is for underwater, on a camera that has underwater, where the other values are the same as #2.

I guess you already have script that can manipulate propcases.

G9X II is DryOS R59p3. AFAIK there are no ported cams using this version, but the propcase ID is likely to be close to nearby versions.

G7x II (dry 58r10) uses propset 13, where WB_MODE is 282, and the possible values are documented (though unclear if verified) as
0 = Auto, 1 = Daylight, 2 = Shade, 3 = Cloudy, 4 = Tungsten, 5 = Fluorescent, 7 = flash, 11 = under water, 6 = Fluorescent H, 9 = Custom 1, 10 = custom 2


SX730 (dry 59p4) uses propset 12, where WB_MODE is 284, and the available values are:
0 = Auto, 1 = Daylight, 3 = Cloudy, 4 = Tungsten, 5 = Fluorescent, 6 = Fluorescent H, 9 = Custom

set_prop(284,11) on sx730 crashes the cam  :(

Don't forget what the H stands for.


*

Offline c_joerg

  • *****
  • 1231
Re: shooting script using Canon basic ?
« Reply #78 on: 14 / October / 2022, 12:21:51 »
Thank you for taking the trouble to investigate this. Too bad it doesn't work.

I looked at the EXIF data of my existing pictures. If I set the white balance to Fluorescent, I always get the same Kelvin value under the entry 'Color Temp As Shot'.

It's different with white balance underwater. I get values between 8500 and 14000K. The values are then depth dependent. So the underwater white balance seems to be a special automatic white balance.

SX730 (dry 59p4) uses propset 12, where WB_MODE is 284, and the available values are:
0 = Auto, 1 = Daylight, 3 = Cloudy, 4 = Tungsten, 5 = Fluorescent, 6 = Fluorescent H, 9 = Custom

set_prop(284,11) on sx730 crashes the cam  :(

May be 10, one after Custom...
« Last Edit: 14 / October / 2022, 12:24:03 by c_joerg »
M100 100a, M3 121a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

*

Offline reyalp

  • ******
  • 13792
Re: shooting script using Canon basic ?
« Reply #79 on: 14 / October / 2022, 15:58:25 »
It's different with white balance underwater. I get values between 8500 and 14000K. The values are then depth dependent. So the underwater white balance seems to be a special automatic white balance.
I haven't tested extensively, but I believe most of the standard (non-custom) WB modes still do some automatic adjustment, just with different limits and biases.

SX730 (dry 59p4) uses propset 12, where WB_MODE is 284, and the available values are:
0 = Auto, 1 = Daylight, 3 = Cloudy, 4 = Tungsten, 5 = Fluorescent, 6 = Fluorescent H, 9 = Custom

set_prop(284,11) on sx730 crashes the cam  :(

May be 10, one after Custom...
[/quote]
My impression is the numbers mostly stay the same (with occasional shifts between camera generations), even if there's gaps for values that aren't supported on particular camera.

Quote
A manual white balance is not possible with my underwater housing.
Is this because the keys are not physically accessible? If so, it's possible you could use a Canon Basic script, though it would likely be awkward.
Don't forget what the H stands for.

 

Related Topics