同様の実験をやった - L-Smash Works（r1281、libavモード）48.8fps - ffmpeg.aui2（a4c6620）：42.9fps - 動画IN（1.0.1、ハードウェアアクセラレーションは自動）：13.0fps うーん？

コードで動画作る仕組みはすでにたくさんあったのでまとめました〜Opus4.8で試したら飛べます🚀 あなたはどれを選びますか？ 【🎬 コードで動画を作る主要ツール50選】 Remotion（Reactベース）のような「コードで動画を作る」便利な仕組みを検索・調査しました。 動画制作って、編集ソフトを触るだけじゃなくて、コードで再現性を持って作る領域にかなり寄ってきているなと。 RemotionやHyperFramesを見ていると、これは単なる動画編集の話ではなく、エンジニアが動画制作を「運用できる仕組み」に変えていく流れだと感じます。 まずは選択肢の地図として整理してみたのでどうぞです☺️ ・これらは「コード（JS/TS/React/HTML/Pythonなど）で構成・アニメーション・合成・レンダリングしてMP4などを出力」するプログラマティック動画生成ツール群です。 ・AIエージェント連携（Hyperframesのように）やJSON/API呼び出し型も含め、2026年現在の主なものをカテゴリ別に50個以上まとめました。 　◻︎ 重複を避け、awesome-videoリストや代替ツール比較から抽出しています。 ・各カテゴリで代表的なものを挙げ、簡単な特徴・用途を付けています。 ・多くはFFmpegを基盤にしつつ、React/HTML/Pythonなどで高レベルに抽象化した「便利な仕組み」です。 ・商用/オープンソース混在なので、ライセンス確認を。 　◻︎ 最新情報は各GitHub/公式サイトで確認してください。 ✅ 1. JavaScript / TypeScript / Webベース 　・ブラウザ・Nodeでコードから直接動画生成するカテゴリです。 　・これらはRemotion/Hyperframesに最も近い「コード＝動画」の仕組みです。 　　◻︎ React/TS/HTML/CSSで記述してMP4出力できます。 　・Remotion 　　- Reactコンポーネントで動画作成（最も人気）。 　・Hyperframes（HeyGen） 　　- HTML/CSS/JSをMP4にレンダリング（AIエージェント特化、オープンソース）。 　・Revideo 　　- Remotionに近いオープンソースTSフレームワーク。 　・Rendervid 　　- Remotion無料代替、JSONテンプレート＋React＋AI統合。 　・Motion Canvas 　　- TS generator関数でアニメーション作成（リアルタイムプレビュー＋動画出力）。 　・FFmpeg.wasm / @ffmpeg /ffmpeg 　　- ブラウザでFFmpeg実行、クライアントサイド動画処理。 　・fluent-ffmpeg（Node.js） 　　- NodeでFFmpegを簡単にラップ。 　・jMuxer 　　- JS純正MP4 muxer（ストリーミング向け）。 　・Rendley SDK 　　- ブラウザ完全動作の動画編集SDK（WebCodecs＋Pixi.js）。 　・WebCodecs API（ブラウザネイティブ） 　　- 低レベルでフレーム操作・動画生成。 　・Helios 　　- オープンソースのプログラムマティック動画エンジン（Web寄り）。 ✅ 2. Pythonベース 　・スクリプトで最も手軽・自動化向きのカテゴリです。 　・動画編集・合成・生成の定番です。 　　◻︎ MoviePyを中心に、科学計算やAIと組み合わせやすいです。 　・12. MoviePy 　　- Pythonで動画編集・合成（最高の初心者向け）。 　・13. ffmpeg-python 　　- FFmpegの複雑フィルタをPythonで記述。 　・14. ffmpy 　　- PythonicなFFmpeg/FFprobeラッパー。 　・15. PyAV 　　- FFmpegライブラリのPythonicバインディング。 　・16. Vidgear 　　- 高性能クロスプラットフォーム動画処理フレームワーク。 　・17. OpenCV (cv2) 　　- VideoWriterなどでフレーム単位動画生成。 　・18. Imageio 　　- 画像/動画を簡単に読み書き・処理。 　・19. VapourSynth 　　- 高性能動画処理スクリプト（Pythonバインディング）。 　・20. fmov 　　- FFmpeg＋PILで高速プログラムマティック動画作成（新しめ）。 　・21. Manim 　　- 数学・説明アニメーションをコードで動画化（YouTube教育動画で有名）。 　・22. webm.py 　　- WebM動画エンコード特化。 　・23. python-video-converter 　　- FFmpegラッパーでフォーマット変換自動化。 　・24. atvk 　　- Audio/Videoツールキット。 　・25. SciPy Pillow 　　- 科学計算＋画像処理で動画生成パイプライン。 　・26. django-video-encoding 　　- Djangoアプリ内動画エンコード（Webアプリ向け）。 ✅ 3. その他のプログラミング言語ベース 　・Java / Go / Rust / C / モバイルなど、低レベル制御や特定プラットフォーム向けのカテゴリです。 　・27. JCodec（Java） 　　- 純JavaでH.264/MP4エンコード。 　・28. JavaCV（Java） 　　- OpenCV＋FFmpegのJavaラッパー。 　・29. Xuggler（Java） 　　- FFmpegベースのJava動画I/O。 　・30. gmf / goav / goffmpeg（Go） 　　- GoでFFmpegバインディング。 　・31. gst（Go） 　　- GStreamer Goバインディング。 　・32. rust-av（Rust） 　　- 純Rustマルチメディアツールキット。 　・33. libav（C/C ） 　　- FFmpeg派生のマルチメディアライブラリ群。 　・34. vpp (Video )（C ） 　　- 高性能動画・画像処理ライブラリ。 　・35. FFmpegKit（Android/iOS） 　　- モバイル向けFFmpegフルビルド。 　・36. LiTr（Android） 　　- 軽量動画/音声変換ライブラリ。 　・37. CameraX（Android） 　　- Jetpackカメラ・動画キャプチャ。 　・38. PBJVision（iOS） 　　- iOSメディアキャプチャ（動画録画特化）。 ✅ 4. ビデオ生成API / JSONベース 　・コードからHTTP/JSONでクラウドレンダリングするカテゴリです。 　・Remotionのように「コードで定義 → API呼び出し」で動画出力できます。 　　◻︎ サーバーレス自動化に最適です。 　・39. JSON2Video 　　- JSONでシーン・テキスト・音声を定義して動画生成。 　・40. Creatomate 　　- JSON/RenderScriptで動画・画像自動生成（Zapier連携強力）。 　・41. Shotstack 　　- JSONタイムラインで完全プログラムマティック編集。 　・42. Plainly 　　- After Effectsテンプレートをコード/JSONで自動化。 　・43. Bannerbear（動画対応） 　　- テンプレートベースJSON動画生成。 　・44. Editframe 　　- コードベース動画編集API（一部比較で登場）。 ✅ 5. 3D / アニメーション / 特殊ツール 　・スクリプトで動画出力するカテゴリです。 　　◻︎ クリエイティブコーディングや3Dレンダリング特化です。 　・45. Blender Python API 　　- Blender内でPythonスクリプトで3D動画レンダリング。 　・46. Unity (C# scripting Video Recorder) 　　- ゲームエンジン内でスクリプト動画出力。 　・47. Godot Engine (GDScript) 　　- 軽量エンジンでコードベースアニメ動画。 　・48. Processing (Java / Pythonモード) 　　- クリエイティブコーディングで動画エクスポート。 　・49. Lottie (Bodymovin) 動画変換ツール 　　- ベクターアニメをコードで作成 → MP4出力。 　・50. GStreamer (C bindings) 　　- パイプライン式高性能動画処理（Go/Python/Javaでも使用可）。 ✅ 合計 　・合計50個（＋α）。 　・これ以外にもFFmpeg CLI＋シェル/スクリプト、VapourSynth拡張、WebGL/Three.js＋canvas録画などの組み合わせで無限に拡張可能です。 ✅ 選び方の目安 　・Remotion/Hyperframesユーザー向けの選び方です。 　・React/TS好き 　　- Remotion / Revideo / Rendervid / Motion Canvas 　・HTML/CSSでサクッと 　　- Hyperframes（AIエージェント最強） 　・Python自動化 　　- MoviePy / ffmpeg-python / Manim 　・クラウドスケール 　　- JSON2Video / Creatomate / Shotstack 　・ブラウザ完全 　　- FFmpeg.wasm Rendley SDK ✅ 実際に使う際の確認ポイント 　・GitHubスター数・更新頻度・ドキュメントを確認してください。 　・無料枠やセルフレンダリング（Remotion Cloudなど）を検討してください。 　・もっと詳細（例: 特定ツールのサンプルコードや比較）が必要なら教えてください！ 　・検索元はGitHub awesome-videoリスト、公式ドキュメント、各代替比較記事（2025-2026年時点）に基づいています。

以前に作ろうとしていたけど、L-Smash WorksのL-Smash抜き（libav L-smashをオフ）で良くね？ってなって開発を辞めてしまった ちなみにL-Smash Worksの方が速いのでそっちを使っといて問題ないと思います

The Engineers Who Said No [I loved this interview that @lexfridman did with @jean_kempf48856 and @kierank_ . Tons of great nuggets for founders and operators. I'm enclosing an executive summary below] Jean-Baptiste Kempf (President of VideoLAN, creator of VLC) and Kieran Kunhya (FFmpeg developer), interviewed by Lex Fridman (Lex Fridman Podcast #496, May 6, 2026) Summary: Two of the people who built the open source video stack that runs Netflix, YouTube, Chrome, OBS, Discord, and basically every video you have ever watched sit down to explain why they refused tens of millions of dollars to keep VLC clean, why "we don't care if you're a dog" is the most important rule in their community, and why public shaming on X is the only escalation channel volunteers have against trillion-dollar companies. The result is the strongest case yet that the internet's most critical infrastructure rests on a few dozen people whose primary skill is saying no. 1. The 5-Person Bottom Layer. Five core developers maintain VLC. Ten to fifteen maintain FFmpeg, which ships inside YouTube, Netflix, Chrome, Discord, OBS, and most smart TVs. Kempf puts the retention math plainly: a thousand contributors land patches over a project's lifetime, and ten stay. People change jobs, have children, get into accidents, drift away, and the runtime of civilization's video pipeline rests on whoever does not drift. 2. Maybe You're a Dog. The community has one rule for accepting contributions: is your code good. Kempf repeats it twice in the episode, almost verbatim: "Maybe you're a dog. I don't care." The patch is the only signal that counts. Teenagers have written more lines of assembly in FFmpeg than Google engineers, and the project shipped at that quality because the maintainers refused to let any other criterion in. 3. Saying No to the Toolbar. Kempf has turned down "dozens of millions of dollars" to keep VLC free of ads, several times. The offers came from spyware toolbars, search-engine hijacks, and in-app ad SDKs. The math was real: take the deal, get rich, and within three years someone forks VLC clean and the user trust collapses. His principle is about being able to live with himself: "I need to go to bed at night and be happy about what I've done." 4. The Clean Buyer Never Showed Up. Kempf is clear he would have taken a Netflix integration deal. The clean buyers never knocked. Every offer he received came from companies whose business model required burying the consent in license text nobody reads. The default state of being a popular free product is getting approached only by predators, and the founder's job is to recognize that pattern before the offer feels flattering. 5. The Nebraska Problem Has Names. XZ is maintained by one person. LibXML, the only library that parses XML at scale, is now unmaintained. Time zones for the entire industry run off one engineer. FFmpeg and VLC are, in Kempf's words, "not the worst" open source projects in this picture, which says everything about the rest. 6. AI Slop as Denial of Service. Google ran AI security scanners across FFmpeg, generated wordy high-severity reports on a 1990s game codec, handed the volunteers a standard 90-day disclosure deadline, and announced its AI's prowess to the press before the bugs were fixed. Kunhya's framing: bug discovery now has industrial-scale funding; bug fixing has none. The volume of reports has become a denial-of-service attack against the maintainers, executed by the same companies who use FFmpeg at millions-of-cores scale and contribute almost nothing back. 7. The Padlock Is Not Fort Knox. Kunhya's keeper analogy: a lock on a house is calibrated to what it protects, not to stop a nation state. Marking every integer overflow in a 1993 game codec as "high priority, scary, scary" trains the world to ignore the actual alarms when they fire. Severity inflation destroys the signal that severity is supposed to carry, and the security industry is now financially incentivized to keep crying wolf. 8. Spicy Tweets Are HR. VLC could not get a human at the Google Play Store to fix a year-old Android distribution bug. The only escalation that worked was tweeting that VLC was about to leave the Play Store and let 100 million Android users notice. The same maneuver worked on Microsoft. Kempf has no ISV rep, no Microsoft point of contact, no SLA, no inbox somebody answers; public shaming is the entire enterprise relations function of every project the internet depends on. 9. The OSPO Gap. A Microsoft Teams manager once filed a "high priority" bug on a public FFmpeg tracker, name-dropping Microsoft as if that obligated the volunteers, and offered "a few thousand dollars" for long-term support. He did not know what an Open Source Program Office was supposed to do, and his employer did not bother to tell him. The disconnect between procurement and engineering inside large companies is the rule, and open source maintainers eat that gap directly. 10. Excellence Because You Cannot Babysit Strangers. Linus Torvalds gets cited as the canonical harsh maintainer, but Kempf reframes the tone. Code review is brutal because the five people in the room are the ones who will own the patch forever after the contributor disappears. "We need excellence because we are very few to maintain something that is critical for the whole." Strictness in review is a survival policy when staffing is one percent of contributors. 11. Forks Are the Pressure Valve. The 2011 FFmpeg/Libav split looked like a community-destroying schism, then ended with FFmpeg absorbing Libav's best work and Libav fading. GCC went through the same thing with EGCS and came out stronger. The right to fork is the mechanism that lets governance disputes resolve without anyone holding the project hostage, which is why the open source license matters more than any feature roadmap. 12. Maintainer Burnout. The XZ supply-chain attack worked because the maintainer was harassed nonstop by the attackers until he handed over commit access just to be left alone. Kempf has received death threats in the mail, with white powder, for deprecating PowerPC support in VLC. The XZ playbook now sits in the open, AI is multiplying the volume of toxic interactions, and most companies that depend on open source still have no line item for hardening the humans who hold up the stack.

THE PEACE DEAL: NOT FROM USA BUT QATAR & PAKISTAN The latest peace proposal offered to Iran is not coming from the United States. Qatar and Pakistan, working with other regional mediators, drafted this revised peace memorandum to bridge the gap between Washington and Tehran. This happens as Trump hesitates on ordering a major strike and clings to existing agreements. THE CORE REVELATION ➡️ The new contract was not issued by the USA but engineered by Qatar and Pakistan. ➡️ It aims to overcome differences while Trump delays any grand attack on Iran. ➡️ Netanyahu remains deeply skeptical and pushes to resume war to further degrade Iranian capabilities. THE PROVOCATION FACTOR ➡️ Iran’s Foreign Ministry spokesman stated the US must end piracy against Iranian ships and release frozen assets for talks to succeed, while Israel ends the Lebanon war. ➡️ Hours later Israel sank an Iranian ship exactly as described. ➡️ The US now moves to freeze Iranian fees from the Strait of Hormuz paid mainly in crypto. WHITE HOUSE MIXED SIGNALS ➡️ Khamenei’s son holds the reins on negotiations, a man who lost his wife, father, and nieces in prior attacks. ➡️ Yet the White House proudly posted: “Justice will be done” with an image showing Trump neutralizing enemies including “Ali Khamenei – assassinated.” ➡️ One side offers a deal, the other tweets execution graphics. THE ESCALATION CLOCK ➡️ Iranian Parliament Speaker Bagak Libav warned: “The war is now imminent. All covert and overt actions indicate the enemy intends to resume the war.” ➡️ Revolutionary Guard Corps stated any new attack would expand the war across the Middle East with devastating strikes at unimaginable locations. ➡️ Russian flight data shows cleared Iranian airspace and ghost ship patterns, exact precursors to prior US-Israeli strikes. THE BOTTOM LINE This so-called American peace plan was never American. Regional mediators crafted the last chance while Netanyahu holds the trigger and provocative signals fly from Washington. Iran now faces a make-or-break decision that could ignite wider war within hours. Control is slipping through everyone’s fingers. #IranPeaceDeal #NotFromUSA #QatarPakistan #NetanyahuWar #StraitOfHormuz #TrumpProvocation #MiddleEastEscalation

The discussion covers video codecs, compression basics, reverse engineering, FFmpeg's history including its Libav fork, Google drama, and the decision to turn down millions to keep VLC ad-free, underscoring volunteer-driven development.

Here's my conversation all about @FFmpeg, the legendary open-source software powering most video on the Internet. In the episode, I talk with Jean-Baptiste Kempf and Kieran Kunhya. JB is lead developer of VLC and Kieran is FFmpeg contributor, codec engineer, and the person behind the now-infamous @FFmpeg account on X. VLC (@videolan), by the way, is also a legendary piece of open-source software: it's a video player that can open basically anything & has been downloaded over 6 billion times. I think both FFmpeg and VLC are two of the most important and impactful software systems ever created, both open source, and both created & maintained by volunteers: brilliant engineers from all walks of life. Thank you to everyone who contributed to FFmpeg and VLC, and in general to all engineers giving their heart & soul to building systems used by millions (or billions) of people, and often doing so not for money, status, or fame, but purely for the love of building great software and doing good for the world. Thank you to the builders! 🙏❤️ Shoutouts in this chat to @ID_AA_Carmack @karpathy @elonmusk @TimSweeneyEpic and everyone who is a contributor & fan of open source! It's here on X in full and is up everywhere else (see comment). Timestamps: 0:00 - Episode highlight 2:17 - Introduction 5:35 - Weirdest things VLC opens 9:59 - How video playback works 19:20 - Video codecs and containers 30:07 - FFmpeg explained 51:07 - Linus Torvalds 55:46 - Turning down millions to keep VLC ad-free 1:10:04 - FFmpeg & Google drama 1:29:18 - FFmpeg developers 1:35:55 - VLC and FFmpeg 1:40:29 - History of FFmpeg 1:43:46 - Reverse engineering codecs 1:57:01 - FFmpeg testing 2:01:08 - Assembly code (handwritten) 2:25:26 - Rust programming language 2:34:42 - FFmpeg and Libav fork 2:43:04 - Open source burnout 2:50:51 - x264 and internet video 3:04:07 - Video compression basics 3:11:04 - CIA and fake VLC 3:21:39 - Ultra low latency streaming 3:39:07 - AV2 codec and video patents 3:48:59 - VLC backdoors 3:59:14 - Video archiving 4:05:51 - Future of FFmpeg and VLC

オープンソースのマルチメディアツール「FFmpeg」と「Libav」はなぜ分裂したのか？(2023)

【解決】AviUtl2のTips。 SONY製のカメラで撮影した映像素材がうまく読み込めない場合は、L-Smash Worksの「Libav L-SMASH」のチェックを外すだけで読み込めるようになる模様です。すみませんでした

Multiple unpatched CVEs in libav (unmaintained FFmpeg fork, last update 2019) openwall.com/lists/oss-secur… it continues to be used as a dependency in some projects. libav GitHub Issues are disabled and no security contact is available.

Day 4 of #BuildInPublic Made a simple audio format converter for SirenMix with libav wasm. Page under 900KB, zero server calls — conversion runs entirely in browser. Drag, convert, done. sirenmix.com/tools/audio-con… #rustlang #svelte #wasm

特に音声多重放送の切り替え、5.1 -> 2ch への切り替え、画質変更 (1080i -> 480i) 、字幕ストリームの追加削除などストリーム構成自体が番組の境目でコロコロ変わるので素でやらせるのは本当に厳しく、それを安定化させて libav が食いやすいストリームにするのが tsreadex の役目

ネイティブ番組表すごい・・・ 放送波にはデュアルモノみたいな通常ありえない超特殊なストリームがバンバン流れてくるため完璧な対応は難しく（ネイティブのデコーダーが libav ベースの場合は特に）、エンコーダーに通すときみたいに一旦 tsreadex を通した方が筋が良いと思われます

なんとコナステをLinuxで動かすパッケージがもう既にあった これ入れたら普通にブラウザから起動できたし音も出た github.com/mizztgc/konaste-l… で、タイトル画面の手前で落ちるのはgst-libav入れたら直った

rendered with webcodecs, libav, @konstipaulus 's diffusionstudio

Day 60 focus: ffmpeg libav, syncing pts breakdown: 3h I've been thinking. I want to master patience over anything else I've learned. Patience in the seconds. Patience in the days. Patience in the years. Patience over my lifetime. I don't recall when I lost her but the absence, once clouded by lost time, is glaring. How ironic to lose time/attention to the throes of impatience, while striving to claim it back. I've caught glimpses of what can be done, the path ahead is clear and walkable, and yet repeatedly I get in my own way. Need to somehow reconcile the gap between delusion and patience. Just studied a bit today on ffmpeg pipeline, trying to figure out how to make a demuxer, parse packets from streams and sync audio and video together. Working on a small standalone version before porting it. Wondering if I should just convert the bulk of my project from rgb to yuv space and skip conversions in the pipeline. I could just use a lut table at the end to print back to rgb for the ANSI true color. A refactor/cleanup would be welcome too

AV1 over MPEG2-TS、定義はされてるけどlibavにも入ってないらしい。 aomediacodec.github.io/av1-m…

j00ru.vexillium.org/2014/01/… (2014) when ffmpeg pulled ahead of libav. Volunteers fixed so many security vulnerabilities found by Google, where ffmpeg won out and regained confidence from community. 1 year later, larger projects started to use ffmpeg again. lwn.net/Articles/650816/

j00ru.vexillium.org/2014/01/… (Pic from 2014) when ffmpeg pulled ahead of libav. Volunteers (mostly @michael__ni) fixed so many security vulnerabilities found by Google, where ffmpeg won out and regained the confidence in the community

Libav Did Nothing Wrong