+1
(I also love gnute’s idea about taking the name from the track)
You have obviously never seen me in the midst of ‘render fury’. No way on earth I am keeping track of all those files.
Also, could the selections please render to the same volume they were being played at in the first place (sans master efects) so that I can do stuff like render a track to sample, then play it back on a new track and not have to figure out the levels again?
This would be so awsome!!!
+1
- the resulting base key should be the note you have used to trigger the sample, if the selection contains only one note:
if you rendered the following selection:
E-4 01 ---
--- -- ---
the resulting sample should have “E-4” as base note
Plus a billion.
Yeah bloody right!!!
Why does Renoise drop the volume upon render? Makes no sense to me.
And thanks to all the other cool ideas linked to my original idea. Good stuff.
Couldnt it be a checkbox in the preferences menu?
Like:
Ask for name when rendering selection to sample?
“box”
Yeah that is a good idea!
“Also, could the selections please render to the same volume they were being played at in the first place (sans master efects) so that I can do stuff like render a track to sample, then play it back on a new track and not have to figure out the levels again?”
yes I would like that too
conclusion: something should be done with this thing.
after this tread came up, it irritates the squits out of me.
Yeah I have totally no idea why this volume drop happens. If you cant handle your levels you need to stop producing.
Renoise still includes the settings/instances on the mastertrack when
rendering the sound-files right?
Could it have anything with the volume-level
not beeing cranked up to max?
I tested this.
I loaded a .wav into renoise.
didnt touch any of the faders. everything at 0
rendered
rendered wav was more quiet
pain in the arse. sorry!
Agree, there should be more control over this feature.
Like:
Volume, render method (low quality? high? same as render2disk option?), dry/wet (without having to disable all the effects manually, before rendering).
The volume of the rendered output is halved.
This was done to avoid that the rendered samples easily clip, because clipped values in samples is something that you can never recover. We had used the original untouched volume in the first betas, when we introduced this feature, but then got lots of complains and bug reports that the output of the render is always distorted…
What we could easily do though, is compensating this automatically with a doubled sample volume (the one in the sample properties) - dunno why I haven’t thought of this before.
Would that help to avoid confusion or be even more confusing?
How about…
Leave the volume untouched so that render-to-sample behaves as people expect/want it to, but during the rendering process Renoise can internally monitor the output and check for clipped samples. If more than X clipped samples are detected, then Renoise can pop up a dialog box when the render is finished, saying something such as:
[Renoise has detected clipping in the rendered sample. To avoid this you should lower the master volume.]
I think something like that could keep everyone happy. The rendered sample volume would be as they expected, and if it does happen to clip, then they are informed that it’s their own fault, not the fault of Renoise.
That box would pop up nearly every time you render if we keep the volume untouched (do not halve it by default). When using normalized samples and a few FX you easily generate such clipped samples…
Sure, I understand this, but… people can’t have everything 
If it’s too damn loud, it will clip… people need to realise this.
Ok, how about a new setting in the prefs screen to set the render-to-sample amplitude? By default it would be at -6dB or whatever it currently is, but we could change it to 0dB if really wanted to (and face the consequences of clipping).
Maybe this would be better?
I just think you have to accept that it’s not possible to hold the user’s hand all the way. If you do want to help prevent clipping in this way, it should at least be possible for advanced users to adjust this in the preferences. Otherwise I think you risk alienating a few people who feel frustrated at not being able to disable this behaviour?
.