A video editing SDK that runs in the browser
Hello HN,Video content is more popular than ever, but the toolkit for creating such content is a bit behind. You usually have to rely on a server for rendering whenever you want to create a video editing project in the browser. This means uploading content to a server, coding complex filters and effects, and more.My friend and I spent a year developing an SDK that handles all these complexities and offers an easy-to-use interface for developers. The SDK works entirely in the browser, manages memory efficiently so it can run even on a 7-year-old Android device, supports GLSL effects and transitions, handles captions, and much more.We also created a custom video editor UI interface using the SDK to showcase its speed and flexibility. You can see the video editor embedded on our landing page: https://rendley.com.As for the tech stack, the SDK was built using TypeScript, Pixi.js, C++, FFmpeg WASM, and WebCodecs. The UI interface was created using Stencil.js and MobX.The SDK is called Rendley SDK and it is live on npm: https://www.npmjs.com/package/@rendley/sdkTo get started, follow this guide: https://docs.rendley.com/installationIf you want to embed the pre-made interface, follow this guide, it’s literally a few lines of code: https://docs.rendley.com/video-editorIf you have any questions about the product or any feedback, feel free to write them below, and I’ll be more than happy to answer them.
Users raised concerns about the product's open source claims, patent issues with mp4, and lack of visible pricing information. Comparisons with similar services like Revideo and Remotion were made, questioning differences in API, rendering, and licensing. Technical issues with ffmpeg wasm, codec support, and file loading were noted. The 'Get in touch' button leading to a 404 page and forced sign-up were criticized. Some users appreciated the service but were deterred by the sales approach and misleading information on the website. There were also requests for transparent pricing and questions about the use of Pixi.js.
Users criticized the product for not being truly open source, misleading claims, and lack of public repositories. Concerns over memory safety, codec errors, and patent issues were noted. The requirement for a license key, forced sign-up, and issues with file compatibility were disliked. Criticisms also focused on the lack of transparent pricing, with many mentioning hidden costs behind email requirements and no fixed pricing. The product's value proposition for non-technical users and small target market were questioned, along with the effectiveness of Show HN/Product Hunt for growth.