Clipsense

The server-side downloader now tries alternative YouTube player clients (default, mweb, tv, web_safari), which significantly reduces "confirm you're not a bot" failures when importing source videos; if a clip is stuck on that error, retry the import. This change reduces failed downloads for end users importing videos from YouTube.

Openable from the library's Use Clip button, the new editor lets you set start/end, crop to vertical 9:16, position a webcam overlay, toggle burned‑in captions, adjust audio and quality, and render a final MP4 from the server.

Clicking Use Clip now kicks off a tracked background job when the source MP4 isn't cached; the button is greyscaled while working and shows live percent and activity messages, and the editor opens automatically when the source is ready.

If a video can't be downloaded from YouTube, the Use Clip flow and the editor now offer a drag‑and‑drop / file input to upload the source MP4 directly so you can continue editing and rendering.

You can now create a render job from the editor (POST /api/renders) that produces a 1080×1920 H.264 + AAC MP4; renders are listed, can be streamed/downloaded, and are retained for one hour.

The public landing now includes an interactive walkthrough/demo that shows sign-in, channel connection, video sync, clip selection, and the editor flow instead of a static autoplay video.

Download status now reports human‑readable progress (percent · downloaded / total · speed · time left) in the library Use Clip button, the dashboard status bar and the editor's preparing screen so you can follow a source download in real time.

The editor now snaps the playhead to the trim start on load and before Play, shows the playhead as time‑into‑clip (m:ss), accepts Start/End as m:ss or seconds, and zooms the timeline to the trim window for easier precision editing.

The editor's Output preview now renders the actual cropped frame (including webcam overlay and captions indicators) instead of a static/blank box so the preview better reflects the final render.

After a successful source download we now remux the file with +faststart so the MP4's metadata is at the front; browser seeks and player scrubbing work immediately rather than stalling while metadata downloads.

Protected video endpoints now accept the user's JWT passed as ?token= in the query string as an alternative to Authorization headers, enabling embedded <video> playback where headers are impractical.

Renders now target 1080×1920 at 30fps using H.264 + AAC with +faststart and three quality presets (high/balanced/small) so exported MP4s are compatible with social platforms.

Downloaded source MP4s and rendered outputs are cached for one hour and then deleted by a periodic sweeper; download or export your renders within that window.

The editor now correctly finds the cached source and authenticates the source stream so the editor no longer gets stuck loading or shows 401 errors when a cached source is available.

Retrying a failed source download now reliably restarts the download (the UI shows a Retry button) instead of skipping straight to the editor when a partial file exists.

My YouTube Videos (and the server-side sync/add endpoints) now filter to public videos only; private and unlisted videos are no longer shown or automatically downloadable — upload their MP4s manually if needed.