What feature are you hoping for in upcoming Renoise releases?

The removal of all forms of numbering and lettering input from the software i.e no hex numbers, no note numbers, no letters, all information must be input in a series of highly specific dots and dashes sequences that require extreme precision with 0% margin of error otherwise your song won’t play at all.

Removal all vst support, only renoise stock devices. Plus they all get hidden in the depreciated effects folder every time you start up the software, so you gotta go find them every time to load them up to just to be able to use them. Oh and they all have a 30 minute time out limiter on them as well, at which point you need to restart the software again to continue using them.

Less tracks, there’s too many. We only need like 3 anyways, I mean come on!! Also groups…what the fucks up with groups? Scrap them to…waste of time!!

A piano roll as well, but it’s right to left instead of left to right and you can’t see the notes you input cause you have to memorize them as you put them in… like a REAL musician would do!!

Get rid of the scopes…I don’t like the squiggly lines and bars and stuff moving all around the place when I’m listening to my synthwave masterpiece, they make me feel nauseous and just hiding them makes me nervous knowing they’re just sitting there in the background still going out of sight. Lose them please.

So in general I think we gotta move awaaaaaaay from user friendliness with the software and get really fucking deep into the whole esoteric experience, I’m talking up to our necks in complexity!! Making music should be hard, like really stupidly hard, like it was always meant to be yaknow!!

Oh and also no more regular updates on future relea… actually no we have that already, nevermind!


As someone still relatively noob-ish, thank you for suggesting so many quality of life improvements.


now you gotta come thru on this…

1 Like

Available on all good streaming platforms soon!! PhotoFunia-1629920029


bahahahahaa :skull:

will buy!

Piano Roll

In case you have missed it. @toimp is working on a totally awesome tool.

Download the Simple Pianoroll tool here
Bow and praise @toimp’s work here

If this video does’nt tickle your senses. You are either a stubborn baby, or a grumpy old fart :wink:


I’m on loop - still hoping for some granular native to the sampler. I have both of the Tools that do single-head granular, now hoping for multi-head granular “built-in”. It’s the pinnacle of sampling! :slightly_smiling_face: whee!

1 Like

Yes. You are on loop :slight_smile:

Granular synthesis is great. But. There are already lots of plugins for this.

1 Like

Just like there are already lots of programs with piano roll editors…

None that can be loaded in Renoise as far as I know

I just won’t use plugins - I know and have purchased many of the granular ones. They all suck enormous resources, and I’m not going to buy another computer for a while. None of my songs currently pull over 15% of my processing power and I’d prefer to remain native to Renoise. Loop-do-loop I go! :grinning_face_with_smiling_eyes:

1 Like

oh what’s the point

good bye

audio rate ish meta devices inside instruments, that’d be cool especially in redux or instead maybe midi routing and side chain and vst support in redux also audio rate ish sample envelopes also tools in redux or instead full rewire support so rewire is a fancier redux (rip rewire btw)


Related to: Midi

  • improved Midi Drag&Drop from VST Instrument:
    • option to pre-determine destination track
    • option to pre-determine destination instrument
    • option to spread the midi data across note-columns, filtered by note value. (every individual note value gets its individual column → especially useful for drums)

Related to: Sidechaining

  • easier setup routine for sidechaining:
    • auto-create sidechain device after right-click drag&drop of sidechain-enabled destination device (e.g. compressor) onto the source track (e.g. kickdrum)
      → the sidechain device is created on the kickdrum track. the receiver track + device are selected in respect to the drag&drop action performed.

Related to: Automation

  • easier setup routine for (instrument) automation:
    • “assign automation” check box is added to the bottom of every VSTi GUI window (where “enable keyboard” and “random” options are located)
      → when enabled, pressing a GUI knob/slider/button in the VSTi GUI will not change the value, but assign the parameter in the Instr. Automation Device on the channel with active keyboard focus. A new Instr. Automation Device will be auto-created. Parameters are assigned from top to bottom / left to right in the Instr. Automation Device consecutively. Already present Automation Devices are being ignored / remain unaltered.
  • an option to keep automation data when moving DSP devices
  • cross-pattern automation with spline curves
  • automatable sample loop start- and end-points
  • ability to temporarily ignore all automation per track (per toggle/switch)

Related to: Effect List

  • drag&drop functionality for organizing favorites in the effect list view.
  • sorting options in the effect list view (alphabetical, most used, last added, by vendor, custom)
  • text- and/or color-based-tagging option for the effect list view
  • effect list remembers the last state of collapsed / uncollapsed tree items


  • ability to show CPU load per VST fx (similar to what we already have for VSTi)
  • ability to show a floating window for all active effects and instruments, sorted by current CPU load (CPU load charts)
  • added option in the preferences: disabled DSP devices / vstfx will no longer be taken into account by PDC ( → e.g. currently disabling a latency-heavy device will not reduce overall latency)
  • “Doofers” for VSTi / a.k.a. Instrument Racks: can load multiple instruments in one single instrument slot for layering purposes. Midi cc effects (e.g. pitchbend / modwheel) will be routed to all inserted instruments. Instr. Automation Device is added with an additional configuration layer: “Sub-Instrument#” (next to Instrument#)
  • LFO Device: “frequency” can go much lower than 1.000 LPC
  • LFO frequency can be set to “hz”
  • option switch to make the Sample-Modulation LFO freerunning
  • added “render pattern selection to sample” option
  • detachable DSP chain + automation views.
  • auto-setup option for audio-routing enabled Instruments (e.g. auto-assign outputs to track x till y)
  • less dependencies in the color settings (e.g. “selection back” currently applies to all selections in sampler and automation, but also pattern cursor location, which is often unfavourable)
  • all of the above will be implemented before even considering the implementation of a piano roll. :wink:

:+1: :stuck_out_tongue_winking_eye:

1 Like

This, but in the current instrument fx context. I have an idea here. instrument number could be selected in device on index 1 (optionally and also midi channel), so in the input device on the left of every dsp lane. The automation device could stay as it is. I think then the API could stay almost same, too…?

A slide random option in LFO

1 Like


  • import data to current track/track you drag to. (pop-up dialog if MIDI contains more than one track)
  • map to current instrument.

Spread the midi data is in the Split into separate tracks tool by @fladd that I tipped you about. However. That tool stopped development in 2016. And there are some desired functionality missing. eg. Does not remember last used settings. Spreads same notes across many columns in a track

Would also be great if MIDI could be imported to a phrase. So Redux users easily could switch between Renoise and different DAWs, without losing the great sampler and tracker functionality. Insentive to create instruments and phrases that works everywhere.

•more assignable macros per instrument: 16, 24, 32
it’s easy to use up the 8 we get!


I hope that in future more and more features will be removed from renoise, so the community will get more opportunities to implement them as lua tools. Over the course of the next releases the core features should eventually be removed bit by bit, until after some releases only a basic lua interpreter is left. The renoise can be made to do anything! Just you have to code it yourself tho…

This also has the benefit to shorten the interval between releases, as it is easier to remove functionalities than to implement new ones, also bug fixing can reach a new dimension - if a feature has bugs, it is much easier to just remove the feature than growing old over trying to fix the damn bug.

1 Like