1

I like to use the record buffers to glitch samples as they’re coming in.

E.g. put a record trig at the start of a pattern. Slice the record buffer into 16 slices. On beat 8, put a trig for slice 8 with a short repeat time and a retrig count of 6 or something.

This lets you do some cool effects where the sound “skips” like a busted DMA loop or a skipping CD or something.

This mostly works fine, BUT:

I often seem to lose the slices in my record buffer when I do things like “sync project to card”. It seems like what’s happening is that the octatrack is (for some reason) seeing that my buffer is (say) only 50% full and therefore deleting all slices after slice 8/16.

Even if I save the sliced sample in the record buffer to disk first, I still lose my slices.

Anyone have any suggestions here? I don’t have a super good model of what “owns” the slice data on the record buffer, so I may be missing a step to make sure that data “survives” certain operations like syncing to card.

2

I’m surprised that syncing to card delete slices settings.

Are you sure you properly saved sample settings ?

If you stop recording before the last slice, or if you change tempo to a faster one, all slices can be messed up.

You can reload the sample in AED File page, and get your slices back.

3

If you stop recording before the last slice… all slices can be messed up.

I record for 16 steps starting on the first step of a 16-step pattern. It’s impossible for me to stop recording anywhere except before the end of the recording (unless I happened to push the stop button at exactly the last microsecond). It doesn’t seem to cause any issues until I e.g. sync the project to the card, however.

Maybe it would be more useful to explain what I want to do, and then you can tell me if it’s possible:

What I want is to always be able to access a given recording buffer by indexing into it on a step (or half/quarter-step) basis. This way, I can index directly to step N of the record buffer from step N of my composition, which is important for e.g. playing glitch effects on sounds I just recorded. I guess I could also get away with indexing to the current record head of the buffer, but I don’t think I can do that on the OT.

Is there a way I can do this that is durable, and won’t get messed up by syncing my project or whatever? I can get what I want by A) recording a full 16-step recording with a 1-shot trig or something B) adding a 16-slice grid C) turning on a record trig to re-record the entire buffer every time the pattern plays. The 16 slice grid “survives” the buffer getting re-recorded. It just doesn’t seem to necessarily survive certain other operations, like saving the project.

4

You can use Start values instead of slices, slice mode off.

You can also use several rec trigs corresponding to flex trigs, and loop the lastest recording chunk. I usually put rec trigs each 2 steps.

Surprising. I need to check.

5

Both of those are good ideas - may just use them instead.

6

If you want to manipulate audio in “realtime”, I think using rec trigs is the simplest and the most efficient. Once a short recording is finished, you can manipulate it as you like, pitch +12, reverse. You can use 2 rec tracks to alternate recordings and play they buffers on the same track, with buffers sample locks. This allow constant pitch up and/or reverse.
Exemple with Amen Break as incoming signal, recorded with IN AB inputs.

Exemple with guitar as incoming audio, only source (no samples).
Manipulated with OT to create drums, bass, synthy sounds from guitar.

1 Like