|
Subject:fluttering muck-a-track (sufferin' suckatash)
Posted by: groovewerx
Date:4/20/2002 8:45:19 AM
remember ping-ponging on a four track?? well...is it just me or does audio quality degrade after bouncing in acid?? lately i've been hearing artifacts in my mixes, not pops and clicks but a sort of fluttering -as if a light gapper/snipper was active and synced to the groove. this happens after i bounce the tracks...the strange thing is that it never happens when i use "render as", nor has it ever happened before this past week. i have made no changes to the daw but i've tried adjusting the "render to new track" attributes and mix volumes/freq's to no avail. if you can help solve this, please do so. and where can i get a better understanding of acid's rendering processes?? |
|
Subject:RE: fluttering muck-a-track (sufferin' suckatash)
Reply by: Maruuk
Date:4/20/2002 1:24:59 PM
I've had that if I forget to convert extended audio tracks to one-shot and leave it as a loop. |
|
Subject:RE: fluttering muck-a-track (sufferin' suckatash)
Reply by: groovewerx
Date:4/20/2002 5:29:10 PM
well mine weren't loops, they were beatmapped but changing them to one-shot did fix it. is it possible to disable beatmapper or change the default to one-shot?? |
|
Subject:RE: fluttering muck-a-track (sufferin' suckatash)
Reply by: SonicJG
Date:4/20/2002 8:03:59 PM
Groovwerx- Try unchecking the second to last pref on the General page in Prefs. HTH, Joel |
|
Subject:RE: fluttering muck-a-track (sufferin' suckatash)
Reply by: groovewerx
Date:4/20/2002 8:54:19 PM
JG, thanks but if you mean 'auto start beatmapper'...i keep it unchecked because i don't like the wizard popping up all the time. besides that, i'm looking for the switch that disables it in the render process |
|
Subject:RE: fluttering muck-a-track (sufferin' suckatash)
Reply by: SonicJG
Date:4/22/2002 12:33:15 PM
A developer just sent me this, as a hackey workaround for now. "You can force your rendered files to be tagged as oneshots if you insert a tempo change (like at the end of the project so you don't hear it). It has to actually be a different value from your project setting -- so 120.001 would do, if your proj was 120." Perhaps something better could be done for 4.0--we'll see. HTH, Joel |