Adding camera stop capture followed by start capture fails stop-start in mission preview
I have a long mission list of multiple components. I want to record the video but it will be longer than I want so I want to stop capture so if saves the file and then immediately start capture for a new file. I placed the stop and start capture commands in the list but it seems that both are ignored in the mission preview as it shows a continuous video. Is this just an error in the preview generation or do the 2 commands join to be a non-command.
I added a 1 second wait command between the stop and start capture commands in the list and this is displayed correctly as a second video in the preview. Is it correct that there must be another command between the start and stop capture commands?
Comments
16 comments
Please share the plan. Once you set the camera at beginning of plan the video will not stop until you add a marker with a command on the path somewhere. Sounds like that may be the issue but without seeing the actual plan it’s hard to say.
And why wouldn't camera start and stop commands in a list be the better way between other components such as path and orbit components?
Need to see the plan. Using a list is fine but it needs to be placed correctly within the plan.
The only issue is with a camera stop followed immediately by camera start. Does is need a wait between the two?
So I'll rephrase the question. Using a list what is the best way to split a long mission video into 2 separate captures? What component commands are needed and specifically where?
Best way is to use Markers on a path. Adjust altitude, speed, drone heading, add components like a camera list etc. Markers are a great way to control many functions along a path.
And that is why I used the camera commands in the list of components rather than part of any path or markers.
Ok. I think we’re Misunderstanding each other. If you want to stop video and start a new recording “file”, you will need to add a component somewhere along the path. The camera needs to know where along the path you want to stop and then another location to start a video again. Makers are used for this. If this doesn’t help then maybe someone else can explain better. It would be much easier to see the plan though. I have no issues starting and stopping video recordings or taking photos anywhere along a path using markers. You can’t just place a camera command list and have it switch a long the path unless you specify where and what to do. This is why you add markers to give commands. Good luck and enjoy.
I already added camera commands to the plan list. I understand how that works. I can place a stop capture on the list between components and that works as expected. I plan place a start capture on the list as long as a stop capture preceded as long as it isn't the first command after a stop capture. So, the question remains as to how to split a video with stop-start commands in a component list? Nowhere have I referenced placing camera commands as part of a path or other component.
Ok. Just trying to help. I’d suggest watching the DL YouTube videos. Without seeing your plan it’s difficult to know what your actually trying to do. As usual there can be many ways to set up camera commands. Everyone has their way to do it. It all needs to be in the proper order and at prior position in plan. Sorry I could not help more. Good luck.
It sounds like it might be just a bug in the preview, so I'd try a short backyard test mission to see what the drone actually does. Either way, it should probably be a bug report, but it sounds like you have a work-around with the wait command.
Thanks. flew the plan today but about the time it went from the orbit component to path component I had an off course error which stopped video. I managed to ascend about 10 feet twice and resume the mission, but I stated video manual. It was an 8 minute flight so I didn't try again. I had stop, wait, start capture commands to be sure. I also thought the there was a possibility that the done camera couldn't respond quickly enough to go from stop to start without a pause.
The preview lower charts show continuous video if I leave out the wait command. As long a the wait command works I'm fine.
Weather was good for my complex mission plan today. I'll try a simple backyard plan to test out some command sequences, maybe tomorrow..
You can adjust the “Motion Error Tolerance” in the settings which is defaulted to 75 feet distance and 25 feet altitude if needed. It may help if the drone is getting pushed around by winds, drifting off-course and/or the speed could be too fast. Just some thoughts. Enjoy..
I understand motion tolerances and I purposely set them tight to avoid crashes. I've made speed and acceleration/deceleration adjustments also as needed in this and past plans.. They are all part of my plans already. I also know how to make mid course corrections to get back on course when a motion tolerance is exceeded.
Ok. Good luck…
I finally took the time to create 3 short test missions to determine which command sequences work or don't work for breaking up a video capture. First was start capture at beginning for a single video--fine. Next, insert a stop capture followed by an immediate start capture between 2 separate components. What's interesting is that the preview shows the 2 capture commands correctly it shows as a single capture 1 from the start. In actual flight, however, the start and stop are correctly interpreted as the video capture and then immediately started again to create the 2 separate video files. The off/on video time was visible on the screen. For the third test I inserted stop capture, wait 1 sec, followed by start capture commands between 2 components. The preview shows the wait and also capture 1 and capture 2. In live flight I could watch the wait as a delay in stopping video and starting again.
So, the stop capture/start capture as successive camera commands works fine in real flight, just not quite with preview.
Please sign in to leave a comment.