getopenscreen/openscreen

Search existing issues I have searched the existing issues Is your feature request related to a problem? I want to make a screencast and narrate what's going on the screen for Transcript Captions, so I'll record with Audio. But then ultimately I want a "silent" clip, e.g. for embedding a landing hero page sort of thing. This does not seem to be supported as-is today. Describe the solution you'd like Export MP4 with a [ ] No Sound (silent) sort of checkbox. Describe alternatives you've considered Export as GIF instead of MP4. Post-process the MP4 to remove the sound track. Additional context @EtienneLescot happy to answer any questions about the FR. Also absolutely no offense taken if you don't want to support and just close this.

Search existing issues I have searched the existing issues Is your feature request related to a problem? It would be cool if there was a Nix cache so that running nix run github:getopenscreen/openscreen or integrating this flake into one's one Nix files, as I have for my https://nixfiles.vorburger.ch/reference/openscreen, would not cause (massive) local compile times as it currently does. There are probably a couple of different ways for going about this? @EtienneLescot bonjour! Are you a Nix user yourself? Are there any Nix-using active contributors to this project? Describe the solution you'd like I guess ideally https://search.nixos.org/packages?channel=unstable&query=openscreen would be switched over from @siddharthvaddem https://github.com/siddharthvaddem/openscreen over to this https://github.com/getopenscreen/openscreen ... ... @Renna42 as the current maintainer would you possibly be open to this? Describe alternatives you've considered An alternative to nixpkgs could be to u

What happens A GIF export runs about 28× slower than an MP4 export of the same project on the same machine. Measured on 2.0.0-rc.1 (Windows 11, AMD Radeon iGPU, 125 % scaling), on a 56.9 s recording with a zoom, a trim, a speed region and a full-camera region: Export Frames Wall time Throughput MP4 720p 30 fps 1495 ~18 s ~84 fps GIF Small (480p → 864×480) 15 fps, loop 748 ~4 min ~3 fps The progress readout advanced at a steady ~9 frames every 3 s, with an ETA of about 5 min at the start. The output itself is correct. ffmpeg decodes it without errors, and ffmpeg and Pillow give byte-identical frames on six sampled frames: 748 frames, 49.87 s, NETSCAPE2.0 loop. Ask Profile where the GIF path spends its time: frame readback, palette quantisation, or LZW encode. Nothing in the GIF path changed between rc.1 and main, so this is not a regression of the release candidate. It makes GIF export impractical beyond short clips.

The recording bar (HUD) tooltips were rewritten in #912. The English is the source of truth. The 14 other locales were machine-translated by an AI agent and reviewed by a second one; they have not been read by a native speaker. Native reviewers are welcome. How to help Open src/i18n/locales/<locale>/launch.json and read the strings changed by #912 (git diff of that PR shows them, or look at the tooltips, cursor, recording and deviceSettings entries). Fix anything unnatural, wrong, or inconsistent with the rest of that locale. The rules are in technical-documentation/engineering/tooltips.md: keep {{placeholders}} as they are, keep each string short (it has to fit a tooltip about 260 px wide), and reuse the terms the locale already uses. Run npm run i18n:check, then open a PR. Locales (tick when a native speaker has reviewed it) ar cs de es fr it ja-JP ko-KR pt-BR ru tr vi zh-CN (#1077) zh-TW Strings the reviewer was least sure about ar: hideHUDTip (the words for "syst

We’re preparing the OpenScreen v2 launch, including a Product Hunt page, and we need a few polished videos showing what the new version can do. v2 artefacts: https://github.com/getopenscreen/openscreen/actions/runs/36336647912 The goal is to create the demos with OpenScreen itself, so the videos demonstrate both the features and the quality of the final output. What we need A short showcase video (30–60 seconds) giving a feel for the product and the results people can achieve. A few focused clips (10–20 seconds each) highlighting features such as automatic zooms, cursor styles and animations, 3D effects, transcript editing, or audio improvements. A before-and-after example, showing a raw recording turned into a finished demo. Real workflows would make good material: presenting an app, walking through a website, or explaining a feature. The videos should be easy to follow and visually appealing, with realistic sample content and no personal information. How to contribute Help wi