Show HN: I created an After Effects alternative
1150 points| clementpiki | 1 year ago |pikimov.com
Inspired by Photopea (a free Photoshop clone), I created this web-based motion design & video editor as an alternative to After Effects, to fill empty void.
It's free, without signup, without cloud uploads (your files stay on your machine), and your projects are not used for AI models training.
[+] [-] doctorpangloss|1 year ago|reply
[+] [-] clementpiki|1 year ago|reply
[+] [-] KennyBlanken|1 year ago|reply
To me, it's "author / project lead has no background in the industry or even basic knowledge of video."
[+] [-] bluelightning2k|1 year ago|reply
[+] [-] earthtograndma|1 year ago|reply
[+] [-] mclightning|1 year ago|reply
[+] [-] suyash|1 year ago|reply
[+] [-] swyx|1 year ago|reply
[+] [-] enobrev|1 year ago|reply
Several years ago I built a prototype of a video renderer on nodejs (v0.8-ish). It's a silly thing to do, rendering video in javascript (especially a decade ago), but it worked well enough to prove that it could be done and a startup pivot was born - one that was eventually acquired by Vimeo.
While a colleague (and now friend) was working on porting my silly little renderer to C/C++ to try to get closer to real-time, I built out a UI to allow us to "templatize" dynamic video for our users. This made it possible for our designers to design the video experience for the videos that were dynamically generated for our users' content.
That UI very much resembled Flash. Since then I've always wanted to do what you've done here. Before acquisition, I was asking our designers to walk me through how they use After Effects, in the hopes of building our tools in that direction, but then Vimeo showed up and... not too long after I left to start a travel startup. I haven't revisited the video space since.
I love this. I _knew_ that it could be done - especially now that WASM is stable - and I'm excited to see someone has done it. And free, no less!
Edit: Thought it was open source - thanks for the correction. Also I was way off on the node version.
[+] [-] wavewash|1 year ago|reply
[+] [-] ramses0|1 year ago|reply
https://techcrunch.com/wp-content/uploads/2006/04/jumpcut.gi...
...sadly, acquired by Yahoo, and you know what happened next.
I can't find a lot of screenshots / video from the era, but the one above should give you a sense of it.
[+] [-] mrandish|1 year ago|reply
Based on the great response you've gotten so far, I'd suggest focusing on ways for the community to expand on what you've built with templates and plug-ins.
[+] [-] alfl23|1 year ago|reply
It will take significant resources, cash and teams to make this into a serious contender, and folks that have problems to solve will always be happy to pay decent dollars for great software.
[+] [-] majani|1 year ago|reply
[+] [-] qingcharles|1 year ago|reply
What's needed now is a page where people can share the templates they've created.
[+] [-] Andrew_nenakhov|1 year ago|reply
[+] [-] padenot|1 year ago|reply
So I spoofed the user-agent in a nightly build here on my Linux desktop workstation, then had to alias one method that we should have implemented years ago but only have with a `moz` prefix (`HTMLMediaElement.mozCaptureStream`). This is on us to fix.
Then it looks like a worker script is served with the `Content-Type` `text/html` instead of `application/javascript` or something like that. We also have a pref flip to bypass that check, so I did that, but this is on the dev to fix.
When you do this it works, I've loaded project demos containing videos, audio, various things composited on top, scrubbed the timeline aggressively in a debug build, moved things around in various bits of the interface and also in the rendering frame, etc., things seem to work as they should, perf is as I'd expect it to be (and again, I'm running it in a debug build with optimizations disabled for anything media related, enabled for other parts of the browser).
What's missing is `window.showSaveFilePicker` and file system related stuff. It's possible to use https://developer.mozilla.org/en-US/docs/Web/API/File_System... instead (that we ship, e.g. Photoshop on the Web uses it). We think that it's much less scary than giving access to the file system to a content process of a Web browser. Maybe because videos can sometimes be extremely big files, direct access to the FS could be of use there. Thankfully, we also ship extremely modern video encoders to make them tiny instead, but that's currently a limitation Firefox has, for better or worse.
https://paul.cx/public/pikimov-firefox-nightly.webm
[+] [-] ayhanfuat|1 year ago|reply
> Why no Firefox support Firefox is my daily web browser. As a web developper, I always make sure my work is comptatible with all major browsers. But you can guess a web based video editor is a complex task to achieve, and Pikimov uses several key features that only exist in Chrome, Edge, and maybe Opera, and maybe, maybe, Brave. That's why Pikimov cannot currently work on Firefox (as of today: v127), there's nothing I can do to fix this, it is just not possible. For the curious ones, here are some of the web API Pikimov requires, but are missing from Firefox: - audio data - window showsavefilepicker - videoencoder Note: There is no Safari support due to similar obstacles.
https://pikimov.com/faq/
[+] [-] uh_uh|1 year ago|reply
[+] [-] AshleysBrain|1 year ago|reply
[+] [-] jampekka|1 year ago|reply
I use Firefox for all my browsing, but do web app development with and for Chromium. I'd gladly do it for Firefox, but people, especially users, suck and sometimes one has to accept this.
Glad to see no time is wasted for Safari/iOS support. It's a huge waste of time and people using Apple devices are to blame.
[+] [-] Aldo_MX|1 year ago|reply
It is the right of developers to say "I don't want to support your browser" and you should respect that decision even if you disagree with it.
As a reality check, see this ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=390936
It took Firefox 17 years of back and forth with developers to add parity with an Internet Explorer feature that Chrome supported since version 1. This late in the game IE is already dead for good.
Not everybody has infinite time or infinite money to support Firefox, as an aside, you knew what you signed up for when you made Firefox your main browser.
So please, change the "clarify why you don't support Firefox" tone with "I want to make the site work with Firefox, how can I help you?". And good luck making the Firefox team change their mind when they decide not to support X feature, because it is also their right to do not implement the whole spectrum of features that Chrome supports.
[+] [-] sadops|1 year ago|reply
[+] [-] mrbluecoat|1 year ago|reply
[+] [-] tombert|1 year ago|reply
[+] [-] gaudystead|1 year ago|reply
[+] [-] codelord|1 year ago|reply
[+] [-] eamonobr|1 year ago|reply
[+] [-] ttoinou|1 year ago|reply
[+] [-] czhu12|1 year ago|reply
I diligently disable Adblock on that website and have donated a few times in the past to support them.
I hope to see many more alternatives on the market, and lend my support to anyone building!
[+] [-] n3storm|1 year ago|reply
[+] [-] Melatonic|1 year ago|reply
[+] [-] billconan|1 year ago|reply
[+] [-] anovc|1 year ago|reply
What are your plans for further development? I guess for this complex project to evolve in order to meet the needs of the professional users it will require lots of work/team/resources/etc.
Do you plan to monetize it somehow in the future? or how are you going to sustain it?
Another free alternative to AE (targeted at more casual users) that comes to mind is CapCut... which is obviously a ByteDance product. And they already offer tons of features for free, so the competition could be tough...
[+] [-] kypro|1 year ago|reply
[+] [-] alok-g|1 year ago|reply
Comparing a web-based software that runs on your own computer vs. installing a (say native) software and frequently updating, isn't it interesting that the former is faster to do? When using a web-based software to ru on your own machine, you are effectively, momentarily, installing it and are able to uninstall by clearing the cache.
[+] [-] whartung|1 year ago|reply
Targeting Chrome targets all of the platforms, and the machines and platform is "fast enough" to do the job without having to dig deep into specific nature of the platforms.
It also leverages, I'm assuming, the deep knowledge the developer has of doing other things for the browser platform.
They probably could have targeted some other portable GUI toolkit, but this was more familiar. It may well be an even smoother experience than using other cross platform GUI toolkits, plus, of course, the platform is free.
Finally, distribution is familiar and likely easier, it's truly cross platform (no need to build executable on the individual platforms, even if its all from the same source base), etc.
No bundling, no signing, no app stores. Just a URL shared in a tweet and you're on your way. If it was OSS, it could be parked on a Github page for all eternity.
Overall, it's a really attractive platform for developers, just not yet fully embraced I think, as client based applications I mean.
[+] [-] crazygringo|1 year ago|reply
You can load+interpret JavaScript files dynamically as the user accesses certain features.
[+] [-] conception|1 year ago|reply
[+] [-] deweywsu|1 year ago|reply
[+] [-] SillyUsername|1 year ago|reply
[+] [-] clementpiki|1 year ago|reply
[+] [-] jagged-chisel|1 year ago|reply
But also, I would like to use motion graphics in an app where the software engineers don't have to re-implement each asset in code.
[+] [-] dorkwood|1 year ago|reply
[+] [-] InsideOutSanta|1 year ago|reply
[+] [-] atum47|1 year ago|reply
Are you planning on creating a company out of this? Are you going to monetize it?
1 - https://m.youtube.com/playlist?list=PL3pnEx5_eGm9BbCp2ZTj6LT...