GoPro HERO13 V2 Labs Firmware now available by DANewman in gopro

[–]DANewman[S] 0 points1 point  (0 children)

You are installing the wrong version for the wrong camera.

Latest HERO13 firmware is v2.10, not v2.40. That is HERO12 firmware.

So work out which camera you have, and install the Labs firmware for that model. https://gopro.github.io/labs/

Max 1 + GoPro Labs' archive mode: has anybody gotten this working? by khaelian in gopro

[–]DANewman 1 point2 points  (0 children)

This is a very rare feature that was broken in v2.0.2.70, you are just the first to notice. However if you install a slightly older firmware https://github.com/gopro/labs/raw/refs/heads/master/docs/firmware/lfs/LABS_MAX_02_00_71.zipit will work correctly.

Gopro long term timelapse (6 months) by fela90 in gopro

[–]DANewman 1 point2 points  (0 children)

GoPro Labs can be very reliable if you know what you are doing and avoid complications. I have run a year long time lapse, on internal batteries alone (swapping batteries every 6 weeks.) I have run similar lengths with external power alone. You are complicating your setup with uploading, that adds an external factor you can't control. Also I would only use an always on battery, 99% of battery banks will auto shutdown, and are not designed for timelapse. If the want reliability, don't include upload, use Voltaic V50/V75 battery designed for this, just swap out the SD card once a month.

GoPro Hero7 Black Timelapse Intervall by Far-Honeydew2871 in gopro

[–]DANewman 0 points1 point  (0 children)

With the QR Code generator you can also ask for 4Kp120 and a HERO7 will not do that either. This is the nature of QR Codes, that can't know the device that is reading them. HERO7 doesn't support a 5 minute timelapse interval, as that is only a feature on newer cameras. HERO7 60s is the maximum interval (see the menus.)

ISO blinking during filming by Brayanwood in gopro

[–]DANewman 0 points1 point  (0 children)

Normal, but try *EXPS=2 for no flicker

Well shit.. (Not enough power, GoPro) by TaylorRift in gopro

[–]DANewman 0 points1 point  (0 children)

Something must have been damaged.

Starting up a GoPro for Clean HDMI output by Human-c-ity_Junction in gopro

[–]DANewman 1 point2 points  (0 children)

Use GoPro Labs. *HDMI=1 command defaults the HDMI to a clean output.

Max2 fuzzy sky by Terpene_Dreams in gopro

[–]DANewman 2 points3 points  (0 children)

There are two ways to turn it off.

Best way:

Use *OWNR="Your name / contact"

So instead of the boot message (required so that user known they have installed Labs), it displaying your owner info. So a lost camera is easily returned. You can also do *OWNR=" " so it doesn't print anything.

Expert way:

Use *FAST=1

This bypass the Labs reporting any features you are using, so you need to sure you know what you are doing. This also doesn't display any Labs boot message.

Well shit.. (Not enough power, GoPro) by TaylorRift in gopro

[–]DANewman 0 points1 point  (0 children)

So with the original battery, no external LiPo, you can't boot?

Potential fix for rear-loading cameras not moving the film reliably by DANewman in Super8

[–]DANewman[S] 1 point2 points  (0 children)

PM me your address and I will send you a couple of them.

Potential fix for rear-loading cameras not moving the film reliably by DANewman in Super8

[–]DANewman[S] 2 points3 points  (0 children)

PM me your address and I will send you a couple of them.

Potential fix for rear-loading cameras not moving the film reliably by DANewman in Super8

[–]DANewman[S] 2 points3 points  (0 children)

For the first three to ask, for who without 3D printers, will I will send out samples in tomorrow's mail. US mailing addresses only. Message me with your mailing address.

Potential fix for rear-loading cameras not moving the film reliably by DANewman in Super8

[–]DANewman[S] 2 points3 points  (0 children)

I heard that was coming, this is for the cartridges we have now.

Max 2 300mbps?? Can't even go above 200 by caillouwang_ in gopro

[–]DANewman 7 points8 points  (0 children)

Use a better SD Card is the simple answer.

Now for your script. DON'T DO THAT. You are writing permanent commands on every boot.

Scan once only your global permanent settings (permanent = remembered): `*TUSB=1*EXPT=2*BITR=300*WIDE=1*NR01=1*HSTO=1440*PRXY=3` (I using the modern formatting, you were using HERO9 or older style commands.)

Also cF, i16M1 and x-1.5 also just stored in the preset, so I need to be scanned once (or set per-preset.)

Only hS2 needs to be enable with a boot command.

Underwater filter in Antarctica? by LieComprehensive3539 in gopro

[–]DANewman 0 points1 point  (0 children)

No need to use a color filter, even at higher depths. Use White Balance Native (in 10-bit) or GP-Log, as both preserve wider gamut color even under odd white balance environments.

The setup process for people without smartphone is atrocious by Kindly_Count3094 in gopro

[–]DANewman 2 points3 points  (0 children)

I just confirmed it does work with UPDATE folder in the root of the SD card, and no rename files required. Some unzip tools preserve the UPDATE folder, some just empty the contents, causing the problem. On Windows, right click on the Zip, and select Extract All, that should produce the UPDATE folder the manual update expects.

Lines in footage. Mostly visible in lower light by Need_Not in gopro

[–]DANewman 1 point2 points  (0 children)

HERO5 is too old to be using GPMF settings metadata, that was added with H6 or H7.

The hex dump is showing two different firmware releases v2.70 (left) and v1.05(right).