FreeFlow
I'm thinking 8+7 is a double separate range. (51 to 55) first toggle and (32 to 34) is second toggle it's like a two click on click at a time. click once toggle back with second click then repeat... Like a three way switch. It kind of did that when I tried to change from MOVIE to PHOTO modes.
Yes...
(51 to 55) Start Video
(32 to 34) Stop video
(1 to 2) shoots
What's ya think?
Or is it...
ON-33 OFF-54 ON-34 OFF-55 etc.....
Hum...?
Microfunguy
FreeFlow
I'm thinking 8+7 is a double separate range.
What's ya think?
Yes, I noticed that earlier but then forgot.
Anyway, I am signing off shortly
in fact, I have had enough for now ...
FreeFlow
Oh right David! have a good night.
achillies
You're right, but the pulse that is being sent out to stop recording doesn't look right. I'll bet Microfunguy is fixing it, and you'll have a new script to use soon.
Even though power off is an option, it sounds kind of final. and since you don't have a close lens option, I might change that to reboot. Freeflow, if you had a choice of camera functions while you were flying, what would they be?
(well maybe he's sleeping already!)
FreeFlow
8+5 is power off. we're looking at 8+7 toggling Start to Stop the Start to stop again...
achillies
I know it is ny friend. I'm just thinking about how I might re-assign the functions (I wouldn't power off, so I might use that button to switch to "bright" mode for instance) The "stop recording function fix" will probably just end up being a delay somewhere in the script (we need at least 62 but less than 68 for that number).
FreeFlow
Focus/ shoot in Photo mode. Zoom could be so so. Think about when you zoom a camcoder or camera in your hand way out it almost need a tripod. Taking that in the sky would REALLY be move'n around the ground. Might have to pan-out to be able to control what your shooting.
Then be able to switch over to VIDEO mode and go back to Vid mode.
FreeFlow
Ah I got ya... Then you can use it for another feature of choice! ...although... Maybe just use the Power Off when my Heli is going to crash in the lake and it's best to shut the camera off before it hits the water. ;0)
Microfunguy
Couldn't resist another Cappucinno before going to bed.
8+7 should alternatively generate pulses of width 325 and 625 msec.
else if a<35 then gosub "rec_video" ..... else if a<67 then gosub "stop_video" should work.
achillies
Yes, good point.
FreeFlow
When my Heli is going to crash in the lake and it's best to shut the camera off before it hits the water. ;0)
Some comments that might help you, and keep in mind that these are only my opinions. I don't fly helicopters, but I know how CHDK/SDM work (well, almost). Plan on "bombing runs". You will need to set up your shots a few seconds before you actually execute them to get the picture you want because there IS a slight delay between command and execution. It might take practice, but once you get use to how it works, it works quite well.
FreeFlow
You got that right with the delay. I think I'll have a camera man handling that and I'll be the pilot. I do have Video goggles and this all works well. a bird eye from the nose of the heli. I have a 900Mhz downlink for viewing camera screen. The camera is recording LIVE to SD so flicker from the wireless doesn't showup in the final product.
achillies
else if a<35 then gosub "rec_video" ..... else if a<67 then gosub "stop_video" should work.
I knew it was close!
Do you know where the line that Microfunguy posted goes ( in your script)?
Wait, am I missing something? pulse generated was only 550ms. don't you need a pulse at 625<> 685 for that to stop recording?
FreeFlow
I don't know much about the pulse generation. I'm not sure.
achillies
Well, MFG does, so we'll wait and see what to do next. I might be misunderstandig the value of "A". I was thinking it was the pulse width, but if that's the case, the trouble with stop video is not (necessarily) the script (it may be the pulse sent by camremote).
FreeFlow
I'm checking on this to get an answer....
http://vp-systems.eu/manual_cr_v2.1.pdf
===============================
Extra Settings (USB/PTP only) (Only PRO version)
================================
Keep camera's LCD on at shooting (disables video out) - This setting turns the LCD on and disables the video signal on the video terminal. This is useful when testing the CR on the bench.
achillies
From what I've read (and my brief experience), PTP adds time to the entire process. It sends commands (much longer than a pulse), that then need to be run to shoot etc.. Neither here-nor-there though, because you don't have the pro version.
For the moment, this one thing that we (well, you guys) have been working on is almost done. When this gets worked out, ask again about the LCD issue.
ledelectronics
PTP is targeted to cameras which have built in PTP support like Canon G5-G10, few old Powershots and DSLRs. In CHDK composite video is most probably uncontrollable I think, always available?
It would be best if David will enable PTP support in his builds then all communication limitation will be solved, both directional communication between CR and camera can be done and very fast. But David has done so much good work already for CHDK so I don't want to but extra burden to him.
Microfunguy
Hi Mark.
Load and run script cr1sdm.bas with ordinary CHDK profile.
Test shoot, zoom in, zoom out, start video, stop video.
FreeFlow
getting setup now to make sure I'm using the right items you mention. I will be using the NEW link for the cr1sdm.bas...?
If Control Method is USB/CHDK then please use script:
http://vp-systems.eu/download/cr1sdm.bas (this is compatible with CR-1 as
well)
If Control Method is USB/CHDK+ then please use script:
http://vp-systems.eu/download/cr2sdm.bas
Microfunguy
Yes.
