Is it me or does loading a VST take way longer than before?
I have to wait for about 15 seconds now while in 2.8 it loaded in a second or two.
Maybe it is placebo, or psychologically…but I feel similar lag when closing or loading a new track. Seems to take longer maybe due to vst(i) handling? Someone with 2.8 still installed please test 
It only keeps me waiting in the first few minutes of starting Renoise. After a little while everything starts up in a second again it seems.
I think it does feel slightly longer but I’m assuming it’s because in R3 the vst interface is automatically opened once the plugin has been loaded. In R 2.x you would load the vst into Renoise and then have to open up it’s own interface manually (a good example of this is Sugar Bytes Cyclop - there is a very noticeable lag when trying to open the interface after the plugin has been loaded into Renoise). It’s hard to test the loading speeds between 2.x and 3 because once you’ve loaded a vst up in one it retains it in the other so will always load quickly the second time around. I guess I could test it with a reboot but I’m feeling lazy.
yes plugin loading is noticeable slower, but sample rendering is almost instant!
Are there release notes for each of the betas? What’s different in b3 from b2? http://www.renoise.com/release-notes/300 is a high level overview. I guess what I’m looking for is more of a change log than release notes?
Only bugs are fixed between the beta’s right now. No new things added or removed. 
Ah cool. Yeah I asked about a bug with midi import crashing it and they said it would be in the next one…I guess they mean b4.
good day to start Renoise 3.0 
awesome version im POWERFULL HAPPY with all the new features… awesome … wow
only one thing phrase lenght maybe visible in the pattern…
Its interesting, switching 2.8.1 to 3.0.0 workflows.
Just a couple of days before beta release, I figure, ok this is a pretty decent workflow.
Now its about transition, how can the old and new come together as one.
My favorite thing about the beta so far is that I am relieved of this “having to finish songs”.
Its an interesting workflow/genre, this weird non genre, this no song.
Technically speaking, the important parts of composition and production can be exported,
its just a matter of organizing the accumulated “Content Library”.
I imagine this can be both useful both for live and collaborative efforts.
Exactly, like a visible block in the background of the pattern, showing length / repeat points (until other note or phrase triggered)
+1 (on which pattern zooming could be applied?)
Though what if there ever be automatable lbp or bpm in phrase? Then it be hard to estimate the length of a phrase, especially if controlled through lfo? Of course, this is all fantasy 
Because to my knowledge there is no proper cross-platform instrument format/sampler available as VSTi. Renoise is cross-platform, however. So not all Renoise users actually can use something like Kontakt.
Redux will be popular for those who want the renoise experience in their linear daw …
Will it atract new users …hell no …
It’s really a smart from the dev’s …We renoise users are just betatesting redux …
Love renoise …but I think there’s a reason why some of the longtime users left …or to say it mildly …are not so impressed with 3.0 …
When you’re trying to think about the way some “realistic virtual instruments” are done, you understand that they’re build with the help of multiple layered samples, that are post-processed with internal dsp fx chains. Some famous VSTis, not only Kontakt, but also, for example the fabulous “reFX Nexus”, are based on this principle. And you can’t say that Renoise goes in the wrong way with this release, because everything that truely works nowadays, (i.e. that people are ready to buy - or sell ) - are banks of cool realistic, rich, and evolving instruments usefull for making the quality music you want. Allowing Renoise - Redux to go in this ground is logical and I’d say, necessary.
Saying that, the .xrni instruments have always been limited, because if they where multi-layered, they could NOT be “modulated” and they didn’t contained any DSP fx… So that’s what changed yiou realized it. And now we’ve got something in our hands that will in a near future allow us to work with something truely realistic, easy to modulate, and also easy to use for newcomers. Think about newbies. They are in the market like everybody. They want to use cool instruments but they’re not hardcore digital muzakers that will use more that one or two knobs. And in the end they make their decisions because of some little details like simplicity, efficiency. And don’t ask you why they simply ignored for now the renoise instruments. Because of the messy GUI !
For example : in Renoise 2.8.1 the “Instruments settings” horizontal tab, was truely confusing, small, but with side pannels hiding some important informations, with 3 different sections (SAMPLES, PLUGINS, EXT MIDI ), but visually, the sample editor was somewhere else, and the keyzones were somewhere else in another tab. And honnestly the result of this, is sad but true : it wasn’t clear, especially for newbies, that finally ignored the “instrument concept”. They often told me that renoise instruments looked far too complicated for them ; some still don’t understand clearly, the difference between “samples” and “instruments”… Don’t ask yourself why lots of user simply ignored the power of “renoise instruments” last years, this is because the messy tabs on the bottom of the old GUI.
Saying that let’s recognise that Redux has “helped” the devteam to re-organise and clarify the “instrument” concept in Renoise, and it probably helped the devteam to get visually, the best possible editing panels for it. And I guess that creating a new “'sampler” tab on the top of the software GUI, that correctly associates the samples lists, the sample editor, they keyzones, the modulations and the post DSP fx chains in a logical way, will also push some people to go deeper and discover the full power of it.
So, in the end, I see Redux as the last step in a bigger process of
(1) grabbing the best existing plugins - remember the “plugin grabber” ?
(2) tweaking the grabbed plugins and making them fully .xrni compatible
(3) exporting .xrnis to “Redux banks” or Redux based VSTis
(4) selling it at a low price (compared to other solutions)
(5) allowing more people to enjoy quality instruments but with “competitive prices”
Isn’t it a game changer ?
Is any one else imagining Redux to be a bit like Xfer’s Nerve, but with a tracker sequencer?
http://www.xferrecords.com/products/nerve
That would be awesome.Or is it just going to be a up straight sampler? Cos then I don’t really see the point…
Nerve looks like it will do a lot less than Redux will do even if Redux would not have the phrase sequencer.
They have a lot of nerves to ask so much money for that though.
that will be a mini renoise then - so we can use it in bitwig…
vV: Nerve is absolutelly great and inspirational, trust mue.
NI finally has Linux versions!!! That’s awesome news! Gotta check that out immediately…