Hm.

I think the template should have a guidance section (with "remove this before submitting", of course) that explains what is likely to be considered, let alone accepted.

That is - Jamulus does what Jamulus does. It avoids doing what other software does deliberately to avoid both processing overhead and maintenance overhead. So if there is another way to solve the problem, that's likely a better solution.

What about:

"Thanks for opening a new feature request! Please keep in mind that Jamulus achieves low latency audio by reducing complexity and following the "Keep it simple and stupid" approach. Adding new features may result in more processing and maintenance overhead so please be sure that your feature can not be achieved by different approaches/software too."

Yep, that's the idea. Maybe add "Make it clear why here." on the end.

I wouldn't stress it too much since it might sound intimidating.

If we go too far it could sound like:

Thanks for your feature request and all the work you put into thinking about it. Since we don't like to introduce too many new features, you can be quite sure that it will not be implemented.

I've now added your suggestion, but my comment is stil valid ;-).

Looks better now :)

Great! merged now.