Forum

Beyond FM rate LFOs and granular/wavetable synthesis, this would be my top suggestion for what Renoise needs, and I don’t think it would be very hard to implement, either, since it’s basically an organizational feature.

There are many trackers and samplers that already do this. The one that always comes to mind for me is LSDJ, but the YouTuber and musician Andrew Huang has a new mobile sampler-based DAW called Flip which also separates patterns this way.

To put it simply, there’s a place where you create patterns, and then there’s a place where you insert and order the created patterns on a timeline, to structure the song.

A pattern doesn’t migrate from the created patterns area to the “in use” area. It always remains in the created patterns area at all times, but then is linked to or ordered within the “in use” area.

See the video I linked above, or watch an LSDJ tutorial, and you’ll see the benefit of this. Beginning at 5:00 in the video you can see the separation, with one area called “patterns” and one area called “order”.

LSDJ lets you create patterns, and each is given a number, but nothing appears in a song until you go to the song section and input the pattern #s in the order you want.

The separation is useful because that way you can create variations on a pattern, test ideas, sketch optional material, etc, without having them automatically be a part of your song the way Renoise does it. It’s a more logical workflow to be able to test ideas out without committing them to a place within the song right away.

Renoise already has the concept of patterns existing even if they are not in use, because it’s possible to change the pattern # in a slot in the pattern matrix so that a pattern # no longer appears in the matrix. The data is still there and the pattern still exists even without being actively used, however there is no place to actually see this unused pattern or edit it, if it’s not being actively used in the matrix. (This is why there is a “delete unused patterns” option.)

There should be a place to see created patterns, edit them, delete, duplicate, etc, perhaps even give them names, which is separate from the matrix where you actually determine the order of patterns which will create the song.

What would the repository / storage / created patterns area look like? It might be possible to tab between the matrix and this new area, so that the matrix shows the song, and the new area shows a list of all patterns whether in use or not, the pattern #s, optional pattern names, categories such as “intro patterns”, “chorus patterns”, etc, and maybe some further info such as lines in each pattern, which tracks each pattern uses, etc. There would be options to clone, delete, cut, paste, etc, and clicking on a pattern here would open it up in the pattern editor. Then, when you’re ready, you can tab back into the pattern matrix to input the pattern #s in the order you want, and build the song from there.

This would make my workflow easier and I think there’s no reason to not include it, because it would be strictly optional. Anyone who wants to work the old way would just continue to use the pattern matrix. This would simply be a new area to list your unused patterns (and used ones, too, since it displays everything) for the purpose of viewing or editing them, and create new patterns without having them appear in the song automatically, for those who wish to use it.

2 posts - 1 participant

Read full topic

Hey

For some reason some plugins don’t show as vst alias (both VST and AU format) why is so ?

(also : I so wish for a midi effect device… Hope it’s in some roadmap somewhere)

1 post - 1 participant

Read full topic

The things I was hoping for in 3.3:

FM rate LFOs
Granular multi-grain capabilities of the Sampler
Finer time-stretch algorithms

3 posts - 3 participants

Read full topic

Is there a way to save multiple instruments in the same file. I got like 3 instances of an FM to do a snare and I rather have the whole synth than a rendered version.

1 post - 1 participant

Read full topic

Hi, I see the mention of Sononym here, and it’s great. But that’s to do with our samples. Now, let’s address smart(ish) organization/simplification of our plugins. I’m a Mac user so I’ll hit it from that angle, but others are welcome to address other OS’s and perhaps have separate threads for that, for the sake of simplicity. I’m looking for tips. It’s a time of year when folks are buying a lot of plugins (Black Friday & Holiday/Easter sales).

Personally when I get a plugin, I install it in both AU and VST3. The VST3 option allows for it to be used in Bitwig, in case I ever want to use that. But apparently even Bitwig doesn’t necessitate non-AU, if one also installs/uses Blue Cat’s MB-7 Mixer.

Regardless, this is more about how to logically organize the files and folders.

-There are things installed at the root level.
That is, “/” AKA “Macintosh HD”

-Also, there are things installed in two user folder (home & shared).
That is, “/Users/Username”
& “/Users/Shared”

Is all of this necessary? Jesus. Is it recommended to leave the installations where they were put during the installation process, and only change from the default installation locations (for the sake of organization) in the cases of being given the option in the installation process?

It just seems bizarre. I’m the only one who uses my computer. Why separate between root and user? And why have stuff in the “shared” folder? Sharing with who exactly? It’s my computer and they want their own I’ll give them some old Mac for X-Mas. Granted, “Shared” is created if you create multiple users. And I have, simply to prevent being locked out (both users are me and both have administrative access). For users who don’t have a “Shared” folder to deal with, just ignore that part. You probably still face the other stuff. Though I don’t see why I “shared” folder would even be needed, if plugins were simply installed at the root level. In fact, I saw a years-old page on the official apple website indicating that it’s best to install plugins at the root level.

And furthermore some things are spread out across the hierarchy of them. Will it go in “Application Support,” “Music,” “Library,” “Audio,” etc. etc.

It’s crazy. Let’s talk about how this stuff can be simplified/streamlined/made more sane. As in, what are the possibilities and limitations. Cheers

1 post - 1 participant

Read full topic

What is the impact of L1,L2 and L3 cache on renoise usage? (I’m buying a new laptop)

1 post - 1 participant

Read full topic

Hi, I bought an APC40MKII and installed the mapping for it I found on here, but it works extremely clunky.
Leds not doing the right thing, some knobs unused or not for the right purpose, some with duplicated actions.

In particular, there’s one button that is mapped to Pre/Post, to determine whether volume sliders affect pre/post mixer.
In the duplex browser I can click it and the light will go on and off, and it’ll work, but not when I push it on the controller.
In fact, the light won’t even toggle in the duplex browser if I push it on the controller!

Even though it is still mapped to

Mixer = {
mappings = {
…
mode = {
group_name = “Note Mode”,
},
and in the XML the group name is a “Note Mode” of type pushbutton

what do ?

1 post - 1 participant

Read full topic

Hi I’d like to know if it is possible to assign a group of fader to a specific effect with index X rather than “current effect”

something like “device = {index = 2}” that will always select the second effect of the current track

Thanks a lot

Best

1 post - 1 participant

Read full topic

Hello,
Sitala drum sampler has new version.
Right here

1 post - 1 participant

Read full topic

Hi all,

Try to find “MrPhenix80” on youtube and you’ll can hear all my remixes made with last renoise version.

example:

1 post - 1 participant

Read full topic

Could we have the LFO device sync to beats as well as lines?

I often move from one LPB setting to another and it’d wonderful to not have to double/halve speeds all my LFO’s when I do. (I use a lot! )

I also often want a lfo to go quicker than 1 LPB. A Hz mode would be wonderful!

1 post - 1 participant

Read full topic

Greetings everyone,

I’ve been lurking around this forum for quite a while now and lost track of how many times it saved my songs, so thank you all in advance!

A project of mine has recently released an EP and I’d be glad if you guys would give it a chance

It was originally supposed to be Synthwave, but this lockdown thing made me a bit too creative so it deviated quite a lot from the formula (one of the tracks has been featured at The80sGuy YouTube channel and some people literally stated they disliked it for deviating from an established formula, which I found amusing).

So, here we go:

The80sGuy video: https://www.youtube.com/watch?v=OkYIbtmFYZU

I hope you guys enjoy it. If you do, please, show us some love on YouTube and social media

Our instagram: @theblankaproject

We are also on Spotify!

Cheers!

1 post - 1 participant

Read full topic

The question is in the title

In the midi mapping list there is : current track, current effect, track X, effect Y from track X… but no “effect X from current track”

I’d like to create a similar channel strip for all channels and map it to my controller with (for instance) a compressor as effect 1, eq as effect 2 etc…

The only way I can think how to do that is by going through each track and manually setting the same CC to each first effect of each tracks, each second effect etc…

Is there a simpler way ?

Duplex or some scripting maybe ?

Thanks !

1 post - 1 participant

Read full topic

I often find Renoise guesses double the speed of samples I load when I enable Beat Sync.

It often reports 8 when 16 would be more appropriate, or 32 when 64 would be a better fit.

This little bit of lua seems to do a better job to me:

-- round value to nearest integer function round(x) return math.floor(0.5 + x) end -- samples length in seconds function sample_length(sample) local frames = sample.sample_buffer.number_of_frames local rate = sample.sample_buffer.sample_rate return frames / rate end -- Guesses the number of lines in a loop at the given bpm function guess_length_in_lines(sample) local rns = renoise.song() local length = sample_length(sample) -- calculate song's beats per second local bps = rns.transport.bpm / 60 -- calculate samples length in beats at current bpm local beats_at_bpm = length * bps -- closest power of two finds us 1, 2, 4, 8, 16, 32 beats etc. local beats_in_loop = 2 ^ round(math.log(beats_at_bpm) / math.log(2)) -- return a nice round number of lines return beats_in_loop * rns.transport.lpb end

I know this kind of guessing can be a little arbitrary but is Renoise finding a floor when it could be rounding?

1 post - 1 participant

Read full topic

I know the answer is going to be “render” but I was wondering if there’s a built in feature that permanently applies transpose and finetune parameters to the sample itself?

1 post - 1 participant

Read full topic

So, all the sample generators I posted a couple’a weeks ago - the same guy made a reverb impulse generator - these can be used with the Convolver built-in plugin. These can not only be crafted to be long and lush, but also short and VERY abstract/bizarro. Many values to adjust.

ryukau.github.io Freeverb

Ryukau also makes some of these available as VST3 and LV2 plugins (which VST3 has become incorporated into the upcoming Renoise update, per the announcement).

Many synths and effects -

GitHub ryukau - Overview

ryukau has 74 repositories available. Follow their code on GitHub.

Neato!

1 post - 1 participant

Read full topic

Is it possible to apply a fade to the end of a sample (like done in the sample editor) through the API?

I want to automatically try and remove all the clicks from the ends of destructively rendered slices.

1 post - 1 participant

Read full topic

Hi guys, hope you all good and safe!

I really need the ability to move around the start points of my WAVs, I know I can use commands to trigger from various points or simply delete/cut the sample start to the point I want.

However this is really not cutting it for me (no pun intended), which VST sampler would you guys recommend as the best replacement? I am looking for small and simple, no Kontakt style monsters

A majority of my samples are basic drum hits so I do use Renoise sampler as they are small and simple but for long samples (synth captures and such) I really need to be able to move that start point to that sweet, perfect spot, thanks in advance!

3 posts - 2 participants

Read full topic

Decided to play with the Renoise repeater a little bit and this became a result, hope You enjoy! Any feedbacks will be appreciated

1 post - 1 participant

Read full topic

In the past we usually have done public betas, where every registered Renoise user could download the betas at the backstage. This time we’d like to do things a bit differently, and only want to invite a bunch of people to help us testing the beta versions before it’s going public. This hopefully eases things on our side by concentrating on fewer people. Also, the 3.3 mostly is about just one feature: VST3 so we’re not expecting many issues that need to be discussed apart from plugin compatibility issues.

We also won’t have time to add new features during the beta and will try to release Renoise 3.3 stable this year - if possible.

If you want to help testing the Renoise 3.3 betas, before they are going public please send me a private message with the following info:

• your backstage email (your login), so we can enable the beta builds at the Renoise backstage for you
• the operating system that you’re going to use mostly (Windows, OSX, Linux), so we can make sure that all platforms get tested somewhat evenly

I think we’ll only need around 30 (33?) people to test the betas, so please understand that we can’t accept all requests.

Please only request access to the betas, if you are planning to do some actual testing

This release basically only is about VST3 support, so there’s really not much more to see.

Thanks a lot for your help!

3 posts - 3 participants

Read full topic