RENDER POLL

[dpel]

everyone,
i've been helping and patiently waiting for ableton to get the RENDER function
right. now it has degraded even further.
now with version 2.1.1 on my AMD 2.6/XP/RME HDSP 9652,
when i render, i get at first a small blank white box, then the whole screen goes blank (for about 30 seconds) then the render begins and ends with a pop. much slower.
when i then play back the render, as always (since version 2.0),
I GET CLICKS!

does this happen to you too?
was this intended for 2.1.1 (i'm sure not)
i don't mean to be so sarcastic but how long do we need to be patient
for something comparatively elementary?

[epilacs]

yes this has been an issue for me, as well.
but...dpel and i have both posted on this before.

anyone else experiencing this?

wm

[mlaboratories.net]

I've never experienced this.

Have you guys tried a clean install yet? I did that and it resolved the problems I was having.

[dpel]

I've never experienced this.

Have you guys tried a clean install yet? I did that and it resolved the problems I was having.

a clean instal of live on the PC?
meaning uninstall all of my old versions.
reinstall 2.0 and then update to the current version?

what was the problem you were having?

dpel

[epilacs]

actually, i did do a fresh install the other night...
i re-rendered a file that i had rendered immediately prior to reinstall.
still clicks in the rendered file. same general location, at different times.

i am certain that this has nothing to do with the clips/loops/samples that i am using, because they are all preprocesssed before being assembled in live.
i am starting to suspect that it might have something to do with the ableton reverb...but havent been able to nail down any patterns, so cant pursue this idea past the hypothesis stage.

on rereading the previous thread http://www.ableton.com/forum/viewtopic. ... highlight=
and the several other threads that come up when searching the forums for 'rendering', here are some responses to questions posed in them:

-the actual rendered waveform does not show any spikes or similar anomalies.
-when rendering i disable any open network connections and/or running programs.
-the crackles and clicks are rarely in the same exact location within the file,
but always in the same general locations.
-i have been bouncing between versions 1.5, 2.0.1, 2.0.3 for the most part.
1.5 is the only version that consistently does not give problems.
-i do not have vstis in the vst folder

winxp/2.0ghz/384sdram/sbliveplat/kx drivers

i am beginning to think that the render to disk function may not be the best way to go when working with multiple tracks. that is, as a multitrack-type recorder.
i am considering, as a workaround, rerouting audio to a soundcard input and recording in a wave editor, as an alternative to rendering.

until effect envelopes and parameters can be copied (correct me if they indeed can) this may be the best solution for me.
otherwise, i would prefer building a track/song in arranger view, then copying each track to a new document, rendering (hopefully with no clicks), and then mixing in a dedicated mulittrack suite.

yikes!
sorry to veer somewhat off-topic and get a little long-winded.

best to all...
william

[dpel]

this is what i've just discoverd:
try this:
open a new 2.1.1 file
in prefs: disable HI-Q!!!
drag a not so busy loop to one track (a pad) or light percussion
and record some audio on another track.

...now render still clicks?

not for me.

it still renders slowly though

[epilacs]

well i reread what the manual has to say about the 'hi-q' setting.
this seems counter-productive in a way, because of course i want all the audio
to be processed and rendered at the highest possible quality.

also, i dont know that this would address the issue for me, because all the samples/clips/loops are at 44.1, and i am rendering to 44.1

interesting, though