webadderall/Recordly

This would be a great feature. A floating preview window of your camera during recording

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.

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.

Also, **there's a selection that I didn't include showing up** :(

Yes, audio not recording still 😢
Tried now version 1.1.9

Awesome input Josh, did you try the 119 version already? and see if those issue are persistent?

@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)

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.

## 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...

## 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...

Still present in v1.1.7? Also, is auto-updating working for you?

现在翻译那么方便的，用什么语言反馈留言已经不重要了吧？哈哈，好吧好吧，我已经翻译了英文贴上去了，希望能实现，谢谢！

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 picture can be freely adjusted. It would be better if the camera picture frame can be removed and the camera picture can be directly suspended on the screen recording screen；Another function suggestion is to add the shortcut key display function during the screen recording process. Thank you for your hard work.

On macOS, after I save or export a project, the video preview inside the app stays frozen on the last frame I previewed — the audio plays well though.

Thanks for working on this project and making it available to everyone!

> 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" when I try to record. When I preview the recording, I can see my original cursor in the recording along with Recordly's cursor. To fix this, I tried downgrading to v1.1.5 and v1.1.4. The original issue was fixed in these versions and I didn't get the windows capture failed error. However, after recording, it says "Failed to load video file" and never lets me preview the video,
>
> Generally, I'd wait for an update but I have my final year uni project submission due tomorrow and I'm supposed to record a video demonstration for that and I feel like this would be super cool to record with. So I'd really appreciate it if you guide me on how to fix this issue. Thanks!
>
> Also, I'm on the latest version of windows with optimization for windowed games turned on.

you need to install cmake, do...