Mastershot – Web based video editor
mastershot.app
mastershot.app
The motivation behind creating Mastershot was because when searching for a simple free video editor to use, they always hit me with either a low-res export or heavily watermarked or an exorbitant subscription fee. Mastershot is able to be free because it uses an WASM port of Ffmpeg.
Currently I only support chrome because of a weird bug in FF that is causing the ffmpeg port to break. I’m working on an approach to make Mastershot work cross-browser the same way that the video trimmer and audio extractor tools work.
How does one comply with the GPL and LGPL with Wasm, other than a complete source dump?
You may want to check with a lawyer, and/or read the ffmpeg FAQ about that, and/or recompile with --disable-gpl --disable-nonfree - and that only brings you to the point where you need to let people use their own ffmpeg.wasm (and not be obligated to provide your source code).
https://www.ffmpeg.org/legal.html is actually required reading for anyone who uses ffmpeg in a product, commercial, free/libre or free/gratis.
I have an acquaintance who's a lawyer specializing in these issues, and he's usually called in to put out (legal) fires because people ignored open source licenses in commercial products. Copyright infringement laws are crazy complicated and in many ways incompatible with the modern ways of software, but they are what they are, and must be considered.
Since you are distributing ffmpeg (as a wasm module), you are under obligations to give access to source code that do not apply to services that merely use ffmpeg within their own organization (even if for a service provided to third parties).
One typical work around for distribution of ffmpeg in a product is to simply use a standalone ffmpeg executable and provide all the source to the ffmpeg executable.
A wasm module is more akin to a library than a standalone executable and likely under stronger obligations. If you are only using LGPL code (it depends on how you compiled ffmpeg [See https://www.ffmpeg.org/legal.html -- "Compile FFmpeg without "--enable-gpl" and without "--enable-nonfree" ), giving access to only the ffmpeg code you used to build the module (and any modifications) would likely suffice for the source code obligation. If you are including any GPL code (because you didn't compile with the options needed to ensure only LGPL code is used), your entire project likely falls under GPL and you would probably need to share the source for the entire project to be compliant.
If another service is using ffmpeg as a wasm without providing a means of accessing the source code (to the wasm module if only using LGPL code, or the entire project if using any GPL code), they (too) are likely in violation of the ffmpeg license copyright and could be sued. Companies and projects can fly under the radar for some time before this happens, but it doesn't mean they are operating legally and will never be sued.
There are claims both for and against this being a derivative work; for “standalone” use, the test is usually something like “if you didn’t use ffmpeg, would the product be significantly less useful?”
MySQL used to claim that including MySQL.exe in a product, even if you don’t link to it, makes that product a derivative work. The generally accepted wisdom is that it’s not.
I don’t know if this was ever tested in court.
It seems like one of these is not like the other.
The video trimmer and mp3 extractor don’t require accounts.
Compare this with Subtitle Horse [0], a fantastic web-based subtitles editor that loads user's video to the browser storage (I guess? it certainly predates the file system access api), and does not require an account.
Please support Firefox.
SAFs were disabled on all major browsers after the Spectre exploit iirc. Slowly but steadily they’ll patch and bring the feature back, and it’ll automatically be compatible with those browsers then.
Edit: Apparently Firefox does have SharedArrayBuffer support[0], but needs special headers.
https://hacks.mozilla.org/2019/09/caniuse-and-mdn-compat-dat...
Wanted to have a little play and see if I liked it.
Maybe this is because by registering you give away something, but you don't really know if it's worth it right at the beginning.
As someone who used to run my own video sharing site in the 2000s, it's super cool seeing how videos can just render so quickly in my browser and be moved around.
Did notice third time scroll that look that a heading for 'security' seemed to explain..
contact and about us so as to see jurisdiction / trust/.
I guess this could be ported as a web app / home screen icon thing?
I'd love to connect this with mediapress/buddypress/wp
and if I could find a way to push a list to a self hosted server app that would run a browser on the server to pull via youtubedl and spit out some mp3s to collect and listen later.
sounds great!
Under what conditions are video and audio uploaded to the site?
So I'm guessing that's how it'll remain free -- as long as you use your own storage space and computing power, you can see use it for free.
But also, depending on codecs, it might be GPL; e.g. x264 itself is GPLd as are some other codecs. There are BSD licensed codecs. As ffmpeg relies on many other projects to provide codecs, it’s on a codec by codec basis - though the original configure makes it easy to disable all GPL upstrrams.
Unrelated to this project, a similar open source tool kit is definitely missing in the general video content creation landscape...
a similar open source tool kit is definitely missing in the general video content creation landscape
I've found that the open source AviDemux (and Handbrake) meets most of my basic video editing needs. I also use FFMpeg to automate some tasks (like adding subtitles and metadata to many videos). OBS Studio is another open source software used by many YouTubers and streamers.