You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 26, 2018. It is now read-only.
A question to the hackers:
How hard would it be to modify the behaviour of the rec button to "record while pressed"?
What for should it be done:
With the Cam on a helmet, one is never shure if it's rolling or not.
So, having a switch vs. a button would be more intuitive, you could feel "left = rec. right = pause".
A mechanical extension to the gopro case would be fairly easy to do, maybe 3d-printable.
A knob that can be slid over the rec. button, which would permanently press the button.
But the difficult question is, can the firmware be modified, so that a permanent press (starting at longer than X seconds) would start record, until button releases.
I even reached out to GoPro with that idea, but they showed no interest...
So, maybe hackers here could help out with some infos about how hard it would be to do?
The text was updated successfully, but these errors were encountered:
A question to the hackers:
How hard would it be to modify the behaviour of the rec button to "record while pressed"?
What for should it be done:
With the Cam on a helmet, one is never shure if it's rolling or not.
So, having a switch vs. a button would be more intuitive, you could feel "left = rec. right = pause".
A mechanical extension to the gopro case would be fairly easy to do, maybe 3d-printable.
A knob that can be slid over the rec. button, which would permanently press the button.
But the difficult question is, can the firmware be modified, so that a permanent press (starting at longer than X seconds) would start record, until button releases.
I even reached out to GoPro with that idea, but they showed no interest...
So, maybe hackers here could help out with some infos about how hard it would be to do?
The text was updated successfully, but these errors were encountered: