Tell me more about manual tedious tasks in Renoise that feel like chores. Maybe they can be scripted

tell me more about the manual tedious tasks in Renoise that feel like chores. if you can break them down into things, i can script them up.

3 Likes

One tedious manual process that comes to mind is:

  • loading a sample
  • chopping the sample
  • saving your chops as a phrase that plays through in time
  • further editing the playback in the pattern editor

I think steps 1-3 here should be a single step so you can go straight from chopping to editing if you want to.

what does “chopping the sample” mean? manually chopping? or something else, like mathematical shopping (divide into 16 equal slices)?

and step 3 seems to be… “slices to phrase”?

or?

it does sound good that you could “slice to x pieces upon load and create phrase”, but just needing to make sure i understand what you’re specifically after.

this is some good stuff. i like 2 + 3.
i think the “hide unused notecolumns across the song” would be pretty good to do. i’ll add it to my todolist in Paketti.

2 Likes

I think that’s where the user has leeway to work the way they want to work. There are different ways to chop samples, and once they’ve got the slices the way they want, there should be a straightforward way to get it into the pattern editor for further editing.

2 Likes

Another common producing task in Renoise that inexplicably takes multiple steps:

  1. copy a pattern (including notes) to a new column
  2. un-mute new track
  3. equalize volume of both tracks
  4. Change instrument of new track

and then optionally

  1. change notes in new track to complement original track in different ways (octave, unison, counterpoint)

this will take the selected track, duplicate it, and select the track, set the track notes to currently selected instrument. additional logic is that if you have a plugin instrument external editor open, then it will be closed upon duplication, and the new one will be selected.
it would be trivial to also do the octave switching for each note (+12? -12?) or randomize the octave switching between x amount of octaves. send me what you’re looking for and i’ll tweak it into Paketti.

btw i’m not sure what “unmute new track” means in light of “copy a pattern to a new column”.

1 Like

btw i’m not sure what “unmute new track” means in light of “copy a pattern to a new column”.

When you use the default Renoise “Duplicate Pattern (incl. notes)”, the new track is muted by default. Just an extra step to unmute it and balance the volumes of the two. I understand why they do it (since it doubles the total volume) but there should be a default that just equalizes the volume of the two tracks.

Save chain settings + routing + related groups and sends into a setting and then restore it into another song, auto-restoring the routing of the setting, adapting to the current/another song. Also optionally save a single track note lane which is played with the dsp chain (for previewing or so), also saving the related instruments. All at once into once setting (xml or fancy json), for quickly buildup a new song from such existing part templates, or quickly copying parts of one song to another. So preventing that tedious process of copying dsp lane settings, then instruments, then notes, then adapting instrument numbers, then restoring group and sends, from one Renoise instance to another (which also has problems recognizing the copy action).

On the other hand, if you could use VSTis within Renoise’s current instrument structure, this would be already possible… :cry: