← Back to Product Feed

GitHub Open Source storytold/filmcraft

FilmCraft: An open-source, nonlinear video editor written by scratch in pure Rust

11,581
Traction Score
4,659
Forks
Sep 30, 2026
Launch Date
View Origin Link

Product Positioning & Context

FilmCraft: An open-source, nonlinear video editor written by scratch in pure Rust
adobe art rust video video-editing video-editor video-processing

Related Ecosystem & Alternatives

Discover adjacent products, open-source repositories, and developer tools sharing similar technical architecture.

Deep-Dive FAQs

What is storytold/filmcraft?
storytold/filmcraft is a digital product or tool described as: FilmCraft: An open-source, nonlinear video editor written by scratch in pure Rust
Where did storytold/filmcraft originate?
Data for storytold/filmcraft was aggregated directly from the GitHub Open Source community ecosystem, representing raw developer and early-adopter sentiment.
When was storytold/filmcraft publicly launched?
The initial public indexing or launch date for storytold/filmcraft within our tracked developer communities was recorded on September 30, 2026.
How popular is storytold/filmcraft?
storytold/filmcraft has achieved measurable traction, logging over 11,581 traction score and facilitating 4,659 recorded discussions or engagements.
Which technical categories define storytold/filmcraft?
Based on metadata extraction, storytold/filmcraft is categorized under topics such as: adobe, art, rust, video.
Are there active development issues for storytold/filmcraft?
Yes, we are currently tracking open architectural debates and bug reports for this project on GitHub. There are currently 3 active high-priority issues logged recently.
What are some commercial alternatives to storytold/filmcraft?
Our semantic intelligence engine identifies potential commercial alternatives in the SaaS space, such as Retold, which offers overlapping value propositions.
How does the creator describe storytold/filmcraft?
The original author or development team describes the product as follows: "FilmCraft: An open-source, nonlinear video editor written by scratch in pure Rust"

Active Developer Issues (GitHub)

open security(control): control port executes JSON smuggled in an HTTP request body (web pages can drive the app while --control is open)
Logged: Oct 7, 2026
open Hardware acceleration: GPU/media-engine decode, GPU effects and GPU export
Logged: Oct 5, 2026
open alsa audio error
Logged: Oct 4, 2026

Community Voice & Feedback

CodexHere • Oct 6, 2026
Running into the same issue, tried tweaking a bunch in app and on my system to no avail...

System:
Kernel: 7.2.9-1-cachyos arch: x86_64 bits: 64
Desktop: KDE Plasma v: 6.7.5 Distro: CachyOS
Audio:
Device-1: Intel 300/C240 Series Family HD Audio driver: snd_hda_intel
Device-2: NVIDIA GP106 High Definition Audio driver: snd_hda_intel
API: ALSA v: k7.2.9-1-cachyos status: kernel-api
Server-1: PipeWire v: 1.6.9 status: active
EddyT1717 • Oct 6, 2026
## Also getting audio issues.

- Manjaro
- Pipewire

## Error
- ALSA lib pcm_dmix.c:1000:(snd_pcm_dmix_open) [error.pcm] unable to open slave
echelon • Oct 6, 2026
**Correction to my earlier update on #33.** VideoToolbox hardware decoding was **not** active in the desktop app until #41 (merged today, 5c8471c).

The desktop app called `filmcraft_platform::register()` only as an argument to `log::info!`. No logger is installed, so the `log` crate never evaluated it and the hardware decoder was never registered. The CLI/MCP and the benchmark harness call `register()` directly. That's why the parity tests and the benchmark numbers in #33 were real, and also why we didn't notice that desktop users, v0.2.0 and v0.2.1 included, still decoded in software.

#41 (by @justjohn12345) registers it unconditionally at startup and adds a test that it happens without a logger. The next release is the first where desktop users get hardware decoding by default. I missed this in review; thanks to the contributor for catching it.
echelon • Oct 5, 2026
**31 common effects now run on the GPU** (#35, merged).

On the GPU:
- **colour:** Brightness & Contrast, ProcAmp, Tint, Black & White, Color Balance, Levels, Gamma, Channel Mix, ASC CDL, Leave/Change/Pass/Replace Color, Invert, Posterize, Extract, Alpha Adjust;
- **geometry:** Crop, Flip, Transform, Mirror, Offset, Edge Feather;
- **blur:** Gaussian, Camera, Directional;
- **sharpen:** Sharpen, Unsharp Mask.

A clip moves to the GPU when all of its effects are on this list; otherwise it renders on the CPU as before. GPU output matches the CPU reference to within 7e-5 relative on 78 cases, including extreme parameters. On a three-layer test with effects, frame-worker time drops from 220–307 ms to 1.8–93 ms per frame.

**Done so far:** blend modes (#32), macOS hardware decode (#33), common effects (#35).

**Next:**
- VA-API (Linux) and Media Foundation (Windows) decode;
- zero-copy upload of decoded frames;
- Lumetri, keys and masks on the GPU;
- moving effect passes off the UI thread;
...
echelon • Oct 5, 2026
**Hardware decoding on macOS is in** (#33, merged).

H.264 and HEVC (8/10-bit, 4:2:0 and 4:2:2) now decode on VideoToolbox's hardware decoder. It's on by default, and Settings ▸ Playback ▸ Hardware decoding switches it off. Output is bit-exact with our software decoders on every test stream. If the hardware fails mid-stream, decoding continues transparently in software.

Apple M4 Pro, load average 150–190, Off → Auto:

| | CPU ms per frame | fps |
|---|---|---|
| H.264 2160p decode | 119 → 4.2 | 35 → 107 |
| HEVC 2160p decode | 86 → 3.7 | 49 → 217 |
| 4K H.264 playback at Full resolution (frames shown/dropped) | ~120 → ~9 | 104/88 → 192/0 |

This also adds `crates/platform`, the one crate allowed `unsafe` for OS media APIs. Linux (VA-API) and Windows (Media Foundation) backends will plug into it.

**Next:**
- effects on the GPU (in progress);
- VA-API for Linux and AMD, which needs a Linux machine to test;
- Media Foundation for Windows;
- passing decoded frames straight to the GPU wit...
echelon • Oct 5, 2026
Progress: **blend modes now run on the GPU** (#32, merged).

All 27 blend modes composite in WGSL, Dissolve included. A clip with a blend mode no longer forces the whole frame through the CPU renderer. The GPU output matches the CPU reference: every mode is within one half-float step on the edge-case tests, and 99% of interior pixels are within one 8-bit level on full sequences.

On a 1080p three-layer stack with Screen and Overlay, playing at Full resolution:

| | shown/dropped frames | CPU ms per frame |
|---|---|---|
| before | 19/173 and 138/54 | 168–214 |
| after | 191/1 and 192/0 | 86–87 |

That's the same cost as the plain Normal stack.

**Coming next:**
- **#33** adds hardware decoding on macOS through VideoToolbox, plus the `crates/platform` FFI crate that the Linux (VA-API) and Windows (Media Foundation) backends will use. It's in final CI. 4K H.264 decode drops from 119 to 4 CPU-ms per frame.
- The most common effects (colour adjustments, crop, flip, transform, Gaussian blur...

Discovery Source

GitHub Open Source GitHub Open Source

Aggregated via automated community intelligence tracking.

Tech Stack Dependencies

No direct open-source NPM package mentions detected in the product documentation.

Media Tractions & Mentions

No mainstream media stories specifically mentioning this product name have been intercepted yet.

Deep Research & Science

No direct peer-reviewed scientific literature matched with this product's architecture.