Renoise 3 speculation thread

General Discussion
102

Don’t know if someone else already did a listing like this,
but here is some more fuel to keep speculation alive: :D/>

  
 June 21st, 2002 -> December 17th, 2002 : 179 Days (~ 6.0 Months) for v1.2  
 December 17th, 2002 -> March 9th, 2003 : 82 Days (~ 2.7 Months) for v1.25  
 March 9th, 2003 -> March 31st, 2003 : 22 Days (~ 0.7 Months) for v1.26  
 March 31st, 2003 -> August 12th, 2003 : 134 Days (~ 4.5 Months) for v1.27  
 August 12th, 2003 -> October 16th, 2003 : 65 Days (~ 2.2 Months) for v1.28  
 October 16th, 2003 -> March 20th, 2005 : 521 Days (~ 17.4 Months) for v1.5.0  
 March 20th, 2005 -> August 24th, 2005 : 157 Days (~ 5.2 Months) for v1.5.1  
 August 24th, 2005 -> December 18th, 2005 : 116 Days (~ 3.9 Months) for v1.5.2  
 December 18th, 2005 -> March 1st, 2007 : 438 Days (~ 14.6 Months) for v1.8.0  
 March 1st, 2007 -> November 3rd, 2007 : 247 Days (~ 8.2 Months) for v1.9.0  
 November 3rd, 2007 -> April 21st, 2008 : 170 Days (~ 5.7 Months) for v1.9.1  
 April 21st, 2008 -> January 15th, 2009 : 269 Days (~ 9.0 Months) for v2.0.0  
 January 15th, 2009 -> May 26th, 2009 : 131 Days (~ 4.4 Months) for v2.1.0  
 May 26th, 2009 -> March 5th, 2010 : 283 Days (~ 9.4 Months) for v2.5.0  
 March 5th, 2010 -> April 1st, 2010 : 27 Days (~ 0.9 Months) for v2.5.1  
 April 1st, 2010 -> November 5th, 2010 : 218 Days (~ 7.3 Months) for v2.6.0  
 November 5th, 2010 -> March 12th, 2011 : 127 Days (~ 4.2 Months) for v2.7.0  
 March 12th, 2011 -> May 27th, 2011 : 76 Days (~ 2.5 Months) for v2.7.1  
 May 27th, 2011 -> July 1st, 2011 : 35 Days (~ 1.2 Months) for v2.7.2  
 July 1st, 2011 -> March 15th, 2012 : 258 Days (~ 8.6 Months) for v2.8.0  
 March 15th, 2012 -> August 15th, 2012 : 153 Days (~ 5.1 Months) for v2.8.1

( i wrote this script to generate that: http://ue.o—o.eu/data/renoise_releases_script.txt )

v1.9 took ~8 Month
v2.0 took ~9 Month
v2.1 took ~4 Month
v2.5 took ~9 Month
v2.6 took ~7 Month
v2.7 took ~4 Month
v2.8 took ~8 Month

Major releases often took around 8-9 Month, so I guess it will take around
9 Months for the next release. August 2012 + 9 Month and we get:

[indent]worst case May 2013 :(/> [/indent]
for the next version. If we are more optimistic, and calculate 4 Month for the next release, we get:

[indent]best case December 2012. :blink:/> [/indent]
Now take the average of 6.5 Month and we get:

[indent]March 1st, 2013 :yeah:/> [/indent]

103

I can’t hold my breath that long :panic:

104

To be even more cruel, I will list the release months of the major releases:

  
March 20th, 2005 v1.5.0  
March 1st, 2007 v1.8.0  
November 3rd, 2007 v1.9.0  
January 15th, 2009 v2.0.0  
May 26th, 2009 v2.1.0  
March 5th, 2010 v2.5.0  
November 5th, 2010 v2.6.0  
March 12th, 2011 v2.7.0  
March 15th, 2012 v2.8.0

Notice how often March appears in that list ;)

105

Better get used to it…

106

Those are the final releases aren’t they? Beta period usually takes months so this will be a big one…

107

To be honest, I think that the beta announcements are more of interest in this discussion than major/stable release dates, I posted a little list a couple of weeks ago:

108

Aw, right! This lessens the pain of vV’s worst case scenario with August 2013 :slight_smile:

109

This has actually made me wonder how Renoise deals with the Alpha/Beta/RC/Stable cycle exactly. We know there is a closed Alpha. We know there is an open Beta. We know no roadmap or promises of forthcoming features is made to users by the developers. But is there a pretty much perpetual Alpha version which the selected testers get on a regular basis with each minor tweak, additional feature and bug fix? Or is it develop, develop, develop - Now it seems pretty much there as far as the actual developers are consider so hand it to the Alpha testers. If the later is the case then would announcing that the next version has gone into the closed Alpha testing stage possibly be a good thing? It would be an additional announcement reassuring that development is well under way and that hopefully the open beta wont be too far off. It still wouldn’t be disclosing anything in the way of features, so if something is found to just be too unstable to leave in the final at this stage it hopefully wont provide disappointment. But I can see it leading to people with Alpha Tester under their avatar and the IRC channel getting pestered for than normal about what the situation is, how long until the Beta and some tasters of the new features to expect (even if unofficial.)

110

Thats a good question kazakore. If I had a software project like Renoise, I would maybe hand alpha versions regularly to the
testers (some “nightly build” version for instance, or at least a weekly build).
It’s probably not only bugs that they find, but also rough edges in the workflow with the new features or just a different view
on the state of the software. So I think a close contact with the alpha testers would definitively be best.
In this case there would be no announceable “alpha phase”.

111

One example we were given of this is apparently the did discuss removing pattern numbers in the last release, or something similar, so I understand it’s more than bugs (in fact I would say the betas are more for mass testing to find bugs whereas the alphas would be more workflow and finding the biggest and most obvious bugs only.)

Agreed. Hence why I explicitly said if that’s not the case maybe announcing that an Alpha round has started might help allay some fears of stagnant development. If it is more running testing and nightly/weekly builds then obviously this can’t be done.

112

Development is not in a stale process that is one thing i can guarantee you.

113

That would be information, just for the sake for information. IMHO, the world is a better place without that

But still, I can relate to the thread topic - I remember back in 2005, I had the same “oh noes, this tracker has been abandoned” fear, since a lot of tracker projects were in fact abandoned in those days.
It turned out taktik had simply redone the UI and cleaned up the codebase :slight_smile:

114

I bet having linux, mac & windows versions all up in the mix also doesn’t speed things up?

115

It’s not that bad I think/guess. The neccessary work should be additive and not multiplicative.
Once you got a well structured code base and sorted out the issues with each platform you can more
or less focus on the actual application again. More platforms should only mean more work when
there are fundamentally new features integrated, like another plugin api, another audio driver
or the platform itself changes (like supporting windows 8). (At least I hope it is like that with Renoise :)

116

I fully believe that. I was thinking more for reassurance to the people that started this and the other similar threads, who might see it as a good sign of faith.

From the few bug reports we’ve already seen for Win8 of features that work flawlessly on every other operating system I’m wondering if getting a stable, Win8 compatible version might be part of the “delay” this time…

117

Whenever it comes I’m pretty sure it will be fantastic. I love 2.8 the way it is now I still learn new shit everyday. TBH I Haven’t been happier in any other daw.

118
119

I liked danoise’s statement about “information, just for the sake for
information.”. People should not get worried too early IMO. There is still
plenty of time until I really get worried. It was just 4 months ago that they
released 2.8.1, and there were was chrismas and other holidays.

I really hope not :) I hope the “delay” (which I don’t see yet), is due to
big features like audio tracks, which probably require some deep structural
changes in the core. And those changes usually require throughout testing and
integration with the rest of the code. Or probably they are beefing up the
routing capabilities in Renoise, which I imagine also require well thought out
design and implementation. Same with the popular “piano roll” wish, mapping notes
between the pattern data to/from piano roll does not seem to be trivial at
first glance for me. What about all those nice effect commands, delay/pan values.
How do effect commands relate to the line the note was on when the note is
moved in the piano roll and so on and on and on.

120

Taking a break. Hopefully forever.

Easily predictable pattern of forum rage.

I don’t want to know, so now I don’t.

Problem solved.

121

Do you always get a e-mail or something when a new renoise version does come out?