CONTACT & SUPPORT
Good tools start
with a conversation.
Tell us what you are making, what gets in the way, or what you would like to explore. Useful session details make feedback easier to act on.
What to include
For a plugin issue, include the product name, operating system, DAW version, sample rate, buffer size and the steps that led to it.
For Tessel, describe the effect chain and any external models. For Paly, include your MIDI routing and the instrument receiving it. Keep passwords, API keys and private file paths out of your message.
Support independent work.
Ko-fi contributions are optional and help make time for development, testing and documentation.
Buy me a coffeeFor RushLink-specific issues, you can also use its public issue tracker.