In the past we usually have done public betas, where every registered Renoise user could download the betas at the backstage. This time weād like to do things a bit differently, and only want to invite a bunch of people to help us testing the beta versions before itās going public. This hopefully eases things on our side by concentrating on fewer people. Also, the 3.3 mostly is about just one feature: VST3 so weāre not expecting many issues that need to be discussed apart from plugin compatibility issues.
We also wonāt have time to add new features during the beta and will try to release Renoise 3.3 stable this year - if possible.
If you want to help testing the Renoise 3.3 betas, before they are going public please send me a private message with the following info:
your backstage email (your login), so we can enable the beta builds at the Renoise backstage for you. Please note: donāt send us your passwords - we just need the login
the operating system that youāre going to use mostly (Windows, OSX, Linux), so we can make sure that all platforms get tested somewhat evenly
I think weāll only need around 30 (33?) people to test the betas, so please understand that we canāt accept all requests.
Please only request access to the betas, if you are planning to do some actual testing
This release basically only is about VST3 support, so thereās really not much more to see.
Nope. Mainly VST3. Thatās it. This alone requires a lot of testing and finetuning, to ensure that all (well, most) plugins work as expected in Renoise.
I couldnāt agree more. Mixbus32c launched VST3 compatibility as it was a minor release, whereas 3 subsequent updates were addressing some serious issues (crashing DAW, not really usable).
Itās a new standard which is not backwards compatible with VST2 - so everything is different āinternallyā. And this means we basically need to test every plugin out there, to ensure that it works correctly in Renoise.
VST2 is deprecated - Steinberg no longer allows new plugin developers to license it. So many new plugins are only available as VST3 plugins.
It has a bit better support for Linux (itās at least defined how it should work on Linux), allows resizing editors (without hacks). And there are a little things here and there which make host and plugin authors life easier, but it wonāt be more CPU efficient.
Is it then possible in Linux to set keyboard focus on vst3 when playing with keyboard and ajust the parameters on the synth? Before it Was not possible like on windows