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.