Ableton Forum

I noticed that rendering a song to disk can create strange glitches in the rendered file. Changing the samplingrate or bit-depth and turning on or off the normalizing or loop option has no influence - the glitches remain. It's not a clipping issue, as the masterlevel does not reach 0dB. The samples used are clean and have no clipping nor any glitches. However - the sonic content of the samples used seems to have a influence - depending on it, there are more or less glitches in the rendered file. The glitches are not always on the same spot when I render a song several times and compare the resulting files.

Now - when I resample the master out (recording the master out within Live) the resulting file is clean and there are no glitches.

Questions:

1. Does anyone else have the same issue ?

2. Is there a quality difference between resampling the master out and rendering?

If there is a no to the second question then resampling is a workaround for this problem.

Specs:

Live 2.1.2
Win XP
HP Omnibook 1500, Mobile PIV 1,7 GHz, 512 MB RAM
M-Audio Quattro USB (newest Drivers)

do a forum search for "render" and you will find a number
of threads dealing with this issue
(known bug?).



best,
wm

Hey, I am incidently just discovering the same bug. I found, actually, that not only does it not render cleanly in Live (i'm having some loops drop in and out, and overall just sounds "Weird") but neither will it export through cubase as a rewire slave - although it ends up doing better through cubase. playback sounds perfect in either live or as a slave, so it is very agitating that i cannot render the track.

incidentally, i have the same audio interface which can be problematic on its own, but it has performed well recently - and rendering is independent. i am on a p4 2.8 laptop running windows xp pro with a gig of ram. there aren't really that many tracks running and it is not coming anywhere even on the radar of hard disk buffering problems, it just seems to be an issue in the rendering engine that I hope is fixed in the 3.0 update that i hope to get tonight. in the meantime i'm doing a defrag and will try to render it off an external firewire drive - but this would mark the first time i've had any drive related problems AND FURTHERMORE it does not seem that RENDERING should have anything to do with the drive, and as some other loops continue playing just fine throughout i imagine, again, that it is just a renderer problem.

and so, yes i am having the same issue - and i will try the resampling workaround - which is kind of lame to have to do, but a workaround is a workaround no?

chris
proteron at yahoo dot com

apeiuso wrote:I noticed that rendering a song to disk can create strange glitches in the rendered file. Changing the samplingrate or bit-depth and turning on or off the normalizing or loop option has no influence - the glitches remain. It's not a clipping issue, as the masterlevel does not reach 0dB. The samples used are clean and have no clipping nor any glitches. However - the sonic content of the samples used seems to have a influence - depending on it, there are more or less glitches in the rendered file. The glitches are not always on the same spot when I render a song several times and compare the resulting files.

Now - when I resample the master out (recording the master out within Live) the resulting file is clean and there are no glitches.

Questions:

1. Does anyone else have the same issue ?

2. Is there a quality difference between resampling the master out and rendering?

If there is a no to the second question then resampling is a workaround for this problem.

Specs:

Live 2.1.2
Win XP
HP Omnibook 1500, Mobile PIV 1,7 GHz, 512 MB RAM
M-Audio Quattro USB (newest Drivers)

welcome to the club

dpel,

thanks.. it's bittersweet, but it is reassuring to know that i'm not the only one with this issue... now i'll go see if the live 3 update had any rendering fixes..

btw devs if you catch this msg i think it has to do with the live effects, particularly the granular delay. could just be a bad analysis though.

chris

Although the initial part of the file sounded better, there is still hardcore clicking in version 3's renders, so I am going to have to posit that the rendering engine didn't change. so now that 3 is released, what is the process for getting this one done?

chris
proteron at yahoo dot com

For my part, the "render to disk" function seems not to produce any more glitches since the upgrade to Live 3.0.

No time yet to test everything - but it looks promising !