Want to join the Surge Synth Team? There’s no application process! Just show up, be friendly, and contribute. We work hard to make a welcoming community of music enthusiasts.
And we really don’t have any rules other than don’t be a jerk! (If you want to be a jerk online there are plenty of options). Have an idea? We would love to hear it. Happen to be a Windows C++ plugin developer? We need your help! Think you’ve found a bug? You probably have! Want to contribute content? Go for it!
We love to hear from our users! Our projects have been able to attain the quality they have today thanks to a dedicated group of musicians who gave patient and clear feedback on bugs and brainstormed ideas for new and improved features. We invite you to share your feedback too.
The best way to reach the development team is either to open an issue on GitHub or join our discord and chat with us. Here are the GitHub issue pages for our projects:
And good bug reports make good software! So please feel free to open a GitHub issue! But there are some guidelines which may help.
Good GitHub issues should have clear titles (like “Mouse doesnt map properly to filter section when modulating”, not “Bug”). They should contain some key information:
And once all of that is included, please include a clear description of the bug. How you demonstrate it and what you expect. Screenshots help, but clear text is good also.
Here’s a great bug report:
“Surge Windows 10 VST3 version 184.108.40.206 in FruityLoops 20. When I am dragging a slider in modulation mode, if I drag off the end of the slider and keep dragging, the modulation slider can reset to the max. Unmodulated the slider doesn’t do that”
That’s a real bug report we got. It was a one line fix once we had that clear description!
For features, be more creative. We love to hear ideas.
And we try to fix bugs in a timely fashion. But as always, the best bug is one which comes with a pull request to fix it. Dive in! The code’s not that scary.
The Surge Synth Team