Join the Cubase Beta Program – Help Shape the Future of Cubase!
We’re inviting passionate Cubase users to take part in the Cubase Beta Program! As a beta tester, you’ll get exclusive early access to upcoming versions of Cubase and have the chance to provide valuable feedback that helps refine new features, improve stability, and optimize performance.
Why Join?
Test new and unreleased features before anyone else
Work directly with the Cubase development team
Help make Cubase even better for the global music production community
What We Expect from You:
Provide detailed feedback and report any issues
Focus on testing stability, performance, and new features
Keep discussions productive and relevant
Respect the confidentiality of the beta program (NDA required)
Interested? Apply now and be part of the future of Cubase!
Very happy to see you guys reaching out for more beta testers like this! In another life when I had more time, I would have applied for sure! I just don’t have enough time right now to do you justice, since good beta testing requires actual time to do well. However, I applaud all the beta testers who sign up and I’m very grateful for their efforts!
And again, cheers to Steinberg for reaching out like this! Please keep it up!
Now IF you ADD the following:
Help us test our new click-and-drag ripple editing mode for upcoming release in Cubase/Nuendo 15!
THEN I would really try to make some time to beta test! Time is just so short in my life right now, but I would really really try to find some time for this one feature, since it is so important to me.
Click-and-drag ripple editing (like PG implemented in WaveLab’s montage, or like what is in Reaper) is the ONE feature I have been hoping for the most for years, and if you were actually testing click-and-drag ripple editing, I would want to help so it is done really well, and figure out some time so I could test it inside-out and probably annoy you so much that you would regret my beta testing, because I would be going for perfection.
Anyway, again, very happy to see you expanding your beta team like this! Your outreach to the community is the right direction for sure! Cheers!
Hello, what are the qualities required to become a beta tester?
It’s pretty much the same at image line (FL Studio 2025), it’s the users who define the imperfections of the new updates and beta software.
For my part, it’s just for what had not been translated into French for the commands and designation, I attached my modest contribution, but I understand that you have to be skilled in the use of such a program to scute in the smallest corners.
To tell the truth I spend more time looking for the who and why than composing, so I understand that it must not be easy to find good elements, but it can’t move forward if there is no feedback for the quality to be there.
Good experimentation for the new version.
Musical friendship
Hi! When I click apply, my info to share displays and my old address is in there. I went to My Steinberg in the Profile section but that just has Name, DOB and Country, I cannot find where to update my home address. I don’t want to agree to share with the old address in there, where do I change that? Thanks!
Pick me!
I have over 15 years of experience with Cubase and know it inside out. I also encounter crashes, so I’d be more than happy to help identify and report issues as a beta tester.
Very nice, but alas I assume that one would need to own Cubase and cross-grading back and forth between Nuendo and Cubase would not be sensible financially.
I am very keen however to see if this becomes the norm, as I may actually purchase Cubase (again) just to be a part of the program because, let’s face it, there’s nothing like learning new features, that you know only exist in your favourite program(s).
I am interested to do beta testing as I have previously been reporting many bugs and had feature requests and improvement ideas.
I have read the terms and conditions and it says I need internet access to use it. So what happens if I loose internet access while using it I have to close the app and stop using it or the app will not work, or the connection is only required to send the usage information and this can be done at later time?
Also, I would like some clarification on how may hours I should use it at minimum because, as I understand this I am not suppose to use it for actual production which is a bit of a setback, I’d rather work on something I want to release while testing this. I already test another software and there are no issues using it for actual production what can I do if I come up with some great song and I cannot release it because of the terms and conditions can this be released once official version is released?
I think Steinberg should embrace including low volume/low skilled users who may represent a very significant portion of the user base and their potential market growth.
Input from expert users is essential of course, but if all the testing is done by those with PhD’s in Cubase already, there will almost certainly be large holes in Steinberg’s understanding of how Cubase’s other users (more typical users?) interact with the program.
Sounds nice at first glance but the actual reports from low volume/low skilled users require a tremendous amount of additional communication just to find out what they are talking about. You can bear witness of this phenomena here in the forum almost on a daily basis. (Not meant in a disrespectful way to anybody.)
In other words, not so much orientated towards finding issues/bugs but more leaning towards the experience itself as in “how does it work, is it self-explantory, intuitive, hard/easy to grasp” kind of way.
Yes, but how else can you gain insights if you want to adress the needs of different user groups? That comes at a price in terms of human resources to “decode” the hurdles in user-product-interaction. Thus, I think this is a valid observation by @alexis to take these considerations into account as well.
Generally speaking, there’s sometimes a huge gap between the quality of a feature (in terms of its brilliant functionality) and the way its functions are communicated/accessible. This applies not only to low volume users but also to experienced/professional users in my opinion. That’s a pity because this way a lot of features go unnoticed and don’t get the credit they deserve.
