CHDK Forum
CHDK Development => General Discussion and Assistance => DryOS Development => Topic started by: TimPeTwo on 29 / October / 2018, 10:49:23
-
Hello,
i would like to offer my labor in creating a port to the SX730. I have general technical and electronical understand, can programm in C , implemented some arduino projects.
Only, i have no working knowledge in creating a CHDK port and don't know where to start. I would be pleased, if some senior developer or project leader could assist in coordinating the next necessary steps.
Cheers
Tim
-
My first step will be to read the firmware version of the camera. This should be pretty easy. I will follow these description:
https://chdk.wikia.com/wiki/FAQ#Q._How_can_I_get_the_original_firmware_version_number_of_my_camera.3F
-
Welcome. Good to see you made it here after you posted on the CHDK Wikia.
You might want to take a look at this thread :
https://chdk.setepontos.com/index.php?topic=13569
If I get a little time, I'm going to try and document the current steps necessary to do a port. In the meantime that thread and the links it contains should be enough to get you started.
-
My first step will be to read the firmware version of the camera. This should be pretty easy. I will follow these description:
https://chdk.wikia.com/wiki/FAQ#Q._How_can_I_get_the_original_firmware_version_number_of_my_camera.3F
The ver.req / vers.req method doesn't work on many modern cameras. You can get the version from a firmware dump, which you will probably want to make anyway.
Use https://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper and when you have the dump file, search for the string starting with "Firmware Ver GM"
-
I also have this camera. I have dumped the firmware and attaching it here:
https://drive.google.com/file/d/18jOTQSY-O_1kLC0UvfTy1uKWzV3uBHU5/view?usp=sharing
-
The ver.req / vers.req method doesn't work on many modern cameras. You can get the version from a firmware dump, which you will probably want to make anyway.
Use https://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper and when you have the dump file, search for the string starting with "Firmware Ver GM"
I did not get it going with the ver.req or vers.req file method. First of all, the SX730HD did not have a DISP button. So i tryed all possible combinations with the FUNC SET button. But without success.
I will give it a try with the Universal Dumper.
-
First of all, the SX730HD did not have a DISP button.
FWIW, new cameras have an INFO button rather than DISP. (DISP is Powershot legacy, INFO comes from DSLRs.) The firmware internally still refers to it as DISP.
finsig_thumb2 needs to be patched to work better on the sx730 dump as it relies on a task named FileWriteTask - which is no longer present in the sx730 firmware.
Index: tools/finsig_thumb2.c
===================================================================
--- tools/finsig_thumb2.c (revision 5108)
+++ tools/finsig_thumb2.c (working copy)
@@ -3607,7 +3607,7 @@
{sig_match_unreg_evp_table,"UnRegisterEventProcTable","MechaUnRegisterEventProcedure"},
{sig_match_evp_table_veneer,"RegisterEventProcTable_alt","RegisterEventProcTable"},
{sig_match_evp_table_veneer,"UnRegisterEventProcTable_alt","UnRegisterEventProcTable"},
-{sig_match_str_r0_call,"CreateTaskStrictly", "FileWriteTask",},
+{sig_match_str_r0_call,"CreateTaskStrictly", "LowConsole",},
{sig_match_str_r0_call,"CreateTask", "EvShel",},
{sig_match_near_str, "dry_memcpy", "EP Slot%d", SIG_NEAR_BEFORE(4,1)},
{NULL},I could check this in as it doesn't affect existing ports, but I'd rather have @reyalp commit it, if possible.
-
I could check this in as it doesn't affect existing ports, but I'd rather have @reyalp commit it, if possible.
If you've verified it doesn't change the output for other firmwares, checking in is totally fine with me. Otherwise I should get to it within a day or so done.
I'm sure there's no special reason I chose FileWriteTask there, it would have just been the first one I happened to see that provided the function.
I'd assume all the existing cameras have LowConsole, but there could be a bad match for other reasons.
-
Added the
full 32MB dump by kmmng from this forum post (https://chdk.setepontos.com/index.php?topic=13573.msg138351#msg138351) to the CHDK P&S FW dumps (https://drive.google.com/folderview?id=0B08pqRtyrObjTy11Y003Sk1lYTQ#list) repository.
-
I dumped the firmware and got the firmware version.
This is what i did:
1) Formated the sd card from within the camera
2) Preparing the sd card on a Debian Linux maschine. Using the script makeScriptCard.sh from https://chdk.wikia.com/wiki/Canon_Basic/Card_Setup to write the string SCRIPT to the boot sector
3) Took the Universal dumper https://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper and saved the script as the file 'extend.m' on the sd card.
4) Started the camera in Play Mode.
As a result i got the file CBDUMPER.LOG and PRIMARY.BIN.
Than (on my linux box) :
$ strings PRIMARY.BIN | grep -C2 "Firmware Ver"
Feb 28 2017
13:26:12
Firmware Version 1.00
Firmware Ver GM1.00B
BuildInfo.c
CheckSum Skip (no %s)
The Firmware Version does not match with that posted from kmmng, who commited a 1.00C Firmware.
Here is a link to the dump: https://github.com/TimPeTwo/chdk_canon_sx730hs_port/blob/master/fw_dump/PRIMARY.BIN
-
The Firmware Version does not match with that posted from kmmng, who commited a 1.00C Firmware.
Fortunately, the main part of the firmware is identical in 100b and 100c (only difference is the build timestamp and the version strings). The loaders differ (that happens quite often lately), but that's not a concern.
edit:
I don't think the following wikia page was mentioned in this thread: http://chdk.wikia.com/wiki/Digic_6_Porting
-
I just found out that the sigfinder still isn't working correctly on the sx730 dump and some of the stubs it outputs are incorrectly identified. Anyone trying to work on a port is advised to double check stubs_entry.S entries.
-
I just found out that the sigfinder still isn't working correctly on the sx730 dump and some of the stubs it outputs are incorrectly identified.
If you have some examples handy, I can take a look.
-
If you have some examples handy, I can take a look.
The one that caught my eye is GetEventFlagValue having the same address as DebugAssert (the latter is okay). Plus, there seems to be another copy of CreateTaskStrictly which is used for creating PhySw.
edit:
The other CreateTaskStrictly is not a copy on D7 cams. "HdmiCecTask" gives a better match finding it (there are several occurrences of the "PhySw" string and sig_match_str_r0_call can't cope with that).
-
If you have some examples handy, I can take a look.
The one that caught my eye is GetEventFlagValue having the same address as DebugAssert (the latter is okay). Plus, there seems to be another copy of CreateTaskStrictly which is used for creating PhySw.
edit:
The other CreateTaskStrictly is not a copy on D7 cams. "HdmiCecTask" gives a better match finding it (there are several occurrences of the "PhySw" string and sig_match_str_r0_call can't cope with that).
Thanks. I added the other CreateTaskStrictly for Dry R59 and later as CreateTaskStrictly_alt, which will be used to search for tasks in addition to the others. The even flag functions should be sorted out too.
I'm still working on some other issues. Should definitely not blindly trust the found sigs on these cams. I've thought about adding some kind of validating or scoring logic to finsig_thumb2, but it's worked well enough up to now that it hasn't felt too urgent.
-
If someone could provide RAM dump(s), we could find out whether the issue (https://chdk.setepontos.com/index.php?topic=12672.msg125582#msg125582) (missing bitmap buffer) philmoz encountered on the G5x is affecting this camera.
The following Canon Basic (http://chdk.wikia.com/wiki/Canon_Basic) script can be used to dump the whole camera RAM (512 MB). The card needs to be set up like this (http://chdk.wikia.com/wiki/Canon_Basic/Card_Setup).
' dump RAM to A/RAM.BIN
' log to A/CBDUMP.LOG
' a working script blocks the camera until finished
DIM startaddr=0
' following is the size of RAM to dump (has to be adjusted to not exceed the amount of camera RAM)
DIM dumpsize=0x20000000
DIM lcdmsg=0
DIM msgstr=0
DIM fname="A/RAM.BIN"
private sub RegisterProcs()
if System.Create() = -1 then
SystemEventInit()
end if
if ExecuteEventProcedure("UI_RegistDebugEventProc") = -1 then
ExecuteEventProcedure("UI.CreatePublic")
end if
end sub
private sub InitMsg()
lcdmsg = ExecuteEventProcedure("LCDMsg_Create",10,10,"Started",2)
if lcdmsg >= 0 then
LCDMsg_ChangeColor(lcdmsg,2)
end if
msgstr = AllocateMemory(80)
end sub
private sub PutMsg(msg)
if lcdmsg >= 0 then
LCDMsg_SetStr(lcdmsg,msg,0)
end if
msgfile = Fopen_Fut("A/CBDUMP.LOG","a")
if msgfile <> 0 then
Fwrite_Fut(msg,strlen(msg),1,msgfile)
Fwrite_Fut("\n",1,1,msgfile)
Fclose_Fut(msgfile)
end if
end sub
private sub Initialize()
RegisterProcs()
InitMsg()
PutMsg("Started")
sprintf(msgstr,"%0X",startaddr)
PutMsg(msgstr)
dumpfile = Fopen_Fut(fname,"w")
if dumpfile <> 0 then
Fwrite_Fut(startaddr,dumpsize,1,dumpfile)
Fclose_Fut(dumpfile)
Wait(500)
PutMsg("done")
else
PutMsg("file error")
end if
FreeMemory(msgstr)
end sub
You can make a dump in either playback or rec mode, but you need to name the script file accordingly.
A script named extend.m can be started by pressing SET in playback mode. A script named autotest.m can be started by holding SET and pressing RIGHT in rec (shooting) mode.
Before you make a dump, make sure there is a visible JPEG (or live view when in rec mode) displayed on the LCD. Also make sure that there is some visible Canon overlay (exposure info, icons and such).
Note that the dump may include file(s) from the card and whatever is displayed on the LCD, so remove anything from there that you don't want to publish.
Compress the dump before sharing it.
-
I have done the dump, it is here:
https://drive.google.com/open?id=1Gk3MygHr_ti4F183bQIgR5CSTeXP-vA9
-
I have done the dump, it is here
Thanks. All needed framebuffers are present in the dump (and their location matches what I've seen in an sx720 dump).
A list of selected locations is attached for use with this (https://chdk.setepontos.com/index.php?topic=12721.0) program.
-
I have done the dump, it is here
Thanks. All needed framebuffers are present in the dump (and their location matches what I've seen in an sx720 dump).
A list of selected locations is attached for use with this (https://chdk.setepontos.com/index.php?topic=12721.0) program.
Just Wondering if anything is working? I unfortunatly cant help, but i send all my morale support
-
I've started a port for this camera, firmware 100d (https://chdk.setepontos.com/index.php?topic=288.msg142007#msg142007). Assuming I get it working, ports for the other versions will follow.
Current status is it boots diskboot or fi2 and runs a blinker task.
FI2 encoding is d4j
dancingbits is 17
Green LED is usual 0xd20b0994 (there is also an orange LED in the same spot, related to charging)
A couple of notable changes from a CHDK perspective
* CreateTask is in ROM, like newer digic 4 cams. CreateTask_low appears to be hookable in the same way.
* The camera supports USB charging (NB micro USB, not mini like earlier cams), and automatically powers on when USB power is present. This may be nice for automation, multicam rigs etc, but has potential for interactions with CHDK boot process. It does appear to boot normally with diskboot when USB is plugged in to a computer.
Perhaps related to the USB charging stuff, windows doesn't recognize this camera (with totally stock firmware) at all on my usual Kensington USB3 hub. It works fine on other USB2 and 3 hubs. The hub has misbehaved in other ways so is likely at fault, but all my other powershots work with it.
-
100d port added to the autobuild in r5347. Please report any bugs here.
I should have test builds for the other known firmwares fairly soon. 100b, 100c, and 100e also in autobuild.
From the notes.txt
General camera and CHDK port information
****************************************
Default alt button is PLAY. VIDEO and WIFI may also be used. Long press to access the original function of the assigned alt button.
SX730 has an adjustable aperture and does not have an ND filter.
SX730 automatically powers on when connected to a USB host. It enters charging mode when connected to a USB charger. CHDK does not appear to interfere with these functions, but it has not been tested extensively. Beware that applying USB power with the CHDK USB remote enabled could cause the camera to power on and extend the lens.
The framing assist key is assigned to ERASE for CHDK functionality and script.
The half press shortcut for zebra toggle is MENU
The half press shortcut for histogram toggle is disabled, due to limited keys.
Subject distance (focus) override is supported in AFLock and MF, not in AF.
~800 KB of free RAM is available. This should be enough for normal operation.
set_led id 0 controls the green indicator LED, 1 controls the AF assist LED.
Control of the orange charge indicator is not currently available.
TESTED
******
- PTP operation, including live view
- Shutter, aperture and ISO override
- Focus override. MF or AF lock is required
- Bracketing in continuous mode
- llibtst.lua (see known bugs)
- hooktest.lua (see known bugs) fixed
- ISO base, real/market conversion
- Propset values
- Fast MD - MD_Tune.bas response times 40-70ms
- USB remote (see known bugs)
- "Firm update" boot
- Dark frame subtraction control
NOT IMPLEMENTED
***************
- Jpeg remote shoot. File write task does not exist in this firmware.
- Video controls (movie_rec task)
- Reboot with firmware update file
- Script hard shutdown (shut_down(1))
- Changing UI resolution for HDMI out
- exp_drv task. Shutter speeds shorter than 1/3200 likely do not work. Long exposures up to 1024s likely work, but have not been tested. implemented in r5350
OTHER ISSUES
************
- Display updating is ugly / has usual Digic 6 limitations
- Flashes a lot if the Canon firmware is updating the display
- Edge overlay does not erase properly when shown live
- Zebra "Draw Over Zebra" and Restore options are non-functional
- Some games don't draw correctly
- DNG color matrix is incorrect (copied from sx60hs) but usable
KNOWN BUGS
**********
- USB remote may shoot multiple shots in continuous mode (general CHDK issue)
- Timestamps on files created before a shot is taken may be 1/1/2000 (general CHDK issue) This causes a failure in llibtst.lua - This was actually a different bug, fixed in r5383
- Script using shoot hooks in continuous mode (such as hooktest.lua) may trigger a HardwareDefect error 14. This appears to be avoided if the shoot key is released immediately after hook_shoot becomes ready for the final shot. - This should be fixed in r5348
-
edit: These have been enabled in the autobuild, based on confirmation 100b works. I'd still like a report from a 100c user, although there's very little chance it will be different from 100b.
---
Here's a test build for SX730 firmwares 100c and 100b.
I don't have either of these firmwares, so it's completely untested. If I didn't mess up, it should work like the 100d port. Both diskboot and firm update loading are supported.
Ping earlier posters @TimPeTwo @kmmng @Oliver Helberg
-
Hello,
Can this version for 100b and 100c be used also for 100e?
Thanks
-
Can this version for 100b and 100c be used also for 100e?
That's very unlikely. Please make a dump (https://chdk.fandom.com/wiki/Canon_Basic/Scripts/Dumper) of your firmware and upload it to some file sharing site.
-
Hello,
I checked that my SX730 HS has firmware version 100b. I've made a firmware dump of it:
https://drive.google.com/file/d/14yNyvzBlxk1hvp3P8aepqVQOWc2ZmPQQ/view?usp=sharing (https://drive.google.com/file/d/14yNyvzBlxk1hvp3P8aepqVQOWc2ZmPQQ/view?usp=sharing)
-
Hello,
I checked that my SX730 HS has firmware version 100b. I've made a firmware dump of it:
Thanks. We already had a dump of 100b. From a CHDK point of view, it should be compatible with 100c. You can try the build in post 21 (https://chdk.setepontos.com/index.php?topic=13573.msg142119#msg142119) above.
-
You can try the build in post 21 (https://chdk.setepontos.com/index.php?topic=13573.msg142119#msg142119) above.
I sucessfully booted this build using 'firmware update' and used info from this post (https://chdk.setepontos.com/index.php?topic=13573.msg142107#msg142107) as a check-list for quick testing. Most of the features listed as 'tested' seem to work fine.
- Display updating is ugly / has usual Digic 6 limitations
This flickering is actually the most noticeable issue (hardware problem as far as I understand).
- DNG color matrix is incorrect (copied from sx60hs) but usable
I've checked this and to my mind it's only a little bit off and not something that cannot be fixed by post processing. Overall, RAW/DNG1.1/DNG1.3 is Ok.
-
I sucessfully booted this build using 'firmware update' and used info from this post (https://chdk.setepontos.com/index.php?topic=13573.msg142107#msg142107) as a check-list for quick testing. Most of the features listed as 'tested' seem to work fine.
Great, thanks. If it boots and shoots, it should be as functional as the 100d port. I've enabled 100b and 100c in the autobuild.
This flickering is actually the most noticeable issue (hardware problem as far as I understand).
It's more of a how CHDK is hacked into the display code issue, but we don't currently have a solution. Switching to play when you are adjusting CHDK settings avoids the worst of it.
- DNG color matrix is incorrect (copied from sx60hs) but usable
I've checked this and to my mind it's only a little bit off and not something that cannot be fixed by post processing. Overall, RAW/DNG1.1/DNG1.3 is Ok.
Yeah, it's the same as I used on sx710, which I believe has essentially the same sensor.
-
Hallo, hier ist canon powershot sx730 hs Firmware 100E Dump https://drive.google.com/drive/folders/1c9HDJrF8ZdcfdQy0QdFYQjwsuZJUKoWx?usp=sharing
-
Hallo, hier ist canon powershot sx730 hs Firmware 100E Dump https://drive.google.com/drive/folders/1c9HDJrF8ZdcfdQy0QdFYQjwsuZJUKoWx?usp=sharing
Thanks. It should be compatible with the 100d port. Here's a test build.
edit:
Confirmed working, test build removed
-
Hallo, hier ist canon powershot sx730 hs Firmware 100E Dump https://drive.google.com/drive/folders/1c9HDJrF8ZdcfdQy0QdFYQjwsuZJUKoWx?usp=sharing
Thanks. It should be compatible with the 100d port. Here's a test build.
Thanks, great work :D
-
I've enabled 100b and 100c in the autobuild.
Thanks! That's great!
Re-tested 100b with build 5365 from the trunk and it works the same as the previous r5352 from post 21 (https://chdk.setepontos.com/index.php?topic=13573.msg142119#msg142119). I also successfully checked USB remote (using powerbank) and Canon app for operating the camera and downloading photos.
-
Thanks, great work :D
Thanks, added to the autobuild :xmas
-
Thanks, added to the autobuild :xmas
Thank you for everything !
-
In r5369 I fixed a bug in key handling that caused zoom presses in alt mode to be seen by the canon firmware, and masked a bit that shouldn't have been. Updating is recommended.
-
// :-* Sx
610 & 620 : maybe same problem solvable?
// Sx610 Yes :xmas , 620 Yes in progress :xmas
// Both done, nice side-effect.
-
In r5383, I fixed a bug that affected the 'stat' function, making raw files show up with the year 2000. (actually, srsa_4c fixed the bug, I just missed the define in the port :-[)
-
All those who have taken the trouble to give the SX730 the long-awaited chdk avery big THANK YOU! :)
I love the newer travel zoom cameras, but I have always really missed chdk there.I came by chance today and am extremely happy that the version DE 100c-1.5.0-5396 works for me so far.You definitely made my day.
-
Great job.
but
I'm getting 'unsupported propset 12' error on a default script
-
Good day to all!
For some reason I can’t find the link to the firmware on the page http://mighty-hoernsche.de
Where is it?
-
Try the autobuild site for the recent development: http://mighty-hoernsche.de/trunk/
msl
-
Great job.
but
I'm getting 'unsupported propset 12' error on a default script
Thanks for mentioning that. I've updated the script to include propset 12
-
Firstly, thanks for porting CHDK to this camera!
Apologies if this is the wrong place to ask, but is it currently possible to get clean HDMI out from the camera, or is that not implemented? Can't figure it out.
Thanks!
-
Apologies if this is the wrong place to ask, but is it currently possible to get clean HDMI out from the camera, or is that not implemented? Can't figure it out.
Unfortunately, this camera does not support HDMI out in shooting mode at all. We haven't found any way to enable that on cameras which don't support it.
-
Try the autobuild site for the recent development: http://mighty-hoernsche.de/trunk/
msl
I am new to this forum, so forgive me if my question is stupid.
I checked the autobuild and I cannot find the SX730HS in stable build.
However, I do find it in unstable build download page.
Does that mean only unstable built is available?
How usable is the unstable build at the moment?
I just want to be able to take RAW and have long exposure.
I dont care much about video.
Thanks in advance.
Additional information: I am looking to buy this camera as I like the small form factor and 40x zoom. Would there be another model that has similar function but has a stable built?
-
I am new to this forum, so forgive me if my question is stupid.
I checked the autobuild and I cannot find the SX730HS in stable build.
However, I do find it in unstable build download page.
Does that mean only unstable built is available?
Yes, currently, all digic 6 ports are only available in the "unstable"
How usable is the unstable build at the moment?
I just want to be able to take RAW and have long exposure.
Both those features work on sx730, and it's fine for day to day use. Actually the "unstable" is only unstable because I've been procrastinating making the stable...
Additional information: I am looking to buy this camera as I like the small form factor and 40x zoom. Would there be another model that has similar function but has a stable built?
Not in that form factor. There are other long zoom cameras, but they are larger.
-
I am new to this forum, so forgive me if my question is stupid.
I checked the autobuild and I cannot find the SX730HS in stable build.
However, I do find it in unstable build download page.
Does that mean only unstable built is available?
Yes, currently, all digic 6 ports are only available in the "unstable"
How usable is the unstable build at the moment?
I just want to be able to take RAW and have long exposure.
Both those features work on sx730, and it's fine for day to day use. Actually the "unstable" is only unstable because I've been procrastinating making the stable...
Additional information: I am looking to buy this camera as I like the small form factor and 40x zoom. Would there be another model that has similar function but has a stable built?
Not in that form factor. There are other long zoom cameras, but they are larger.
Thanks for the information.
I think I am going to get this model and explore CHDK.
I will pull out my point and shoot for night sky picture while others are using their big DSLR.
-
Thanks for the information.
I think I am going to get this model and explore CHDK.
I will pull out my point and shoot for night sky picture while others are using their big DSLR.
FWIW, the SX730 and all similar models have quite "slow" lenses, F8 at full zoom. You'll definitely need a tracking mount to do much astrophotography at the long end of the zoom, and even at the wide end you'll see trailing with exposures over 30s or so.
-
Thanks for the information.
I think I am going to get this model and explore CHDK.
I will pull out my point and shoot for night sky picture while others are using their big DSLR.
FWIW, the SX730 and all similar models have quite "slow" lenses, F8 at full zoom. You'll definitely need a tracking mount to do much astrophotography at the long end of the zoom, and even at the wide end you'll see trailing with exposures over 30s or so.
I will probably do ISO 3200 24mm 3.3 20s. So no need to worry about star trailing.
Thanks.
-
I am trying to get my version number and it seems that ver.req and vers.req method does not work at all.
So I get the dump with extend.m script.
But then I have no idea how to get the firmware version number from the script.
Help!
-
I am trying to get my version number and it seems that ver.req and vers.req method does not work at all.
So I get the dump with extend.m script.
But then I have no idea how to get the firmware version number from the script.
Help!
FWIW You can use an application like ACID http://www.zenoshrdlu.com/acid/acid.html to get the version number from exif of an image, or an application like Stick or CHIMP to prepare a card with the right tool https://chdk.fandom.com/wiki/Prepare_your_SD_card
If you already made a dump, you can also get it by searching for a string starting with "Firmware Ver GM", using the strings and grep, or a hex editor or a text editor that doesn't mind binary files.
-
I am trying to get my version number and it seems that ver.req and vers.req method does not work at all.
So I get the dump with extend.m script.
But then I have no idea how to get the firmware version number from the script.
Help!
FWIW You can use an application like ACID http://www.zenoshrdlu.com/acid/acid.html to get the version number from exif of an image, or an application like Stick or CHIMP to prepare a card with the right tool https://chdk.fandom.com/wiki/Prepare_your_SD_card
If you already made a dump, you can also get it by searching for a string starting with "Firmware Ver GM", using the strings and grep, or a hex editor or a text editor that doesn't mind binary files.
Thanks. I finally get my version number and got CHDK working.
I realize the RAW files I get is distorted.
I tried to use lightroom to correct the distortion. But even when I pull the bar all the way, it is still not completely corrected.
What software you use to correct the distortion? Is there a profile for this camera somewhere?
-
I tried to use lightroom to correct the distortion. But even when I pull the bar all the way, it is still not completely corrected.
What software you use to correct the distortion? Is there a profile for this camera somewhere?
FWIW, I use raw therapee (https://rawtherapee.com/) with a few presets I made by eyeball at various focal lengths. But I mostly only use that camera at the long end of the zoom.
-
I tried to use lightroom to correct the distortion. But even when I pull the bar all the way, it is still not completely corrected.
What software you use to correct the distortion? Is there a profile for this camera somewhere?
FWIW, I use raw therapee (https://rawtherapee.com/) with a few presets I made by eyeball at various focal lengths. But I mostly only use that camera at the long end of the zoom.
Thanks. I will try that.
-
Thanks all for the work in making this port work.
Is there any chance of making "Filewrite Task" support working with this port, or is there an architectural reason this isn't working?
Thanks again!
Joe
-
Is there any chance of making "Filewrite Task" support working with this port, or is there an architectural reason this isn't working?
Canon changed how they write files, so filewrite task doesn't exist on this model.
That doesn't necessarily mean it's impossible to implement remote shoot, filewrite was replaced with something else. I think a lot of it happens in task_RdWrJobExec now. I poked around that a bit, but haven't got around to really digging into it yet.
-
I appreciate the quick response. I will plan my workflow accordingly.
And once again, thanks for the work on this. Those of us out there that use CHDK appreciate all of you with the skills to make these ports.
Joe