There you go ! I approve this message !
I’ve just downloaded 3b1 last night and I am really impressed! There are a few bugs here and there but nothing that has stopped me yet!
DSP chains in the instrument! Great move! Until now, I’ve had to save my instrument and DSP chains in a folder together.
The new 0YXX effect! I can’t go back to version 2 just because of this one feature! But can I get 0Y in a track group affecting all the contained tracks please?
Patterns! Woo! I have big plans to write whole songs in a single instrument with patterns, just like the multis on VA synths. I sense something great coming!
Macros! This is such an awesome idea! Very useful way to make a complex instrument easy to manage!
There’s some GUI clean up to do and maybe some usability kinks to be worked out but all in all, unless I get some really nasty crashes, I’m not going back to 2.
Thanks for all the great work! I just started using Renoise this year! Why didn’t I get here sooner! B-)
If this is your opinion, you plainly either have no clue how groundbreaking the features they’ve just added truly are, or you just don’t care for the way Renoise works in the first place. The instrument has been completely rehauled to add a shit-tonne of features that MANY of the users on these forums have been requesting for YEARS. Instrument phrases, per-sample effect chains, a complete rehaul of the envelope system to make it entirely modular… these functions alone are huge, and a substantial refactoring of Renoise’s code base. Just because you chalk them up to “a few GUI changes”, doesn’t make them any less powerful… they’re going to completely change how music is made with Renoise.
Cheers to the devs for actually listening to the userbase and adding the features we need to take our composing to the next level
I, for one, am totally and utterly blown away by how awesome this release is, and how on-point the Renoise team has been, consistently, through every release thus-far. I never in a million years thought that what started out to be a cool FT2-style tracker for windows would wind up being this robust, fully functional music workstation. Thank you taktik, phazze, pulsar, martinal, simon, kRAkEn/gORe, sharevari and dblue for working so damned hard to make Renoise the best DAW I’ve ever used.
RENOISE 4 LIFE.
Hear hear!
The new features do not disappoint!
I feel like it has totally been worth the wait and I cannot wait to see how the new features evolve/develop in future releases!
Haters gonna hate. This shit is mindblowing.
Indeed. Even though we don’t have every single feature we want yet, the evolution of Renoise is right on track.
Wait for Bitwig Studio or use Ableton Live. Otherwise pretty all DAW’s out there are based on audio/midi tracks. I personally use Reaper, since it’s lightweight, super-versatile + high performance, great WAV arranging features + handling, really cheap and can be run from USB stick.
I think it really depends on what you expect Renoise to be or Renoise to become. For a lot of people things like live performace options are obviously much more important than e.g. traditional mixing and recording features. It seems that the creative “instrument”-flavor is more important than the DAW-flavor. I personally understand what you mean, I feel similar, but since this release I think it’s clear for me that Renoise probably won’t become what I hoped for. So I will use Renoise in the future primarily as sound design engine / flexible phrase editor, which I will insert as plugin into Reaper. Things like recording, mixing, mastering, arranging will be done in Reaper. It really rocks in this areas.
Heck yeah my man, agree 108%!!! 
As someone who has always been more of a “casual” music maker (even if I might use a program daily for hours and have hundreds of completed things) and never gone too deep into the structure of the programs because I’ve never felt my style of music required it (LOL, what’s an LFO?): I don’t understand this update at all or what, if anything, I can do with it. Don’t take that as an insult; I’m the same type of user that never used Hydra or automation or most of those types of features before anyway. For me it will take some time to get used to the new GUI.
I appreciate the hard work the devs have put into this program and the dedication they have to this project after so many years. Thanks a lot!
An LFO is a Low Frequency Oscillator…
Well, at the very least, there are some clearly marked, and very cool new native fx. The update, has a lot of deep things for power users, but on the hobby side the GUI has been matured beautifully, the instrument has evolved to become a more refined sampler, and since phrases are the basic building blocks of all modern musical compositions to get in there and be able to transpose them throughout your tracks is an extremely powerful new function.
So, those are the big things you want to look at, and clearly there is so much more. I think it will take a good 6 months of working with the new version to see everything.
Think of Instrument Phrases like arpeggios. Really kick-ass arpeggios… that can do more than most arpeggios. They allow you to define entire melodies or drum patterns inside the instrument itself… so you can trigger them with a single note. You can also pitch the melodies by changing the note you’re using to trigger them. You can also create arpeggios that are faster than the song’s LPB (line per beat) … meaning you no longer need to have super-huge patterns for a song that contains complex/fast patterns… just encode them into phrases and you can have a simple looking pattern filled with hidden complexities.
Sample based instruments can how have (multiple) effect chains attached to the instrument itself… where in the past effect chains could only be applied to channels. This particularly kicks ass for percussion because now you can have an entire kit that has different effects on each sample that are all layed out on one channel … previously I’d often need like 5 channels per drum pattern.
Those are the two biggest ones for regular users IMHO
Agreed, AudioMulch is an amazing piece of software especially for freeform improvisation, ambient and similar genres. It has a very slooooooooow development, though. As a hobbyist, I have been running AM for the last year, and will most likely not upgrade my Renoise 1.8 license, as this update unfortunately goes in the opposite direction of what I would like. But huge thanks to taktik and all the developers for the many years of fun with this great program!
Some comments on attempting to run the new Renoise. (tl;dr: it screwed up some tools for use with 2.8 and then failed to run anyway)
I hoped to be able to run Renoise 3 alongside my current Renoise (2.8.2) while evaluating the differences and compatibility.
What I wanted to avoid was a being forced to update everything and running into possible issues because of that.
I edited install.sh and renamed the binary to renoise3, and thought I caught everything to ensure the new version would not stomp my 2.8 install.
This was not the case.
When I ran renoise3 it started up and then announced that it was going to update all of my tools. No prompt, no option to decline. It just told me it was doing it and then did it.
Some tools did not pass the update (rubberband, for example).
Then, after the forced tool update, I got some errors
Failed to initialize MIDI actions. MIDI mapping actions will not be available. Please try reinstalling the application.
no static 'UPPER_FRAME_DISK_BROWSER' in class 'ApplicationWindow'
stack traceback:
[C]: ?
GlobalMidiActions.lua:1965: in main chunk
and
An error occurred while launching the application:
'Failed to load the resource file: '/home/james/bin/Resources/Skin/Icons/Transport_AutoVolume.bmp'.
Please reinstall the application using the latest installer from http://www.renoise.com/demo !'
Please report this problem by sending a mail with the Log.txt,
a detailed description of the error and your system configuration to: <bug><br>```
<br>
<br>
And that was it. The program exited. <br>
<br>
I tried running renoise 2.8.2, and it came up, but complained about some of my tools being meant for more recent version of Renoise; these were now not loading. <br>
<br>
Any major-version update of a program should install into a clean location and not forcible update existing files and tools, since (as we see) such updating might not go so well. Users would be better served with the option to migrate over their existing files to the new version without losing the use of them with the earlier version.<br>
<br>
In the meantime I think I can restore the broken tools from another Renoise 2.8 install on another box. <br>
<br>
I may then make a full backup of my Renoise installation and try to re-edit the install script to properly install into a distinct clean location where it won't forcible alter any of my 2.8 stuff.<br>
<br>
<br>
Also, the update notifier for Renoise 2.8.2 popped up earlier and told me there was a new version, the 3.0 beta. <br>
<br>
Having that popup suggest people update to [i]beta[/i] software is a really bad idea.<br>
<br>
Edit: Oh the irony. Just noticed that among the tools broken by the failed install of Renoise 3 are ToolUpdater and UpdateChecker.</bug>I think this version actually makes it easier for casual users because it is better at sharing content e.g. Doofers and the new Instruments/content libraries. You can just use what others have created without really needing to go under the hood.
Please let’s talk about such things in “Help and Support”, then others with the same problem can find such info more easily.
The installer got broken with this change. You can install multiple Renoise version side by side already without modifying the install scripts: the only thing that gets overwritten when installing a new version on top of another version is the main “renoise” link in /usr/local/bin. It will always point to the most recently installed renoise version. It’s a link only. The real installed binaries are at /usr/local/bin/renoise-$RENOISE_VERSION, so you can also start the version of your choice by launching e.g. “renoise-3.0.0” directly.
Please try uninstalling everything again, then install 2.8.1 and then 3.0.0 again. Without the changes to the install script.
Are you speaking about native effects per sample , or are vst effects also possible .?
dude, why are you not checking it out for yourself? Of course vst effects are possible 
VSTs are allowed in the sample instrument effect chains 
… additionally, you can set up many different effect chains and assign them differently to each sample in the instrument
So the effect per sample are native effects then …
Ah I will see in a few days time …
Phrase is acid on steroids…