Record your screen, ship a demo. Free and open-source, GPU-accelerated, no watermarks, no subscriptions. Windows, macOS, Linux. Actively maintained.
TypeScript cross-platformelectronffmpegopen-sourceproduct-demorustscreen-capturescreen-recorderscreen-recordingscreen-studioscreencastspeech-to-texttypescriptvideo-editingvideo-editorwaylandwgpuwhisper
docs(mcp): the export and record options, on the site and in the skill
EtienneLescot22454406e757
diff --git a/skills/openscreen-demo/SKILL.md b/skills/openscreen-demo/SKILL.mdindex 4cce647e1..19c3025bd 100644--- a/skills/openscreen-demo/SKILL.md+++ b/skills/openscreen-demo/SKILL.md@@ -60,7 +60,7 @@ Write a storyboard and show it to the user in a few lines, then carry on unless## 4. Record-1. `startRecording` with `window`. It returns once capture has started. Connected to the server in the app, the take goes through OpenScreen's recording bar: the editor closes, the bar counts down, and `stopRecording` opens the take in the editor.+1. `startRecording` with `window`. It returns once capture has started. Connected to the server in the app, the take goes through OpenScreen's recording bar: the editor closes, the bar counts down, and `stopRecording` opens the take in the editor. Pass `camera` only when the user wants to appear on screen: the webcam then shows as a picture-in-picture.2. Play the storyboard. Move deliberately, and pause about one second after each result appears.3. `stopRecording` with a `title`. Keep what it returns: `projectId`, `checkpointId`, `videoPath`, `recordingStartedAt`.@@ -94,7 +94,7 @@ Keep the rest as it is: the background, padding, shadow and cursor style are cho## 7. Export and review-1. `exportVideo` with the `projectId` and an absolute path: resolve, say, `demo/demo.mp4` against your working directory first, since the server in the app refuses a relative path. For a pull request video, pass `quality: "medium"` (720p) to keep the file small.+1. `exportVideo` with the `projectId` and an absolute path: resolve, say, `demo/demo.mp4` against your working directory first, since the server in the app refuses a relative path. For a pull request video, pass `quality: "medium"` (720p) to keep the file small. For a GIF (a README, say), end the path in `.gif` and pass `gifSize: "small"` (480p).2. `getFrames` with the `projectId`, at the ruler seconds of your beats.3. Check every frame:- Is each callout readable and clear of the action?diff --git a/technical-documentation/architecture/mcp-server.md b/technical-documentation/architecture/mcp-server.mdindex 4594714bf..555ebfd7d 100644--- a/technical-documentation/architecture/mcp-server.md+++ b/technical-documentation/architecture/mcp-server.md@@ -146,15 +146,16 @@ What differs between the two servers is who records, handed in as a `TakeRecorde| | In-app server | `openscreen mcp` ||---|---|---|| Recorder | `createAppRecorder` (app-recorder.ts) | `runnerRecorder` (media-tools.ts) |-| `startRecording` | Points the recording bar at the request, as the editor's Record mode does before it hands over: the source, picked from the list `listSources` shows (`pickRecordingSource`, as `openscreen record`), and the microphone, system audio and editable cursor in the recording prefs. Then hands over as the editor's Record button does (`start-new-recording`): the editor closes, the HUD starts the take with its countdown and its camera setting. Returns once `set-recording-state` says it records. Refused while the editor has unsaved changes, since the editor closes. Where the system's picker owns the choice (the Linux portal, Apple's picker on macOS 15.2+), the request picks nothing: that picker asks the user. | A hidden `cli-record` runner of its own process, as `openscreen record`. |-| `stopRecording` | Presses the HUD's Stop, as the tray does. The HUD saves the take and hands it to the editor (`set-current-recording-session`), which imports it as for any take: one clip, measured, and the zooms on its clicks when Record mode's *Auto-zoom after recording* is on. The recorder waits for the editor's document to hold the take with its real length, then for its revision to hold still for 1.5 s, and returns that project, open in the editor. A `title` is applied through the editor. | Stops the runner and makes the project here (`createProjectFromVideo`): a fresh id no editor can hold, the zooms planned from the clicks. |-| The user's settings | The source, microphone, system audio and cursor mode the user had come back once the take is captured, or as the app quits mid-take. A request that fails before the take changes none of them. | Untouched: the runner never saves them. |+| `startRecording` | Points the recording bar at the request, as the editor's Record mode does before it hands over: the source, picked from the list `listSources` shows (`pickRecordingSource`, as `openscreen record`), and the microphone, camera, system audio and cursor mode in the recording prefs (`takePrefs`; a device named by the client is looked up in the same list, for its id beside its name). Then hands over as the editor's Record button does (`start-new-recording`): the editor closes, the HUD starts the take with its countdown. Returns once `set-recording-state` says it records. Refused while the editor has unsaved changes, since the editor closes. Where the system's picker owns the choice (the Linux portal, Apple's picker on macOS 15.2+), the request picks nothing: that picker asks the user. | A hidden `cli-record` runner of its own process, as `openscreen record`, with the same request (`CliRecordRequest`: source, microphone, camera, system audio, cursor mode). |+| `stopRecording` | Presses the HUD's Stop, as the tray does. The HUD saves the take and hands it to the editor (`set-current-recording-session`), which imports it as for any take: one clip, measured, and the zooms on its clicks when Record mode's *Auto-zoom after recording* is on. The recorder waits for the editor's document to hold the take with its real length, then for its revision to hold still for 1.5 s, and returns that project, open in the editor. A `title` is applied through the editor. | Stops the runner and makes the project here (`createProjectFromVideo`): a fresh id no editor can hold, the zooms planned from the clicks, and the webcam, when one was recorded, linked to the take's asset as the editor links it (its offset and size). |+| The user's settings | The source, microphone, camera, system audio and cursor mode the user had (`TAKE_PREF_KEYS`) come back once the take is captured, or as the app quits mid-take. A request that fails before the take changes none of them. | Untouched: the runner never saves them. |Then both servers carry on alike:- `stopRecording` creates the take's checkpoint through the runner, and records when the take started, by its video, for `setPointerTrack`.- `setPointerTrack` gives a script-driven take a pointer track and plans zooms on its clicks. `pointerTrackEdit` computes the new sidecar and the zooms from the project the runner read, writes nothing itself, and hands both to the runner as a `RunnerEdit`. The runner then applies the same refusals as any edit (another process's editor, no checkpoint, a project changed mid-call) before writing anything, saves the project, and only then writes the sidecar, keeping its previous content for the checkpoints. Every refusal comes back as the tool's own text result. A sidecar write that fails after the save is reported as a partial edit: the project was saved, the pointer track was not. A `RunnerEdit` is a closure and cannot be forwarded, so the call carries what the edit needs (`events`, and `takes`, each take's start time by video): the app's channel serves `setPointerTrack` with those args and runs `pointerTrackEdit` in its own runner. That is the channel's own registration, not the in-app server's tool: the takes of `openscreen mcp` are known to it alone.- `exportVideo` renders in a hidden `cli-export` runner, the same in both processes: in the app, `listSources` and `exportVideo` run the CLI's runners (`createRunnerHost` with `createRunnerWindow`), whose IPC the app registers on first use. The runner reads the project by id (`CliExportRequest.projectId`, the editor's own `aiEdition.get`), not by path: opening a file by path moves the main process's current project and recording-session slot, which in the app is the hand-off from the recorder to the editor.+- `exportVideo` takes the Export dialog's options and choices: `quality` and `fps` (24, 30, 60) for an MP4, `gifFrameRate`, `gifSize` and `gifLoop` for a GIF, the dialog's defaults when left out. An option of the other format is refused rather than ignored. Hiding the desktop icons is not a `startRecording` option: the HUD has no such control, so it follows the user's Record mode setting on both servers. Nor are the CLI's `--auto-zoom` and `--audio`: zooms and a voiceover are edits of the project, and an export that added them would not be the project `getFrames` maps through.- `exportVideo` and `getFrames` read projects; they write none. Over HTTP their paths must be absolute.- `createProject` makes a project with `DocumentService.createProject`, so it starts in the look new projects take (the preset marked for them, else the last edited project's), as the editor's New does. With a `videoPath` it lays the video out with `createProjectFromVideo`, the path a stdio take goes through: one clip, measured, and the zooms on its clicks when a pointer track sits beside it. Either way it returns a checkpoint, as `stopRecording` does, so the client can edit the closed project at once. It runs where the media tools run (in the CLI process for `openscreen mcp`): a new project is one no editor holds. **MCP edits** gates it.diff --git a/technical-documentation/testing/manual-e2e-checklist.md b/technical-documentation/testing/manual-e2e-checklist.mdindex ccb79b010..524bdf526 100644--- a/technical-documentation/testing/manual-e2e-checklist.md+++ b/technical-documentation/testing/manual-e2e-checklist.md@@ -574,12 +574,13 @@ Two servers. The **in-app** one is HTTP, in *AI settings* → *MCP server*, off- [ ] In *AI settings*, confirm *Enable MCP server* and *Allow MCP clients to edit your projects, record and export* are off by default; enable the server and confirm the status reads *Running* with a *Port*, an *Access token* (Show, Copy, Regenerate) and the Claude Code and Codex snippets. Change the port, *Apply*, and confirm a client reconnects on it.- [ ] With edits not allowed, confirm an edit tool, `startRecording` and `exportVideo` are refused, naming *MCP edits*; allow them and confirm the edit lands in the open editor and undoes with `Ctrl/Cmd+Z`.-- [ ] From a client of the **in-app** server, `startRecording` on a window: the editor closes and the recording bar records, its countdown first, with no second recorder process. Click in the window, `stopRecording`: the editor opens on the take, laid out and zoomed as after a take started by hand, and the returned `projectId` is that project. An edit to it lands live and undoes with `Ctrl/Cmd+Z`; `exportVideo` to an absolute path and `getFrames` on it work. Confirm the recording bar's microphone and system audio are back to what they were before the take, and that `startRecording` is refused while the editor has unsaved changes.-- [ ] Confirm `"<exe>" help` lists `mcp`, register the stdio server in an MCP client, and confirm `listSources` lists displays, windows and microphones.+- [ ] From a client of the **in-app** server, `startRecording` on a window: the editor closes and the recording bar records, its countdown first, with no second recorder process. Click in the window, `stopRecording`: the editor opens on the take, laid out and zoomed as after a take started by hand, and the returned `projectId` is that project. An edit to it lands live and undoes with `Ctrl/Cmd+Z`; `exportVideo` to an absolute path and `getFrames` on it work. Confirm the recording bar's microphone, camera, system audio and cursor mode are back to what they were before the take, and that `startRecording` is refused while the editor has unsaved changes.+- [ ] Confirm `"<exe>" help` lists `mcp`, register the stdio server in an MCP client, and confirm `listSources` lists displays, windows, microphones and cameras.- [ ] Run `startRecording` on a window, click inside it a few times, `stopRecording`, and confirm the returned project is in the editor's project list with one clip and the zooms its `autoZooms` count announces. Clicks close in time (3 s or less) and on screen share one zoom, and a click in the first seconds or the stopping click gets none, so there can be fewer zooms than clicks. On macOS 15.2+, confirm Apple's picker never appears; on Linux, confirm the portal asks.- [ ] Edit that project while it is closed, `restoreCheckpoint` with the returned checkpoint, and confirm the project is back to the raw take. Confirm an edit to a closed project with no checkpoint is refused.- [ ] Open the project in the editor, with the in-app MCP server turned off, then send an edit to it through the **stdio** server, a process apart from the app (#1174): `listProjects` reports the project `open: true`, the edit shows in the editor at once, Ctrl+Z takes it back in one step, and a later change in the editor (its autosave) keeps it. `restoreCheckpoint` with the checkpoint from `stopRecording` also lands in the editor as one undo step. Quit OpenScreen mid-session: the next stdio edit to that project, now closed, asks for a checkpoint (the app's left with it), and after `createCheckpoint` lands in its file. Relaunch OpenScreen and open the project: the next stdio edit goes through the editor again, with no restart of the MCP client.- [ ] `exportVideo`, then `getFrames` at a few ruler seconds after a trim, and confirm the frames show the moments asked for; edit the project again and confirm `getFrames` warns that the export is stale.+- [ ] On each server, `startRecording` with `camera: true` (then a camera's name from `listSources`) and `cursor: "system"`: the take opens with the webcam as a picture-in-picture, the system pointer is in the video and no zoom was planned. `exportVideo` at `fps: 30` gives a 30 fps MP4; to a `.gif` with `gifSize: "small"` and `gifLoop: false` a GIF 480 pixels high that plays once; `gifLoop` on an `.mp4` path is refused.- [ ] Drive a take from a script instead of the mouse, hand its action log to `setPointerTrack`, and confirm the export draws a cursor and zooms on the logged clicks.## Native compositor preview and export — v1.8.0diff --git a/website/docs/ai-editing.md b/website/docs/ai-editing.mdindex 34b23ac74..2a6d13204 100644--- a/website/docs/ai-editing.md+++ b/website/docs/ai-editing.md@@ -76,7 +76,7 @@ Checkpoints are kept in OpenScreen's memory: they are lost when it quits or when## Letting an agent make the whole video-An agent can make a whole video on its own, from the recording to the export. Besides the editing tools, both ways of adding OpenScreen to it give it `listSources`, `startRecording`, `stopRecording`, `setPointerTrack`, `exportVideo`, `getFrames` and `createProject`.+An agent can make a whole video on its own, from the recording to the export. Besides the editing tools, both ways of adding OpenScreen to it give it `listSources`, `startRecording`, `stopRecording`, `setPointerTrack`, `exportVideo`, `getFrames` and `createProject`. A take can also record your webcam and the system's own cursor, as the recording bar can, and an export takes the Export dialog's options: quality and frame rate for an MP4; frame rate, size and looping for a GIF.**Through the server above**, a take is recorded by OpenScreen itself, as with its Record button: the editor closes, the recording bar counts down and records, and the take opens in the editor as a new project, where you watch each edit land. It needs **MCP edits** on, and the recording bar gets your own settings back once the take ends.diff --git a/website/docs/cli.md b/website/docs/cli.mdindex d433ab800..ec375387f 100644--- a/website/docs/cli.md+++ b/website/docs/cli.md@@ -64,12 +64,14 @@ openscreen record --display 1 --cursor system| `--mic` | Capture the default microphone || `--mic-device <name>` | Capture the microphone whose label contains `<name>`, ignoring case. Implies `--mic` || `--system-audio` | Capture system audio |+| `--camera` | Record the default webcam beside the screen |+| `--camera-device <name>` | Record the camera whose label contains `<name>`, ignoring case. Implies `--camera` || `--cursor <editable-overlay\|system>` | `editable-overlay` (default) hides the system pointer and records it as data, so the editor can restyle it. `system` draws the pointer into the video || `--duration <seconds>` | Stop automatically after this long || `--project <out.openscreen>` | When done, write a project file that references the recording, ready for `export` or the editor. Must end in `.openscreen` || `--json` | NDJSON events on stdout |-There is no webcam option: a CLI recording contains the screen and audio only.+With `--camera`, the webcam is recorded beside the screen, and the `--project` file links it.**Stopping.** Without `--duration`, stop a recording with Ctrl+C (SIGINT), SIGTERM, or by typing `stop`, `q` or `quit` and Enter on its stdin. Closing stdin does not stop it. A forced kill skips the normal finish, so no `done` event and no project file are written.@@ -81,7 +83,7 @@ There is no webcam option: a CLI recording contains the screen and audio only.### `openscreen sources`-Lists the displays, windows and microphones the app can see, so a script can choose `--display`, `--window` and `--mic-device` values. On Linux the portal picker still decides what `record` captures.+Lists the displays, windows, microphones and cameras the app can see, so a script can choose `--display`, `--window`, `--mic-device` and `--camera-device` values. On Linux the portal picker still decides what `record` captures.```bashopenscreen sources # human-readable@@ -99,12 +101,14 @@ With `--json`, the payload arrives inside the final `done` event:"displays": [{ "index": 0, "id": "screen:1:0", "name": "Entire screen" }],"windows": [{ "id": "window:210:0", "name": "My App" }],"microphones": [{ "label": "Built-in Microphone" }],- "microphoneLabelsUnavailable": false+ "microphoneLabelsUnavailable": false,+ "cameras": [{ "label": "FaceTime HD Camera" }],+ "cameraLabelsUnavailable": false}}```-`microphoneLabelsUnavailable` is `true` when device names need a permission that has not been granted, or when the device list could not be read within a few seconds.+`microphoneLabelsUnavailable` is `true` when device names need a permission that has not been granted, or when the device list could not be read within a few seconds. `cameraLabelsUnavailable` says the same of cameras.**Why `-o` exists.** The CLI writes only its own output to stdout; Chromium's diagnostics go to stderr. The wrapper around the process is another matter. Ubuntu's `xvfb-run`, the usual way to run a GUI binary on a machine without a screen, merges stderr into stdout, so Chromium's startup warnings land ahead of the JSON and `openscreen sources --json | jq` fails. `-o <file>` writes to a place no wrapper can redirect, and it avoids shell quoting and encoding differences.@@ -132,16 +136,18 @@ openscreen export demo.openscreen -o out.mp4 --auto-zoom --json|---|---|| `-o, --out <path>` | Output file. The extension, `.mp4` or `.gif`, sets the format. Default: the project's path with `.mp4` or `.gif` || `--format <mp4\|gif>` | Override the format stored in the project. Must agree with `--out` |-| `--quality <medium\|good\|source>` | Output size: `medium` is 720p, `good` is 1080p, `source` follows the smallest clip after cropping, so it never upscales. A GIF starts from this size too |+| `--quality <medium\|good\|source>` | Output size: `medium` is 720p, `good` is 1080p, `source` follows the smallest clip after cropping, so it never upscales. MP4 only: a GIF starts from the source size, as in the app |+| `--fps <24\|30\|60>` | MP4 frame rate (default 60) || `--gif-fps <15\|20\|25\|30>` | GIF frame rate |-| `--gif-size <medium\|large\|original>` | GIF height cap applied to that size: 720, 1080, or none |+| `--gif-size <small\|medium\|large\|original>` | GIF height cap applied to the source size: 480, 720, 1080, or none |+| `--gif-loop`, `--no-gif-loop` | The GIF loops forever, or plays once. Default: from the project || `--auto-zoom` | Before rendering, add zooms on the recorded clicks, with the same engine as the editor's [automatic zooms](/features/auto-zoom/). Existing zooms are kept, and new ones keep clear of them || `--audio <file>` | Mix a voiceover file (mp3, wav or m4a) into the MP4. MP4 only || `--audio-mode <mix\|replace>` | `mix` (default) keeps the recording's audio under the voiceover at 40% gain; `replace` drops it || `--audio-offset <seconds>` | Delay before the voiceover starts (default 0) || `--json` | NDJSON progress and result on stdout |-MP4 exports from the CLI are always **H.264 at 60 fps**. There is no codec or frame-rate option. The desktop app's [Export](./export.md) dialog also offers 24 or 30 fps.+MP4 exports from the CLI are always **H.264**, at 60 fps unless `--fps` says otherwise. There is no codec option.`--audio` works after the render: the video stream is copied untouched, and a new AAC track is mixed and written over the same output file.@@ -288,8 +294,7 @@ Save it in the same folder as the clip. Without cursor telemetry, `--auto-zoom`- **You need to record on a server** with no display or desktop session. Recording needs a real desktop, and on Linux someone has to answer the portal picker on each run.- **You need a stable, versioned API.** The CLI and the project format can still change between releases.-- **You need codec, frame-rate or bitrate control from the command line.** CLI MP4 exports are H.264 at 60 fps, and the MP4 bitrate is not adjustable in the app either.-- **You need the webcam in a scripted recording.** `record` has no camera option.+- **You need codec or bitrate control from the command line.** CLI MP4 exports are H.264, and the MP4 bitrate is not adjustable in the app either.- **You need subtitle files.** Captions are burned into the video only.For a hands-on walkthrough of the same steps in the editor, see [How to make a product demo video](./guides/product-demo-video.md). Answers on licensing and network use are in the [FAQ](./faq.md).diff --git a/website/i18n/de/docusaurus-plugin-content-docs/current/ai-editing.md b/website/i18n/de/docusaurus-plugin-content-docs/current/ai-editing.mdindex 1a8954b16..ca10e9f4d 100644--- a/website/i18n/de/docusaurus-plugin-content-docs/current/ai-editing.md+++ b/website/i18n/de/docusaurus-plugin-content-docs/current/ai-editing.md@@ -76,7 +76,7 @@ Wiederherstellungspunkte liegen im Speicher von OpenScreen: Sie gehen verloren,## Einen Agenten das ganze Video erstellen lassen {#letting-an-agent-make-the-whole-video}-Ein Agent kann ein ganzes Video selbstständig erstellen, von der Aufnahme bis zum Export. Neben den Bearbeitungswerkzeugen geben ihm beide Wege, OpenScreen hinzuzufügen, `listSources`, `startRecording`, `stopRecording`, `setPointerTrack`, `exportVideo`, `getFrames` und `createProject`.+Ein Agent kann ein ganzes Video selbstständig erstellen, von der Aufnahme bis zum Export. Neben den Bearbeitungswerkzeugen geben ihm beide Wege, OpenScreen hinzuzufügen, `listSources`, `startRecording`, `stopRecording`, `setPointerTrack`, `exportVideo`, `getFrames` und `createProject`. Eine Aufnahme kann wie mit der Aufnahmeleiste auch Ihre Webcam und den eigenen Mauszeiger des Systems aufnehmen, und ein Export übernimmt die Optionen des Export-Dialogs: Qualität und Bildrate für ein MP4; Bildrate, Größe und Wiederholung für ein GIF.**Über den Server oben** nimmt OpenScreen eine Aufnahme selbst auf, wie mit seinem Aufnahme-Button: Der Editor schließt sich, die Aufnahmeleiste zählt herunter und nimmt auf, und die Aufnahme öffnet sich im Editor als neues Projekt, wo du jede Änderung ankommen siehst. Dafür muss **MCP-Änderungen** an sein, und die Aufnahmeleiste bekommt am Ende der Aufnahme deine eigenen Einstellungen zurück.diff --git a/website/i18n/de/docusaurus-plugin-content-docs/current/cli.md b/website/i18n/de/docusaurus-plugin-content-docs/current/cli.mdindex 52740c759..33c128334 100644--- a/website/i18n/de/docusaurus-plugin-content-docs/current/cli.md+++ b/website/i18n/de/docusaurus-plugin-content-docs/current/cli.md@@ -64,12 +64,14 @@ openscreen record --display 1 --cursor system| `--mic` | Das Standardmikrofon aufnehmen || `--mic-device <name>` | Das Mikrofon aufnehmen, dessen Bezeichnung `<name>` enthält, ohne Beachtung der Groß-/Kleinschreibung. Schließt `--mic` ein || `--system-audio` | Systemaudio aufnehmen |+| `--camera` | Die Standard-Webcam neben dem Bildschirm aufnehmen |+| `--camera-device <name>` | Die Kamera aufnehmen, deren Name `<name>` enthält, ohne Beachtung der Groß- und Kleinschreibung. Impliziert `--camera` || `--cursor <editable-overlay\|system>` | `editable-overlay` (Standard) blendet den Systemzeiger aus und zeichnet ihn als Daten auf, damit der Editor ihn neu gestalten kann. `system` zeichnet den Zeiger ins Video || `--duration <seconds>` | Nach dieser Dauer automatisch stoppen || `--project <out.openscreen>` | Am Ende eine Projektdatei schreiben, die auf die Aufnahme verweist, bereit für `export` oder den Editor. Muss auf `.openscreen` enden || `--json` | NDJSON-Ereignisse auf stdout |-Eine Webcam-Option gibt es nicht: Eine CLI-Aufnahme enthält nur Bildschirm und Audio.+Mit `--camera` wird die Webcam neben dem Bildschirm aufgenommen, und die `--project`-Datei verweist auf sie.**Stoppen.** Ohne `--duration` stoppst du eine Aufnahme mit Ctrl+C (SIGINT), mit SIGTERM oder indem du `stop`, `q` oder `quit` und Enter auf ihrem stdin eingibst. Das Schließen von stdin stoppt sie nicht. Ein erzwungenes Beenden überspringt den normalen Abschluss, es wird also weder ein `done`-Ereignis noch eine Projektdatei geschrieben.@@ -81,7 +83,7 @@ Eine Webcam-Option gibt es nicht: Eine CLI-Aufnahme enthält nur Bildschirm und### `openscreen sources` {#openscreen-sources}-Listet die Bildschirme, Fenster und Mikrofone auf, die die App sieht, damit ein Skript Werte für `--display`, `--window` und `--mic-device` wählen kann. Unter Linux entscheidet trotzdem die Portal-Auswahl, was `record` aufnimmt.+Listet die Bildschirme, Fenster, Mikrofone und Kameras auf, die die App sieht, damit ein Skript Werte für `--display`, `--window`, `--mic-device` und `--camera-device` wählen kann. Unter Linux entscheidet trotzdem die Portal-Auswahl, was `record` aufnimmt.```bashopenscreen sources # human-readable@@ -99,12 +101,14 @@ Mit `--json` kommen die Nutzdaten im abschließenden `done`-Ereignis an:"displays": [{ "index": 0, "id": "screen:1:0", "name": "Entire screen" }],"windows": [{ "id": "window:210:0", "name": "My App" }],"microphones": [{ "label": "Built-in Microphone" }],- "microphoneLabelsUnavailable": false+ "microphoneLabelsUnavailable": false,+ "cameras": [{ "label": "FaceTime HD Camera" }],+ "cameraLabelsUnavailable": false}}```-`microphoneLabelsUnavailable` ist `true`, wenn die Gerätenamen eine Berechtigung brauchen, die nicht erteilt wurde, oder wenn die Geräteliste nicht innerhalb weniger Sekunden gelesen werden konnte.+`microphoneLabelsUnavailable` ist `true`, wenn die Gerätenamen eine Berechtigung brauchen, die nicht erteilt wurde, oder wenn die Geräteliste nicht innerhalb weniger Sekunden gelesen werden konnte. `cameraLabelsUnavailable` gilt ebenso für Kameras.**Wozu `-o` da ist.** Die CLI schreibt nur ihre eigene Ausgabe auf stdout; die Diagnosemeldungen von Chromium gehen auf stderr. Der Wrapper um den Prozess ist eine andere Sache. Ubuntus `xvfb-run`, der übliche Weg, ein GUI-Programm auf einem Rechner ohne Bildschirm auszuführen, führt stderr mit stdout zusammen. Die Startwarnungen von Chromium landen dann vor dem JSON, und `openscreen sources --json | jq` schlägt fehl. `-o <file>` schreibt an eine Stelle, die kein Wrapper umleiten kann, und umgeht Unterschiede bei Shell-Quoting und Zeichenkodierung.@@ -132,16 +136,18 @@ openscreen export demo.openscreen -o out.mp4 --auto-zoom --json|---|---|| `-o, --out <path>` | Ausgabedatei. Die Endung, `.mp4` oder `.gif`, legt das Format fest. Standard: der Pfad des Projekts mit `.mp4` oder `.gif` || `--format <mp4\|gif>` | Das im Projekt gespeicherte Format überschreiben. Muss zu `--out` passen |-| `--quality <medium\|good\|source>` | Ausgabegröße: `medium` ist 720p, `good` ist 1080p, `source` richtet sich nach dem kleinsten Clip nach dem Zuschnitt und skaliert daher nie hoch. Auch ein GIF geht von dieser Größe aus |+| `--quality <medium\|good\|source>` | Ausgabegröße: `medium` ist 720p, `good` ist 1080p, `source` richtet sich nach dem kleinsten Clip nach dem Zuschnitt und skaliert daher nie hoch. Nur MP4: Ein GIF geht wie in der App von der Quellgröße aus |+| `--fps <24\|30\|60>` | Bildrate des MP4 (Standard 60) || `--gif-fps <15\|20\|25\|30>` | Bildrate des GIF |-| `--gif-size <medium\|large\|original>` | Höhenbegrenzung des GIF, angewendet auf diese Größe: 720, 1080 oder keine |+| `--gif-size <small\|medium\|large\|original>` | Höhenbegrenzung des GIF, angewendet auf die Quellgröße: 480, 720, 1080 oder keine |+| `--gif-loop`, `--no-gif-loop` | Das GIF läuft endlos in Schleife oder wird einmal abgespielt. Standard: aus dem Projekt || `--auto-zoom` | Vor dem Rendern Zooms auf die aufgezeichneten Klicks setzen, mit derselben Engine wie die [automatischen Zooms](/features/auto-zoom/) des Editors. Vorhandene Zooms bleiben erhalten, und neue halten Abstand zu ihnen || `--audio <file>` | Eine Voice-over-Datei (mp3, wav oder m4a) ins MP4 mischen. Nur MP4 || `--audio-mode <mix\|replace>` | `mix` (Standard) behält den Ton der Aufnahme mit 40 % Pegel unter dem Voice-over; `replace` entfernt ihn || `--audio-offset <seconds>` | Verzögerung, bevor das Voice-over beginnt (Standard 0) || `--json` | NDJSON für Fortschritt und Ergebnis auf stdout |-MP4-Exporte aus der CLI sind immer **H.264 mit 60 fps**. Eine Option für Codec oder Bildrate gibt es nicht. Der [Export](./export.md)-Dialog der Desktop-App bietet zusätzlich 24 oder 30 fps.+MP4-Exporte aus der CLI sind immer **H.264**, mit 60 fps, sofern `--fps` nichts anderes angibt. Eine Codec-Option gibt es nicht.`--audio` greift nach dem Rendern: Der Videostream wird unverändert kopiert, und eine neue AAC-Spur wird gemischt und über dieselbe Ausgabedatei geschrieben.@@ -288,8 +294,7 @@ Speichere das Projekt im selben Ordner wie den Clip. Ohne Cursor-Telemetrie hat- **Du musst auf einem Server aufnehmen**, ohne Display oder Desktop-Sitzung. Die Aufnahme braucht einen echten Desktop, und unter Linux muss bei jedem Lauf jemand die Portal-Auswahl beantworten.- **Du brauchst eine stabile, versionierte API.** Die CLI und das Projektformat können sich zwischen Versionen noch ändern.-- **Du willst Codec, Bildrate oder Bitrate über die Kommandozeile steuern.** CLI-MP4-Exporte sind H.264 mit 60 fps, und die MP4-Bitrate lässt sich auch in der App nicht einstellen.-- **Du brauchst die Webcam in einer skriptgesteuerten Aufnahme.** `record` hat keine Kamera-Option.+- **Du willst Codec oder Bitrate über die Kommandozeile steuern.** CLI-MP4-Exporte sind H.264, und die MP4-Bitrate lässt sich auch in der App nicht einstellen.- **Du brauchst Untertiteldateien.** Untertitel werden nur ins Video eingebrannt.Eine praktische Anleitung mit denselben Schritten im Editor findest du unter [So erstellst du ein Produktdemo-Video](./guides/product-demo-video.md). Antworten zu Lizenz und Netzwerknutzung stehen in der [FAQ](./faq.md).diff --git a/website/i18n/es/docusaurus-plugin-content-docs/current/ai-editing.md b/website/i18n/es/docusaurus-plugin-content-docs/current/ai-editing.mdindex b0c79e2bb..02162af31 100644--- a/website/i18n/es/docusaurus-plugin-content-docs/current/ai-editing.md+++ b/website/i18n/es/docusaurus-plugin-content-docs/current/ai-editing.md@@ -76,7 +76,7 @@ Los puntos de restauración se guardan en la memoria de OpenScreen: se pierden c## Dejar que un agente haga todo el video {#letting-an-agent-make-the-whole-video}-Un agente puede hacer un video completo por sí solo, desde la grabación hasta la exportación. Además de las herramientas de edición, las dos formas de agregar OpenScreen al agente le dan `listSources`, `startRecording`, `stopRecording`, `setPointerTrack`, `exportVideo`, `getFrames` y `createProject`.+Un agente puede hacer un video completo por sí solo, desde la grabación hasta la exportación. Además de las herramientas de edición, las dos formas de agregar OpenScreen al agente le dan `listSources`, `startRecording`, `stopRecording`, `setPointerTrack`, `exportVideo`, `getFrames` y `createProject`. Una toma también puede grabar tu cámara web y el cursor propio del sistema, como la barra de grabación, y una exportación acepta las opciones del diálogo de exportación: calidad y velocidad de fotogramas para un MP4; velocidad de fotogramas, tamaño y bucle para un GIF.**Con el servidor de arriba**, la toma la graba el propio OpenScreen, como con su botón Grabar: el editor se cierra, la barra de grabación hace su cuenta regresiva y graba, y la toma se abre en el editor como un proyecto nuevo, donde ves llegar cada edición. Necesita **Ediciones por MCP** activado, y la barra de grabación recupera tus propios ajustes al terminar la toma.diff --git a/website/i18n/es/docusaurus-plugin-content-docs/current/cli.md b/website/i18n/es/docusaurus-plugin-content-docs/current/cli.mdindex 650b5f0ed..50d42e33d 100644--- a/website/i18n/es/docusaurus-plugin-content-docs/current/cli.md+++ b/website/i18n/es/docusaurus-plugin-content-docs/current/cli.md@@ -64,12 +64,14 @@ openscreen record --display 1 --cursor system| `--mic` | Captura el micrófono predeterminado || `--mic-device <name>` | Captura el micrófono cuya etiqueta contenga `<name>`, sin distinguir mayúsculas de minúsculas. Implica `--mic` || `--system-audio` | Captura el audio del sistema |+| `--camera` | Graba la cámara web predeterminada junto a la pantalla |+| `--camera-device <name>` | Graba la cámara cuyo nombre contiene `<name>`, sin distinguir mayúsculas de minúsculas. Implica `--camera` || `--cursor <editable-overlay\|system>` | `editable-overlay` (predeterminado) oculta el puntero del sistema y lo graba como datos, para que el editor pueda cambiar su estilo. `system` dibuja el puntero en el video || `--duration <seconds>` | Se detiene automáticamente tras ese tiempo || `--project <out.openscreen>` | Al terminar, escribe un archivo de proyecto que hace referencia a la grabación, listo para `export` o para el editor. Debe terminar en `.openscreen` || `--json` | Eventos NDJSON por stdout |-No hay opción de cámara web: una grabación hecha desde la CLI solo contiene la pantalla y el audio.+Con `--camera`, la cámara web se graba junto a la pantalla, y el archivo de `--project` la enlaza.**Detener la grabación.** Sin `--duration`, detén una grabación con Ctrl+C (SIGINT), con SIGTERM o escribiendo `stop`, `q` o `quit` seguido de Enter en su stdin. Cerrar stdin no la detiene. Forzar la terminación del proceso omite el cierre normal, así que no se escriben ni el evento `done` ni el archivo de proyecto.@@ -81,7 +83,7 @@ No hay opción de cámara web: una grabación hecha desde la CLI solo contiene l### `openscreen sources` {#openscreen-sources}-Muestra las pantallas, las ventanas y los micrófonos que la app puede ver, para que un script elija los valores de `--display`, `--window` y `--mic-device`. En Linux, el selector del portal sigue decidiendo qué captura `record`.+Muestra las pantallas, las ventanas, los micrófonos y las cámaras que la app puede ver, para que un script elija los valores de `--display`, `--window`, `--mic-device` y `--camera-device`. En Linux, el selector del portal sigue decidiendo qué captura `record`.```bashopenscreen sources # human-readable@@ -99,12 +101,14 @@ Con `--json`, los datos llegan dentro del evento final `done`:"displays": [{ "index": 0, "id": "screen:1:0", "name": "Entire screen" }],"windows": [{ "id": "window:210:0", "name": "My App" }],"microphones": [{ "label": "Built-in Microphone" }],- "microphoneLabelsUnavailable": false+ "microphoneLabelsUnavailable": false,+ "cameras": [{ "label": "FaceTime HD Camera" }],+ "cameraLabelsUnavailable": false}}```-`microphoneLabelsUnavailable` vale `true` cuando los nombres de los dispositivos requieren un permiso que no se ha concedido, o cuando no se pudo leer la lista de dispositivos en unos segundos.+`microphoneLabelsUnavailable` vale `true` cuando los nombres de los dispositivos requieren un permiso que no se ha concedido, o cuando no se pudo leer la lista de dispositivos en unos segundos. `cameraLabelsUnavailable` indica lo mismo para las cámaras.**Por qué existe `-o`.** La CLI solo escribe su propia salida en stdout; los diagnósticos de Chromium van a stderr. Lo que envuelve al proceso es otra historia. `xvfb-run` de Ubuntu, la forma habitual de ejecutar un binario con interfaz gráfica en una máquina sin pantalla, mezcla stderr con stdout, así que las advertencias de inicio de Chromium llegan antes que el JSON y `openscreen sources --json | jq` falla. `-o <file>` escribe en un lugar que ningún envoltorio puede redirigir, y evita las diferencias de comillas y de codificación entre shells.@@ -132,16 +136,18 @@ openscreen export demo.openscreen -o out.mp4 --auto-zoom --json|---|---|| `-o, --out <path>` | Archivo de salida. La extensión, `.mp4` o `.gif`, define el formato. Predeterminado: la ruta del proyecto con `.mp4` o `.gif` || `--format <mp4\|gif>` | Reemplaza el formato guardado en el proyecto. Debe coincidir con `--out` |-| `--quality <medium\|good\|source>` | Tamaño de salida: `medium` es 720p, `good` es 1080p y `source` sigue al clip más pequeño una vez recortado, así que nunca amplía. Un GIF también parte de este tamaño |+| `--quality <medium\|good\|source>` | Tamaño de salida: `medium` es 720p, `good` es 1080p y `source` sigue al clip más pequeño una vez recortado, así que nunca amplía. Solo MP4: un GIF parte del tamaño de origen, como en la app |+| `--fps <24\|30\|60>` | Fotogramas por segundo del MP4 (60 por defecto) || `--gif-fps <15\|20\|25\|30>` | Fotogramas por segundo del GIF |-| `--gif-size <medium\|large\|original>` | Límite de altura del GIF que se aplica a ese tamaño: 720, 1080 o ninguno |+| `--gif-size <small\|medium\|large\|original>` | Límite de altura del GIF que se aplica al tamaño de origen: 480, 720, 1080 o ninguno |+| `--gif-loop`, `--no-gif-loop` | El GIF se repite sin fin o se reproduce una vez. Por defecto: lo que indica el proyecto || `--auto-zoom` | Antes de renderizar, agrega zooms en los clics grabados, con el mismo motor que los [zooms automáticos](/features/auto-zoom/) del editor. Los zooms existentes se conservan, y los nuevos quedan apartados de ellos || `--audio <file>` | Mezcla un archivo de voz en off (mp3, wav o m4a) en el MP4. Solo MP4 || `--audio-mode <mix\|replace>` | `mix` (predeterminado) mantiene el audio de la grabación debajo de la voz en off, con una ganancia del 40 %; `replace` lo elimina || `--audio-offset <seconds>` | Retraso antes de que empiece la voz en off (predeterminado: 0) || `--json` | Progreso y resultado en NDJSON por stdout |-Las exportaciones MP4 desde la CLI son siempre **H.264 a 60 fps**. No hay opción de códec ni de fotogramas por segundo. El cuadro de diálogo de [Exportación](./export.md) de la app de escritorio ofrece además 24 o 30 fps.+Las exportaciones MP4 desde la CLI son siempre **H.264**, a 60 fps salvo que `--fps` indique otra cosa. No hay opción de códec.`--audio` actúa después del renderizado: el flujo de video se copia sin cambios, y se mezcla una nueva pista AAC que se escribe sobre el mismo archivo de salida.@@ -288,8 +294,7 @@ Guárdalo en la misma carpeta que el clip. Sin telemetría del cursor, `--auto-z- **Necesitas grabar en un servidor** sin pantalla ni sesión de escritorio. Grabar requiere un escritorio real, y en Linux alguien tiene que responder al selector del portal en cada ejecución.- **Necesitas una API estable y versionada.** La CLI y el formato de proyecto todavía pueden cambiar entre versiones.-- **Necesitas controlar el códec, los fotogramas por segundo o la tasa de bits desde la línea de comandos.** Las exportaciones MP4 de la CLI son H.264 a 60 fps, y la tasa de bits del MP4 tampoco se puede ajustar en la app.-- **Necesitas la cámara web en una grabación automatizada.** `record` no tiene opción de cámara.+- **Necesitas controlar el códec o la tasa de bits desde la línea de comandos.** Las exportaciones MP4 de la CLI son H.264, y la tasa de bits del MP4 tampoco se puede ajustar en la app.- **Necesitas archivos de subtítulos.** Los subtítulos solo se incrustan en el video.Para un recorrido práctico por los mismos pasos en el editor, consulta [Cómo hacer un video de demostración de producto](./guides/product-demo-video.md). Las respuestas sobre la licencia y el uso de la red están en las [preguntas frecuentes](./faq.md).diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/current/ai-editing.md b/website/i18n/fr/docusaurus-plugin-content-docs/current/ai-editing.mdindex 14245df5e..4c7bacfd7 100644--- a/website/i18n/fr/docusaurus-plugin-content-docs/current/ai-editing.md+++ b/website/i18n/fr/docusaurus-plugin-content-docs/current/ai-editing.md@@ -76,7 +76,7 @@ Les points de restauration sont gardés dans la mémoire d'OpenScreen : ils son## Laisser un agent faire toute la vidéo {#letting-an-agent-make-the-whole-video}-Un agent peut faire une vidéo entière tout seul, de l'enregistrement à l'export. En plus des outils d'édition, les deux façons d'ajouter OpenScreen à l'agent lui donnent `listSources`, `startRecording`, `stopRecording`, `setPointerTrack`, `exportVideo`, `getFrames` et `createProject`.+Un agent peut faire une vidéo entière tout seul, de l'enregistrement à l'export. En plus des outils d'édition, les deux façons d'ajouter OpenScreen à l'agent lui donnent `listSources`, `startRecording`, `stopRecording`, `setPointerTrack`, `exportVideo`, `getFrames` et `createProject`. Une prise peut aussi enregistrer votre webcam et le curseur du système, comme la barre d'enregistrement, et un export prend les options de la boîte d'export : qualité et fréquence d'images pour un MP4 ; fréquence d'images, taille et boucle pour un GIF.**Par le serveur ci-dessus**, une prise est enregistrée par OpenScreen lui-même, comme avec son bouton Enregistrer : l'éditeur se ferme, la barre d'enregistrement fait son décompte et enregistre, et la prise s'ouvre dans l'éditeur comme nouveau projet, où vous voyez chaque modification arriver. Il faut que **Modifications par MCP** soit activé, et la barre d'enregistrement retrouve vos propres réglages à la fin de la prise.diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/current/cli.md b/website/i18n/fr/docusaurus-plugin-content-docs/current/cli.mdindex 3b69d90f4..104e63f2c 100644--- a/website/i18n/fr/docusaurus-plugin-content-docs/current/cli.md+++ b/website/i18n/fr/docusaurus-plugin-content-docs/current/cli.md@@ -64,12 +64,14 @@ openscreen record --display 1 --cursor system| `--mic` | Capture le microphone par défaut || `--mic-device <name>` | Capture le microphone dont le nom contient `<name>`, sans tenir compte de la casse. Implique `--mic` || `--system-audio` | Capture l'audio système |+| `--camera` | Enregistre la webcam par défaut à côté de l'écran |+| `--camera-device <name>` | Enregistre la caméra dont le nom contient `<name>`, sans tenir compte de la casse. Implique `--camera` || `--cursor <editable-overlay\|system>` | `editable-overlay` (par défaut) masque le pointeur du système et l'enregistre sous forme de données, pour que l'éditeur puisse en changer le style. `system` dessine le pointeur dans la vidéo || `--duration <seconds>` | S'arrête automatiquement après cette durée || `--project <out.openscreen>` | À la fin, écrit un fichier de projet qui référence l'enregistrement, prêt pour `export` ou pour l'éditeur. Doit se terminer par `.openscreen` || `--json` | Événements NDJSON sur stdout |-Il n'y a pas d'option webcam : un enregistrement fait avec la CLI ne contient que l'écran et l'audio.+Avec `--camera`, la webcam est enregistrée à côté de l'écran, et le fichier `--project` la référence.**Arrêter.** Sans `--duration`, arrêtez un enregistrement avec Ctrl+C (SIGINT), SIGTERM, ou en tapant `stop`, `q` ou `quit` puis Entrée sur son stdin. Fermer stdin ne l'arrête pas. Un arrêt forcé court-circuite la fin normale : ni événement `done` ni fichier de projet ne sont alors écrits.@@ -81,7 +83,7 @@ Il n'y a pas d'option webcam : un enregistrement fait avec la CLI ne contient q### `openscreen sources` {#openscreen-sources}-Liste les écrans, fenêtres et microphones que voit l'application, pour qu'un script puisse choisir les valeurs de `--display`, `--window` et `--mic-device`. Sous Linux, c'est toujours le sélecteur du portail qui décide de ce que `record` capture.+Liste les écrans, fenêtres, microphones et caméras que voit l'application, pour qu'un script puisse choisir les valeurs de `--display`, `--window`, `--mic-device` et `--camera-device`. Sous Linux, c'est toujours le sélecteur du portail qui décide de ce que `record` capture.```bashopenscreen sources # human-readable@@ -99,12 +101,14 @@ Avec `--json`, les données arrivent dans l'événement `done` final :"displays": [{ "index": 0, "id": "screen:1:0", "name": "Entire screen" }],"windows": [{ "id": "window:210:0", "name": "My App" }],"microphones": [{ "label": "Built-in Microphone" }],- "microphoneLabelsUnavailable": false+ "microphoneLabelsUnavailable": false,+ "cameras": [{ "label": "FaceTime HD Camera" }],+ "cameraLabelsUnavailable": false}}```-`microphoneLabelsUnavailable` vaut `true` quand les noms des périphériques exigent une autorisation qui n'a pas été accordée, ou quand la liste des périphériques n'a pas pu être lue en quelques secondes.+`microphoneLabelsUnavailable` vaut `true` quand les noms des périphériques exigent une autorisation qui n'a pas été accordée, ou quand la liste des périphériques n'a pas pu être lue en quelques secondes. `cameraLabelsUnavailable` dit la même chose des caméras.**Pourquoi `-o` existe.** La CLI n'écrit que sa propre sortie sur stdout ; les diagnostics de Chromium vont sur stderr. Le programme qui enveloppe le processus, lui, est une autre affaire. `xvfb-run` d'Ubuntu, la façon habituelle de lancer un binaire graphique sur une machine sans écran, fusionne stderr dans stdout : les avertissements de démarrage de Chromium arrivent alors avant le JSON, et `openscreen sources --json | jq` échoue. `-o <file>` écrit à un endroit qu'aucun programme enveloppant ne peut rediriger, et évite les différences de guillemets et d'encodage entre shells.@@ -132,16 +136,18 @@ openscreen export demo.openscreen -o out.mp4 --auto-zoom --json|---|---|| `-o, --out <path>` | Fichier de sortie. L'extension, `.mp4` ou `.gif`, détermine le format. Par défaut : le chemin du projet avec `.mp4` ou `.gif` || `--format <mp4\|gif>` | Remplace le format enregistré dans le projet. Doit concorder avec `--out` |-| `--quality <medium\|good\|source>` | Taille de sortie : `medium` correspond à 720p, `good` à 1080p, et `source` suit le plus petit clip après recadrage, donc n'agrandit jamais. Un GIF part lui aussi de cette taille |+| `--quality <medium\|good\|source>` | Taille de sortie : `medium` correspond à 720p, `good` à 1080p, et `source` suit le plus petit clip après recadrage, donc n'agrandit jamais. MP4 uniquement : un GIF part de la taille source, comme dans l'application |+| `--fps <24\|30\|60>` | Fréquence d'images du MP4 (60 par défaut) || `--gif-fps <15\|20\|25\|30>` | Fréquence d'images du GIF |-| `--gif-size <medium\|large\|original>` | Hauteur maximale du GIF, appliquée à cette taille : 720, 1080, ou aucune |+| `--gif-size <small\|medium\|large\|original>` | Hauteur maximale du GIF, appliquée à la taille source : 480, 720, 1080, ou aucune |+| `--gif-loop`, `--no-gif-loop` | Le GIF boucle indéfiniment, ou se lit une fois. Par défaut : selon le projet || `--auto-zoom` | Avant le rendu, ajoute des zooms sur les clics enregistrés, avec le même moteur que les [zooms automatiques](/features/auto-zoom/) de l'éditeur. Les zooms existants sont conservés, et les nouveaux s'en tiennent à l'écart || `--audio <file>` | Mixe un fichier de voix off (mp3, wav ou m4a) dans le MP4. MP4 uniquement || `--audio-mode <mix\|replace>` | `mix` (par défaut) garde l'audio de l'enregistrement sous la voix off, avec un gain de 40 % ; `replace` le supprime || `--audio-offset <seconds>` | Délai avant le début de la voix off (0 par défaut) || `--json` | Progression et résultat en NDJSON sur stdout |-Les exports MP4 de la CLI sont toujours en **H.264 à 60 fps**. Il n'y a pas d'option de codec ni de fréquence d'images. La fenêtre [Export](./export.md) de l'application de bureau propose en plus 24 ou 30 fps.+Les exports MP4 de la CLI sont toujours en **H.264**, à 60 fps sauf si `--fps` en décide autrement. Il n'y a pas d'option de codec.`--audio` intervient après le rendu : le flux vidéo est copié sans modification, et une nouvelle piste AAC est mixée puis écrite par-dessus le même fichier de sortie.@@ -288,8 +294,7 @@ Enregistrez-le dans le même dossier que le clip. Sans télémétrie du curseur,- **Vous devez enregistrer sur un serveur** sans affichage ni session de bureau. L'enregistrement exige un vrai bureau, et sous Linux quelqu'un doit répondre au sélecteur du portail à chaque exécution.- **Vous avez besoin d'une API stable et versionnée.** La CLI et le format de projet peuvent encore changer d'une version à l'autre.-- **Vous voulez régler le codec, la fréquence d'images ou le débit en ligne de commande.** Les exports MP4 de la CLI sont en H.264 à 60 fps, et le débit MP4 n'est pas réglable non plus dans l'application.-- **Vous avez besoin de la webcam dans un enregistrement scripté.** `record` n'a pas d'option caméra.+- **Vous voulez régler le codec ou le débit en ligne de commande.** Les exports MP4 de la CLI sont en H.264, et le débit MP4 n'est pas réglable non plus dans l'application.- **Vous avez besoin de fichiers de sous-titres.** Les sous-titres sont uniquement incrustés dans la vidéo.Pour une mise en pratique des mêmes étapes dans l'éditeur, voir [Comment faire une vidéo de démo produit](./guides/product-demo-video.md). Les réponses sur la licence et l'usage du réseau se trouvent dans la [FAQ](./faq.md).diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/current/ai-editing.md b/website/i18n/ja/docusaurus-plugin-content-docs/current/ai-editing.mdindex 36cb414d5..bbc2f3ceb 100644--- a/website/i18n/ja/docusaurus-plugin-content-docs/current/ai-editing.md+++ b/website/i18n/ja/docusaurus-plugin-content-docs/current/ai-editing.md@@ -76,7 +76,7 @@ Claude Code や Codex などの AI コーディングエージェントをすで## エージェントに動画全体を作らせる {#letting-an-agent-make-the-whole-video}-エージェントは、録画からエクスポートまで、動画全体を自力で作れます。どちらの方法で OpenScreen を追加しても、編集ツールに加えて `listSources`、`startRecording`、`stopRecording`、`setPointerTrack`、`exportVideo`、`getFrames`、`createProject` を使えます。+エージェントは、録画からエクスポートまで、動画全体を自力で作れます。どちらの方法で OpenScreen を追加しても、編集ツールに加えて `listSources`、`startRecording`、`stopRecording`、`setPointerTrack`、`exportVideo`、`getFrames`、`createProject` を使えます。録画バーと同じく、テイクには Web カメラやシステム自身のカーソルも録画でき、エクスポートでは書き出しダイアログのオプションを使えます。MP4 なら画質とフレームレート、GIF ならフレームレート、サイズ、ループです。**上のサーバーを使う場合**、録画は OpenScreen 自身が、録画ボタンを押したときと同じように行います。エディターが閉じ、録画バーがカウントダウンして録画し、録画は新しいプロジェクトとしてエディターで開きます。そこで各編集が反映されるのを確認できます。**MCP による編集**をオンにする必要があり、録画が終わると録画バーの設定はあなた自身のものに戻ります。diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/current/cli.md b/website/i18n/ja/docusaurus-plugin-content-docs/current/cli.mdindex 01f8f1525..160ac5808 100644--- a/website/i18n/ja/docusaurus-plugin-content-docs/current/cli.md+++ b/website/i18n/ja/docusaurus-plugin-content-docs/current/cli.md@@ -64,12 +64,14 @@ openscreen record --display 1 --cursor system| `--mic` | 既定のマイクから録音します || `--mic-device <name>` | ラベルに `<name>` を含むマイクから録音します(大文字と小文字は区別しません)。`--mic` も指定したことになります || `--system-audio` | システム音声を録音します |+| `--camera` | 既定のウェブカメラを画面と一緒に録画します |+| `--camera-device <name>` | 名前に `<name>` を含むカメラを録画します(大文字と小文字は区別しません)。`--camera` を含意します || `--cursor <editable-overlay\|system>` | `editable-overlay`(既定)はシステムのポインターを隠してデータとして記録し、エディターでスタイルを変えられるようにします。`system` はポインターを映像に描き込みます || `--duration <seconds>` | 指定した時間が経過したら自動的に停止します || `--project <out.openscreen>` | 終了時に、録画を参照するプロジェクトファイルを書き出します。`export` やエディターですぐに使えます。末尾は `.openscreen` でなければなりません || `--json` | stdout に NDJSON のイベントを出力します |-ウェブカメラのオプションはありません。CLI の録画に含まれるのは、画面と音声だけです。+`--camera` を付けると、ウェブカメラも画面と一緒に録画され、`--project` のファイルから参照されます。**停止方法。** `--duration` を指定しない場合は、Ctrl+C(SIGINT)、SIGTERM、または stdin に `stop`、`q`、`quit` のいずれかを入力して Enter を押すと、録画が停止します。stdin を閉じても停止しません。強制終了すると通常の終了処理が省かれるため、`done` イベントもプロジェクトファイルも書き出されません。@@ -81,7 +83,7 @@ openscreen record --display 1 --cursor system### `openscreen sources` {#openscreen-sources}-アプリから見えるディスプレイ、ウィンドウ、マイクを一覧表示し、スクリプトが `--display`、`--window`、`--mic-device` の値を選べるようにします。Linux では、`record` で何をキャプチャするかは、それでもポータルのピッカーが決めます。+アプリから見えるディスプレイ、ウィンドウ、マイク、カメラを一覧表示し、スクリプトが `--display`、`--window`、`--mic-device`、`--camera-device` の値を選べるようにします。Linux では、`record` で何をキャプチャするかは、それでもポータルのピッカーが決めます。```bashopenscreen sources # human-readable@@ -99,12 +101,14 @@ openscreen sources -o sources.json # payload written to a file"displays": [{ "index": 0, "id": "screen:1:0", "name": "Entire screen" }],"windows": [{ "id": "window:210:0", "name": "My App" }],"microphones": [{ "label": "Built-in Microphone" }],- "microphoneLabelsUnavailable": false+ "microphoneLabelsUnavailable": false,+ "cameras": [{ "label": "FaceTime HD Camera" }],+ "cameraLabelsUnavailable": false}}```-`microphoneLabelsUnavailable` は、デバイス名の取得にまだ許可されていない権限が必要な場合や、数秒以内にデバイスの一覧を読み取れなかった場合に `true` になります。+`microphoneLabelsUnavailable` は、デバイス名の取得にまだ許可されていない権限が必要な場合や、数秒以内にデバイスの一覧を読み取れなかった場合に `true` になります。`cameraLabelsUnavailable` はカメラについて同じことを示します。**`-o` がある理由。** CLI が stdout に書き込むのは自身の出力だけで、Chromium の診断情報は stderr に送られます。問題は、プロセスを包むラッパーのほうです。画面のないマシンで GUI のバイナリを動かす一般的な方法である Ubuntu の `xvfb-run` は、stderr を stdout にまとめます。そのため、Chromium の起動時の警告が JSON の前に入り込み、`openscreen sources --json | jq` が失敗します。`-o <file>` なら、どのラッパーにもリダイレクトされない場所に書き込めるうえ、シェルのクォートやエンコーディングの違いも避けられます。@@ -132,16 +136,18 @@ openscreen export demo.openscreen -o out.mp4 --auto-zoom --json|---|---|| `-o, --out <path>` | 出力ファイル。拡張子(`.mp4` または `.gif`)で形式が決まります。既定値は、プロジェクトのパスの拡張子を `.mp4` または `.gif` にしたものです || `--format <mp4\|gif>` | プロジェクトに保存された形式を上書きします。`--out` と一致している必要があります |-| `--quality <medium\|good\|source>` | 出力サイズ。`medium` は 720p、`good` は 1080p、`source` はクロップ後のもっとも小さいクリップに合わせるため、アップスケールしません。GIF もこのサイズが出発点になります |+| `--quality <medium\|good\|source>` | 出力サイズ。`medium` は 720p、`good` は 1080p、`source` はクロップ後のもっとも小さいクリップに合わせるため、アップスケールしません。MP4 のみ。GIF はアプリと同じく元のサイズが出発点になります |+| `--fps <24\|30\|60>` | MP4 のフレームレート(既定は 60) || `--gif-fps <15\|20\|25\|30>` | GIF のフレームレート |-| `--gif-size <medium\|large\|original>` | 上記のサイズに適用する GIF の高さの上限。720、1080、上限なしのいずれかです |+| `--gif-size <small\|medium\|large\|original>` | 元のサイズに適用する GIF の高さの上限。480、720、1080、上限なしのいずれかです |+| `--gif-loop`, `--no-gif-loop` | GIF を無限にループするか、1 回だけ再生します。既定はプロジェクトの設定です || `--auto-zoom` | レンダリングの前に、記録されたクリックの箇所にズームを追加します。エディターの[自動ズーム](/features/auto-zoom/)と同じエンジンを使います。既存のズームは保持され、新しいズームはそれらを避けて配置されます || `--audio <file>` | ナレーションのファイル(mp3、wav、m4a)を MP4 にミックスします。MP4 のみ || `--audio-mode <mix\|replace>` | `mix`(既定)は録画の音声を 40% のゲインでナレーションの下に残し、`replace` は録画の音声を取り除きます || `--audio-offset <seconds>` | ナレーションが始まるまでの遅延(既定値 0) || `--json` | stdout に NDJSON で進行状況と結果を出力します |-CLI からの MP4 エクスポートは、常に **H.264・60 fps** です。コーデックやフレームレートのオプションはありません。デスクトップアプリの[エクスポート](./export.md)ダイアログでは、24 または 30 fps も選べます。+CLI からの MP4 エクスポートは常に **H.264** で、`--fps` を指定しない限り 60 fps です。コーデックのオプションはありません。`--audio` はレンダリングのあとに処理されます。映像ストリームは手を加えずにコピーされ、新しい AAC トラックがミックスされて、同じ出力ファイルに上書きされます。@@ -288,8 +294,7 @@ openscreen export demo.openscreen -o demo.mp4 --auto-zoom --audio voice.m4a --au- **ディスプレイやデスクトップセッションのないサーバーで録画したい。** 録画には実際のデスクトップが必要で、Linux では実行のたびに誰かがポータルのピッカーに応答しなければなりません。- **安定した、バージョン管理された API が必要。** CLI とプロジェクト形式は、リリース間で変わる可能性があります。-- **コマンドラインからコーデック、フレームレート、ビットレートを制御したい。** CLI の MP4 エクスポートは H.264・60 fps で、MP4 のビットレートはアプリでも調整できません。-- **スクリプトによる録画でウェブカメラを使いたい。** `record` にはカメラのオプションがありません。+- **コマンドラインからコーデックやビットレートを制御したい。** CLI の MP4 エクスポートは H.264 で、MP4 のビットレートはアプリでも調整できません。- **字幕ファイルが必要。** 字幕は動画に焼き込まれるだけです。エディターで同じ手順を実際に行う方法は、[プロダクトデモ動画の作り方](./guides/product-demo-video.md)を参照してください。ライセンスとネットワーク利用については、[よくある質問](./faq.md)で回答しています。diff --git a/website/i18n/pt-BR/docusaurus-plugin-content-docs/current/ai-editing.md b/website/i18n/pt-BR/docusaurus-plugin-content-docs/current/ai-editing.mdindex fb2c30356..41591063a 100644--- a/website/i18n/pt-BR/docusaurus-plugin-content-docs/current/ai-editing.md+++ b/website/i18n/pt-BR/docusaurus-plugin-content-docs/current/ai-editing.md@@ -76,7 +76,7 @@ Os pontos de restauração ficam na memória do OpenScreen: eles se perdem quand## Como deixar um agente fazer o vídeo inteiro {#letting-an-agent-make-the-whole-video}-Um agente pode fazer um vídeo inteiro sozinho, da gravação à exportação. Além das ferramentas de edição, as duas formas de adicionar o OpenScreen ao agente lhe dão `listSources`, `startRecording`, `stopRecording`, `setPointerTrack`, `exportVideo`, `getFrames` e `createProject`.+Um agente pode fazer um vídeo inteiro sozinho, da gravação à exportação. Além das ferramentas de edição, as duas formas de adicionar o OpenScreen ao agente lhe dão `listSources`, `startRecording`, `stopRecording`, `setPointerTrack`, `exportVideo`, `getFrames` e `createProject`. Uma gravação também pode incluir sua webcam e o cursor do próprio sistema, como a barra de gravação, e uma exportação aceita as opções da caixa de exportação: qualidade e taxa de quadros para um MP4; taxa de quadros, tamanho e repetição para um GIF.**Pelo servidor acima**, a gravação é feita pelo próprio OpenScreen, como com o botão Gravar: o editor fecha, a barra de gravação faz a contagem regressiva e grava, e a gravação abre no editor como um novo projeto, onde você vê cada edição chegar. É preciso ativar **Edições via MCP**, e a barra de gravação volta às suas próprias configurações quando a gravação termina.diff --git a/website/i18n/pt-BR/docusaurus-plugin-content-docs/current/cli.md b/website/i18n/pt-BR/docusaurus-plugin-content-docs/current/cli.mdindex f740bcec4..be5d02ef7 100644--- a/website/i18n/pt-BR/docusaurus-plugin-content-docs/current/cli.md+++ b/website/i18n/pt-BR/docusaurus-plugin-content-docs/current/cli.md@@ -64,12 +64,14 @@ openscreen record --display 1 --cursor system| `--mic` | Captura o microfone padrão || `--mic-device <name>` | Captura o microfone cujo nome contém `<name>`, sem diferenciar maiúsculas de minúsculas. Implica `--mic` || `--system-audio` | Captura o áudio do sistema |+| `--camera` | Grava a webcam padrão junto com a tela |+| `--camera-device <name>` | Grava a câmera cujo nome contém `<name>`, sem diferenciar maiúsculas de minúsculas. Implica `--camera` || `--cursor <editable-overlay\|system>` | `editable-overlay` (padrão) oculta o ponteiro do sistema e o grava como dados, para que o editor possa mudar o estilo dele. `system` desenha o ponteiro no vídeo || `--duration <seconds>` | Para automaticamente depois desse tempo || `--project <out.openscreen>` | Ao terminar, grava um arquivo de projeto que referencia a gravação, pronto para `export` ou para o editor. Precisa terminar em `.openscreen` || `--json` | Eventos NDJSON no stdout |-Não há opção de webcam: uma gravação pela CLI contém só a tela e o áudio.+Com `--camera`, a webcam é gravada junto com a tela, e o arquivo de `--project` a referencia.**Como parar.** Sem `--duration`, pare uma gravação com Ctrl+C (SIGINT), com SIGTERM ou digitando `stop`, `q` ou `quit` e Enter no stdin dela. Fechar o stdin não para a gravação. Um encerramento forçado pula a finalização normal, então não há evento `done` nem arquivo de projeto.@@ -81,7 +83,7 @@ Não há opção de webcam: uma gravação pela CLI contém só a tela e o áudi### `openscreen sources` {#openscreen-sources}-Lista as telas, as janelas e os microfones que o app enxerga, para que um script possa escolher valores de `--display`, `--window` e `--mic-device`. No Linux, o seletor do portal continua decidindo o que `record` captura.+Lista as telas, as janelas, os microfones e as câmeras que o app enxerga, para que um script possa escolher valores de `--display`, `--window`, `--mic-device` e `--camera-device`. No Linux, o seletor do portal continua decidindo o que `record` captura.```bashopenscreen sources # human-readable@@ -99,12 +101,14 @@ Com `--json`, o payload chega dentro do evento final `done`:"displays": [{ "index": 0, "id": "screen:1:0", "name": "Entire screen" }],"windows": [{ "id": "window:210:0", "name": "My App" }],"microphones": [{ "label": "Built-in Microphone" }],- "microphoneLabelsUnavailable": false+ "microphoneLabelsUnavailable": false,+ "cameras": [{ "label": "FaceTime HD Camera" }],+ "cameraLabelsUnavailable": false}}```-`microphoneLabelsUnavailable` é `true` quando os nomes dos dispositivos dependem de uma permissão que não foi concedida, ou quando a lista de dispositivos não pôde ser lida em poucos segundos.+`microphoneLabelsUnavailable` é `true` quando os nomes dos dispositivos dependem de uma permissão que não foi concedida, ou quando a lista de dispositivos não pôde ser lida em poucos segundos. `cameraLabelsUnavailable` diz o mesmo das câmeras.**Por que `-o` existe.** A CLI escreve no stdout apenas a própria saída; os diagnósticos do Chromium vão para o stderr. Já o wrapper em volta do processo é outra história. O `xvfb-run` do Ubuntu, a forma usual de rodar um binário gráfico em uma máquina sem tela, junta o stderr ao stdout, então os avisos de inicialização do Chromium chegam antes do JSON e `openscreen sources --json | jq` falha. `-o <file>` escreve em um lugar que nenhum wrapper consegue redirecionar, e evita diferenças de aspas e de codificação entre shells.@@ -132,16 +136,18 @@ openscreen export demo.openscreen -o out.mp4 --auto-zoom --json|---|---|| `-o, --out <path>` | Arquivo de saída. A extensão, `.mp4` ou `.gif`, define o formato. Padrão: o caminho do projeto com `.mp4` ou `.gif` || `--format <mp4\|gif>` | Substitui o formato salvo no projeto. Precisa ser coerente com `--out` |-| `--quality <medium\|good\|source>` | Tamanho de saída: `medium` é 720p, `good` é 1080p, `source` segue o menor clipe depois do corte da imagem, então nunca amplia. Um GIF também parte desse tamanho |+| `--quality <medium\|good\|source>` | Tamanho de saída: `medium` é 720p, `good` é 1080p, `source` segue o menor clipe depois do corte da imagem, então nunca amplia. Só MP4: um GIF parte do tamanho de origem, como no app |+| `--fps <24\|30\|60>` | Taxa de quadros do MP4 (padrão 60) || `--gif-fps <15\|20\|25\|30>` | Taxa de quadros do GIF |-| `--gif-size <medium\|large\|original>` | Limite de altura do GIF aplicado a esse tamanho: 720, 1080 ou nenhum |+| `--gif-size <small\|medium\|large\|original>` | Limite de altura do GIF aplicado ao tamanho de origem: 480, 720, 1080 ou nenhum |+| `--gif-loop`, `--no-gif-loop` | O GIF repete sem parar ou toca uma vez. Padrão: o do projeto || `--auto-zoom` | Antes de renderizar, adiciona zooms nos cliques gravados, com o mesmo mecanismo dos [zooms automáticos do editor](/features/auto-zoom/). Os zooms existentes são mantidos, e os novos ficam afastados deles || `--audio <file>` | Mixa um arquivo de narração (mp3, wav ou m4a) no MP4. Só MP4 || `--audio-mode <mix\|replace>` | `mix` (padrão) mantém o áudio da gravação por baixo da narração, com ganho de 40%; `replace` o descarta || `--audio-offset <seconds>` | Atraso antes de a narração começar (padrão 0) || `--json` | Progresso e resultado em NDJSON no stdout |-As exportações MP4 pela CLI são sempre **H.264 a 60 fps**. Não há opção de codec nem de taxa de quadros. A caixa de diálogo de [exportação](./export.md) do app para desktop também oferece 24 ou 30 fps.+As exportações MP4 pela CLI são sempre **H.264**, a 60 fps, a menos que `--fps` diga outra coisa. Não há opção de codec.`--audio` atua depois da renderização: o fluxo de vídeo é copiado sem alteração, e uma nova faixa AAC é mixada e gravada sobre o mesmo arquivo de saída.@@ -288,8 +294,7 @@ Salve-o na mesma pasta do clipe. Sem telemetria do cursor, `--auto-zoom` não te- **Você precisa gravar em um servidor** sem tela nem sessão de desktop. A gravação precisa de um desktop real, e no Linux alguém precisa responder ao seletor do portal a cada execução.- **Você precisa de uma API estável e versionada.** A CLI e o formato de projeto ainda podem mudar entre versões.-- **Você precisa controlar codec, taxa de quadros ou bitrate pela linha de comando.** As exportações MP4 pela CLI são H.264 a 60 fps, e o bitrate do MP4 também não é ajustável no app.-- **Você precisa da webcam em uma gravação por script.** `record` não tem opção de câmera.+- **Você precisa controlar codec ou bitrate pela linha de comando.** As exportações MP4 pela CLI são H.264, e o bitrate do MP4 também não é ajustável no app.- **Você precisa de arquivos de legenda.** As legendas são apenas embutidas no vídeo.Para ver os mesmos passos na prática, no editor, consulte [Como fazer um vídeo de demonstração de produto](./guides/product-demo-video.md). As respostas sobre licença e uso da rede estão nas [Perguntas frequentes](./faq.md).diff --git a/website/i18n/zh-CN/docusaurus-plugin-content-docs/current/ai-editing.md b/website/i18n/zh-CN/docusaurus-plugin-content-docs/current/ai-editing.mdindex e6a0b22b0..785c6d617 100644--- a/website/i18n/zh-CN/docusaurus-plugin-content-docs/current/ai-editing.md+++ b/website/i18n/zh-CN/docusaurus-plugin-content-docs/current/ai-editing.md@@ -76,7 +76,7 @@ ChatGPT 和 GitHub Copilot 登录选项已**在 1.8.0 中移除**。它们的工## 让 AI 代理制作整段视频 {#letting-an-agent-make-the-whole-video}-AI 代理可以从录制到导出独立完成一整段视频。无论以哪种方式添加 OpenScreen,除编辑工具外,AI 代理都能使用 `listSources`、`startRecording`、`stopRecording`、`setPointerTrack`、`exportVideo`、`getFrames` 和 `createProject`。+AI 代理可以从录制到导出独立完成一整段视频。无论以哪种方式添加 OpenScreen,除编辑工具外,AI 代理都能使用 `listSources`、`startRecording`、`stopRecording`、`setPointerTrack`、`exportVideo`、`getFrames` 和 `createProject`。与录制栏一样,录制时也可以录下你的摄像头和系统自带的光标;导出则接受导出对话框的选项:MP4 的画质和帧率,GIF 的帧率、尺寸和循环。**通过上面的服务器**,录制由 OpenScreen 自己完成,就像按下它的录制按钮一样:编辑器关闭,录制栏倒计时后开始录制,录好的内容作为新项目在编辑器中打开,你可以看到每项编辑实时生效。这需要开启**MCP 编辑**,录制结束后,录制栏会恢复你自己的设置。diff --git a/website/i18n/zh-CN/docusaurus-plugin-content-docs/current/cli.md b/website/i18n/zh-CN/docusaurus-plugin-content-docs/current/cli.mdindex 4196c75ad..e25a6be45 100644--- a/website/i18n/zh-CN/docusaurus-plugin-content-docs/current/cli.md+++ b/website/i18n/zh-CN/docusaurus-plugin-content-docs/current/cli.md@@ -64,12 +64,14 @@ openscreen record --display 1 --cursor system| `--mic` | 采集默认麦克风 || `--mic-device <name>` | 采集名称包含 `<name>` 的麦克风,不区分大小写。隐含 `--mic` || `--system-audio` | 采集系统音频 |+| `--camera` | 在录制屏幕的同时录制默认摄像头 |+| `--camera-device <name>` | 录制名称包含 `<name>` 的摄像头,不区分大小写。隐含 `--camera` || `--cursor <editable-overlay\|system>` | `editable-overlay`(默认)会隐藏系统指针并将其记录为数据,以便编辑器重新设置样式。`system` 会把指针绘制到视频中 || `--duration <seconds>` | 经过这段时间后自动停止 || `--project <out.openscreen>` | 完成后写出一个引用该录制的项目文件,可直接用于 `export` 或编辑器。必须以 `.openscreen` 结尾 || `--json` | 在 stdout 上输出 NDJSON 事件 |-没有摄像头选项:CLI 录制只包含屏幕和音频。+使用 `--camera` 时,摄像头会与屏幕一同录制,`--project` 文件会引用它。**停止录制**。未指定 `--duration` 时,可以按 Ctrl+C(SIGINT)、发送 SIGTERM,或在其 stdin 中输入 `stop`、`q` 或 `quit` 并按回车来停止录制。关闭 stdin 不会停止录制。强制终止进程会跳过正常的收尾流程,因此既不会写出 `done` 事件,也不会写出项目文件。@@ -81,7 +83,7 @@ openscreen record --display 1 --cursor system### `openscreen sources` {#openscreen-sources}-列出应用能看到的显示器、窗口和麦克风,方便脚本选择 `--display`、`--window` 和 `--mic-device` 的值。在 Linux 上,`record` 采集什么仍由门户选择器决定。+列出应用能看到的显示器、窗口、麦克风和摄像头,方便脚本选择 `--display`、`--window`、`--mic-device` 和 `--camera-device` 的值。在 Linux 上,`record` 采集什么仍由门户选择器决定。```bashopenscreen sources # human-readable@@ -99,12 +101,14 @@ openscreen sources -o sources.json # payload written to a file"displays": [{ "index": 0, "id": "screen:1:0", "name": "Entire screen" }],"windows": [{ "id": "window:210:0", "name": "My App" }],"microphones": [{ "label": "Built-in Microphone" }],- "microphoneLabelsUnavailable": false+ "microphoneLabelsUnavailable": false,+ "cameras": [{ "label": "FaceTime HD Camera" }],+ "cameraLabelsUnavailable": false}}```-当读取设备名称需要尚未授予的权限,或者无法在几秒内读取到设备列表时,`microphoneLabelsUnavailable` 为 `true`。+当读取设备名称需要尚未授予的权限,或者无法在几秒内读取到设备列表时,`microphoneLabelsUnavailable` 为 `true`。`cameraLabelsUnavailable` 对摄像头的含义相同。**为什么要有 `-o`**。CLI 只把自己的输出写到 stdout;Chromium 的诊断信息会写到 stderr。但包装该进程的程序就是另一回事了。Ubuntu 的 `xvfb-run` 是在没有屏幕的机器上运行图形界面程序的常用方式,它会把 stderr 合并到 stdout 中,于是 Chromium 的启动警告会出现在 JSON 之前,导致 `openscreen sources --json | jq` 失败。`-o <file>` 会写入任何包装程序都无法重定向的位置,同时还能避开 shell 引号和编码方面的差异。@@ -132,16 +136,18 @@ openscreen export demo.openscreen -o out.mp4 --auto-zoom --json|---|---|| `-o, --out <path>` | 输出文件。扩展名(`.mp4` 或 `.gif`)决定格式。默认:项目路径,扩展名换成 `.mp4` 或 `.gif` || `--format <mp4\|gif>` | 覆盖项目中保存的格式。必须与 `--out` 一致 |-| `--quality <medium\|good\|source>` | 输出尺寸:`medium` 为 720p,`good` 为 1080p,`source` 以裁剪后最小的片段为准,因此绝不会放大。GIF 也以这个尺寸为起点 |+| `--quality <medium\|good\|source>` | 输出尺寸:`medium` 为 720p,`good` 为 1080p,`source` 以裁剪后最小的片段为准,因此绝不会放大。仅限 MP4:GIF 与应用中一样以源尺寸为起点 |+| `--fps <24\|30\|60>` | MP4 帧率(默认 60) || `--gif-fps <15\|20\|25\|30>` | GIF 帧率 |-| `--gif-size <medium\|large\|original>` | 在上述尺寸基础上施加的 GIF 高度上限:720、1080 或不限 |+| `--gif-size <small\|medium\|large\|original>` | 在源尺寸基础上施加的 GIF 高度上限:480、720、1080 或不限 |+| `--gif-loop`, `--no-gif-loop` | GIF 无限循环,或只播放一次。默认:沿用项目设置 || `--auto-zoom` | 渲染之前,在录制的点击处添加缩放,使用与编辑器[自动缩放](/features/auto-zoom/)相同的引擎。已有的缩放会保留,新的缩放会与它们保持间隔 || `--audio <file>` | 把一个配音文件(mp3、wav 或 m4a)混入 MP4。仅限 MP4 || `--audio-mode <mix\|replace>` | `mix`(默认)会以 40% 增益把录制原声保留在配音之下;`replace` 则去掉原声 || `--audio-offset <seconds>` | 配音开始前的延迟(默认为 0) || `--json` | 在 stdout 上输出 NDJSON 格式的进度和结果 |-CLI 导出的 MP4 始终是 **60 fps 的 H.264**。没有编码格式或帧率选项。桌面应用的[导出](./export.md)对话框另外还提供 24 或 30 fps。+CLI 导出的 MP4 始终是 **H.264**,除非用 `--fps` 另行指定,帧率为 60 fps。没有编码格式选项。`--audio` 在渲染完成后才起作用:视频流会原样复制,然后混合出一条新的 AAC 音轨,并覆盖写入同一个输出文件。@@ -288,8 +294,7 @@ openscreen export demo.openscreen -o demo.mp4 --auto-zoom --audio voice.m4a --au- **你需要在服务器上录制**,而服务器没有显示器或桌面会话。录制需要真实的桌面环境,而且在 Linux 上,每次运行都得有人回应门户选择器。- **你需要稳定且带版本号的 API**。CLI 和项目格式在不同版本之间仍可能变化。-- **你需要在命令行中控制编码格式、帧率或码率**。CLI 导出的 MP4 固定为 60 fps 的 H.264,而 MP4 的码率在应用中也无法调整。-- **你需要在脚本录制中包含摄像头**。`record` 没有摄像头选项。+- **你需要在命令行中控制编码格式或码率**。CLI 导出的 MP4 固定为 H.264,而 MP4 的码率在应用中也无法调整。- **你需要字幕文件**。字幕只会烧录进视频。想在编辑器中亲手完成同样的步骤,请参阅[如何制作产品演示视频](./guides/product-demo-video.md)。关于许可证和网络使用的解答,请参阅[常见问题](./faq.md)。diff --git a/website/i18n/zh-TW/docusaurus-plugin-content-docs/current/ai-editing.md b/website/i18n/zh-TW/docusaurus-plugin-content-docs/current/ai-editing.mdindex 2b63380da..b6518c020 100644--- a/website/i18n/zh-TW/docusaurus-plugin-content-docs/current/ai-editing.md+++ b/website/i18n/zh-TW/docusaurus-plugin-content-docs/current/ai-editing.md@@ -76,7 +76,7 @@ ChatGPT 與 GitHub Copilot 的登入選項已**在 1.8.0 中移除**。它們的## 讓代理製作整支影片 {#letting-an-agent-make-the-whole-video}-代理可以從錄影到匯出自行製作一整支影片。無論以哪種方式加入 OpenScreen,除了剪輯工具之外,代理都能使用 `listSources`、`startRecording`、`stopRecording`、`setPointerTrack`、`exportVideo`、`getFrames` 與 `createProject`。+代理可以從錄影到匯出自行製作一整支影片。無論以哪種方式加入 OpenScreen,除了剪輯工具之外,代理都能使用 `listSources`、`startRecording`、`stopRecording`、`setPointerTrack`、`exportVideo`、`getFrames` 與 `createProject`。與錄影列一樣,錄影時也能錄下你的網路攝影機與系統本身的游標;匯出則接受匯出對話框的選項:MP4 的畫質與影格速率,GIF 的影格速率、尺寸與循環播放。**透過上述伺服器**,錄影由 OpenScreen 自己完成,就像按下它的錄影按鈕一樣:編輯器會關閉,錄影列倒數後開始錄影,錄好的內容會以新專案在編輯器中開啟,你可以看到每項編輯即時生效。這需要開啟**MCP 編輯**,錄影結束後,錄影列會恢復你自己的設定。diff --git a/website/i18n/zh-TW/docusaurus-plugin-content-docs/current/cli.md b/website/i18n/zh-TW/docusaurus-plugin-content-docs/current/cli.mdindex 008326c14..bd610a18a 100644--- a/website/i18n/zh-TW/docusaurus-plugin-content-docs/current/cli.md+++ b/website/i18n/zh-TW/docusaurus-plugin-content-docs/current/cli.md@@ -64,12 +64,14 @@ openscreen record --display 1 --cursor system| `--mic` | 錄製預設麥克風 || `--mic-device <name>` | 錄製名稱包含 `<name>` 的麥克風,不分大小寫。隱含 `--mic` || `--system-audio` | 錄製系統音訊 |+| `--camera` | 在錄製螢幕的同時錄製預設網路攝影機 |+| `--camera-device <name>` | 錄製名稱包含 `<name>` 的攝影機,不區分大小寫。隱含 `--camera` || `--cursor <editable-overlay\|system>` | `editable-overlay`(預設)會隱藏系統指標,並將它記錄為資料,讓編輯器可以重新設定樣式。`system` 會將指標直接繪入影片 || `--duration <seconds>` | 經過這段時間後自動停止 || `--project <out.openscreen>` | 完成後寫出一個參照這段錄影的專案檔,可直接用於 `export` 或編輯器。副檔名必須是 `.openscreen` || `--json` | 在 stdout 上輸出 NDJSON 事件 |-沒有網路攝影機選項:CLI 錄影只包含螢幕畫面與音訊。+使用 `--camera` 時,網路攝影機會與螢幕一同錄製,`--project` 檔案會參照它。**停止錄影。** 沒有指定 `--duration` 時,可以用 Ctrl+C(SIGINT)、SIGTERM,或在 stdin 輸入 `stop`、`q` 或 `quit` 再按 Enter 來停止錄影。關閉 stdin 並不會停止錄影。強制終止會跳過正常的收尾流程,因此不會寫出 `done` 事件,也不會寫出專案檔。@@ -81,7 +83,7 @@ openscreen record --display 1 --cursor system### `openscreen sources` {#openscreen-sources}-列出應用程式能看到的顯示器、視窗與麥克風,讓腳本可以選擇 `--display`、`--window` 與 `--mic-device` 的值。在 Linux 上,`record` 錄製的內容仍由 portal 選擇器決定。+列出應用程式能看到的顯示器、視窗、麥克風與攝影機,讓腳本可以選擇 `--display`、`--window`、`--mic-device` 與 `--camera-device` 的值。在 Linux 上,`record` 錄製的內容仍由 portal 選擇器決定。```bashopenscreen sources # human-readable@@ -99,12 +101,14 @@ openscreen sources -o sources.json # payload written to a file"displays": [{ "index": 0, "id": "screen:1:0", "name": "Entire screen" }],"windows": [{ "id": "window:210:0", "name": "My App" }],"microphones": [{ "label": "Built-in Microphone" }],- "microphoneLabelsUnavailable": false+ "microphoneLabelsUnavailable": false,+ "cameras": [{ "label": "FaceTime HD Camera" }],+ "cameraLabelsUnavailable": false}}```-當裝置名稱需要尚未授予的權限,或是無法在幾秒內讀取裝置清單時,`microphoneLabelsUnavailable` 會是 `true`。+當裝置名稱需要尚未授予的權限,或是無法在幾秒內讀取裝置清單時,`microphoneLabelsUnavailable` 會是 `true`。`cameraLabelsUnavailable` 對攝影機的意義相同。**為什麼要有 `-o`?** CLI 只會把自己的輸出寫到 stdout;Chromium 的診斷訊息則會寫到 stderr。但包在程序外面的包裝程式就另當別論了。Ubuntu 的 `xvfb-run` 是在沒有螢幕的機器上執行圖形介面程式的常見方式,它會把 stderr 合併到 stdout,於是 Chromium 的啟動警告會出現在 JSON 之前,導致 `openscreen sources --json | jq` 失敗。`-o <file>` 會寫到任何包裝程式都無法重新導向的位置,也能避開 shell 引號與編碼上的差異。@@ -132,16 +136,18 @@ openscreen export demo.openscreen -o out.mp4 --auto-zoom --json|---|---|| `-o, --out <path>` | 輸出檔案。副檔名(`.mp4` 或 `.gif`)決定格式。預設:專案的路徑,副檔名改為 `.mp4` 或 `.gif` || `--format <mp4\|gif>` | 覆寫專案中儲存的格式。必須與 `--out` 一致 |-| `--quality <medium\|good\|source>` | 輸出尺寸:`medium` 為 720p,`good` 為 1080p,`source` 依裁切後最小的片段而定,所以絕不會放大。GIF 也以這個尺寸為起點 |+| `--quality <medium\|good\|source>` | 輸出尺寸:`medium` 為 720p,`good` 為 1080p,`source` 依裁切後最小的片段而定,所以絕不會放大。僅限 MP4:GIF 與應用程式中一樣以來源尺寸為起點 |+| `--fps <24\|30\|60>` | MP4 影格率(預設 60) || `--gif-fps <15\|20\|25\|30>` | GIF 影格率 |-| `--gif-size <medium\|large\|original>` | 套用在上述尺寸上的 GIF 高度上限:720、1080,或不設上限 |+| `--gif-size <small\|medium\|large\|original>` | 套用在來源尺寸上的 GIF 高度上限:480、720、1080,或不設上限 |+| `--gif-loop`, `--no-gif-loop` | GIF 無限循環播放,或只播放一次。預設:沿用專案設定 || `--auto-zoom` | 算繪之前,在錄下的點擊處加入縮放,使用的引擎與編輯器的[自動縮放](/features/auto-zoom/)相同。既有的縮放會保留,新的縮放會與它們保持距離 || `--audio <file>` | 將旁白檔(mp3、wav 或 m4a)混入 MP4。僅限 MP4 || `--audio-mode <mix\|replace>` | `mix`(預設)會保留錄影的音訊,以 40% 增益墊在旁白底下;`replace` 則捨棄錄影的音訊 || `--audio-offset <seconds>` | 旁白開始前的延遲(預設為 0) || `--json` | 在 stdout 上輸出 NDJSON 格式的進度與結果 |-CLI 匯出的 MP4 一律是 **H.264、60 fps**。沒有編碼格式或影格率選項。桌面應用程式的[匯出](./export.md)對話框另外提供 24 或 30 fps。+CLI 匯出的 MP4 一律是 **H.264**,除非以 `--fps` 另行指定,影格率為 60 fps。沒有編碼格式選項。`--audio` 會在算繪之後才作用:視訊串流會原封不動地複製,再混入一條新的 AAC 音軌,並寫回同一個輸出檔案。@@ -288,8 +294,7 @@ openscreen export demo.openscreen -o demo.mp4 --auto-zoom --audio voice.m4a --au- **你需要在伺服器上錄影**,而且沒有顯示環境或桌面工作階段。錄影需要真正的桌面,而在 Linux 上,每次執行都必須有人回應 portal 選擇器。- **你需要穩定且有版本管理的 API。** CLI 與專案格式在不同版本之間仍可能改變。-- **你需要從命令列控制編碼格式、影格率或位元率。** CLI 匯出的 MP4 是 H.264、60 fps,而且 MP4 的位元率在應用程式中也無法調整。-- **你需要在腳本化的錄影中加入網路攝影機。** `record` 沒有攝影機選項。+- **你需要從命令列控制編碼格式或位元率。** CLI 匯出的 MP4 是 H.264,而且 MP4 的位元率在應用程式中也無法調整。- **你需要字幕檔。** 字幕只會燒錄進影片。若要在編輯器中實際走一遍相同的步驟,請參閱[如何製作產品示範影片](./guides/product-demo-video.md)。關於授權與網路使用的問題,請參閱[常見問題](./faq.md)。