Rendering Adds Silence/junk?

[audington]

Hi all

Quick question, sorry if this is explained elsewhere.

I’ve just rendered a very short sinewave sweep from Renoise, 16bit, Arguru’s Sync. The sweep starts at the star of the pattern and ends after 8 lines (it’s a very short sweep!).

I rendered the song and the resulting wav has about 3300 samples of ‘almost’ silence at the start. Near the start of the render in the ‘silent’ part there is a little bit of very low level junk… inaudible, but still it wasn’t part of the original.

Is there a reason for this?

Cheers

[vvoois (vV)]

@willmorton

Hi all

Quick question, sorry if this is explained elsewhere.

I’ve just rendered a very short sinewave sweep from Renoise, 16bit, Arguru’s Sync. The sweep starts at the star of the pattern and ends after 8 lines (it’s a very short sweep!).

I rendered the song and the resulting wav has about 3300 samples of ‘almost’ silence at the start. Near the start of the render in the ‘silent’ part there is a little bit of very low level junk… inaudible, but still it wasn’t part of the original.

Is there a reason for this?

Cheers

Yeps, to to give enough prebuffering for VST(i) plugins so none of the VST(i) output would get unexpectedly chopped off at the beginning.

[Johann]

@vV

Yeps, to to give enough prebuffering for VST(i) plugins so none of the VST(i) output would get unexpectedly chopped off at the beginning.

1.) Make the prebuffer configurable (time in ms). Plus: don’t write it to the file!

2.) Allow for selection of the pattern/line where a.) “render simulation” starts and b.) from when on the sound gets actually written to the output file.

[vvoois (vV)]

You could also perform “render selection to sample” and then don’t experience this silence. You can save the sample to disk, no problem.

[audington]

Thanks guys