Question
Is the MISSION 1 PRO ILS supported by Open GoPro?
The supported-camera list in the docs currently reads:
MISSION 1, MISSION 1 Pro, LIT HERO, MAX 2, HERO13 Black, HERO12 Black,
HERO11 Black Mini, HERO11 Black, HERO10 Black, HERO9 Black
MISSION 1 and MISSION 1 Pro are both listed, but the ILS is not. Since the ILS
appears to share the Mission 1 Pro's body, sensor and GP3 processor — differing
in the lens mount — I suspect this is documentation lag rather than a statement
of non-support, but I would rather confirm than assume.
Specifically:
- Does the ILS support the same wireless control surface as the Mission 1 Pro —
BLE pairing and control, the camera's Wi-Fi AP, the HTTP API, the UDP preview
stream, and the media list?
- Are there any known model-specific differences beyond the lens mount?
Why it matters
I maintain an app that controls GoPro cameras over BLE and Wi-Fi (currently
HERO13 Black, with the Mission series as the next target). Whether the ILS
speaks the same API is the difference between adding a capability-table entry
and porting a transport layer, so it is a purchasing decision rather than a
curiosity.
Related: does setting 121 (VIDEO_LENS) exist on the ILS?
Because the ILS takes physical Micro Four Thirds glass, I would expect it to
have no digital lens setting at all. My implementation currently assumes 121 is
absent on that model and never writes it, on the basis that writing an option to
a setting a camera does not have could select an unintended mode rather than
failing cleanly.
Is that the correct assumption, or does the ILS still expose 121 in some form?
Happy to test and report back if that would be useful.
Question
Is the MISSION 1 PRO ILS supported by Open GoPro?
The supported-camera list in the docs currently reads:
MISSION 1 and MISSION 1 Pro are both listed, but the ILS is not. Since the ILS
appears to share the Mission 1 Pro's body, sensor and GP3 processor — differing
in the lens mount — I suspect this is documentation lag rather than a statement
of non-support, but I would rather confirm than assume.
Specifically:
BLE pairing and control, the camera's Wi-Fi AP, the HTTP API, the UDP preview
stream, and the media list?
Why it matters
I maintain an app that controls GoPro cameras over BLE and Wi-Fi (currently
HERO13 Black, with the Mission series as the next target). Whether the ILS
speaks the same API is the difference between adding a capability-table entry
and porting a transport layer, so it is a purchasing decision rather than a
curiosity.
Related: does setting 121 (VIDEO_LENS) exist on the ILS?
Because the ILS takes physical Micro Four Thirds glass, I would expect it to
have no digital lens setting at all. My implementation currently assumes 121 is
absent on that model and never writes it, on the basis that writing an option to
a setting a camera does not have could select an unintended mode rather than
failing cleanly.
Is that the correct assumption, or does the ILS still expose 121 in some form?
Happy to test and report back if that would be useful.