ZacharyZhang-NY
e74dafcd36
Three independently ugly bugs that all fed the same log flood:
* Electron's `WebFrameMain.send` writes every "Render frame was disposed"
to stderr via `console.error`. When the worker fans a second
agent-event past a reloading renderer, we produced thousands of
identical lines and stalled the main loop on stderr I/O. Added a
`mainFrame.detached` guard so the send is short-circuited before
Electron's own catch block fires, and installed a targeted filter in
`suppress-warnings.ts` (now actually imported from the entry point)
so the specific `console.error("Error sending from webFrameMain:"…)`
noise never reaches the terminal. Any other payload still surfaces.
* `dispatchAgentMessage` accepted the human-reader sentinel as a wake
target when an agent replied to `__board__` — `wakeAgentIfPossible`
then called `db.getAgent("__board__")`, threw, and the dispatcher
kept repeating on every send. Strip `HUMAN_SENDER_ID` at
`resolveMessageWakeTargets`, and keep a defense-in-depth guard in the
heartbeat so a stray caller (future automation fan-out) cannot
reintroduce the crash.
* Pi's skills loader rejects any SKILL.md whose frontmatter `name`
diverges from its parent directory. The four bundled `my-writing-style`
copies declared `name: writing-style-skill`, so every install emitted
a warning and dropped the skill. They also lived as orphan gitlinks
(mode 160000 without .gitmodules), and the global `*.md` gitignore
hid every other SKILL.md from version control. Fixed the frontmatter
to match the dir, converted the dangling submodules to plain trees,
and allowlisted `builtin-skills/**/*.md` so a fresh clone carries the
catalogue instead of silently losing it.
52 lines
1.2 KiB
Markdown
52 lines
1.2 KiB
Markdown
---
|
|
name: trimming
|
|
description: Trimming patterns for Remotion - cut the beginning or end of animations
|
|
metadata:
|
|
tags: sequence, trim, clip, cut, offset
|
|
---
|
|
|
|
Use `<Sequence>` with a negative `from` value to trim the start of an animation.
|
|
|
|
## Trim the Beginning
|
|
|
|
A negative `from` value shifts time backwards, making the animation start partway through:
|
|
|
|
```tsx
|
|
import { Sequence, useVideoConfig } from "remotion";
|
|
|
|
const fps = useVideoConfig();
|
|
|
|
<Sequence from={-0.5 * fps}>
|
|
<MyAnimation />
|
|
</Sequence>;
|
|
```
|
|
|
|
The animation appears 15 frames into its progress - the first 15 frames are trimmed off.
|
|
Inside `<MyAnimation>`, `useCurrentFrame()` starts at 15 instead of 0.
|
|
|
|
## Trim the End
|
|
|
|
Use `durationInFrames` to unmount content after a specified duration:
|
|
|
|
```tsx
|
|
<Sequence durationInFrames={1.5 * fps}>
|
|
<MyAnimation />
|
|
</Sequence>
|
|
```
|
|
|
|
The animation plays for 45 frames, then the component unmounts.
|
|
|
|
## Trim and Delay
|
|
|
|
Nest sequences to both trim the beginning and delay when it appears:
|
|
|
|
```tsx
|
|
<Sequence from={30}>
|
|
<Sequence from={-15}>
|
|
<MyAnimation />
|
|
</Sequence>
|
|
</Sequence>
|
|
```
|
|
|
|
The inner sequence trims 15 frames from the start, and the outer sequence delays the result by 30 frames.
|