Future command enhancements #210
Replies: 4 comments 1 reply
-
Man. This is insane. Nice job! Here's a quick suggestion off the top of my head:
For scenarios where you want to start/stop recording under certain lighting conditions. Should probably be combined with r and/or sleeping for a simple hysteresis mechanism. No idea what the unit would be, but if this is possible to do then you probably already have some convertable unit of measurement for this in the GoPro. |
Beta Was this translation helpful? Give feedback.
-
Temperature sensors readouts (in particular, sensors involved in triggering overheating shutdowns) might be useful. The goal being the ability to stop recording and sleep for a while to cool down before resuming recording to prevent shutdowns due to overheating. |
Beta Was this translation helpful? Give feedback.
-
Thanks for chiming in, and more is welcome. You can use the current ISO and shutter values to compute a simple light meter, although there might be a system light level that could be exposed through these controls. DSP and/or battery temperature could be exposed, although they have less creative applications. Also coming are variables and basic math, so lots creative capture solutions will become possible. |
Beta Was this translation helpful? Give feedback.
-
Even if it's mostly an outdoor camera where the GPS is available, for indoor use will be useful to be able to sync the time by connecting to internet, by a time server or even the Gopro cloud service; I noticed that when powered only by usb for few hours a day the internal time shift a lot. |
Beta Was this translation helpful? Give feedback.
-
While Labs is constantly adding hacks to help you create the perfect image, much of the core command set hasn't changed since the first introduction on HERO8. In the next Labs release we hope to expand the command language to have more if-this-then-that conditional commands, as there are some great ideas that may be achievable with these new scripting controls.
Today's conditionals are only time based. If(time > value) do_command_A else do_command_B. e.g. Labs command
>10:00mV~mT
. This is good for day versus night controls, but little more. Coming soon are other camera conditionals. The command format is xValue where x is a status type, and Value is used in the conditionals that <xValue is the same as if(x_status < Value) then ...Some status type:
With these command you can create custom capture motion triggers, or geofencing a capture, setting a region of interest for capture to auto start.
oMFRMA=36.5854815,-121.7640418!DcA:1000!S~"%dm to Laguna Seca"+!600R
This will start recording when within 1000 meters of Laguna Seca raceway.
Explained:
oMFRMA=36.5854815,-121.7640418
- sets the GPS coordinate of capture region!D
- waits for a GPS lock<r
- if not recording yet<c:A1000
- if distance to coordinate A is less than 1000 meters!S
- start recording~
- else"%dm to Laguna Seca"
- display the distance the location+
- more in else!600R
- Sleep for 10 minutes and repeatThe above uses only the recording status and the coordinate distance status.
Other examples:
Please suggest other status variables to look for (only used 13 characters so far.)
PS. I thought of one more - day of the week, could be useful is work week construction time-lapses.
PPS. These features could be a month or so away, so this is a good time for feedback.
Beta Was this translation helpful? Give feedback.
All reactions