How to process requests that contain many features

[icaria36]

From the https://bitwish.top/t/better-piano-roll/35 discussion…

@icaria36

The general feedback is clear, but in order to have effective feature requests, they need to be precise, and not to mix multiple features at once.

It doesn’t matter how many votes this request has, a developer cannot do much with a request consisting on “better [something]”.

@pier

What you’re saying makes absolute sense. “Improving the piano roll” is very vague and both the community and the Bitwig team needs precise requests for this Bitwish initiative to be productive.

OTOH I could think of maybe a dozen improvements just on the piano roll view. I think creating tons of threads could become very tedious.

@abraxa

Those 15 upvotes are likely a general feeling of “the piano roll sucks compared to other DAWs and needs some love and attention”, rather than concrete feature requests. It just doesn’t look polished, feel polished and the workflow isn’t great either. While requesting specific features is of course a good thing, making the bitwig team simply aware that they need to focus on this part of the DAW is also valid, in my opinion.