7893 
Importing DSP effect presets from Renoise 3.1 should work now
Log in to the Renoise backstage to download your copy*
https://backstage.renoise.com/
*The release is currently available to registered users only - demo version will arrive shortly.
Hey danoise,
I just tested out loading / importing DSP effect presets from Renoise 3.1, and that seems to work fine now, awesome!
FYI – not to give you a new headache so soon – but try re-naming anything in the program that can be renamed (FX chain, instrument, anything where you enter text) and see what happens. For me, the new text is shown overlapping the old text up until you hit enter, at which point the new text appears as it should, but it can look very awkward while typing! Thought you should know.
-M
Hey danoise,
I just tested out loading / importing DSP effect presets from Renoise 3.1, and that seems to work fine now, awesome!
FYI – not to give you a new headache so soon – but try re-naming anything in the program that can be renamed (FX chain, instrument, anything where you enter text) and see what happens. For me, the new text is shown overlapping the old text up until you hit enter, at which point the new text appears as it should, but it can look very awkward while typing! Thought you should know.
-M
Same here. 8 macros still 
Why not 256? 16 per page, and 16 buttons, M1-M16 
Just had a crash in Redux GUI after closing the GUI, reproducible almost always after a short time and resizing gui:
VstPlugs: Trying to instantiate '/Library/Audio/Plug-Ins/VST/Renoise_Redux.vst/Contents/MacOS/Redux'...
VstPlugs: Plugin is a Mach-O executable...
VstPlugs: Analyzing VST plugin 'Renoise: Redux', Unique ID:1381123160, Version:2400
VstPlugs: Plugin supports extended string<>parameter conversions
VstPlugs: Instantiate OK
VstPlugs: CreateInstance succeeded
VstPlugs: Opening custom cocoa editor window for plug 'Renoise: Redux'...
VstPlugs: Cocoa Editor window for plug 'Renoise: Redux' was closed
VstPlugs: Opening custom cocoa editor window for plug 'Renoise: Redux'...
VstPlugs: Cocoa Editor window for plug 'Renoise: Redux' was closed
VstPlugs: Opening custom cocoa editor window for plug 'Renoise: Redux'...
VstPlugs: Cocoa Editor window for plug 'Renoise: Redux' was closed
VstPlugs: Caught exception in VSTPlug::Dispatch
Warning Message: Ouch. The VST plugin 'Renoise: Redux (from Renoise)' crashed in VST event/function: 'Dispatch', Thread: 'GUI'
Warning Message: IMPORTANT: This is a fatal error. Please save the current document under a !new! name to prevent losing important data. Renoise will silently ignore any following errors from this plug-in.
Warning Message: DO NOT IGNORE THIS ERROR; DO NOT CONTINUE USING THE PLUGIN. THIS CAN DESTROY YOUR SONG OR CAUSE OTHER RANDOM CRASHES AND PROBLEMS!
Warning Message: It's most likely that this is a bug in the VST plugin, so please report this problem to the authors of this plugin in order to get the problem fixed!
After that message I reloaded Redux, and the resizing was a lot more slow, including black screen while resizing. After reloading Renoise, resizing is back normal.
Steps to reproduce:
Renoise 3.1.1 64bit macos 10.12.6, loading redux
open gui, resize it to a very small size, leave it open for 30 secs
close the gui and reopen it
resize it to maximum size
close the gui
if it is not crashing, repeat the steps
Thank you.
Will you publish a bugfix 1.02-fixed version soon, or will you leave us with this unstable release for the next two years? Because then, I will revert back to 1.01.
BTW. I am pretty sure after reading lots about vst instabilities that targeting a very old macos SDK can be the cause for memory leaks and instabilities in vsts. A simple SDK upgrade seemed to improve the stability for a bunch of get vendors. Maybe it is time to set the minimum requirement to 10.11?
Will you publish a bugfix 1.02-fixed version soon
You mean, with regard to the problem you reported just above?
It’s very specific, dealing with sequence of opening windows - reverting would most likely not solve it.
But fixing it would 
As for memory leaks, I don’t know of such problems in Redux.
We will surely continue the support for older OS versions for as long as it doesn’t affect the stability of the software itself.
Ok that makes sense.
But: I think you safely can assume that nobody on this planet still uses 10.5, 10.6 or 10.7. or even 10.8. 10.9 is pretty old but was a very stable version. What about targeting 10.9 then?
The above bug can happen any time while working with the redux window. I think it was not about a sequence of actions, but about simple resizing, triggering some memory leak or so,
Cheers for the update Danoise 
Has the text issue been confirmed, danoise? I assume it’s not just happening to me… it’s pretty annoying as it makes it impossible to see what you’re typing until after you’ve entered it.
another issue: when assigning macros, the macro assignment pop-up disappears (or loses focus, mostly likely, e.g. “goes behind” the redux window) the second that I select a macro destination, which is not the behavior in Renoise. It’s annoying, because it disappears before I’ve had a chance to adjust the min/max values, so I have to click the macro assign button again to get it to re-appear.
-M