When 2.8 ????

Bear in mind that most people using Win7 have a serious issue with the Caps Lock key, which it seems may be down to using the depreciated DirectInput method for taking keyboard input, that if this has been fixed it will only be a minor bug-fix on the surface but a lot of work under the cover and a godsend for a lot of people!

But it is only conjecture on my part that they have managed to do something about this problem. Maybe we’ll have to wait for a 64bit Windows version with a 32bit VST-Bridge. Maybe that is what we have… (Although not going to hope too strongly.)

Next official release will be a maintenance update, so yeah, bugfixes, but not 2.8.

awesome. does the addition of autofade into the api count as a bugfix? :)

So that could mean the next update after the maintenance update won’t be 2.8? Rather 3.0?

Ahhh. Just when I thought the speculation was over. The sweet tingling of doubt. :)

Maybe it’s important to first give a “final 2.7.x version” and lock 2.7 development to that, and then start/continue the extensive testing of a possible eventual Beta RCx of Vx.x or Vx.x.x

one never knows

I was more thinking about the time spent on version > 2.7. I guess besides fixing bugs there are some bigger features in development. And when they get released it won’t be 2.8 after that long period.
But I know that speculations concerning updates, new features and version numbers are practically worthless here :D

Though all of it is still very intriguing. I have my licence since 1.9 so why I’m worried is that I’d be happy to have one more new beta at least. :unsure:

stability first is a good thing ! IMO it’s the most important feature at all.
Though I hadn’t many problems with 2.7 so far.

Everybody wants to know when they will release the 2.8 because everybody is curious to see what will be the next features in it.

I think that the devteam has allready said that Renoise 2.7 introduced several new features, that will be improved in future versions.

So let’s have a look in the more recent features.

Since the EQs are always improved the EQ bands and Q should be 100% fully automatable now.

And for example Renoise 2.8 will improve the multilayer instruments logic in some way… the sample keyzones will be improved, with the ability to zoom vertically in it ; a multilayered instrument could allow something like a round robin sample playback selection, or something “humanized”.

It’s possible that we’ll get envelopes per samples instead of envelopes per instruments directly in the 2.8 release, otherwise it should be ready for the 2.9 one.

The instruments envelopes should be improved, for example, a better pitch envelope definition, and maybe, an integrated arpeggiator.

The automation envelopes have been improved but some DSPs and Instruments still have limited envelopes so we can probably expect something that should make all envelopes look better and behave exactly the same in the GUI.

The Phase meter will be “coherent” and more usable.

The beat slicer will probably be improved, and moving slices will probably also “move” (timestretch) audio data on the fly.

They said that lots of bugs we noticed in the actual release have been fixed. So we can expect an improved multiband send device for example.

Same thing for the bunch of VSTs and VSTis troubles that have been tested and fixed during the last Renoise version.

The highly alpha stage of the *Formula device will end, the highly beta phase will start.

The GUI will allow a selection of more customized fonts for the pattern and more renoise logos in the upper-right corner.

The GUI will allow to have curtomize the background track color instead of a top track color for those who need to group/organize their setups.

Concerning the new DSPs/FX that would come in addition to the previously ones, I don’t know why but I expect something totally unpredictable… like… like a basic 3D binaural “emulation”. And concerning the new meta devices, thay will probably deal with real time “spectral” analysis.

MIDI controls recognition and assignment will be improved as usual.

A new “community radio” will be introduced, and renoise users will be able to play a random selection of xrns tracks (sorted by genre) that license owners will be able to upload in their backstage section.

yeah, but what is new in 2.8 is probably that the developers have designed renoise as a game

remember those upgrades of the castle in the old sid meier’s civilization games? you get a new fence, a new window, a wall of stone instead of a wall of wood, or whatever

so now you need to spend some time with the tracker to unlock the new features, or to be exact you need to script the keys to unlock the features

so mxb will unlock 150% of the features in his renoise version while i will unlock 2% in my renoise version :)

I don’t kid around about the official updates. Besides, maintenance updates don’t come with any new extra’s. (Well except for the few lacking API calls that definately should have been in there)

We can send note data to VSTfx with alias instruments, but we still can’t send audio to VSTi…

;)

I imagine this could work with a new type of send device for the DSP chain, where you select a VSTi instead of a track, and you’d probably have to assign the VSTi to a single (different, and not previous) track, right?

Can it be done?

I’ve still never heard what the vocoder in Arguru Voyager sounds like because I can’t bear to use anything else other than Renoise :)

no collapsible channel groups? :(

Awesome! Cant wait to see some missing API functionalities added :)

I’m sure collapsible channel groups will be in 2.9! I think so!

Insert guru as an effect ( might want to change the dll suffix to vst.fx )

So, when 2.9?

Click to view contents

Wat?

I really wish the next version of renoise would be called “Ganymede”, or “Europa”, or simply “Ed”. ;)

We could do different animals like OSX does, leopard, snow leopard, lion, etc… But I guess it would have to be something nerdy because Renoise is ultra-nerdcore…