Renoise Forum

@Ledger wrote:

I`m not too familiar with Regular Expressions but I found a simple one that helps searching through the scripting docs using Notepad++

You can search for multiple words in a line by using .* between multiple search terms

In the screenshot we have search string: pattern.*automation.*clear which finds the line

renoise.song().patterns[].tracks[].automation[]:clear()

Just make sure ‘Regular expression’ is checked on the bottom left

//////////////////////////////////////////////////////

Use Return and Shift + Return (or same with F3) to jump forward and back through results

EDIT: Shift also works with Find Next button

Posts: 1

Participants: 1

Read full topic

@ffx wrote:

Hi there,

let’s say you are automating a gain device on a track for a fadein of that track. Later you want to delete all parts/sequence prior to this fadein, and including the fadein part. And you have automation following enabled.

After deletion, your track now will be quiet, caused by a silencing gainer device without automation.

Wouldn’t it be more logical to populate the automation values like it would have been before seq- deletion exactly at the point after the selection? So the gainer device was left at 0dB instead after deletion?

If often find this kind of annoying, if you delete bigger parts in a song, automation can be messed up a bit. And this could be fixed.

Posts: 1

Participants: 1

Read full topic

@Ledger wrote:

Nevermind I found the undo button just click the [three dots] again to find it

Posts: 2

Participants: 1

Read full topic

@Raul wrote:

It seems that the latest modification of the renoise.com website regarding the tools has affected the operation of the “~ Find Tool Updates” tool.
@Taktik, can you fix this? Or are you waiting to update the web of www.renoise.com?

…

On the other hand, would it be possible to change the way of showing the versions in the web tools section?

I do not know if I’m doing something wrong, but it seems that it is only possible to upload a single version of the tool for each version of Renoise. Does this work like this? Renoise is updated very few times. But the tools can have many updates…

Posts: 2

Participants: 2

Read full topic

@ffx wrote:

Here is an idea how the midi automation problems could be solved (EDIT: see also idea 2):

Use two track fx columns instead, so have 32 bit space:

FX1 FX2 M1E0 4800 | | | Cmd | | Delay | Value

Extra benefit: Using multiple midi automation at once, e.g. aftertouch + pitchbend, by using 4 columns of fx. Saves one track column of space for sake of one fx column.

Disadvantage: Would it be a serious problem, if this midi commands were applied to any instrument playing in that line (assuming you are using multiple instruments in one and the same track)? You couldn’t have individual midi commands per instrument before either.

Any better ideas?

Posts: 2

Participants: 1

Read full topic

@ffx wrote:

Hi,

if I have a midi automation like this

and now am dragging the last track column one position to the left

and then decrease the number of track columns

the fx commands will not be reconnected together to valid midi events again (which will happen if I drag the column back to last position instead) and the fx stays/turns into ugly random like device on/off automation instead.

Also I would like to highly suggest to you to totally decouple on/off device automation from midi automation, e.g. using unique fx command instead of double-use Mx-commands and providing a automatic song conversion then. Or maybe it would be even even better, if you were providing graphical on/off automation.

Besides the above reason, there are also the following reasons to change the double-usage of Mx:

• In the above scenario, if I accidentally change the song position and the song option “automation following” is enabled, and the song position now passes those values, a lot of on/off automation and preset hopping will appear, which also will not be saved in undo history. So it will end up irreparable

• There are other scenarios AFAIK which I did forget in detail, when a midi automation will accidentally turn into on/off automation. I think it was quantization in adv. tools and also as a tool

• You can never say for sure, if a device will be accidentally automated, because there is no automation indicator at all. So Russian roulette style. Also there is no indicator for preset switch automation

Thanks!

Posts: 1

Participants: 1

Read full topic

@trueschool wrote:

I know this is a big job but it’s MUCH appreciated. I had a hard time using the old forums on mobile and I’m hopeful these’ll be an improvement.

Posts: 1

Participants: 1

Read full topic

@trueschool wrote:

Hi, I’m on Mac Mojave and recently am unable to load any VST or AU instruments. I get the error below.

I don’t understand what changed or how to fix this. Any help?

https://media.giphy.com/media/ratutTQG2Nqbm/giphy-downsized-large.gif(image larger than 4096KB)

Posts: 1

Participants: 1

Read full topic

@taktik wrote:

Live demo: https://www.stef.be/bassoontracker

Posts: 1

Participants: 1

Read full topic

@Ledger wrote:

After a scripting render operation, and though I have set song to 0dB headroom; renders of an individual track seem to come out a couple of dB quieter.

Does anyone know why?

Posts: 1

Participants: 1

Read full topic

@milkyheart wrote:

final track from my upcoming seventh ep. 10/4 time signature when there is one

Posts: 1

Participants: 1

Read full topic

@milkyheart wrote:

been sitting on my hard drive since november. now available on bandcamp

Posts: 1

Participants: 1

Read full topic

@Garf wrote:

Let’s imagine you have two of the same patterns playing but don’t want the last notes in a track to play, it could be a drum fill or a build-in, then you simply “paint over” (like the select function) to mute these parts of the track without have to make a new pattern to make these changes, so it should be independent on pattern and therefore leave other instances of the pattern untouched.

Posts: 1

Participants: 1

Read full topic

@Raul wrote:

RANDOMRANGETRACK, What is this?
The RandomRangeTrack tool contains a double function to randomizes the notes or values of the selected range within the selected track.

First it is necessary to select an area in the pattern editor. The first line and the last line selected must have different notes/values, which define the minimum and maximum notes/values of the range to randomize.

Use “ALT + mouse select” to the precise selection.

Access: “Pattern Editor/Selection/Randomize Notes… (or Randomize Effects…)”.

DOWNLOAD:
https://www.renoise.com/tools/random-range-track

Enjoy!

Posts: 1

Participants: 1

Read full topic

@Fabrice wrote:

Hi Renoiser!

I’ve posted a form like this, but a long long time ago, so a repost one, by curiosity :

What genre of music you mainly compose with Renoise?
Multiple choices are ok

• Drum’n’bass / Breakbeat / Step
• EDM
• Dance / House
• Techno / Trance
• Experimental
• Chill-out / Lounge / Healing
• Ambient
• Synthwave
• Electronica
• Chiptune
• Pop / Rock / Electro rock
• Hip-hop / Rap / Trap
• Jazz / Blues / Fusion
• Cinematic / Orchestral
• Other

0 voters

Posts: 1

Participants: 1

Read full topic

@Fabrice wrote:

Hi!

I’am quite in a future bass / kawaii composing period and here is a short chill track I’ve tracked yesterday. With a touch of vocaloid glitches.

Posts: 1

Participants: 1

Read full topic

@Meef_Chaloin wrote:

At the very least there should be the 4 icons to change locations but also would be great if there was a drop down for previous locations. It quickly gets very tedious moving around.

MP3 support, now the codec is free why not? I would find it very handy for exporting a mix ready to put on my mp3 player. Other formats would be good, ogg etc.

When setting a pattern selection to export, highlight the area being exported (or darken/blur the unexported areas).

Posts: 1

Participants: 1

Read full topic

@ffx wrote:

Hi,

the GUI of the freeware Helm VSTi doesn’t work properly anymore in Renoise 3.1.1 64bit, I guess since macOS Sierra. The Gui won’t update anymore, it only shows the initial graphics drawing.

It works just normal in any other DAW though.

Is there any way or workaround how I could make this version work again? Any ideas?

Here is the version: Helm 0.85 64bit macos

Thanks!

P.S. I’ve seen similar problems in other VSTis, too.

Posts: 1

Participants: 1

Read full topic

@29a wrote:

Anyone knows what would be command to change basenote from which slices keyzones will start?
it is not same as (…).sample[1].sample_mapping.base_note, after i change it when creating first slices everything is back to previous settings (c3 in my case)

Posts: 1

Participants: 1

Read full topic

@Ledger wrote:

The following code will crash renoise completely. The necessary components of the crash are

• add a new pattern to the sequencer
• render the new pattern (or a portion of it)
• delete the pattern that was just rendered

There seems to be something going on with the :delete_sequence_at() method aswell where the sequence indexes are not properly updated so the next line of code doesn`t work in some cases. I will try to post back a snippet for that too.

--song local song = renoise.song() --final pattern index local final_pattern = #song.sequencer.pattern_sequence --add a temporary pattern local pat = song.sequencer:insert_new_pattern_at(final_pattern + 1) --insert a c-4 in new pattern ----------------------------- song:pattern(pat):track(1):line(1):note_column(1).note_string = "C-4" --render newly created pattern ------------------------------------------ --renoise.SongPos objects for render range ------------------------------------------ local start_pos = renoise.SongPos() local end_pos = renoise.SongPos() start_pos.line = 1 start_pos.sequence = final_pattern + 1 end_pos.line = 16 end_pos.sequence = final_pattern + 1 --update options table ---------------------- local options = {} options["start_pos"] = start_pos options["end_pos"] = end_pos --prompt user for path local file_path = renoise.app():prompt_for_filename_to_write("wav", "Save Wav") --render -------- song:render(options,file_path,function()end) --delete new pattern --------------------- song.sequencer:delete_sequence_at(#song.sequencer.pattern_sequence)

Posts: 1

Participants: 1

Read full topic