How does it compare to https://omniclip.app/ , https://tooscut.app , or https://clipjs.mohy.dev/ ?
Tbh I don't know, will check them out.
I did not know they existed, thank you for sharing them!
Show HN: VidStudio, a browser based video editor that doesn't upload your files
41–50 of 120 posts
Re: Show HN: VidStudio, a browser based video editor that doesn't upload your files
#42Wild that apps used to be completely local, no accounts, no uploads, and we're back to that as a value prop.
Except the part of them actually being native to the OS they are running on.
Re: Show HN: VidStudio, a browser based video editor that doesn't upload your files
#43Earlier quoted context omitted.
Closed source is fine, but there are a few other things that are required of LGPL, some of which are - Provide links to the source of the version of ffmpeg you used in your code - User should be able to replace the ffmpeg libs with his own compatible builds if you're using dynamically linked libs. For statically linked libs, you need to provide the tools to re-link against a compatible build. I went through an LGPL r…
I knew about the soft copyleft (the source code requirements) but didn't know there was the requirement to have libs be replaceable. Now I want to know how useful that would be in reverse engineering closed systems (particularly nintendos, since I've always had an interest in the homebrew scene there)
iirc, the video player application VLC used to come without any mpeg support, and you had to go through a process to download ffmpeg separately ...not sure how easy it made it to replace individual libs, but I'm also not sure the license requires you to make it easy.
Re: Show HN: VidStudio, a browser based video editor that doesn't upload your files
#44Earlier quoted context omitted.
> Any reason not to just open source it? Mmmm...potential commercialisation? Always find it curious that people expect to get source code for free in ways that they don't do for other work (ask George Martin to release his drafts and notes).
The parent commenter is making that comment because this is precisely the nature of why the GPL license exists. Most of the processing of this application is FFMPEG, so why should someone who has done zero development on that library commercialize it?
Most of the processing of the application is FFMPEG yes, but there's a whole lot of application outside of the processing. Video editors UIs that don't make you want to tear your hair out are a valuable commodity and I think OP has the right to commercialize that if they want to. They just need to use FFMPEG in the right way as they do it.
Re: Show HN: VidStudio, a browser based video editor that doesn't upload your files
#45Earlier quoted context omitted.
Thank you for pointing this out, to be completely honest, I did not consider licensing because the website started as a collection of tools I built to run locally and get into video/audio codecs then I realised it is already a decent collection of tools that other people might want to use too. But I will be making the needed changes to comply fully tonight. At least I comply with this: `Do not misspell FFmpeg (two ca…
You should look into how other companies and tools that use FFMPEG handle this situation. I wonder if you can keep your application itself closed source, but make an open-source adapter that handles the interaction with FFMPEG. I'm not super familiar with open source licensing, and IANAL, so make sure to do your own research :) As an example, I believe Audacity required me to install ffmpeg manually myself, and add i…
Thank you, I guess I won't be fixing any bugs tonight but at least I will figure out how to comply.
I appreciate the help for real!
Re: Show HN: VidStudio, a browser based video editor that doesn't upload your files
#46Wild that privacy became a feature and not the default. Building in this space too and the no uploads needed angle is surprisingly hard to communicate to users who've been trained to expect everything to live in the cloud.
Re: Show HN: VidStudio, a browser based video editor that doesn't upload your files
#47Earlier quoted context omitted.
Thank you for pointing this out, to be completely honest, I did not consider licensing because the website started as a collection of tools I built to run locally and get into video/audio codecs then I realised it is already a decent collection of tools that other people might want to use too. But I will be making the needed changes to comply fully tonight. At least I comply with this: `Do not misspell FFmpeg (two ca…
You should look into how other companies and tools that use FFMPEG handle this situation. I wonder if you can keep your application itself closed source, but make an open-source adapter that handles the interaction with FFMPEG. I'm not super familiar with open source licensing, and IANAL, so make sure to do your own research :) As an example, I believe Audacity required me to install ffmpeg manually myself, and add i…
Yes, Audacity definitely requires that. It can't open or save mp3s unless you separately install ffmpeg.
Re: Show HN: VidStudio, a browser based video editor that doesn't upload your files
#48Wild that apps used to be completely local, no accounts, no uploads, and we're back to that as a value prop.
Except the part of them actually being native to the OS they are running on.
A recommendation I make where I can: OpenShot. FOSS, cross-platform, no accounts and very capable and easy to use.
Re: Show HN: VidStudio, a browser based video editor that doesn't upload your files
#49Earlier quoted context omitted.
Closed source is fine, but there are a few other things that are required of LGPL, some of which are - Provide links to the source of the version of ffmpeg you used in your code - User should be able to replace the ffmpeg libs with his own compatible builds if you're using dynamically linked libs. For statically linked libs, you need to provide the tools to re-link against a compatible build. I went through an LGPL r…
Dynamically and statically linked libs is hilarious in the context of webassembly running in the browser.
You can have multiple WASM modules communicating with each other (though you would probably need extra interop code?), or statically link them into a single module, the concepts work mostly the same
Re: Show HN: VidStudio, a browser based video editor that doesn't upload your files
#50Wild that privacy became a feature and not the default. Building in this space too and the no uploads needed angle is surprisingly hard to communicate to users who've been trained to expect everything to live in the cloud.
Yes and yet perfectly logical when the most successful business models are about selling private data.