Show HN: A Video Editing SDK That Runs in the Browser
Rendley SDK provides an in-browser video editing solution with client-side processing, supporting various formats. It is customizable, lightweight, and scalable, with multiple pricing plans and extensive APIs for unique features.
Read original article
Rendley SDK offers an in-browser video editing solution that allows users to modify videos directly on their platforms without server reliance, as all processing occurs client-side. It supports a wide range of video codecs and containers, including MP4, MKV, MOV, and AVI, as well as various audio formats like MP3 and AAC, and image formats such as JPEG and PNG. Users can render a one-minute video in under 15 seconds, and embedding the SDK into a website takes less than five minutes. The SDK integrates smoothly with platforms like React, Angular, and PHP, and is fully customizable, allowing for adjustments in colors and individual elements. It is lightweight, responsive across devices, and open source, enabling users to create custom video editors and automation tools. The SDK features extensive APIs for adding unique filters and effects, and it ensures security through on-device storage. Scalability is a key feature, accommodating growth with device-based operations. The SDK is compatible with all browsers, ensuring accessibility. Pricing options include a free tier for exploration, a standard plan for enhanced capabilities, and an enterprise option for organizations needing comprehensive support and control. Each plan offers various features, including unlimited clips and projects, dedicated support, and advanced analytics. Overall, Rendley SDK aims to enhance website experiences by providing powerful video editing tools.
Related
We increased our rendering speeds by 70x using the WebCodecs API
Revideo, a TypeScript framework, boosted rendering speeds by 70 times with WebCodecs API. Challenges overcome by browser-based video encoding. Limited audio processing and browser compatibility remain.
Ask HN: Share your FFmpeg settings for video hosting
A user is developing a video hosting site allowing MP4 uploads, utilizing H.264 for video and Opus for audio. They seek advice on encoding settings and challenges faced in the process.
19 commentsNote that a lot of the ffmpeg code is not memory safe and some of the file/codec plugins contain memory errors. An out-of-bounds read or write will bring down the entire wasm subsystem (and does). You have to manually figure out which codecs are actually safe to use in the browser, vs which ones are merely exposed by the ffmpeg wasm builds.
It seems pretty unconventional to offer an sdk where people have to enter a license key, but I understand that it's hard to monetize differently when one of your key features is that you want to enable client-side rendering (not saying that this is bad - I relate to the challenge since we are offering a cloud rendering service and at some point when webcodecs is supported in all browsers, it might make sense to run revideo purely on a client device as well).
(though as I am working on a similar product I am aware that handling all the codecs is quite a bit more painful than it first seems)
Now I’ve also logged in to see if I get pricing. Still no pricing. Seriously guys. This is just silly.
Related
We increased our rendering speeds by 70x using the WebCodecs API
Revideo, a TypeScript framework, boosted rendering speeds by 70 times with WebCodecs API. Challenges overcome by browser-based video encoding. Limited audio processing and browser compatibility remain.
Ask HN: Share your FFmpeg settings for video hosting
A user is developing a video hosting site allowing MP4 uploads, utilizing H.264 for video and Opus for audio. They seek advice on encoding settings and challenges faced in the process.