Forum

Hi

I’m using renoise as sequencer and for midi cc on a lot of external synths.

I might be wrong, but I do beleive I am experiencing some inconvenient midi cc behavior.

I use the *Instr Midi Control for all CC’s.

When i load a project/song into renoise, the midi CC is initially not send to the synths. And if I mute tracks, the are not send at all, I believe? I have to fiddle with the CC settings in the

Is it possible, the initiate all midi cc states immediately after loading a song?

I ususally have a lot tracks muted on load, since I will unmute thos along the track is playing in my live set up. Usually only one 64 pattern long song, with a lot mute on/off.

Does this make sense at all?

1 post - 1 participant

Read full topic

This cinematic soundtrack is part of a commercial project which works as background music.
Intensity and melodics build up towards the end
I am not entirely happy with the arrangement but you have to finish something at the end of the day.

9 posts - 1 participant

Read full topic

#WTFFB

1 post - 1 participant

Read full topic

I have started this topic to discuss Glitch [dot] cool of which i am a co-founder…
Glitch[dot]cool is a collective of producers, sound designers, programmers, and visual artists orbiting the glitch aesthetic, founded in 2019.
we are a collectively operated publishing platform, releasing sample packs, albums, and educational content.
we seek to promote and encourage the development of burgeoning fields at the intersection of technology and the arts.
we also run a large discord server with an active community of audiovisual creatives and a focus on education, collaboration, and camaraderie.

Glitch [dot] cool is not exclusively renoise based, it includes some users such as myself and I think it may be a good resource and something some of you may be interested in.

Website: https://www.glitch.cool/
Discord: https://discord.gg/rF8zf2x9 [this link may expire, please message me or reply here for an invite]

2 posts - 2 participants

Read full topic

Testing this in the terminal I find that the VST3 names appear as long numbers. Only occurs with VST3 names.

rprint(renoise.song().selected_instrument.plugin_properties.available_plugins)

... [29] => Audio/Generators/VST/Piano V2 [30] => Audio/Generators/VST/TAL-BassLine-101-64 [31] => Audio/Generators/VST3/4172747541564953416C617650726F63 [32] => Audio/Generators/VST3/41727475415649534B61743150726F63 ...

At least I know the first one should be called something like this:

[31] => Audio/Generators/VST3/Analog Lab V

This happens at least with Arturia plugins. But I suspect it will happen with any VST3 name.

1 post - 1 participant

Read full topic

Considering VST3 is now a thing in Renoise, this would be an interesting feature for a “off the shelf/it just works” approach. Typically a doofer is self-contained “block box” FX DSP. You can definitely control parameters from an input perspective but it doesn’t have outputs. The reasoning is because the internal DSPs only see themselves and nothing outside of the doofer. An rather unorthodox example of a doffer that can have a signal generator.

My suggestion would be to have a built in output DSP for the doffer. From the example above the hydra hooking parameters can latch to something.

1 post - 1 participant

Read full topic

If you setup this, the post level meter stays at zero all the time:

If you now add another disabled send device after the first send device, you suddenly get a level meter peak:

Also if you now swap the send devices, there is a level meter peak:

Is this a bug, or am I missing anything? Would be nice, if the level meter peak was working always!

1 post - 1 participant

Read full topic

I’ve been playing around with using Renoise to control some external synths (MB6582, Virus Classic, some others). I kinda wanted a “tracker” sound and to try using Renoise as my primary method of writing songs instead of Ableton.

I was definitely able to get a tracker vibe on the MB6582 by adjusting the filter on notes, but started to run into a bit of a snag - I couldn’t figure out a way to send more than one CC via the pattern data. That’s something you can do in a DAW and, I think, can do in Renoise with some automation?

I just wanted to make sure I am indeed correct that I can only change one CC per row per channel?

EDIT: Docs I am referencing are here: https://tutorials.renoise.com/wiki/Effect_Commands

2 posts - 2 participants

Read full topic

This was brought to my attention on the Discord server because I was a little befuddled by something not so trivial and kind of annoying: automating BPM through a whole song. Typically you can automate the BPM off the master track.

Pretty easy stuff, but try doing this for multiple patterns with the line tool spanning through the whole song where you want to accurately pinpoint BPMs between 120 to 170.

Not easy or elegant, more so not even accurate. You simply can’t tell what BPM you’re hitting at. You could argue: “I can adjust each point appropriately as need be” but that’s tedious work.

I determined the easiest to go about this is using a Hydra on the master track where you attach to the BPM parameter of the Mixer and Transport DSP. From there you can define the min and max of the curve so you don’t over shoot or undershoot by accident.

1 post - 1 participant

Read full topic

for those who don’t know sully is a uk producer , started with dubstep and for the last few years makes awesome jungle tunes (my favorite for some time , really kickass style and approach)
heres an interview + xrns made with renoise 3.2
enjoy

Native Instruments Blog – 10 Sep 20 Jungle revivalist Sully sketches out haunting atmospherics – at 168 BPM

From his base in the small English city of Norwich, Sully has become known as one of the most formidable talents in modern jungle. Originally emerging from the hazy territory between dark garage, dubstep and grime, Jack Stevens tightened his focus to...

1 post - 1 participant

Read full topic

Makes all sorts of video game sounds AND if you know your synthesis, all sorts of tones for the sampler. Export to .WAV, but you will probably have to put ‘.wav’ at the end of the exported file.

itch.io ChipTone by SFBGames

Free game sound effects tool

1 post - 1 participant

Read full topic

The marvelous rc808 drummachine is not showing up , it is located in the correct folder
Program files/commonfiles/vst 3 on a win 10 machine

2 posts - 1 participant

Read full topic

(Renoise and Redux) New #Sidechain device

A nice trick with the new Sidechain device is to route it to melda MRatio’s sidechain and you can create a local send out of a normal track. mRatio allows you to hear its sidechain signal and blend it with the main signal.

Basically turn the Ratio control all the way to 100% to get full SC signal passing through. You can then use the Amount slider on the SC Device as you would on a normal a Send Device.

• https://www.meldaproduction.com/MRatio

1 post - 1 participant

Read full topic

R3.3.0 Win10 x64

Device: Signal Follower device
First parameter: Dest. Track. The current .value_min returned is 0. But it must be -1.

It should be able to reach the value of the parameter: CT.

Note: this can also conflict with .default_value, which returns -1.

Related Doc

renoise.song().tracks[].devices[].parameters[].value_min
-> [read-only, number]

renoise.song().instruments[].sample_device_chains[].devices[].parameters[].value_min
-> [read-only, number]

The same happens with parameters 2 and 3: Dest. Effect and Dest. Parameter.

1 post - 1 participant

Read full topic

1 post - 1 participant

Read full topic

As per title:

• Launch Renoise 3.3
• Scans for plugins
• Hits Waves Shell 9.92 x64 VST3.
• Sits there using more and more memory until it runs out

Renoise may be incorrectly detecting it as a 32 bit plugin, as it scans the plugin twice, once with ->32 bit appended. (it’s NOT the 32 bit Waves Shell).

Last lines of log file:

Audio Plugins: Searching for VST3 plugins in 'C:\Program Files\Common Files\VST3\' Vst3Plugs: Instantiating: C:\Program Files\Common Files\VST3\WaveShell1-VST3 9.92_x64.vst3... Vst3Plugs: Instantiating: C:\Program Files\Common Files\VST3\WaveShell1-VST3 9.92_x64.vst3... Vst3Plugs: Failed to suggest speaker arrangement (not critical) Vst3Plugs: Releasing: Waves: C1 comp-sc Mono... Vst3Plugs: Instantiating: C:\Program Files\Common Files\VST3\WaveShell1-VST3 9.92_x64.vst3... Vst3Plugs: Releasing: Waves: C1 comp-sc Stereo... Vst3Plugs: Instantiating: C:\Program Files\Common Files\VST3\WaveShell1-VST3 9.92_x64.vst3... Vst3Plugs: Failed to suggest speaker arrangement (not critical)

3 posts - 2 participants

Read full topic

[Edit: originally noticed with Reason 11 but it’s apparent for other VST3 plugins also]

Description:

I’ve just installed Renoise 3.3 and several VST3 instruments/effects (including: Reason 11, Dexed, and Ozone9 Elements) aren’t appearing in VST instruments nor effects.

Steps to reproduce:

1. Go to plugin view (or DSP pane)
2. Open list of instruments (or DSP effects)
3. Search for Reason/Dexed/Ozone

Expected results:

Listed VST3 plugins appear.

Actual results:

Listed VST3 plugins VST3 plugins do not appear.

Extras:

Due diligence:

• confirmed VSTs in correct directory
• rescanned VST directory
• removed/re-added VST directory
• ensured that Enable VST3 plugins is ticked
• tested that instruments/effects work in another DAW (Reaper)
• definitely in Renoise 3.3 (just in case)

Possibly useful:

• after re-scanning, status bar indicates “Found ‘1’ VST3 effects and ‘0’ VST instruments”
• the detected VST3 effect is Izotope Vocal Doubler

1 post - 1 participant

Read full topic

did some breakcore after 3 years

1 post - 1 participant

Read full topic

Download

• Registered users can download the update at the Renoise Backstage
• Demo versions are going to be uploaded later today.

What’s new

In summary:

• VST3 plugin support
• Audio Sidechain support for VST2/3 and AU plugins and for some native Renoise FX devices
• a few little other tweaks and fixes

In detail:

• (Renoise only) VST3 support: The VST2 protocol was deprecated by Steinberg a while ago and replaced with the VST3 protocol. More and more plugins will be available in the new VST3 format only.
  VST3 support is by default enabled on Windows and Linux. On OSX it can be enabled in the Renoise Plugin/Misc preferences. Feature-wise, VST3 behaves similar to VST2, but sidechaining is a lot easier to realize in VST3 (see below) and external VST3 editors can more easily be resized - when supported by the plugin.

• (Renoise and Redux) New #Sidechain device (in the Native/Routing sections in Renoise’s Track FX browser), to send audio in tracks or instrument chains to sidechain ports of plugins (VST2/3, AU) and the following native devices: Compressor, Bus Compressor, Gate.
  Please note that the sidechain support in VST2s is a bit wonky: The VST2 protocol never had an official way to support side-chains, so the support in hosts and plugins is problematic. The VST3 protocol simplifies this, so it’s preferred to use a VST3 version of a plugin, if available, for side-chaining.

• (Renoise, Linux only): Timing fixes for ALSA MIDI: previous version of Renoise may not have applied note delays in MIDI events correctly.

• (Renoise and Redux) Alt-Tabbing to Renoise sometimes could have frozen the Renoise GUI for a few seconds when a lot of sub folders were visible in the Renoise Disk Browser.

• (Renoise and Redux, Linux only): Use XDG_CONFIG_HOME and XDG_DATA_HOME paths on Linux (defaulting to “~/.config/Renoise” and “~/.local/share/Renoise”) to get rid of the Renoise folder in your home directory. The old “~/.renoise” and “~/Renoise” folders are symlinked to the new paths, so older versions of Renoise, when installed, can still use the old paths. If you don’t have older versions of Renoise installed you can remove them.

• (Renoise and Redux) Various compatibility tweaks and fixes for OSX - but most of them got released in the Renoise 3.2 bug fix updates already: All builds are notarized now, a few drawing fixes for OSX Big Sur, replaced Renoise’s “custom” full screen mode with the standard OSX’ full screen mode for better compatibility in newer versions of OSX.

• (Renoise only) Lua API changes (new API version is 6.1 - this is a minor, fully backwards compatible update - so all old tools will auto-upgrade). See here for the complete list of changes.

A big thanks for the alpha and beta tester crews who helped to make this happen.

Happy tracking!

4 posts - 4 participants

Read full topic

Hi,

I’m new here and I could not find anything about external soundcard problems. When I start renoise i get the error:
Failed to initialize audio buffers for device ‘primary sound device’. When I try to change it to M-Audio in the preferences I get another error: Failed to initialize audio buffers for device M-Audio… Audio is disabled. I run win10.

Thanks.

Edit: No problems with other software, only renoise.

1 post - 1 participant

Read full topic