Page 1 of 2
Serios problems with mixdowns
Posted: Wed Oct 01, 2003 9:31 am
by Bob
When I mixdown a finished tune strange glitches and digitals tiny tics appears in the final master wave file.
The CPU goes at maximum to 65% and no HD overload...it´s running smooth when playing back the opened Live file but
after the down mix it isn´t correct. Please let me know how to manage this.
Thanks in advance!
/Bob
Posted: Wed Oct 01, 2003 1:58 pm
by Guest
check your fader levels, especially on the master. If you're playing it back listening to it in real time, and the master meter hits the red at all, though you might not hear the clipping with the way your monitors are set up, when you render it, it will clip. I find that with a lot of tracks I'll have to turn the master pretty far down, around the middle of the fader. When converting a track to mono, the summing adds 3.8 dB, so you need to compensate by turning down the master fader. Sometimes normalizing can help keep clipping at bay. Check fader and buss levels, try rendering the clip again, and adjust and re-render until its right.
ryan
Excellent
Posted: Wed Oct 01, 2003 2:36 pm
by Guest
Great thanks for the superb tip!
Thanks
Bob
Re: Serios problems with mixdowns
Posted: Wed Oct 01, 2003 8:28 pm
by pharmakonMtl
Bob wrote:When I mixdown a finished tune strange glitches and digitals tiny tics appears in the final master wave file.
The CPU goes at maximum to 65% and no HD overload...it´s running smooth when playing back the opened Live file but
after the down mix it isn´t correct. Please let me know how to manage this.
Thanks in advance!
/Bob
i had that same problem the other day, where i made a bounce-- sorry Render -- and it came out with pops and clicks over one part. the funny thing was that it seemed the pop went through Send1's delay or something cause it echoed to the beat. the track was ambient and very quiet, so spikes in dB is not a possible cause.
Posted: Thu Oct 02, 2003 5:42 pm
by epilacs
hi bob.
do a forum search for "render" and you will find a number
of threads dealing with this issue (known bug?).
enjoy wading through the posts and good luck with finding a work-around!!
best,
wm
confirming the bug
Posted: Fri Oct 10, 2003 5:19 am
by proteron
I confirm the same bug with Live 2.12 on Win XP. definitely not a clipping nor a disk speed issue, but an internal issue in the mixdown process. er, render. it also occurs when live is doing a disk render as a rewire slave.
chris
proteron at yahoo dot com
and in v3
Posted: Sat Oct 11, 2003 8:46 pm
by proteron
I also confirm the same issues in V3, however i was able to circumvent the clicks by making all the samples RAM samples - which is "acceptable" for me with a gig of ram but bad for folks who are working with less. this leads me to believe that there is a problem with how the samples are treated during the disc write ... (i guess that is obvious)
the new sample features make it worth doing circumventions for now. it is really ironic that such core functionality is broken but some really twiddly features still make it quite a treat.
chris
Posted: Sat Oct 11, 2003 11:57 pm
by dpel
it's curious as to "why" this hasn't been officially addressed
or aknowledged.
?????????
dpel
Posted: Fri Oct 17, 2003 8:34 pm
by proteron
resurrection.
Posted: Fri Oct 17, 2003 9:51 pm
by Alex Reynolds
I could never get the Render function to work properly due to the same clicking and scratching symptoms.
It's been an issue at least since v1.5 and possibly earlier.
My recommendation to you is to output to mixer and record to external device (DAT, MD, etc.). That's the only way I've been able to record clean sound out of Live.
-Alex
Posted: Sat Oct 18, 2003 6:16 am
by dpel
or to cassette
use maxell tapes, they have less drop outs.
Posted: Sat Oct 18, 2003 6:32 am
by Alex Reynolds
Is it Live? Or is it Memorex?
http://www.vintagetechnology.com/ad_sca ... s_1974.jpg
Sorry, I just couldn't resist...
-Alex
Posted: Sat Oct 18, 2003 1:41 pm
by proteron
Alex,
the two workarounds mentioned in these posts work fine, but they are just workarounds. The first is arming a record track and doing a realtime bounce. this sounds fine, but the disadvantage clearly grows with the length of your track.
the other workaround in live 3 is to put all the loop samples in RAM by clicking the RAM button on the sample subwindow. yes, this works, but it demonstrates that there is obviously a problem in the reading/writing of the samples during the rendering process.
the rendering process should make a clean mixdown even on a 386 with the world's slowest, most horrible fragmented hard drive
Posted: Sat Oct 18, 2003 5:08 pm
by Alex Reynolds
I agree but it is up to Ableton to fix this problem. Not much I can do about it.
-Alex
Posted: Sun Oct 19, 2003 12:31 am
by dpel
excellent.
dpel
