SaaS Metrics
Gemini Executive Synthesis
Failure to generate cursor telemetry (`.cursor.json`) after DMG installation on macOS, impacting editor features.
Technical Positioning
Ensuring full feature functionality across all installation methods and target platforms, particularly for core features like cursor-based suggestions in a professional screen recorder.
SaaS Insight & Market Implications
This bug reports a critical functional regression: cursor telemetry, essential for editor suggestions, fails to generate after DMG installation on macOS, despite correct permissions. The discrepancy between dev builds (working) and DMG installs (failing) points to a packaging or deployment issue. This directly impacts Recordly's value proposition as a "professional product videos, demos, and tutorials" tool, as a core editing feature is unavailable. Market implication: installation-specific bugs that disable core features are severe. They erode user trust, increase support burden, and directly hinder adoption, especially for a tool targeting professional use cases where reliability is paramount. Resolving this packaging defect is critical for market credibility.
Proprietary Technical Taxonomy
Raw Developer Origin & Technical Request
GitHub Issue
Mar 29, 2026
Repo: webadderall/Recordly
macOS: Cursor telemetry not saved after DMG install (Apple Silicon, macOS 26)
## Bug Description
After installing Recordly v1.1.7 via the DMG on macOS 26.2 (Apple Silicon M3), cursor telemetry `.cursor.json` files are not being created alongside recordings. The editor shows "No cursor telemetry available — Record a screencast first to generate cursor-based suggestions."
## Environment
- **OS**: macOS 26.2 (Build 25C56) — Apple Silicon (M3 MacBook Pro)
- **Recordly version**: v1.1.7 (DMG install to `/Applications/Recordly.app`)
- **Permissions granted**: Screen Recording ✅, Accessibility ✅
- **Quarantine flags**: Cleared via `xattr -cr`
## Reproduction Steps
1. Install Recordly v1.1.7 via DMG
2. Grant Screen Recording and Accessibility permissions in System Settings
3. Record a screencast (any duration, tried multiple 30s+ recordings)
4. Open recording in editor
5. Click the zoom suggestions / wand button
6. See toast: "No cursor telemetry available"
## Evidence
Recordings made with `npm run dev` (dev build) **do** produce `.cursor.json` files. Recordings made with the DMG-installed app **do not**.
```
# Recordings WITH cursor.json (dev build, same machine, same day):
recording-1774718957877.mp4.cursor.json (1.5MB, ~10:35am)
recording-1774719579103.mp4.cursor.json (1.5MB, ~10:45am)
recording-1774743781164.mp4.cursor.json (77KB, ~5:23pm)
# Recordings WITHOUT cursor.json (DMG install, 7pm onward):
recording-1774749616308.mp4 ← no .cursor.json
recording-1774750149033.mp4 ← no .cursor.json
recording-1774750394518.mp4 ← no .cursor.json
record...
Developer Debate & Comments
## Root Cause Found The cursor telemetry issue is a **downstream symptom** of an ffmpeg permission error. ### Error Chain 1. `node_modules/ffmpeg-static/ffmpeg` lacks execute permission after `npm install --ignore-scripts` 2. Audio muxing fails: `spawn ffmpeg EACCES` 3. `validateRecordedVideo()` fails because the MP4 can't be decoded (audio mux produced no output) 4. `finalizeStoredVideo()` throws at the validation step (line ~2611) 5. **`persistPendingCursorTelemetry()` is never reached** — cursor data is lost ### Fix ```bash chmod +x node_modules/ffmpeg-static/ffmpeg ``` ### Suggested Code Fix `finalizeStoredVideo()` should persist cursor telemetry **before** video validation, or at minimum wrap validation in a try-catch so telemetry isn't lost when validation fails: ```typescript async function finalizeStoredVideo(videoPath: string) { // Persist cursor telemetry FIRST — don't let validation failures lose cursor data snapshotCursorTelemetryForPersistence() currentVideoP...
## Confirmed Fix Symlinking `node_modules/ffmpeg-static/ffmpeg` to Homebrew's `/opt/homebrew/bin/ffmpeg` resolves the issue completely. Cursor telemetry, auto-zoom suggestions, and audio muxing all work. ### Root Cause (refined) The `ffmpeg-static` npm package bundles an unsigned ffmpeg binary that **cannot be ad-hoc signed** (`codesign` returns "invalid or unsupported format for signature"). macOS 26 (Tahoe) blocks execution of unsigned binaries, producing `Unknown system error -88` at spawn time. ### Workaround ```bash # Install ffmpeg via Homebrew (if not already installed) brew install ffmpeg # Replace the broken npm binary with a symlink mv node_modules/ffmpeg-static/ffmpeg node_modules/ffmpeg-static/ffmpeg.broken ln -s /opt/homebrew/bin/ffmpeg node_modules/ffmpeg-static/ffmpeg ``` ### Suggested Permanent Fix Consider one of: 1. **Prefer system ffmpeg** — check `which ffmpeg` before falling back to `ffmpeg-static` 2. **Ad-hoc sign during postinstall** — though this specifi...
Awesome input Josh, did you try the 119 version already? and see if those issue are persistent?
the macOS 26 unsigned binary rejection thing bit us too. we build a screen capture SDK and initially tried bundling ffmpeg for encoding, but the codesigning requirements on Tahoe made it unreliable. switched to using VideoToolbox's VTCompressionSession for H.265 encoding directly - no child process to spawn, no permission issues, and the hardware encoder on Apple Silicon is basically free. biggest gotcha was getting the pixel format right from the ScreenCaptureKit output - kCVPixelFormatType_420YpCbCr8BiPlanarVideoRange works but you need to match the color space or you get washed out colors in the output.
fwiw here's how we handle the VideoToolbox encoding pipeline for screen capture: https://github.com/m13v/macos-session-replay/blob/main/Sources/SessionReplay/VideoChunkEncoder.swift - the chunked encoding approach means you can write segments to disk continuously without keeping everything in memory.
Adjacent Repository Pain Points
Other highly discussed features and pain points extracted from webadderall/Recordly.
Extracted Positioning
Recordly's cursor following feature on Linux.
Delivering reliable, professional-grade screen recording functionality across supported operating systems, specifically Linux, for 'professional product videos, demos, and tutorials'.
Top Replies
Same here, i am using Fedora.
same issue, they said "Linux currently use Electron's capture path, which means the OS cursor cannot always be hidden during recording." so i think is the reason why but idk lmk if this can be fixed
[fix(linux): restore cursor follow with linux bounds + hook mouse cache](https://github.com/webadderall/Recordly/commit/a648c3fecaab290be8b96d412053b9a23f1937e5) Let me know if this changes anything
Extracted Positioning
Critical bugs in screen recording and video processing (v1.1.6 regressions)
Reliable, cross-platform screen recording for professional use
Top Replies
This is so I can assign priority to the really annoying bugs that you guys may be facing 😅
Hi webadderall. First of all, I absolutely love this project. I downloaded and tried out the latest release (v1.1.6) and it says "Native window capture failed, falling back to browser based capture...
The latest update seems to have introduced a number of regressions, try v1.1.5 for now 😅 A clean update should ship tomorrow or today
Extracted Positioning
Audio input/output loss and webcam display issues after updating Recordly on Windows 11.
Maintaining core recording and editing functionality across updates and operating systems, ensuring a stable and reliable user experience for professional video creation.
Top Replies
Still present in v1.1.7? Also, is auto-updating working for you?
version v1.1.8 auto update is working but still the audio and webcam are not working. I redownloaded v1.1.5 the audio and webcam are working fine.
@matomitw @webadderall I have described the Recordly errors on [Windows in more detail here for v1.1.9](https://github.com/webadderall/Recordly/issues/140)
Extracted Positioning
Enhanced webcam overlay and shortcut display during screen recording
Professional video creation tool with advanced customization
Top Replies
Translation: [Feature]: I hope that while screen recording is being done with the webcam, the webcam image can be displayed on the desktop, and its position and shape can be freely adjusted. It wou...
写中文，用AI转化需求啊。服了，你这个老6
I hope that in the process of recording the screen and turning on the camera recording at the same time, the camera picture can be displayed on the desktop, and the position and shape of the camera...
Extracted Positioning
Feature request for basic audio track editing controls within Recordly's video editor.
Enhancing Recordly's capabilities as a "professional product videos, demos, and tutorials" tool by integrating essential audio editing functionalities, reducing reliance on external software and streamlining the production workflow.
Frequently Asked Questions
Market intelligence mapped to Failure to generate cursor telemetry (`.cursor.json`) after DMG installation on macOS, impacting editor features..
What problem does Failure to generate cursor telemetry (`.cursor.json`) after DMG installation on macOS, impacting editor features. solve?
Based on our AI analysis of the original developer request, its primary technical positioning is: Ensuring full feature functionality across all installation methods and target platforms, particularly for core features like cursor-based suggestions in a professional screen recorder.
How is the developer community reacting to Failure to generate cursor telemetry (`.cursor.json`) after DMG installation on macOS, impacting editor features.?
Yes, we have tracked 3 direct responses and active debates regarding this specific topic originating from GitHub Issue.
Which technical concepts are associated with Failure to generate cursor telemetry (`.cursor.json`) after DMG installation on macOS, impacting editor features.?
Our proprietary extraction maps Failure to generate cursor telemetry (`.cursor.json`) after DMG installation on macOS, impacting editor features. to adjacent architectural concepts including Cursor telemetry, .cursor.json files, DMG install, Apple Silicon M3.
Engagement Signals
Cross-Market Term Frequency
Quantifies the cross-market adoption of foundational terms like Cursor telemetry and .cursor.json files by tracking occurrence frequency across active SaaS architectures and enterprise developer debates.