Cherry Audio Forums

@CA team.

It’s a shame that some of the issues with VM2 dampened the launch party, but as the platform and user-base grows so does the expectation - especially for those of us heavily invested (money/time/both) in VM for our music production.

I don’t know what your internal QA process looks like, but as a veteran of the software development industry myself I can see that a lot of the frustrations about VM2 would have been entirely avoided with a limited public beta comprising us VM users with different platforms and use-cases.

I’d be happy to help here, as I’m sure would many VMers.

Please consider.

+1, as another software developer.

Me three, ALSO as a software developer.

Yes, we had the same discussion. We are taking steps to ensure that this mistake doesn't happen again, including a beta team. We have another update coming, as well.

Great, thanks for the update. Do let me know if I can assist with any beta team.

Cherry Garcia wrote: ↑Tue May 26, 2020 3:19 pm We have another update coming, as well.

Nice!

Make that an inhouse beat team and a selected public beta team. End users are the best punishment for software. It's funny how you can have a team of ten super brilliant developers produce a program with no bugs and you give it to a user and they crash it in ten minutes. I have studied this phenomenon - it's because the mindsets are different.

Hopefully not only VM can improve but also your development process. The highly public nature of the mistakes in VM 2.0 cant be good for company image.

I'd like to volunteer for the public beta team. Not a developer, unless you count shell scripts.