Recent submissions

Comment · 1 month ago
https://vidstudio.app/text-based-video-editor

Orator: A text based video editor that runs inside the browser without any back end. You can load a video which will get automatically transcribed. Then highlight to: delete, duplicate, replace video, replace background or export.

It is also possible to export the project to a NLE video editor https://vidstudio.app/video-editor for more advanced editing even using keyframes. The entire pipeline runs on inside a browser tab including the transcription.

The best thing about it imo is that you do not need an account you just start editing and everything will be persisted in your machine so you can come back to it later.

Comment · 6 months ago
Hey, I had to rework a few things to try and address this issue and that exposed another bigger problem so thank you very much for flagging this. I released a fix primarily for chrome but firefox seems to be a lot harder to solve but I will start working on a fix for that as well.
Comment · 6 months ago
Cool project will check it out. I have not checked Remotion but will certainly take a look.
Comment · 6 months ago
I have not checked out Remotion but will do thanks for pointing it out!
Comment · 6 months ago
Free!
Comment · 6 months ago
Wasm ffmpeg is much slower for sure and multithreading for wasm ffmpeg is buggy you need to control threads per pipeline step to get it working.
Comment · 6 months ago
It is on my to do list to add automatic subtitles. The 3 editors you mentioned are backed by cloud juggernauts that either asked already or will ask for a perpetual licence to any content you process with them because they can and they also offer cloud options. I do have to say that they are probably more mature and feature rich than VidStudio at this point in time ahhaha
Comment · 6 months ago
Hey this is on my todo list and will make it a point to get back to you here once it is fixed. The main issue is that codec support is patchy most muxer software that I found has gaps in codec support and I had no clue but the codec names for audio and video seem to be named differently based on platform and browser even for some cases. Will be looking again at this topic asap and will get back to you here!
Comment · 6 months ago
Wow this is really cool thanks a lot for sharing I was a bit demotivated from all the errors I have on sentry ahahha. I did give ffmpeg wasm my best shot, even trying worker fs to deal with the memory problems but yeah a lot of effort for marginal gains imo. Video codecs are really impressive but they are raw in the sense that I underestimated how much ffmpeg carries by giving you a decode, transform encode pipeline.
Comment · 6 months ago
Yeah you are right about the wasm issues with video apps. The editor itself relies fully on web codecs and the rest of the tools are halfway migrated from ffmpeg wasm anyways. I did not look into any other alternatives for ffmpeg thinking that wasm will give me the next best thing to the cli tool and ofc since the browser is the main delivery mechanism the I was limited in my options. I have seen your project and it is really cool!
Comment · 6 months ago
Good idea. Once I am through the licensing ordeal I have a giant stack of errors to tackle which should increase usability.
Comment · 6 months ago
Thanks for encouragement. You are right ffmpeg-wasm doesn't really cut it for long videos but I have pivoted to web/audio codecs now, and there I can work based on streams at least for video. So once I harden the tools a bit more memory limits should be large enough to do some good editing.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton