![]() That could be one vote (depending on how broadly we interpret a feature request.)Īnother one is the handling of “Mute Pre-Send when Mute”, that from what I gathered went through “Issues” at one point, only to decide that it’s implemented as intended and misunderstood. 4/6 votes I cast are in topics regarding key commands. ![]() The votes are too few and the requests too dispersed.įor example, I personally am out of votes at the moment. I think it will be a hard nut to crack, voting for feature requests. When you are entering you ideas, please make sure to tag your post with “Feature-Request” and please keep each thread focused on a specific suggestion instead of long lists. So more active users in this community will have more chances to vote. But ideas or suggestions that are discussed and supported widely by the community, will definitely be considered by the team.ĭepending on your Member Level you will have a specific amount of votes. There are a lot of factors that influence the decision what improvements the next Cubase version will introduce. Of course, this is not a direct vote on the Cubase development backlog. But as diverse as the use cases, musical genres or production techniques of the Cubase user community are, as much differ the opinions on how Cubase should be improved in the future. I would like to encourage you to use your votes to let us know what your priorities are in the “Feature Request” category.Įveryday new ideas on how to improve Cubase are discussed in this community. Some of you may have noticed the “Vote” function in our new forum.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |