The plugdata community is welcoming and active. Whether you’re looking for help, want to share your patches, or just want to connect with other users, there are several ways to get involved.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/plugdata-team/plugdata/llms.txt
Use this file to discover all available pages before exploring further.
Get Help and Support
Discord Server
The plugdata Discord server is the best place for real-time help and community interaction.Join the Discord
Get help, share patches, report issues, and request features
- Getting quick answers to questions
- Sharing your patches and projects
- Discussing feature ideas
- Reporting bugs and issues
- Connecting with other plugdata users
- Learning from community examples
GitHub Discussions
For more structured conversations, GitHub Discussions is an excellent resource.GitHub Discussions
Browse topics, ask questions, and participate in longer discussions
- Technical questions and answers
- Feature proposals and discussions
- Sharing techniques and workflows
- Long-form tutorials and guides
- Searchable Q&A archive
Report Bugs and Issues
Found a bug or experiencing problems? Help improve plugdata by reporting issues.GitHub Issues
Report bugs, crashes, or unexpected behavior
- Your operating system and version
- plugdata version number
- Plugin format (VST3, AU, LV2, CLAP, or standalone)
- DAW name and version (if applicable)
- Steps to reproduce the issue
- Expected vs actual behavior
- Screenshots or patches that demonstrate the issue
- Search existing issues to avoid duplicates
- Try the latest version to see if it’s already fixed
- Gather all relevant information
Request Features
Have an idea for a new feature? The community welcomes suggestions. Where to request features:- Discord: Quick ideas and informal discussions
- GitHub Discussions: More detailed feature proposals
- GitHub Issues: Formal feature requests with labels
- Explain the use case and why it would be valuable
- Describe how you envision it working
- Consider if it can be achieved with existing features
- Be open to alternative implementations
Share Your Work
The community loves seeing what you create with plugdata. Ways to share:- Discord: Post patches, demos, and projects in relevant channels
- GitHub Discussions: Share detailed write-ups and tutorials
- Social media: Tag your posts with #plugdata to reach the wider community
- Original patches and instruments
- Effect processors and utilities
- Tutorials and learning resources
- Music and audio created with plugdata
- Tips and techniques
Contributing to Development
Interested in contributing code, documentation, or other improvements?Contributing Guide
Learn how to contribute to plugdata development
- Code contributions (bug fixes, features, optimizations)
- Documentation improvements
- Testing and bug reports
- Translations
- Example patches and tutorials
Code of Conduct
The plugdata community follows the Contributor Covenant Code of Conduct to ensure a welcoming and inclusive environment for everyone. Core principles:- Be respectful and kind to others
- Welcome newcomers and help them learn
- Accept constructive feedback gracefully
- Focus on what’s best for the community
- Avoid harassment, trolling, or offensive behavior
Stay Updated
Follow plugdata development:- GitHub: Watch the repository for updates
- Releases: Check the releases page for new versions
- Discord: Get announcements about updates and new features
- Website: Visit plugdata.org for downloads and news
Related Communities
Since plugdata is based on Pure Data, these communities may also be helpful:- Pure Data Forum: forum.pdpatchrepo.info
- Pd mailing list: lists.iem.at/listinfo/pd-list
- ELSE library: github.com/porres/pd-else
- Pure Data website: puredata.info
Community Resources
Learn from others:- Browse patches shared on Discord
- Explore GitHub Discussions for tutorials
- Check out Pure Data learning resources (many concepts apply to plugdata)
- Watch community-created videos and demos