FOUT behavior

CH3OH · 2014-12-10T22:10:39.000Z

hey everyone

How does FOUT work? From what I see in the manual:

FOUT applies a fade out to the recording. The value is expressed in sequencer steps. The fade out is added after the recording stops. If for example recording occurs for 16 steps and FOUT is set to 2, the total length of the sample will be 18 sequencer steps.

I expect, that recorder should sample its full length + length of FOUT and then apply attenuation to the last FOUT steps of recording. So I set up my recorder as follows: INAB:AB, RLEN:MAX, TRIG:ONE2, LOOP:OFF, FIN:0, FOUT:16, QREC:16
and start manual sampling of incoming audio. I trig recorder by pressing track + AB and record 4 bar sample. When I look at this recoding in sample editor, it is indeed has length of five bars (4 bar actual sample and 1 bar tail), but last bar is not even close to the linear or logarithmic fade out, common to all audio editors. Yes, there is certain tail, but it dies too quickly and the rest of the bar is just silence. Increasing FOUT to 64 makes tail longer, but there is still a lot of silence in the last bars.
Is this expected behavior?

Alex

Ma-chew · 2014-12-10T22:36:02.000Z

From my understanding Fout is to help deal with clicks/pops at the begining/end of a looping sample and may have a shorter length then you’re expecting.

CH3OH · 2014-12-11T10:58:56.000Z

So what’s the point of setting it to 64 then? Since it still produces a lot of silence. To maintain precise sample length? I can do that with QREC and RLEN:MAX too (actually, this is the only workaround I came up with — record 5 bar sample and fade out the last bar in audio editor).