remotion VS mantine

Hey HN! We’re building Revideo (https://github.com/redotvideo/revideo), an open source toolkit that lets you programmatically create and export videos with the animation library Motion Canvas (https://github.com/motion-canvas/motion-canvas). This is useful whenever you want to build apps that automate certain video tasks, which is increasingly possible using AI tools - for instance, one of our first users is building an app that turns code documentation into video tutorials.

Revideo extends Motion Canvas with features that are essential for creating video, such as the ability to export audio tracks, a nodejs package for headless, parameterized & much faster rendering, and audio components that make audio editing and syncing easier. While Motion Canvas aims to be a standalone editor [1], we want to build a set of libraries that lets developers integrate video editing functionality into their apps. Our goal is to provide an open-source alternative to Remotion (https://github.com/remotion-dev/remotion).

At the start of this year, we explored a bunch of product ideas in the space of AI-based video creation. For example, we’ve built apps that automatically create educational short videos and have experimented with automatically A/B testing and personalizing video ads.

While building these products, we were frustrated with the video editing frameworks we used: Moviepy (https://github.com/Zulko/moviepy), which we relied on initially, doesn’t offer a way to preview your videos, so we’d often have to wait minutes for a video to render to test our code changes. Remotion (https://github.com/remotion-dev/remotion), which we switched to later, is really good, but we didn’t want to rely on it as it is not open source (source-available only). That’s why we decided to build Revideo.

We’d already been following Motion Canvas for some time and really liked using it, so we thought that extending it would get us to something useful much faster than building an animation library from scratch. Initially, we tried to build our features as Motion Canvas plugins, but this did not provide enough flexibility to achieve the desired functionality. Additionally, video-specific features (such as audio support) were generally considered out of scope by the Motion Canvas maintainers, which is why we ultimately ended up creating a fork. We’re unsure if this is the right way to go in the long term, and would prefer to find a way to build Revideo without diverging from Motion Canvas too much - if you have suggestions on how to solve this, we’d love your input.

Compared to Remotion, which builds on top of React, Motion Canvas uses the HTML Canvas API and makes you define animation flows with generator functions. Its API is more “procedural”, as it makes you define the things that happen in your animation as a sequence of yields, whereas Remotion gives you a frame number and lets you declare how your video should look like at that frame.

Our current focus is improving the open source project. In the long term, we want to make money by building a rendering service for developers building apps with Revideo. Such a service would offer a pretty similar deployment experience to Vercel, but instead of web apps, we let developers deploy Revideo projects and expose a rendering endpoint for them. Letting us manage the infrastructure will allow us to offer much faster rendering, as we can massively parallelize rendering jobs on our servers (e.g. spinning up 100 headless browsers that render 100 frames each to render a video with 10,000 frames).

We’d love to hear your feedback and suggestions! You can find our repo at https://github.com/redotvideo/revideo, We’ve also released an example video editing app at https://github.com/redotvideo/revideo-saas-template. Thank you!

[1] “Motion Canvas is not a normal npm package. It's a standalone tool that happens to be distributed via npm.” - https://github.com/orgs/motion-canvas/discussions/1015

We collaborated with the vibrant Remotion Open-source community to find the answer for using GPU with Remotion for server-side rendering. After encountering some setbacks on our way, we were able to make it work for Remotion eventually. We consolidated our findings in the Remotion Docs at Using the GPU in the Cloud and simplified the instructions for Remotion developers to make the most out of it. Although the whole research was done for Remotion, the same process will work for any headless application that requires GPU power, especially in headless mode.

Under the hood, it is powered by: - Remotion - Google TTS - OpenAI

When I was talking with Jonny Burger (the creator of Remotion) about the challenges small open source projects face and how it becomes harder for individual maintainers who work because of their goodwill to carry their project forward, I did not realize the conversation would give birth to the idea of Relano.

I loved the idea of creating videos with dynamic data using Remotion, and started to dabble with it. I had a vague idea that it can be used to make simple videos that convey some text.

thank you for your input! the best way to ensure everyone has a great experience is to spec & scope bounty issues + provide acceptance criteria.

you can look at Remotion's 17 completed bounties, where specs & acceptance criteria are always included: https://github.com/remotion-dev/remotion/issues?q=label%3A%2...

that being said, we have only had a handful of projects using OSS bounties so far so we haven't seen everything under the sun. I acknowledge what you mean by blurry lines and how/when they might occur. but as I said before, when specs/scope/acceptance-criteria are in place, it's really hard to go wrong

7: Remotion

I recently worked on a hobby project recently that used ffmpeg and Remotion to render short videos before uploading them to Cloud Storage from a Cloud Run service. I used Pub/Sub to start renders by pushing messages to a rendering container with the info required to generate a video.

As for the PRs, one of our developers, Stefan Uzunov improved the Remotion CLI by adding some enhanced interactivity and sane defaults when picking which composition gets rendered, while Ilija Boshkov contributed by packaging an existing component into a mainline Remotion package for adding motion blur to Remotion videos.

If you don't have to stay in AE, you could look into ReMotion which can create animations by code and export a video file.

Here’s another mentality shift for you. If you were thinking in a providers pattern, you need to snap out of it. You can no longer store your theme in a provider. No more RadixUI or MantineUI for you.

import { TextInput, Select } from '@mantine/core'; // Example usage ; ; Enter fullscreen mode Exit fullscreen mode Maps: React Simple Maps provides maps that are valuable for visualizing geospatial data. You can integrate interactive maps into your dashboard to represent data points geographically. import {ComposableMap, Geographies, Geography, Marker} from "react-simple-maps"; // Example usage {...} {... return ( ); })} Enter fullscreen mode Exit fullscreen mode By incorporating these core components, our template accelerates the development of admin dashboards. These components are designed to work seamlessly together, providing a cohesive user experience. You can effortlessly create complex data visualizations, interactive tables, intuitive forms, and interactive maps — essential elements that transform raw data into meaningful insights. Deploying the Template to a Live Environment Deploying our admin dashboard template to a live environment is a straightforward process. We recommend utilizing popular hosting platforms like Vercel, Netlify, or Firebase Hosting. These platforms offer seamless integration with Next.js and allow you to deploy with a few simple steps: Install Required Dependencies: Ensure you have the necessary dependencies specified in the package.json file. Build the Project: Generate a production build of your Next.js application using the command: npm run build. Select Hosting Platform: Choose your preferred hosting platform (e.g., Vercel). Connect Repository: Link your template’s GitHub repository to the hosting platform. Configure Deployment Settings: Configure deployment settings, such as branch selection and build commands. Deploy: Trigger the deployment process. The hosting platform will automatically build and deploy your admin dashboard template. Real-World Use Cases The versatility of our admin dashboard template knows no bounds. It caters to a myriad of real-world use cases, each tailored to specific industries and applications: E-Commerce Management: The template can be employed to manage product listings, order processing, and inventory tracking for online stores. Data Analytics: With its data visualization components, the template can serve as a dashboard for analyzing metrics, trends, and insights. Project Management: The template’s customizable components facilitate the creation of project management tools for tracking tasks, deadlines, and team collaboration. SaaS Applications: As the foundation of a Software as a Service (SaaS) application, the template streamlines user management, subscription tracking, and data presentation. Content Management: It can also function as a content management system dashboard, offering tools to manage articles, media, and user-generated content. Live Demo For a hands-on experience, explore the live demo of our admin dashboard template: Live demo — https://mantine-analytics-dashboard.netlify.app/ Witness the template’s adaptability, responsiveness, and functionality firsthand. Feel free to interact with its components, navigate through its sections, and envisage how it could seamlessly integrate into your projects. Contributing and Support I welcome all developers and enthusiasts to contribute to the growth of our open-source admin dashboard template. Contributing is a collaborative process that empowers us to collectively enhance the template’s capabilities and quality. To get started: Fork the Repository: Fork the template’s GitHub repository to your own GitHub account. Clone the Fork: Clone the forked repository to your local machine using Git. Create a Branch: Create a new branch for your contributions to keep the main codebase intact. Implement Changes: Make your desired changes, add new components, or refine existing features. Commit and Push: Commit your changes to the new branch and push them to your GitHub fork. Submit a Pull Request: Submit a pull request from your forked repository to the main template repository. Your changes will be reviewed and potentially merged. Conclusion In summary, our Mantine and Next.js admin dashboard template offers a range of benefits that empower developers, designers, and entrepreneurs to create exceptional admin interfaces: Efficiency and Speed: The template expedites development by providing a pre-built foundation of components and features, allowing you to focus on customization and innovation. Consistency and Aesthetics: Mantine’s design-first approach and Next.js’s performance optimizations ensure a consistent and visually appealing user experience. Flexibility and Customization: The template’s modularity and theming options facilitate easy customization to align with your project’s unique branding and requirements. Rich Functionality: The integration of core components such as charts, tables, forms, and maps equips you with tools to tackle diverse dashboard functionalities. Invitation to Explore and Utilize The Mantine and Next.js admin dashboard template isn’t just an end; it’s a beginning — a starting point for your creative journey. Whether you’re a seasoned developer seeking a rapid launch or an enthusiast keen on learning modern development practices, this template is your canvas. Additional Resources GitHub repository — https://github.com/design-sparx/mantine-analytics-dashboard Mantine — https://mantine.dev/ Nextjs — https://nextjs.org/ Code documentation — https://mantine-analytics-dashboard-docs.netlify.app/

While I have experience with Tailwind and frontend development, I don’t really have the patience to use it. I usually end up using something like Mantine, which is a complete component library UI kit, or Daisy UI, which is a component library built on top of Tailwind. Shadcn/ui is quite similar to Daisy in this sense, but being able to customize the individual components, since they get installed to your components folder, made development more streamlined and more customizable. On top of that being able to change my components style with natural language thanks to v0 made development super easy and fast. Shadcn may be too minimalist of a style for some, but thanks to all the components being local, you can customize them quickly and easily!

Great compilation. Thanks for putting that together.

Curious what your take is on these UI libraries that "claim" they are accessible:

https://mantine.dev - "Build fully functional accessible web applications faster than ever"

29.react-mantine

I am currently using mantine.dev , and i am very happy with the results, i haven't done any customization, if you want to give a look on my website: https://culturadocaractere.com.br

GitHub stars: 21.9k GitHub link: https://github.com/mantinedev/mantine Documentation: https://mantine.dev/getting-started/