GoPro Mission 1 Pro ILS menu masks NTSC-derived rates as integers

GoPro’s Mission 1 Pro ILS presents several common NTSC-derived frame rates in its on-camera menu using simple integer labels rather than the precise fractional values they actually record. In plain terms: the camera will show 59.94 as «60», 29.97 as «30», and 23.976 as «24» inside the settings screens.

That presentation is important because many workflows, logging systems and edit decisions rely on knowing whether footage is a precise drop-frame/non-integer NTSC speed or an exact integer format. The Mission 1 Pro ILS records the NTSC-derived speeds but the menu treats those speeds as the corresponding integer numbers, which can lead to misunderstandings about the file’s true timebase during acquisition and handoff.

The camera does not offer native exact-integer 60.00, 30.00 or 24.00 capture in its standard menu options; those integer modes are not supplied as factory selections. If you need true integer frame rates rather than NTSC-derived values, the only documented way to obtain them on this model is to use GoPro’s experimental toolchain. The manufacturer’s optional toolset can alter the camera’s behavior so the device will output integer frame rates — in short, the integer modes are obtainable through a post-purchase Labs change rather than as part of the stock firmware.

The device therefore behaves in two distinct ways: in normal factory firmware it records 59.94, 29.97 and 23.976 while showing the menu labels «60», «30» and «24» respectively; applying changes via GoPro Labs can switch the camera to true integer 60.00, 30.00 or 24.00 capture. The company’s own documentation refers to this pathway with the phrase "Framerate changes which can be post-hacked by downloading the optional GoPro Labs software".

For shooters, the menu shorthand can be misleading. An operator selecting the on-screen option labeled «60» will be choosing 59.94 in the camera’s standard state, not a native 60.00 timebase. Similarly, choosing the menu entry shown as «30» yields 29.97, and the display that reads «24» corresponds to 23.976. That mismatch between label and encoded rate is the core of the complaint around how the Mission 1 Pro ILS presents its capture options.

On-set confusion can cascade. Metadata, clips delivered to post, conform settings and frame-rate interpretation in editors depend on knowing whether a clip’s frame rate is an NTSC-derived fractional number or a whole-number standard. When a camera’s menu hides that distinction behind a rounded label, the risk is that downstream teams will assume the simpler integer standard was used and make grading or conforming choices on that basis.

GoPro’s approach contrasts with some other manufacturers that display NTSC-derived values as fractional numbers in their menus or label the exact values more explicitly. In the case of the Mission 1 Pro ILS, the fractional capture rates are present and correctly encoded in the files; the issue is how those rates are described to the person operating the camera.

Because the exact integer formats are reachable only via the optional GoPro Labs route, the company has effectively separated the convenience of selecting an integer label in the menu from the reality of the native encoded timebase. That separation is what prompts calls from some users for a straightforward, official firmware revision that would present the real capture values in the camera’s menus rather than the rounded integers.

A further point to note is the camera’s retail positioning: the Mission 1 Pro ILS is listed with an MSRP of US$699.99. For buyers comparing action or compact cinema devices, the way a camera labels its frame rates can be an important tiebreaker when matching rigs for multicam shoots or integrating footage into longer-form projects.

Several exact examples worth keeping in mind when operating the Mission 1 Pro ILS: 23.976 will appear as «24» in the menu while recording as the 23.976 timebase; 29.97 will appear as «30» while recording 29.97 fps; and 59.94 will appear as «60» despite the encoded file using 59.94 fps. If you require true integer 24.00, 30.00 or 60.00, you must apply GoPro Labs modifications to reach those modes from the stock configuration.

Some members of the community have urged GoPro to address this presentation mismatch without requiring the optional Labs step. A direct request from those users is captured verbatim in the facts: "Please offer a free firmware update to improve this situation." Whether the company responds by changing menu copy, adding explicit fractional labels, or providing native integer modes in standard firmware remains to be seen.

Until a factory firmware change appears, the safest workflow is to verify the recorded clip’s exact frame-rate metadata after capture and to communicate that timebase clearly to post-production. When handing off footage to editors or clients, confirm whether files are 23.976, 29.97 or 59.94 rather than relying on the camera’s menu text alone.

For now, shooters using the Mission 1 Pro ILS should treat the menu integers as shorthand rather than definitive technical statements about the encoded timebase, and consider GoPro Labs only if an actual integer rate is required for a specific workflow.