chdkptp - alternative ptp client

reyalp

tpont
Yes, this is likely the biggest factor. I'll look around for a replacement to the A490 camera. Do you, or anyone else reading, know if some newer models like the powershot A2500 (in CHDK alpha I read) has the filewrite feature, meaning it is possible that they in the future may support remote shoot?

See the FWT column in this table http://chdk.wikia.com/wiki/CameraFeatureTable

However, if you get a camera that isn't supported, there is a fair chance someone will be willing to add support.

reyalp
Ok. In continous remote shooting ( rs -cont=20 ) the A490 cycle is around 1.8 seconds per shoot which is very good.

If you can accept fixed focus and exposure, it may be possible to create a "synchronized continuous" mode, where the camera operates in continuous mode, but waits until it gets a signal from the pc for each shot. Doing this correctly would probably require some changes in the core (like what lapser did for continuous mode timelapse) but it might be possible to get fairly close by not downloading something until you are ready for the next shot. The camera jpeg saving can overlap with shooting (up until the raw hook, where the remote shoot code forces a wait), so this might have to be done using the DNG header.

tpont

reyalp
See the FWT column in this table http://chdk.wikia.com/wiki/CameraFeatureTable
However, if you get a camera that isn't supported, there is a fair chance someone will be willing to add support.

Ok thanks.

reyalp
If you can accept fixed focus and exposure, it may be possible to create a "synchronized continuous" mode, where the camera operates in continuous mode, but waits until it gets a signal from the pc for each shot. Doing this correctly would probably require some changes in the core (like what lapser did for continuous mode timelapse) but it might be possible to get fairly close by not downloading something until you are ready for the next shot. The camera jpeg saving can overlap with shooting (up until the raw hook, where the remote shoot code forces a wait), so this might have to be done using the DNG header.

That sounds very good. I already lock the focus manually in the setup steps and the lighting conditions do not change between the shoots.

tpont

Let me add that I'd happily beta test attempts at such a "synchronized continuous" mode if anyone takes a shot at it.

reyalp

tpont
Let me add that I'd happily beta test attempts at such a "synchronized continuous" mode if anyone takes a shot at it.

The "shooting hooks" feature recently added to the trunk should enable this. I'll see if I can put something together.

bigboss97

I just started using chdkptp. Are there shortcut keys assigned to the buttons. So I can control the camera using keyboard?

Phuoc

reyalp

bigboss97
I just started using chdkptp. Are there shortcut keys assigned to the buttons. So I can control the camera using keyboard?

Not currently, but it's a good suggestion.

bigboss97

reyalp
Not currently, but it's a good suggestion.

Thanks, it should be a simple enhancement for developers. But it would be a giant leap for users 😀 because then I can use e.g. WiiMote to control my camera.
Hope to see the feature very soon, thanks.

bigboss97

This is what I see with my S100, the image is a bit distorted:

Can I do anything with settings to get it right?

2nd question, can I flip the viewfinder left-to-right? It's easier to use a mirror image when I turn the camera to me.

reyalp

bigboss97
Can I do anything with settings to get it right?

No, it needs to be fixed in the CHDK code. It looks like there are two things missing:
1) The bitmap palette for the UI colors
2) The viewfinder size and offsets. These might change depending on the aspect ration selected on the camera, so you may be able to find one that looks better.

If you can create a "quick dump" from the debug tab, that may make it easier for us to fix.

2nd question, can I flip the viewfinder left-to-right? It's easier to use a mirror image when I turn the camera to me.

Not currently. It would probably be fairly straightforward to do in code.

bigboss97

reyalp

If you can create a "quick dump" from the debug tab, that may make it easier for us to fix.

Dump attached.

chdk_3236_20140113_222155.zip

625.09KB

reyalp

reyalp

tpont
Let me add that I'd happily beta test attempts at such a "synchronized continuous" mode if anyone takes a shot at it.

The "shooting hooks" feature recently added to the trunk should enable this. I'll see if I can put something together.

I added some code to do this in chdkptp r479. There are no changes in the C code since the last release, so you can just update the lua files if you want.

This is very preliminary. It doesn't do much error checking, and has some hard coded timeouts.

To load the new code use
!require'extras/rsint'.init()
This adds a new cli command call rsint. This takes options similar to the 'rs' command, but instead of shooting right away, it makes the camera wait at the "shutter" hook and gives you a prompt.

entering s shoots, downloads and prompts again when it's done
entering l shoots and exits rshoot mode.

The is no way to quit without shooting the final shot, because at the point the hook is called, the camera is already committed to taking the shot. It would be nice to have a hook after the jpeg is done before the next shot is started, but I'm not sure this is possible given that the jpeg saving can overlap with the next shot in continuous mode.

It doesn't allow you to adjust exposure while between shots, but this could be added.

reyalp

bigboss97
This is what I see with my S100, the image is a bit distorted:

I had a closer look at this, and it appears you are using a quite old build (protocol 2.4 on the camera)

It looks like all the code should be there, so can you try the latest 1.2 build from http://mighty-hoernsche.de/ ?

bigboss97

reyalp

bigboss97
This is what I see with my S100, the image is a bit distorted:

I had a closer look at this, and it appears you are using a quite old build (protocol 2.4 on the camera)

It looks like all the code should be there, so can you try the latest 1.2 build from http://mighty-hoernsche.de/ ?

Installed s100-101a-1.2.0-3317, all display issues fixed. Thank you so much.

tpont

reyalp
I added some code to do this in chdkptp r479. There are no changes in the C code since the last release, so you can just update the lua files if you want.

Nice, will try it out when I find some more spare time.

poussin

Hello
Using A2200 chdk build 1.3.0.3152 and chdkptp build r438, I wanted to store the video directly on the PC.
The way , I found is to dump frames with debug.
Although I am able to play the dump from files , I would like to be able to extract individual frames from the dump file.
Can you advise on this topic ?
Cordially

reyalp

poussin
Using A2200 chdk build 1.3.0.3152 and chdkptp build r438, I wanted to store the video directly on the PC.
The way , I found is to dump frames with debug.

This doesn't have the same quality as actual video files recorded by the camera. Currently there is no way to record actual camera video over USB.

Although I am able to play the dump from files , I would like to be able to extract individual frames from the dump file.

I guess you want to convert frames in the dump file to some kind of image format? There is currently not a command do to this, but it is something I would like to add. Most of the pieces are there.

If you explain exactly what you want to do, I may be able to come up with something.

The "screenshot" button saves a ppm image of the current live view display. In theory you could just call this every frame somewhere in redraw_canvas, but the function written in lua and isn't optimized at all so it would be quite slow.

You could also write your own code to read the dump file. The dump is essentially the live view data stream, plus a small header, and a per frame header giving the frame size. The live view stream is described in
https://tools.assembla.com/svn/chdk/trunk/core/live_view.h
In addition to the image data for the viewport and/or bitmap, it also includes information about the dimensions, aspect ratio, and position on the camera screen. These are necessary to display a correct image, and can change at runtime.

The dump header is described in chdku.lua live_dump_start https://tools.assembla.com/svn/chdkptp/trunk/lua/chdku.lua

The functions in liveimg.c https://tools.assembla.com/svn/chdkptp/trunk/liveimg.c are used to convert the camera YUV data to planer RGB. The scaling and positioning of the RGB data is done using CD code in gui_live.lua.

waterwingz

poussin
Hello
Using A2200 chdk build 1.3.0.3152 and chdkptp build r438,

@poussin : if you have some time, we still need test results for the A2200 manual focus test.

Instructions and download links are here : Setting focus from scripts or menus : please run this script and report back

TIA !

NaveedESahar

Hi Everyone! Dont know if I'm interrupting with some off the topic question, but I'm having some issues in my camera while using ptp commands.

I want to delete all files in my camera using ptpcam.exe. What i'm doing is first executing the command ptpcam -D (which is used to delete all files in camera). then i'm using command ptpcam --chdk="reboot" to reboot camera. But in case I have more then 1 files (yes only 1) to be deleted, camera hangs and doesn't recognize any command succeeding ptpcam -D. After that, only way to get camera to normal state is remove and insert the battery again. Any guide for solution?

Regards.

poussin

waterwingz

poussin
Hello
Using A2200 chdk build 1.3.0.3152 and chdkptp build r438,

@poussin : if you have some time, we still need test results for the A2200 manual focus test.

Instructions and download links are here : Setting focus from scripts or menus : please run this script and report back

TIA !

Ok , I will do it by this week end

poussin

reyalp

poussin
Using A2200 chdk build 1.3.0.3152 and chdkptp build r438, I wanted to store the video directly on the PC.
The way , I found is to dump frames with debug.

This doesn't have the same quality as actual video files recorded by the camera. Currently there is no way to record actual camera video over USB.

Although I am able to play the dump from files , I would like to be able to extract individual frames from the dump file.

I guess you want to convert frames in the dump file to some kind of image format? There is currently not a command do to this, but it is something I would like to add. Most of the pieces are there.

If you explain exactly what you want to do, I may be able to come up with something.

The "screenshot" button saves a ppm image of the current live view display. In theory you could just call this every frame somewhere in redraw_canvas, but the function written in lua and isn't optimized at all so it would be quite slow.

You could also write your own code to read the dump file. The dump is essentially the live view data stream, plus a small header, and a per frame header giving the frame size. The live view stream is described in
https://tools.assembla.com/svn/chdk/trunk/core/live_view.h
In addition to the image data for the viewport and/or bitmap, it also includes information about the dimensions, aspect ratio, and position on the camera screen. These are necessary to display a correct image, and can change at runtime.

The dump header is described in chdku.lua live_dump_start https://tools.assembla.com/svn/chdkptp/trunk/lua/chdku.lua

The functions in liveimg.c https://tools.assembla.com/svn/chdkptp/trunk/liveimg.c are used to convert the camera YUV data to planer RGB. The scaling and positioning of the RGB data is done using CD code in gui_live.lua.

Thanks for your answer and sorry for being late to answer you.

When I move the camera , I need to be able to monitor the video and record it ( on the PC to overcome the size limitations of the SD card )
When the picture is suitable , I want to record in high resolution preferably using remoteshoot ( to be sure that the image is recorded on the PC disk )
During the replay , I want to be able to pause it and examine a particular frame.
Note: a series of remote shoots takes too long.

Tia !

« Previous Page Next Page »