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.
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.
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).
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.
@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.
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ā¦).
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.
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.
Weird. I dont get that on my MK1 .
Flex and static should behave the same, the only difference is flex can keep up with fast modulations ( from LFO or xfader) more efficiently than static.
With whatever sampler I worked even in a DAW I often select a small section at the beginning and end of the sample and apply a fade in and out respectively.
I didnāt notice any noticeable click compare to other sampler, it all depends from the source material.
