COMPATIBILITY & TESTING

What’s untested.

Here’s what has been checked, and what still needs testing. Both apps support Premiere Pro, Resolve Studio and individual MOV exports. Final Cut Pro setups are available on Mac only.

Last reviewed: October 16, 2026 · Mac 1.5.4 / native Windows 1.5.1. A successful sample test does not cover every recording mode, export setting, or software version for that camera.

The camera and editor coverage below includes tests from earlier versions; it does not imply every source has been retested with each update.

Camera footage

AngleSelect opens stitched, full 360° MP4 or MOV files in 2:1 equirectangular format. Export that format from your camera’s software first. Raw camera files need stitching; a camera name alone does not establish compatibility.

Stabilization and orientation-lock settings can change where your views point as the camera moves. Check the stitched export itself; correct raw playback in the camera’s software is only part of the test.

Timing and timecode

These two cases came up during code review. They are possible compatibility issues awaiting representative files, not confirmed failures in the footage tested so far. The current checks could refuse to open a file with either characteristic.

A slightly different final-frame duration

Frame timing describes how long each image lasts. AngleSelect currently expects consistent timing throughout the video. An otherwise constant-rate export whose last frame lasts slightly longer or shorter could be rejected. A representative sample is needed before changing what the app accepts.

Video and timecode using different rates

Timecode labels frames for editing and synchronization. Its rate can differ from the video rate—for example, 59.94 fps video with 29.97-based timecode. AngleSelect currently expects matching rates. That combination still needs a sample test before we change how it is interpreted.

You do not need to measure either of these yourself. They are pending development checks. If AngleSelect reports a timing or timecode error, keep the exact message and your camera and export settings for troubleshooting.

Final Cut Pro on Mac

App-generated HLG and PQ projects passed four-angle 4K portrait imports, deliberate cuts, source-audio timing and native save/close/reopen with fresh exports. All 120 decoded frames and both audio channels matched the first export after reopening. The HLG test used a Dolby Vision 8.4 camera excerpt; the PQ test used a converted camera excerpt, not a native PQ camera recording.

Controlled HLG/PQ pattern exports preserved all 15 measured one-code brightness steps. Final Cut’s automatic Color Conform is disabled on matching HDR picture clips to avoid clipping bright PQ values. These checks measure encoded values; they do not establish calibrated HDR-display appearance or every camera mode. Use a Wide Gamut HDR library and follow the Final Cut guide.

Premiere Pro

Premiere export requires Premiere Pro 26 or later, with the matching free plugin. GoPro Reframe 2 or later handles HD/4K landscape and portrait; lower-resolution SDR 4K portrait sources use Insta360 Reframe V2. The project references one original stitched 2:1 MP4 or MOV for three or four fixed views, with no separate angle renders. Raw camera import and stitching are outside the app.

• Checked in Premiere on Mac: opening generated native projects, matching fixed-view framing, three and four angles, HD/4K landscape, HD portrait, and silent, mono, and stereo audio. The new 4K portrait checks are described below. Short stitched GoPro and Insta360 samples and generated fixtures have been used.
• Native Windows app checks: installer, settings migration and reset, agreement, update verification, playback, scrubbing, all eight preview layouts, GPU projection, seam fixes, mouse aiming, and MOV export checks in a Windows 11 ARM virtual machine under x64 emulation. This does not establish physical x64 PC performance or Premiere compatibility.
• GoPro HDR and 4K portrait checked on Mac and a physical Windows PC (October 13): Premiere 26.5.2 with GoPro Reframe 2.0.1 opened actual app-generated projects. Four-angle X6 Dolby Vision 8.4 tests passed deliberate camera cuts, combined pan/tilt/roll/zoom, 2160 × 3840 HLG export, and save/close/reopen with a fresh export. All 120 video frames matched each platform’s first export after reopening; PCM audio had zero measured offset from the source. Three-angle silent HDR tests preserved all 15 measured one-code brightness steps within one 10-bit code, including the bright patches. This measures encoded picture values, not calibrated HDR-display appearance.
• Earlier Insta360 4K portrait checks (October 12): Premiere 26.5.2 with Insta360 Reframe V2 imported app-generated X5 projects, exported the full 154-second recording, saved/closed/reopened, and exported again. Independent exact-frame comparisons passed camera cuts and combined pan/tilt/roll/zoom. Short three-angle X5/GoPro checks and earlier three/four-angle plugin qualification supplement those app checks. Tested outputs were 2160 × 3840 at 29.97 fps with stereo audio.
• Audio finding: X5 AAC exports had a fixed 1,024-sample (21.3 ms) delay, with no measured accumulation through 150 seconds or change after reopening. A native Premiere baseline reproduced the delay without AngleSelect or a reframe effect; PCM-input AAC exports did too. Native WAV controls were sample aligned. Keep camera switching video-only and check a short finished export; compare PCM/WAV output when precise sync matters. These results do not establish sample-perfect AAC sync.
• Three-angle SDR regression: the new GoPro 4K portrait path also passed native cuts across all three views and save/close/reopen on both platforms. All 270 frames and decoded audio matched each platform’s first export, with zero measured audio offset for this short GoPro sample.
• PQ checked on Mac and physical Windows: actual app-generated four-angle 2160 × 3840 projects passed all-view framing, camera cuts, 10-bit PQ export, zero measured source-audio offset and fresh save/close/reopen exports. All 120 decoded video frames and PCM audio matched after reopening. The camera excerpt was converted from HLG to PQ; a separate controlled PQ pattern checks fine brightness precision.
• Still pending: broader camera modes, longer HDR recordings, portrait/HDR exports at additional frame rates, and broader GPU/driver coverage. Automated writer checks cover exact 25/60 fps timing; native checks here used 29.97 fps SDR and 30 fps HLG/PQ. Playback speed varies with footage and hardware.

See the shared supported formats and editor exceptions for source requirements, HDR and the small-source Premiere portrait limit. The existing Premiere AAC timing caveat above remains separate from PCM sync checks.

Resolve Studio

Both apps prepare three or four angles for paid DaVinci Resolve Studio 21.1.1. Mac uses the separately installed Insta360 Reframe plugin. Windows uses built-in Fusion tools and needs no reframe plugin. The angles share one original stitched 360° video, and source audio stays continuous on its own track. The free Resolve edition is not supported by this workflow.

• Source requirements: use the shared supported formats FAQ. Resolve supports the ten standard rates listed there; additional rates remain guarded.
• Frame-rate checks on Mac and a physical Windows PC: all ten rates passed four-angle import, save/close/reopen and short finished-video exports in Studio 21.1.1.10. Generated SDR clips with timed flashes and distinct left/right audio cues verified exact frame rates, frame counts and stereo audio sync. These short timing checks do not establish sustained playback performance or cover additional camera recording modes.
• Checked on Mac: Insta360 X5, stitched GoPro and Insta360 X6 HLG samples; native project import, shared-source links, landscape/portrait framing, proxy use, and short playback checks. A silent portrait fixture also passed. These samples do not establish every mode from those cameras.
• Four-angle X6 playback on Mac: the tested Mac reached 30 fps in both the angle viewer and main preview with a shared Half-resolution ProRes proxy and Half timeline playback resolution. This is a short playback result, not a sustained benchmark.
• PQ checked on Mac and physical Windows (October 13): app-generated four-angle projects passed import, 4K portrait framing/cuts, 10-bit PQ export and native save/close/reopen. All 120 decoded video frames and PCM audio matched after reopening, with zero measured source-audio offset. The PQ excerpt was converted from a camera HLG recording. Mac uses Insta360 Reframe; Windows uses built-in Fusion. These checks use original media and Full timeline playback resolution; on Mac, save, close and reopen after switching back from reduced-resolution editing, then queue a new render.
• Mac save and final-export check: a separate X6 project retained all source frames, deliberate cuts across four views, and continuous audio after saving, closing and reopening. A complete 12-second original-media render produced four full-frame 3840 × 2160 views at 30 fps, 10-bit ProRes 422 HLG, and continuous stereo audio, without Dolby Vision metadata.

• Checked on a physical Windows PC: paid Resolve Studio 21.1.1.10 with the full stitched X5 SDR source at 29.97 fps and X6 HLG source at 30 fps. Creating the projects, saving/closing/reopening, all-angle first/last-frame checks, and video-only cuts with continuous stereo audio passed. The X6 check also covered switching from the original to an existing proxy and back.
• Windows playback and short exports: Sam confirmed normal X6 picture, motion and audio during 45–60 seconds of four-view playback. Fresh original-media exports passed complete decoding and Sam’s picture/sound check: 360 frames of X5 H.264 Rec.709 (12.012 seconds) and X6 10-bit HEVC HLG (12 seconds). X6 audio alignment also passed. Its export stays HDR without Dolby Vision metadata. These are bounded sample checks, not a whole-recording render or a benchmark for every PC.

Follow the Mac final-export steps. An initial render placed a smaller picture inside the 4K frame. Switching to Full timeline playback and Prefer Camera Originals, then saving, closing and reopening before queuing a fresh render, cleared it in our test. The exact internal cause is unconfirmed. The Mac Resolve guide includes these steps and the Deliver settings. The Windows Resolve guide covers its separate built-in Fusion workflow.

A complete eight-minute GoPro recording passed Resolve HD exports on Mac and the physical Windows PC after save/close/reopen: all four views and cuts, 14,460 frames and continuous stereo audio matched. A four-second real X6 50 fps SDR sample also passed 4K portrait import, views/cuts, audio timing and fresh reopened export in Final Cut on Mac and Premiere/Resolve on Mac and physical Windows. One-view individual-video exports also passed on both platforms. The current Mac app includes the source-range fix for that valid Resolve clip. Premiere’s repeated renders showed small picture/audio sample differences, so those checks establish framing and timing rather than bit-identical output. These checks cover those recordings and settings, not every long or high-frame-rate source. Broader whole-recording coverage, calibrated HDR-display appearance, other GPUs and other Resolve versions still need validation. Windows proxy generation and native silent/mono imports also need separate checks; the physical Windows samples used stereo audio.

Preview performance

Windows previews share one decoded frame and try hardware decoding for H.264 and HEVC, with software fallback when hardware decoding is unavailable. Mac previews share one decoded frame and use Metal for framing. These paths reduce repeated work across views; they do not establish smooth playback on every recording, drive, GPU, or driver. Sustained physical-PC performance and broader hardware coverage still need testing.

Reported physical Windows playback: Sam tested the updated decoding path on an RTX 5090 PC using both local and external copies. Reports measured about 29 delivered frames per second with maximum video-clock lag of 41–45 ms, and Sam reported that both played smoothly. These short sessions do not establish every codec, recording, GPU, or driver.

If previews are choppy, first try the preview and editor playback checks. If the issue remains, play a short section, pause, and choose Help → Save Debug Report…. Review the saved text and choose it in the optional report field on the contact page. The report includes format and playback/export details without footage, video names, local paths, or installation identifiers. Saving it sends nothing; submitting the contact form sends the report text with your message.

Flat-video export

Mac and Windows checks cover selected-view export, landscape/portrait framing, HD/4K dimensions, per-file and total size estimates, H.264 and 10-bit ProRes 422, frame timing, audio, progress, cancellation, and source protection. Generated 10-bit SDR, HLG and PQ fixtures verify precision, color tags and HDR10 mastering metadata. Internal uncompressed reference tests verify the renderer; uncompressed export is not offered in the app. Windows tests use bundled FFmpeg in a Windows 11 VM.

The main-window close warning has been checked during real exports on both platforms, including keeping the export running, stopping and quitting after unfinished-file cleanup, and refusing to quit after an export or cleanup failure. The native Windows closing-window warning error has been fixed and retested. Full-length large recordings, sustained performance, physical Windows PC performance, and disk-full behavior remain unverified. Start with a short clip.

Exports use a lower scheduling priority. Windows also bounds decoding, filtering, and encoding workers and processes one view at a time. These controls leave more room for foreground work; exporting can still affect CPU, graphics, disk use, and responsiveness.

Source requirements are in the shared supported formats FAQ. Individual-video export works without an editor or plugin and automatically chooses H.264 or 10-bit ProRes 422. It is separate from shared-source editor projects. HDR display/grading and physical-PC performance still depend on the intended setup.

The Mac app includes a separate Uninstall AngleSelect… command in the app menu and Privacy settings. It clears AngleSelect’s local settings and caches, moves the current app to Trash, and quits after confirmation. Reset All Settings and Quit… clears settings while leaving the app installed. Both preserve footage, saved projects, exported videos, editors, and plugins. Uninstall is unavailable while the app is busy or an update is in progress, or from a read-only disk image. Windows uninstall and reset behavior are unchanged.

Other pending checks

• More complete interface testing. The current interface has been used with the developer’s airplane and car recordings, alongside generated test footage. Finder drag-and-drop, dark appearance, broader window-size and display-scale coverage, and a full spoken VoiceOver session still need verification.
• Installation on a separate clean Mac. The app is signed and notarized by Apple. First launch and actual signed updates were checked in a separate new Parallels macOS VM, including saved-session restoration. Installation on additional physical Macs remains unverified.
• Saving XML to exFAT drives and SMB network shares. The save fallback has passed direct tests, but its automatic use on those volumes still needs a real-drive check. Saving to the Mac’s local drive is an alternative.
• Every Mac, macOS, and Final Cut combination. Current requirements are Apple silicon and macOS 14 or later; Final Cut import has been tested with Final Cut Pro 12.3. This does not establish coverage of every supported system.

Intel Macs and the free Resolve edition are not supported. Resolve Studio integration is available on Mac and Windows within the limits above. Premiere Pro is supported; broader independent Premiere checks on physical Windows PCs, display-scale and driver checks, and confirmed overwrite on an exFAT drive remain pending. Raw stitching and correction of orientation drift already baked into a video are also outside the current app’s features.

Try your footage

Start with a short stitched export before preparing a long recording. Open it in AngleSelect, check your views at several points, then save and open the setup in your selected editor. Check framing, playback, and audio there. The quick-start guide walks through those steps.

You do not need special timing test files to try your footage.

Open this page on your Mac or Windows PC to download.