Usual disclaimer: I apologise if this was mentioned already somewhere. I did a few searches and didn’t immediately find anything.
Sometime in the future, I think a nice option for the DiskOp area (specifically the Song section) would be the ability to select multiple song files, then right-click on the selection and choose “render to wav” from the context menu (or simply press the normal Render button). Basically a batch rendering option.
Renoise would then pop up the render options dialog as usual, but it would be slightly modified. An additional option in the “part to render” choices would be an option for the length of time to render in HH:MM:SS. So for example, if you wanted to create some quick previews of a lot of songs, you could easily choose to render only the first 60 seconds of each song, rather than relying on what number of patterns it should be (which will probably be very different in every song anyway).
The destination field would be changed to provide a directory name to render all the wavs in, rather than giving the individual filename. To avoid duplicate files I think the filename of the .wav that is created should be based on the .rns filename, instead of the internal song name. For example, I will often create a song then save several different versions from the same session, resulting in things like mysong1.rns, mysong2.rns, mysong3.rns, etc., but I forget to change the song name so they’re all titled “mysong1”, and would therefore result in several mysong1.wav files. Basing the .wav filename on the .rns filename would easily avoid this situation.
To make the batch rendering actually work smoothly/transparently, some other things would have to be handled automatically by Renoise. For example, Renoise will obviously have to automatically load every song in the selection and work its way through the list. Perhaps loading them into the background and working “silently” somehow, leaving any currently open session intact? (though is not that important really I don’t think).
When loading a song, if there’s an error of some kind which would normally cause a dialog box to appear (such as a missing VST or something), this will have to be ignored and handled automatically. Renoise will simply process the song as well as it can, and do whatever it needs to be able to create the wav. If a VST is missing, it simply won’t be included in the rendered wav, and it will be the user’s fault for not making sure his/her songs and plugins are not correctly up to date. A log file could probably be generated in the same directory as the .wavs for that batch rendering session, which would detail any errors that occured.
While Renoise is rendering a song, the usual progress bar and Stop button should be visible, but probably with a couple of changes. There should be a button for “skip/cancel this song” and also “cancel entire batch job”.
And I think that’s about it really, you get the idea.
Maybe you are working on a whole album of tunes, and you’ve finally tweaked all the .rns files just the way you like them. One night you select all the songs, set up the batch to render the final .wav’s using Arguru’s sinc/32bit/96khz, then go to bed, and all your lovely tracks are ready by the morning!