[Top] [All Lists]

Re: sound edit pops

Subject: Re: sound edit pops
From: "Scott Fraser" scottbfraser
Date: Fri Oct 7, 2011 10:34 am ((PDT))
<<The discussion here has had me thinking things I've not thought about bef=
ore. I'm wondering if the application's code routines may have an effect on=
 the various experiences people are having. Until an edited file is saved a=
s a single section it's quite likely that the component parts are being sen=
t to the hardware as seperate buffer feeds. The software could be responsib=
le for the click in that situation.>>

This could explain what seems to be happening for some people. I know that =
in older versions of Digital Performer a crossfade was rendered as an SD2 a=
udiofile & inserted at the edit point. This could take some seconds to rend=
er & while that was underway playing across the edit would play the 2 sound=
 bites butted up against one another but without the crossfade, which was s=
till under construction, revealing a click. With the last 2 versions of Dig=
ital Performer a crossfade is now implemented as volume automation & it occ=
urs instantly, thus no waiting required, & no additional audiofiles are bei=
ng generated. This has sped up the process considerably. Every DAW implemen=
ts edits in its own way, some of which seem very clunky & counterintuitive =
to me. Could be some problems are arising from the older implementation of =
a separate crossfade audiofile.

Scott Fraser

<Prev in Thread] Current Thread [Next in Thread>

The University of NSW School of Computer and Engineering takes no responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the naturerecordists mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU