# Styles, animations and sounds

The libraries solve different needs. You can combine them in the same edit.

| Library | What it is for | What choosing something does not mean |
| --- | --- | --- |
| Editing styles | Study the structure, pace and resources of a complete edit | Copy its topic, brand or all of its footage |
| Animations | Solve one scene: a fact, a comparison, a title, a process or a CTA | Use that animation in every video |
| Sounds | Accent an action and follow the pace | Turn the volume up or fill everything with effects |

## Choose from the web

Open the library, filter and watch the preview. You can copy an animation's prompt or select several to combine them. Add instructions such as "use this for the comparison in the second point." The agent retrieves the selections and adapts the code to the project.

Likes save a member's candidates for that brand; they are not an order to use them. Preferences, exclusions and the fit with the scene still win. The agent compares the relevant favorites with other candidates; a like does not prove a fit or an automatic ranking improvement. It does not force a favorite sound when SFX are off.

## Download a style's code

When you choose a style that has code available, start from its package instead of rebuilding the demo. Use the ID, version and SHA-256 the selection returns:

```sh
editorbrain styles source STYLE_ID --style-version VERSION --out .editorbrain-local/style.tar.gz
editorbrain styles prepare STYLE_ID --style-version VERSION --file .editorbrain-local/style.tar.gz --out .editorbrain-local/adapted-style
```

In MCP, use `get_style_source` with `id`, `version` and `sha256`. Access depends on your plan; the preview does not grant a download. The temporary link is not saved as a permanent reference.

The CLI checks the catalog hash on download; `styles prepare` creates a separate adapted copy and keeps the original file. Read its README and `PROJECT-BINDING.md`, replace the demo media with the client's authorized footage, and apply their brand and preferences. Downloading does not install dependencies, run code or render. Some preprocessors require macOS; check the package's requirements and alternatives.

## Search animations from the CLI

```sh
editorbrain motion scenes "compare two options" --material motion --limit 6
editorbrain motion scenes --material fotos --limit 6
editorbrain motion scenes --material video --limit 6
```

The function (`--funcion`), framing (`--encuadre`) and 3D (`--tresD`) filters use the catalog's facets, not invented labels. Use the IDs the response returns. Framing matches scenes in "Over your video."

**Over your video** needs a prepared clip of a person talking to camera. The scene does not automatically crop or generate that person.

To open a result, use its exact `id` and `version`:

```sh
editorbrain motion scene ID --scene-version VERSION
editorbrain motion preview ID --scene-version VERSION --ratio tall
editorbrain motion source ID --scene-version VERSION --out .editorbrain-local/scene.tar.gz
```

`wide`, `square` and `tall` are 16:9, 1:1 and 9:16. The catalog that groups scenes and the version of an inherited scene can differ: keep the value from the result. Downloading code does not run it or render it.

## Go to the next page

Use `nextCursor` as `--after`, keeping the query, filters, limit and version. Do not decode it or change it. If you change filters, start over without a cursor. That avoids the incompatible-cursor error.

## Do not mix up the catalogs

`motion scenes` searches complete scenes. `motion list/get/prepare` works with reusable components. `media styles/style` holds image or motion recipes. Their IDs and versions belong to different catalogs.

## Search editing techniques

```sh
editorbrain library search "demonstration" --limit 10
editorbrain library get VIDEO_ID
```

For a full edit, the agent first inspects your footage and prepares a brief for `search brief`. The results are candidates; it should read the evidence before claiming that a technique fits.

## Use SFX according to your preferences

```sh
editorbrain sfx search --project my-project --query "soft impact" --scene-role body
```

The connected search applies the project's preferences. With SFX off it returns an empty selection; sparse, balanced and rich are editorial intentions, not quotas or volume. Keep `bankId` and `catalogSha256` to retrieve a sound:

```sh
editorbrain sfx get SOUND_ID --project my-project --bank BANK_ID --catalog-sha256 HASH
```

The agent should listen to it, align it with the action and review the mix. A description such as "soft" does not replace listening. If you have your own library, `sfx index` creates a local index; it does not publish it for other users.

## Your own styles

You can save an edit with its method and assets. You have capture from a project, asset transport, local adaptation tests and shared templates with a link; see [Save and reuse your styles](https://editorbrain.com/en/docs/estilos-propios) for syntax and availability.
