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.
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
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!
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.
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!
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.
So FFmpeg is part of the website in general but it is not used in the editor itself.
I did built on top of the Video Codec APIs and ofc a muxer library like mp4box.js
Agreed but I guess at the same time those who spend money to develop software need to find ways to monetise I just wish they were not so predatory.
Everything is a subscription now siphoning money out of users on a monthly basis.
Thank you for the encouragement.
Regarding the track manipulation I have not fully cracked it yet so you can't move clips between tracks yet and track reordering didn't cross my mind but will look into it.
Regarding transforms once you manage to get a clip in the track you should be able to click on it and then get on the right hand side of the program monitor you should see a transforms panel with a limited selection of options, at least what I could sort of understand how to program together with LLMs ofc ahahaha.
I never maintained an open source project and not sure how to even do it properly.
I am also not sure how much effort would I have to put to an open source project. I imagine I would need to collaborate with a pretty much anyone who has an interest in the area. Again not that I mind just not sure how much time I have to spare. Right now this is a really slow process and tbh I have to rely on manual testing at least for the editor.
Thank you for flagging this, indeed you are right. I do have a long list of problems to go through. The editor mostly relies on the browser Audio/Video codecs which I learned after trying FFmpeg out. They have wide support but also a bunch of limitations. Actively working on it, thank you for the feedback. It is the first time I take such a deep dive to all of these.