Renoise 3 speculation thread

[Airmann]

@Gooze

Not sure if trolling. />/>/>/>/>

Fact is, that I almost daily check if either Renoise or Bitwig have announced public betas, yet.
Right now, I use Renoise because I love the automation features for e.g. sound design. And Bitwig seems to be pretty good in here, too.
Everything WAV-related I do in Reaper, since it’s so much better for cutting/slicing audio clips.

Any DAW which combines these two worlds is very attractive, and Bitwig seems to be such a DAW.
If Renoise will be such a DAW, is totally open right now. So yes, Bitwig also provides no release date, yet,
but at least they give information about the contained features in 1.0.

Since I know Renoise already, I’d prefer Renoise, but I’m kind of fed up working with RAM-only based samples
which we had since over 20 years now (starting with Ultimate Soundtracker et al).

[Daed]

I am definitely more-than-anxious and simply giddy at the concept of a 2-years-in-development game-changing Renoise 3.0 release looming some time ahead. In the meantime, I know that I already do quite well with 2.8’s already abundant feature set even when using it as a live tool, so I can’t wait to see what sorts of goodies I receive when 3.0 drops.

I am, of course, packed with all sorts of empty hopes about all sorts of speculative features and release dates. Gotta say: I highly respect the alpha dudes. I tend to get super excited about anything I’m working on and gush to whoever’s nearby…

[AVALANCHE]

Just wanted to say there are some users who don’t care about the release date, and who wait patiently. I’m part of them, and in fact I found the time between the two last releases too short ! I felt like a spoilt child.

I guess this time we’re going back to reality. Lousy users tend to speak louder than the others. Personally I’m just happy to know something is coming.

[Airmann]

@mr_mark_dollin

I’ve noticed that Christmas stresses people out and sometimes causes anger.

No, it’s not Christmas in this case. It’s the long wait and the uncertainty.

Devs posted on facebook in May (!) 2013:

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),

I think this not very helpfull, because if I hope for feature A/B/C being implemented, wait 2 years and then it will not be implemented, I’m much more disappointed
than knowing from the beginning that it will not be there.

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.

Understandable, but what about the features that already have been implemented. Why are they so secret ?

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 actually 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!

I’ve stayed tuned the whole year, hope you devs will soon be finally happy with it.

[gentleclockdivider]

renoise 3.0 will be released on june 30 ,2014 …when summer vacation begins .
The developers decided it was the best date to release renoise 3.0 , so we have a whole summer to explore all it’s new features .
So , all happy now that we know the final release date , close thread .

[Airmann]

@gentleclockdivider

renoise 3.0 will be released on june 30 ,2014 …when summer vacation begins .
The developers decided it was the best date to release renoise 3.0 , so we have a whole summer to explore all it’s new features .
So , all happy now that we know the final release date , close thread .

I hope this is not another cruel joke !

[Conner_Bw]

http://www.youtube.com/watch?v=eRppqaanECA

[Conner_Bw]

“Dans ses écrits, un sage Italien
Dit que le mieux est l’ennemi du bien.”
- Voltaire

[Raegae]

I’m sure they try to implement something like this -->

[danoise]

@Airmann

I hope this is not another cruel joke !

Guess what - it’s another cruel joke. Starting to think that WaitingInLine3d (the game) was a good observation by Connor

[Sense_Net]

That quote about Renoise and Christmas has been so misunderstood.

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),

It means that releases should be like Christmas, not by Christmas. Like being used in the way a present on Christmas (or your birthday, etc) is a total surprise, not that the release will be at Christmas. Seven months later and this still is being confused.

Just in case, a translation:

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 a total surprise you did not expect at all),

News: Renoise 3.0 released on your birthday. All of your birthdays. Every user. Check the backstage at 00:01 on the day you were born.

[danoise]

@Sense/Net

That quote about Renoise and Christmas has been so misunderstood.

Hey, Seriously, I didn’t catch that…
Appropriate name you have, sir

[midierror]

I think that if the 35 pages of conjecture and speculation about the NEXT renoise were spent using the current renoise…the (renoise) world would be a better place.

Consumerism always leaves you wanting more.

[Airmann]

@Sense/Net

It means that releases should be like Christmas, not by Christmas. Like being used in the way a present on Christmas (or your birthday, etc) is a total surprise, not that the release will be at Christmas. Seven months later and this still is being confused.

No, I’ve undertstood that quite well,
it’s just the irony of the metaphor: Renoise 3.0 should be like Christmas, but Christmas is probably this time without Renoise 3.0

[Garf]

… i tried waiting years for a vsti tracker, pinning my hopes on madtracker for more years, so everday has been like christmas since renoise came along.

[Airmann]

@danoise

Guess what - it’s another cruel joke. Starting to think that WaitingInLine3d (the game) was a good observation by Connor

Who knows, in the meanwhile I think it’s possible that he could be right.

@danoise

I think that if the 35 pages of conjecture and speculation about the NEXT renoise were spent using the current renoise…the (renoise) world would be a better place.

Consumerism always leaves you wanting more.

Then why posting here instead of tracking ? Gogogo

[wahrk]

@Garf

… i tried waiting years for a vsti tracker

Behold. I give you reViSiT.

[tavernamax (sevenscientist)]

I speculate that renoise will have most of the features everyone has asked for…
What I struggle to speculate is if LUA will continue to be part of it?
If existing Tools will work?
When the blog will see an update?

It would be nice if even one of the alphas were allowed to share something on the Blog. I understand it may be to early, but even Kickstarter projects share small bits of information or how things are unfolding. I know this could be opening a can of worms and I respect the Dev Teams decision.

Renoise is GREAT for the product that it is, and we are very lucky it is here at 2.8
I anticipate great things as we all do, but apart from your every day users, those of us involved in developing tools are really and truly in in the dark right now. Please shed a little light?

[Airmann]

@sevenscientist

I speculate that renoise will have most of the features everyone has asked for…
What I struggle to speculate is if LUA will continue to be part of it?
If existing Tools will work?
When the blog will see an update?

It would be nice if even one of the alphas were allowed to share something on the Blog. I understand it may be to early, but even Kickstarter projects share small bits of information or how things are unfolding. I know this could be opening a can of worms and I respect the Dev Teams decision.

Renoise is GREAT for the product that it is, and we are very lucky it is here at 2.8
I anticipate great things as we all do, but apart from your every day users, those of us involved in developing tools are really and truly in in the dark right now. Please shed a little light?

I really don’t think that LUA support will be dropped. I expect new interfaces which cover the new features. Of course existing interfaces could be changed, too - that would be not so good for 3rd party tools and their maintainers. But if the changes are minor like in 2.8.x it shouldn’t be a problem. On the other hand it seems that they have changed a lot of code under the hood, already. Hope that doesn’t affect existing scripting interfaces, too much.

[xrns]

I just want some more bits of information to feed my speculation hunger.

Like for example: will Renoise 3.0 be mostly about few but bigger new features or will it be more about many but smaller new features?

I think that kind of information could be made available without any risk of causing stress and other unpleasant things, neither for the users nor the devs. I think the vast majority of Renoise users are able to properly handle such information.