Forum

1 post - 1 participant

Read full topic

I’ve encountered several crashing plugins with Renoise 3.3 in the last few days, very few of the crashed ones are VST3 plugins though. I can’t replicate the crashes but it happens way more often than with Renoise 3.2.4 and they’re not the typical crash prone plugins that I got used to crashing every now and then but plugins that have pretty much never (or very rarely) crashed before even when I’ve used them for years.

Most often it happens right after render to disk, sometimes in playback, sometimes when idle. Sometimes Renoise just disappears on its own or disappears after clicking ok on the fatal error popup.

My CPU is Ryzen 2600X, motherboard Asus B450 Prime Plus, 32 gigs of ram, 2x AMD R9 280X’s in crossfire mode (one display), three SSD’s, two HDDs, Behringer UMC204HD audio interface in a USB 3.1 Gen 2 port. running at 24bit/96khz, Windows 10 Pro with all the latest updates and drivers. Akai MPK49 Midi Keyboard connected with USB.

Warning Message: Ouch. The VST plugin ‘Best Service: Engine 2 (from Best Service)’ crashed in VST event/function: ‘Dispatch’, Thread: ‘GUI’

Warning Message: Ouch. The VST plugin ‘Best Service: Engine 2 (from Best Service)’ crashed in VST event/function: ‘Dispatch’, Thread: ‘GUI’

VstPlugs: Plugin ‘Native Instruments GmbH: Kontakt’ crashed in its audio process function!

Warning Message: Ouch. The VST plugin ‘Native Instruments GmbH: Kontakt (from Native Instruments GmbH)’ crashed in VST event/function: ‘Process’, Thread: ‘AUDIO Slaves’

these are the only mentions of crashes in the logfile, even though there have been tens of crashes. Other crashing plugins have been Waves VST3 plugins (IR1, IR-L, H-Reverb), Izotope Ozone 9 Advanced, and VST plugins such as UVI Workstation, EastWest Play, Scaler 2. Most often it has however been the usually very stable trio of Native Instruments Kontakt 6.4.2, Best Service Engine 2.7 and UVI Workstation 3.0.16. The two former ones crash spectacularly with warning popups, the UVI crashes silently only showing a red rim inside the plugin around the loaded instrument and just doesn’t produce any audio.

1 post - 1 participant

Read full topic

Hello all,

Was wondering if anyone had any interesting doofers, hydras or other presets for the native effects for Renoise. Always like to see what everyone comes up with and learn from these types of things as I’m always learning new things within Renoise! Felt it would be nice to get a snapshot forum post so people can have an easier time finding these sorts of things. Providing the patch information values or screenshots will work in most cases too! Thanks in advance.

3 posts - 2 participants

Read full topic

Is anyone else having problems with renoise crashing upon loading an second instance of the same vst3 plugin ? I am having this problem with zenology.

3 posts - 3 participants

Read full topic

Hi all, it is possible to update SysExLibrarian Tool for new version of Renoise?
Thanks
Emanuele

1 post - 1 participant

Read full topic

Hi all, I repost and old post of mine, where I would like to have into the same instruments, more than one vsti and more than one MIDI OUT!
Hope this feature will interest not just me!
Emanuele

1 post - 1 participant

Read full topic

Is there a way to get rid of the reverb tails that sometimes appear in the beginning of a song in a render? I’m making a new song which starts very quiet and when the first note plays I get a BOOM from the reverb tails and it’s extremely annoying. I tried adding an empty pattern in front, but they tails only play when the first notes are played, so the only thing I can think of is play a single note with all the instruments in the beginning of an empty pattern and it’s really a hassle and shouldn’t be required.

I’ve also started to get snaps in the rendered wav, every now and then there are 1-2 loud snaps that you can clearly see in the waveform and you have to render it again and they’re either gone or moved to another place. Any idea about those?

1 post - 1 participant

Read full topic

I was wondering if anyone has experienced this or something similar in Renoise with Zebra 2 or other VSTi / AU plugins. My issue seems to be localised to when using Zebra 2 in Renoise (both in Renoise 3.2 and the new 3.3). I don’t have the issue in Reaper. I’m on Mac OS Catalina.

The issue is that none of the dropdown menu selections in Zebra 2 work, the parameters just won’t change when selected from the menus - this applies to patch editing only, not preset selection. The issue exists in AU, VST2 and VST3 instances of the plugin and only with menu dropdowns in Zebra 2, and not with menu dropdown selections in other plugins I’ve tried.

The only time I can get the parameters from the menus to change is if I choose to enable keyboard at the bottom of the plugin window. The only problem with this solution is that I have to continually turn enable keyboard on / off between when wanting to use the qwerty keyboard to play notes or edit a patch. Also, this behaviour seems to only have occurred since I upgraded the OS on my crumby old mac, so I’m thinking it might down to using the most recent version of Zebra 2 with Renoise which I may have not been using before I performed a complete reinstall of my system, DAWs and plugins.

I was wondering whether if anybody else has experienced this kind of thing before in Renoise and what the possible cause could be. I’m also onto u-he’s support to see whether it might be a bug in Zebra 2.

Any suggestions or advice would be really appreciated.

Cheers

2 posts - 2 participants

Read full topic

I have never used a tracker previously but I have been messing with the demo for Renoise recently and I have been really digging it.

I have a question though and hoping that someone might be able to help.

I have a drum sample that I call upon using the sample region fx and then I play it backwards, and I’m curious the best way to apply delay to or retrigger the backwards region while the same instrument it playing on the track.

I don’t know enough about the application so I’m sorry if that is a poor question.
I guess I’m wondering if the move is to just make that a unique sample and apply effects to it in it’s own track or not? I feel like I could do this without creating my own sample but I haven’t been able to decipher the best method from the manual quite yet.

Here is the bit that I am playing with for reference, I’d like to delay the sweep at the end of pattern 5 into 6.

I hope this is the right place for a question like this!
Thank you!

1 post - 1 participant

Read full topic

Hi,

Is there a way or plugin that can recieve audio from the sidechain device, and just pass the audio thru on the track where that ‘receiver’ plugin is inserted?

That way I could use every track as a return track, and split audio paths etc.

ps: Love the the sidechain device, best implementation of sidechaining I’ve seen. No extra dummy channels needed etc.

1 post - 1 participant

Read full topic

As you might now, with the #Line input device it is possible to use Redux as a bare multifx.

Using static effects on any topology that has no feedback loops is supported. Macros allow external automation. This means that one can modulate a lot of parameters.

It is also possible to do some pattern-based effects, as e.g. the legendary CamelSpace VST did, unfortunately the best bet now is to write patterns externally as DAW automation controlling a macro. This has the side effect that patterns can’t be recalled on presets, so it is desirable to do this internally.

I will first explain a way to do this internally and then the rough edges with the approach.

To have internal patterns the next devices are needed in series: LFO envelope with Custom waveform (pattern), Formula, LFO envelope with Custom waveform (pattern), Formula, Hydra.

If we ignore both the formulas, the second LFO pattern is an AD envelope and the first LFO is modulating the Reset (envelope position) of this AD envelope. This way to add more gating or sustain requires only chaging this AD envelope, not tedious redrawing of every peak on the graph.

The first formula is just “y = 0.5 - A” to invert the first LFO, as the Reset parameter on LFOs goes from 1 to 0. The second formula is just “y = 2*A” to get the envelope to full range. The Hydra is just for forwarding these envelopes to any parameter.

Unfortunately this approach has some problems:

-The envelopes/LFOS don’t sync with the host, they are free running. This means that playing and stopping doesn’t work. There is a “painful” workaround to Retrigger by using MIDI via a Note/Velocity tracker. This requires a dummy sample with silence and an own channel for Redux with MIDI and routing on the DAW.
-The LFO envelopes can store up to six presets (patterns), but there is no way to automate the pattern recall. Macros don’t allow it.
-This is a global problem on Redux as a FX. At least on Reaper when using the #line input the original signal aren’t replaced on the DAW. Redux acts as a send effect. Workarounds have to be made too with track channel redirections on the DAW.

camelspacey.xrni (6.0 KB)

1 post - 1 participant

Read full topic

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