If 2.8 beta overlaps The Elder Scrolls V release… I am not sure if I can take it.
it’d be sweet to have the 2.8 api additions be releasd before 2.8 is released
So the Interface, e.g. the I in API, connects to?
Quantum Renoise and a time travelling API!
no. just a “changeslog” or “new api function list”
what the hell is wrong with these weird member infos beneath the names?
and where are my other 4 dots, taktik???
about the release … patience, young ones!
[irony] LoL [/irony]
ok, I see it’s ready when it’s finished.
OTOH why not release a kind of roadmap ?
it has been mentioned elsewhere that any roadmap would put undue pressure on the developers, raise extremely exuberant hopes as to changes between versions, and all that perfectly rational stuff.
the added bonus is that a new version of Renoise is always a glad surprise with lots and lots of new goodies. It’s always a shock when a Beta is announced.
Except this time we’ve been warned to expect little more than bug-fixes.
(We can but hope this is a lie and told just to keep our expectations low and make even more exuberant when it does get announced.)
One never knows. We might get an “interim update with bugfixes” which will then however be in preparation for future, grander updates. you know, magic stuff that would make one believe in the worthiness of the new version being called v3.0. what’s missing from the 1.8 votinglist? 
1.8 voting results were:
- a mixer view (??)
- an arranger view (visually arrange patternsequences and blocks) (??)
- audio recording in the sample editor
- sub-tick timing (??)
- improved instrument (RNI) structure
- a better and bigger disk browser (??)
- more modulation meta devices (??)
- more and more complex midi mappings
- a renoise vst plug
- a piano roll view
- renoise as rewire slave
- directx plugins support (windows) (??)
- renoise as rewire master
- audio-units support (mac)
good arguments. And yeah … it’s always a surprise
what is meant with this?
i would hope some sort of a Logic Environment on steroids. (Arpeggiator, note-Transformer, Delay Line, being able to press one key on the pckeyboard and toggle 9 Instruments instead of only 1, etc…) but with API functions.
who knows!
But Jonas, overall, would you agree with the strikethroughs? I put a (??) on the bits that I’m not sure would generally be agreed upon as a development response to the 1.8 voting.?
Yeah, I agree to that. Why do we have to break all the plugins in beta all the time?
Except, as far as I know this time around the API doesn’t have too many breaking changes.
Think so, other than direct-x plugins implementation which has become irrelevant through the years (imo), most old wishes can be checked, although always improved upon further / never-ending story .
I hope 2.8 isn’t just bug fixes, it is taking long enough and i won’t be buying an upgrade at v3 unless it has something spectacular, so these are my last few updates, so i hope they have something nice
Can’t have taken this long just to do bug fixes surely ?
I think the release of 2.7 was at the end of June or July(?), summer vacation in between and it really hasn’t been that long, no?
Personally I wouldn’t mind. Of course it would be sweet if there’s something new and exciting, but it would certainly be enough for me, if the update would be just making the existing functionality more robust or more fluid workflow-wise.
The background here is that I’m working every single workday on a major CAD-software that adds more ‘exciting’ features on every update, and these new features are almost always crippled or nonfunctional until hotfixes, which may or may not come. And adding new features while leaving old functionality non-functional really is a bitch…
I play a game (which shall remain nameless) that seems to follow that process too, and it is very annoying. Always more hyped features, always more content, but fundamental bugs are left unfixed for years (and the new features and content introduce additional ones too).
The Renoise development model is how software should be done.