Anyone noticed Voice Control glitches on Labs?

[sjmarcy2]

With Voice Control ON in the Dashboard from startup, it shows ON status if I check, yet does not work. But if I toggle it OFF then back ON, now it works and will stay on for the session.

Or from the main screen, just swipe left or right to change camera modes, and then it is back on. Maybe there is a setting I have to revise? Labs features used at the moment are BITR and GCMP. Thanks.

[dnewman-gpsw]

It was recently reported on HERO13 (only) and there is a fix coming. Currently the only workaround is the menu.

[sjmarcy2]

Labs FW v1.30.70 still has Voice Control woes not present on V1.30.

Plus gained the new extra beeps from v1.30, even if beeps (now called "Camera Volume" in the Audio tab) are turned off.

[FlyTieGuy]

[FlyTieGuy]

In that order

[dnewman-gpsw]

which one broke it? I mean you should test it one at a time.

[dnewman-gpsw]

I am able to reproduce the error.

[FlyTieGuy]

Hi any progress on this one.

[DemonViewLLC]

I've noticed it when using the Max Lens Mod. The voice commands don't work on startup (using normal power up, not quik capture). You have to turn off and on the voice commands in the menu to make them work again.

Using the standard camera lenses, no such issue. Voice commands work as normal when the camera is turned on.

Haven't seen if the issue is present when using other lens mods (Macro, ND filters etc).

[FlyTieGuy]

Ok. Thanks for your help so far. Getting late here so I’ll reply tomorrow

…

On Wed, 2 Apr 2025 at 19:40, David Newman ***@***.***> wrote: which one broke it? I mean you should test it one at a time. — Reply to this email directly, view it on GitHub <#1172 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BCXXK7Z3D3RBQVDLC6CVGFD2XQVKRAVCNFSM6AAAAABR3LEI3GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENZQGUZTGOI> . You are receiving this because you commented.Message ID: ***@***.***>

[FlyTieGuy]

Good man. Do you need anything further from me in the meantime?

…

On Wed, 2 Apr 2025 at 20:33, David Newman ***@***.***> wrote: I am able to reproduce the error. — Reply to this email directly, view it on GitHub <#1172 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BCXXK766E55YFCCYZUEY74L2XQ3RXAVCNFSM6AAAAABR3LEI3GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENZQGU3TMOA> . You are receiving this because you commented.Message ID: ***@***.***>

[LordWimmi]

I have the same issue with GP13 since firmware 1.30 and now still with 2.02 (only Labs). Very annoying!!! My workaround:
*BOOT="!Lbt"!SAVEbt=v0v1
(for safety reasons you better put the script on the micro SD-Card)
It works for me! But that has 2 disadvantages:

1. Voice Control is alway on when you start the GP, even if turned off before
2. If you use the QuickCaptureButton, you will probably experience short sound issues at the point where the script is loaded while GP is already recording.

So, I hope that bug will be finally fixed soon by a working firmware! Labs firmware is indispensable for me :(

[sjmarcy2]

For now I just have the Hero 13 default to Time Lapse / Warp mode.

So after powering on, one routine-memorized side button press gets me to my true default, video. Not bad once done a few times. That way I don't have to cycle thru the options with more button presses.

It will all be sorted soon in any event.

[motigchelaar]

What makes you think it will be sorted soon? This has been an issue for months already...

[sjmarcy2]

Because a few posts above, Mr Newman noted (2 weeks ago) that he can reproduce the issue?

So, perhaps the next Labs update..

[motigchelaar]

I have this same issue on my GP13 with latest labs firmware. No matter what lens or ND-filter is attached. I have to either manually toggle voice control off and back on or switch to a different camera mode - and then back again.

I may have to resort to using the boot script method. Annoying nonetheless.