New Tool (3.2): The Deliverer

Renoise Tools
4

Looks like the exclamation marks in your folder name might be causing the issue. Can you try on a folder without them?

Edit: Never mind, I need to push a fix for windows users.

5

tried different foldername combinations to no avail.

i guess so :wink:

6

Thank you, great tool indeed it save lot of time!

1 Like
7

This should work for you:
https://www.renoise.com/tools/the-deliverer

Edit: Link changed to tool page (instead of direct download to v0.9 XRNX, to avoid outdated versions floating around)

1 Like
8

this worked. highly useful tool - thanks mate!

3 Likes
9

Excellent, glad it worked!

10

btw: it would be nice if i could tell the tool to not create a new subfolder for each raw sample exported.

it also seems to return the same error message as posted above when i try export samples from a tune which cointains no samples.

11

Thanks for letting me know. I’ll have a look at it.

1 Like
12

An excellent addition to this tool would be batch song loading similar to:
https://www.renoise.com/tools/batch-render

I was actually working on a tool last week to batch load songs and export all instrument samples as .WAV,
merging the above tool, and:
https://www.renoise.com/tools/exportallsamples

Being able to easily batch a folder of songs into stems and samples at will would be rad.

Thanks!

2 Likes
13

That’s on my list!

1 Like
14

Superb. Works like a charm. /Mac OS X 10.15.7

1 Like
15

Thanks for making this amazing plugin, @dltfm! :pray: It serves all my needs and more. There’s just one thing I would love if The Deliverer did and that was to fold in the (poor) functionality I’ve built in Oversample, which is to:

… increase all quality parameters (such as “oversampling”, “quality”, “phase”, etc.) in all active devices in the song to maximum, so you get the best quality when rendering a song to WAV.

Since my knowledge of both Lua and Renoise’s API is terrible, Oversample is also quite terrible. But I’m certain that under your masterful stewardship, the crappy code I’ve written could be made to shine like a diamond within The Deliverer and thus render (pun intended) Oversample completely superfluous to my workflow.

Thoughts?

2 Likes
16

Hey @dltfm - thanks for this amazing tool!

Check out my post below. Would you consider adding the functionality I describe here, so that The Deliverer can extract effected stems exactly as they appear in the context of a song, which, when summed, would sound precisely the same as the master output? Essentially I realised, after trying to extract a set of “wet” stems, that muting unwanted tracks - rather than soloing as you go - produces stems that incorporate effects that are dependent on other tracks, eg a signal follower controlling the “ducking” of a stem you are extracting.

1 Like
17

I love this tool.
can’t believe there isn’t an option to render group fx to indiviual tracks natively in Renoise… This helps… Thanks!

1 Like
18

can you add an optione for it to save each section into a sepreate file?

19

for some reason it assumes my tracks name is untitled :confused:

20

awesome! thank you for the hard work!

21

Having two issues, one is that {FILENAME} doesn’t seem to be recognised in the filepath

image

The other is that after rendering the master, it solos the first track like it’s going to render that next but just stalls on )% and doesn’t move. During this time you can scroll around etc, so it’s like the render hasn’t been initated.

22

Thanks man, I’m interested in exporting the xrni’s, looks great.

23

Thanks for the great tool!

  • When setting Solo mode to Mute others in renoise, Deliverer renders the stems with the signal follower sidechains intact.