Replies: 3 comments 6 replies
-
Please share the script exactly as you're running it, or even as a QR code, because the script you shared is not fully valid, so I assume that it was just presented incorrectly. Script should never have spaces. It's normally not a good idea to set everything within a repeating script. Your camera does remember the last settings for video moded, so you should set that separately. It helps keep the scripts simple for debugging. There should be no reason you can't leave the battery in, we should determine why that is not working for you. This is the best way to ensure the real-time clock doesn't lose its time. Waiting 45 seconds to charge the battery that's not there, is not going to really help. If you must run with the battery out, try scanning *BYPS=1 it removes many of the nagging pop-ups. However, I'm not sure on HERO12 whether it removes the time and date pop-up, it does on 13. |
Beta Was this translation helpful? Give feedback.
-
Here's the actual QR code as a PDF. Also the Python code that produces it (it does remove spaces; the spaces are just to make it more readable for me). I forget exactly what the problem was running it with the battery installed. I think much of the time the script just didn't work, and when I checked the Hero 12 after a failure the battery was dead. Also maybe (maybe!) there as an issue with the camera overheating on the ground (once in the air there's plenty of airflow and it doesn't overheat). I think somebody online suggested removing the battery; that 100% fixed it until the recent problem with the Date/Time pop-up blocking the script from running on USB-C power-up.
|
Beta Was this translation helpful? Give feedback.
-
I'm closing this are not a Labs bug to fix (i.e. not an official issue.) But moving it to discussions. Your script is unnecessarily complex, so you do add failure points. Who created this Python code? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I use a Labs script to have my GoPro 12 automatically start video recording when USB-C power is applied.
(It's mounted on the wing of my airplane...power comes on when the aircraft starts. I can't use a battery because flights are often longer than one battery will power.)
It was a bit unstable until (per some advice here) I removed the battery from it - then it worked great.
Until yesterday. I powered it up and found no recording afterward. When I tried it at home, I saw that the script was blocked from running by the "Please set date/time" screen. Once I set the clock it worked fine.
I assume the clock battery ran down. Does it not charge while recording? Does it not charge without a battery installed?
My script waits 45 seconds after USB connection before it starts recording; I had hoped that would be enough to keep things charged. I guess not.
Is there a workaround?
Here's my script, with some notes about what it does (from my QR-printing Python script):
Wakes on power. Trusts USB. Boots to script "bt".
Script "bt" saved on reading QR code:
If on battery at boot:
Exits script.
Sets Standard video mode, 5k exteme 8:7, 30 fps, Wide lens, HyperSmooth ON, high bitrate, 10 bits/pixel.
Prints message about mode and charging time..
Waits 45 seconds (charges battery that long). [note maximum wait time is 9 seconds per command]
Starts recording, then:
Waits 3 seconds
If not on USB power:
Print "Shtting down"
Close video.
Wait 2 seconds.
Turn off camera.
If not recording (because user pressed button):
Print "Exiting script"
Wait 1 second.
Exit script.
Loop back to waiting 3 seconds above.
data = R'*WAKE=2 *TUSB=1 *BOOT="!Lbt" mS r5X p30 fW e1 b1 d10!SAVEbt= <u0 "On battery" + !X mS r5X p30 fW e1 b1 d10 "5.3k 8:7 std video\nCharging 45s..."!9N !9N !9N !9N !9N !S !3N <u0 "Shutting down" + !E + !2O <r0"Exiting script"+ !1N + !X !R85'
Beta Was this translation helpful? Give feedback.
All reactions