Some people here start to get nervous and wonder if we are actually working on a new release or not. Don’t worry, of course we are. Just takes a little bit longer this time.
Can’t give you any details about the final feature set here now though. We do keep the content and status of internal (and alpha) releases private for two good reasons:
first, because the best surprises are those you don’t expect (Renoise releases should be like Christmas), and second, to avoid discussions about features in progress we actually haven’t implemented yet and thus can not make any promises about yet. If we promise that release X.Y will contain feature Z, and it actually can’t be realized or we don’t want to keep it because it turned out to not be what we hoped it could be, this will only result into disappointment on the user side and a lot of stress on our side.
Only thing I can reveal here now is that it will be Renoise 3.0 and its new features probably will be a bit unexpected for many. We took the time to experiment with a few things. Revised them a lot. Thrown away large parts of it again because we haven’t been fully happy with them, and partly started from scratch.
Some of those features also required rewriting large parts of the codebase; with Renoise getting bigger and more complex internally, new features also will take longer to realize with every new release. And hey, we’re a small team too. We don’t have a big bunch of people working off feature after feature and actuall also don’t want to work this way.
So please be a little bit patient. Next news will be the official beta announcement for 3.0. Also can’t promise when exactly this will be. It’s ready when it’s ready. And it’s ready, when we are happy with it and not because some financial department says that it has to be ready. That’s a very luxury way of working but I hope also a way of working many of you can acknowledge.
So, stay tuned. In the meanwhile, enjoy Renoise 2.8