Community
Ask questions, share your work, contribute to AIVE, and connect with fellow creators worldwide.
Loading community...
Community Guidelines
AIVE Community is a welcoming space for creators of all skill levels. By participating, you agree to follow these guidelines.
What We Encourage
Be respectful and constructive
Treat every member with respect. Disagree with ideas, not people. Offer constructive feedback that helps others improve.
Share knowledge freely
Post tutorials, workflows, and tips. Answer questions when you can. The community grows when knowledge is shared.
Search before posting
Your question may already have an answer. Use the search function to check existing threads before creating a new one.
Use clear titles and categories
Write descriptive thread titles and select the appropriate category and platform tag so others can find and help you.
What We Do Not Allow
Harassment and discrimination
No personal attacks, hate speech, or discrimination based on race, gender, religion, nationality, disability, or any other characteristic.
Spam and self-promotion
No unsolicited promotion, affiliate links, or repetitive posting. Share your work in the "Show Your Work" category only.
Piracy and illegal content
Do not share pirated software, cracked plugins, or copyrighted content you do not have rights to distribute.
NSFW or inappropriate content
All shared content must be appropriate for a general audience. Mark any mature creative work with appropriate warnings.
Enforcement
Violations are handled progressively: verbal warning, temporary mute (24 hours), temporary ban (7 days), permanent ban. Severe violations (threats, illegal content) result in immediate permanent bans. Appeals can be sent to community@aive.one.
Contribution Guide
AIVE welcomes contributions from the community. Here is how you can get involved.
Ways to Contribute
- Bug reports — Report bugs via the Bug Reports tab or on GitHub Issues.
- Feature requests — Submit and vote on feature requests through the Feature Requests tab.
- Documentation — Help improve our docs by emailing suggestions to support@aive.one.
- Translations — Help translate AIVE ONE Beta into your language via our Crowdin project.
- Community support — Answer questions in the forum and Discord to help fellow creators.
- Plugins and extensions — Build and share plugins using the AIVE Plugin SDK.
- Tutorials — Write tutorials and guides and share them in the community.
Code Contributions
Fork the repository
Fork the relevant repository on GitHub and clone it to your local machine.
Create a branch
Create a feature branch from main with a descriptive name: feature/your-feature-name or fix/issue-number.
Make your changes
Follow the coding standards in the repository's CONTRIBUTING.md file. Write tests for new features and ensure existing tests pass.
Submit a pull request
Push your branch and open a PR with a clear description of changes. Reference any related issues.
Code review
A maintainer will review your PR. Address any feedback and the PR will be merged once approved.
Contributor License Agreement
By submitting a pull request, you agree that your contributions will be licensed under the same licence as the project. First-time contributors will be asked to sign a CLA.
AIVE Discord Server
Our community channels are coming soon. In the meantime, reach out to the team at support@aive.one for help and discussion.
Planned Channel Structure
When the Discord server launches, we plan to include channels such as general discussion, help and support, AI features, show your work, feature requests, bug reports, tutorials, color grading, and audio. The exact structure will be finalized closer to launch.
Feature Request Process
We build AIVE ONE Beta based on what creators need. Here is how feature requests move from idea to implementation.
Submit your idea
Post a feature request in the forum (Feature Requests category) or on Discord. Describe the problem you are solving and the desired outcome.
Community voting
Other creators upvote your request. Higher-voted requests get prioritised. Add your use case to existing requests instead of creating duplicates.
Team review
The AIVE product team reviews top-voted requests monthly. We assess feasibility, alignment with our roadmap, and impact on the creator community.
Status updates
Accepted requests are tagged with status: Planned, In Progress, or Shipped. We update the thread when status changes.
Beta testing
Selected creators get early access to test new features before public release. Sign up for the beta programme in your account settings.
Writing a Good Feature Request
- Be specific — Describe exactly what you want the feature to do, not just a vague idea.
- Explain the problem — What workflow limitation or pain point does this solve?
- Provide context — What type of content do you create? How often would you use this feature?
- Include examples — Screenshots, mockups, or references to similar features in other tools.
Bug Report Template
When reporting a bug, include as much detail as possible. Use this template for the most effective reports.
Severity Levels
- Critical — App crashes, data loss, or renders are corrupted. Prioritised for immediate fix.
- Major — Feature is broken or unusable but a workaround exists.
- Minor — Cosmetic issues, incorrect labels, or minor UI glitches.
- Enhancement — Not a bug, but an improvement to existing behaviour.
Where to Report
- Forum — Post in the Bug Reports category for community visibility.
- Discord — Use the
#bug-reportschannel for quick reports. - Email — Send a detailed report to support@aive.one for tracking.
- In-app — Use Help > Report a Bug to send a report with diagnostic data attached automatically.
Open Source Components
AIVE ONE Beta is built on the shoulders of the open-source community. We contribute back where we can, and these are the components we have open-sourced.
| Project | Licence | Description |
|---|---|---|
| aive-timeline-engine | MIT | Magnetic timeline constraint solver and layout engine |
| aive-codec-bridge | LGPL-2.1 | FFmpeg wrapper with hardware acceleration for Node.js |
| aive-subtitle-parser | MIT | SRT, VTT, ASS, and TTML subtitle parser and generator |
| aive-design-tokens | MIT | AIVE ONE Beta design token system for consistent UI theming |
| aive-waveform | MIT | High-performance audio waveform renderer for canvas |
| aive-fcpxml | Apache-2.0 | FCPXML parser and generator for FCP interoperability |
Contributing to Open Source
AIVE open-source repositories will be published soon. We follow the Contributor Covenant code of conduct across all projects. Watch this page for updates.
Full Licence Information
For complete third-party licence details, see the Licenses page. A machine-readable SBOM (Software Bill of Materials) is available at Help > Open Source Licenses within the application.
Community Events
Join live events, workshops, and community challenges to learn, connect, and showcase your work.
Upcoming Events
AIVE Creator Meetup — Virtual
Monthly community meetup with live demos, Q&A with the AIVE team, and creator spotlights. Open to all members.
Virtual / DiscordColor Grading Workshop
Learn professional color grading workflows in AIVE ONE Beta with colorist Priya Menon. From log footage to final grade.
Workshop / Live30-Second Short Film Challenge
Create a 30-second short film using only AIVE ONE Beta. Community voting determines winners. Prizes include 1 year of AIVE Pro.
Challenge / CompetitionRecurring Events
- Monthly Creator Meetup — First Saturday of every month, 18:30 IST on Discord voice channel.
- Weekly Office Hours — Every Thursday 16:00 IST. Drop in with questions for the AIVE engineering team.
- Quarterly Editing Challenge — Themed editing challenges with community voting and prizes.
- Annual AIVE Creator Awards — Celebrate the best community-created content of the year.
Host an Event
Want to host a workshop, tutorial stream, or local meetup? Reach out to community@aive.one and we will help you organise and promote it.