AKAIK it extends length with FOUT, adding silence after the fade, and delay FIN adding silence before the fade, without extending the length.
I’ve left fin and fout at lowest levels for both PU and flex recordings. I record 4 bar AR loops with flex and live instruments with pu’s. I don’t really ever get clicks but I feel I’m the odd one out. I don’t even trim my samples as they’re set up to instantly loop in real time.
For slices I sometimes get clicks but I just use the general amp settings on the track (no plocks) and raise the amp attack to 1 or 2, hold at 1 or 2, and release in the 40’s…
The Elektrodork part of me is strangely tempted to try different fin/fout or maybe just fin and no fout, make observations, analyze, yada yada yada, but from where I’m sitting it’s kind of an “if it ain’t broke” situation on my end right now…
2 Likes
I used to add rides to cover tape hiss. Now I add tape hiss to cover pure digital silence
3 Likes
Oh daaamn, this might explain a lot of my frustrations… I remember all sorts of timing issues with loops when using fin/fout…
Like @Open_Mike I tend to use the minimum fade settings with no timing issues, for ambient type sounds like say a sustained chord drone then I set attack a little higher to get rid of any obvious bump on the loop, I will add though that I rarely use pickups other than for capturing overdubs then grabbing stuff from the buffer to use in a flex slot, so far.
2 Likes
I did some testing yesterday, and I can confirm what @sezare56 says about the delayed application of FIN and FOUT. Those settings are pretty useless, especially when sampling looping patterns where there is some latency. The reason is that the placement of the fade will probably not necessarily line up with the placement of the audio due to the latency.
In the course of my testing, I learned some other important things. I am sharing here in case it helps anyone else.
- When you are sampling a looping pattern from, say, Ableton, there might be a little latency between the start of the sampling and the actual placement of the audio. The best remedy? Set the start point, and do a ROTATE POS TO START in the sample edit menu. This is a huge revelation for me.
- It is not neccessary to use fades all the time (duh - lol). I think the only time they are needed is for pads and drones, etc., where the tail of the sample gets cut.
- If fades are needed, then what I think is the easiest and fastest way to fade is: i) Go to EDIT screen. ii) First, move the LEVEL knob all the way to the end. iii) Then, hold FUNC, and bring START POS to end minus 0.02 to 0.05 seconds. iv) FADE OUT v) Then, move level knob to zero (important note: it maintains the same time span you selected!). vi) FADE IN.
- This last point is really important: As I have seen written in other threads, if you have unexplainable clicks in your audio, then clear the sample slot and try again. There might be some bugs in OT when sampling over non-empty recording buffers. Knowing that would have saved me a lot of frustration lol.
Thanks to all for all the help in this thread.
7 Likes
Very useful tips, Thanks!
Step V: keep hold FUNC too or not?
If you want your trim or edit points to snap to zero (which you probably do), then I am pretty sure you need to hold FUNC while turning the knobs to move the trim or edit points.
1 Like
Actually, technically you might not need to hold FUNC while moving the level knob to zero, since you are, well, moving it to zero.
My tip : Fn+Knob seems to work for active channel view only (left by default).
Set change to both channel view to select zero crossings for both channels (it selects also left channel zero crossing when there is only left, same for right).
4 Likes
One of the best and most innovative features of the audio editor in the Octatrack, you can use it for lots of creative applications, I’m surprised it isn’t mentioned more.
4 Likes
@sezare56 - Wow, I did not even know you could change the view like this. Nice.
Questions though:
If you are only viewing the left channel and are making edits, will those edits apply to both channels?
Do you have to be viewing both channels for Fn+Knob to work right? If yes, that’s pretty weird? You would essentially be unknowingly making different edits to each channel?
Edit: I just tested it, and it seems to work as I would expect; that is, using FUNC + Knob selects zero crossings in both channels even when the view is only set to the left.
I’m still curious to understand more about what you said.
I edited my post. Something you didn’t understand? I was pretty sure it was possible to select both channels with stereo view of but I tested it with attention for the first time. 
I didn’t know it was possible to select left/right too in stereo view.
1 Like
I had an RC-505 for a while, and yes, it did not click when playing back loops on the RC. But when I imported the loops I recorded on the RC-505 into a computer and played them back in a DAW (Logic in this case), the clicked so noticably that I had to apply small fade ins and fade outs on every loop.
So I assume that the RC-505 applies non-destructive real-time fade-ins/outs (something the OT can only dream about…).
1 Like
Record a loop on the OT with FOUT enabled. Save it and reload it into a project with timestretch enabled and it will be slightly out of time now, because of the extra silence inserted at the end.
1 Like
If you set trim points and save the sample, then it will load with those points. So trim the extra space at the end and save.
In any case, FIN and FOUT are pretty useless for other reasons as we described above.
Figured I’d hop on this thread instead of starting another one. I’ve been messing around with slicing up loops on the OT and I’m getting inconsistent clicking behavior when going between certain slices. However, NONE of the slices actually click when I play them on their own. If you watch the video below, you’ll see what I’m talking about. I’ve tried to search for answers on this, but I couldn’t find anything that was talking about what I’m experiencing (at least I don’t think I did). You can also see how it almost doesn’t matter how much time I leave between triggering the next note, it still clicks anyway.
1 Like
Is this a flex or static file? I have noticed it happens on static files and I sent in a bug report a few months back.
1 Like
Does that click happen when your slices are sequenced?
Static. I’ll try it on flex.
Yup.