I’ve tried this on flex and static tracks. Slice mode enabled, length set to 1, slice mode on the pads… I’ve tried manual slices that don’t overlap, as well as grid mode, and also with/without auto zero crossing.
When I slice a drum loop, it plays slice 1 on pads 1 and 2, even though the waveform displayed is correct (start/end of 1 when pressing button 1, start/end of 2 when pressing button 2). then, all of the slices are offset, i.e. pressing button 3 plays slice 2 but shows start/end of 3, pressing button 4 plays slice 3 but shows start/end of 4, etc.
I’ve also noticed when setting up playback triggers that it does not reliably play back the right slice. sometimes, I set it to SL2 and it plays SL1, other times it plays SL2. this cascades forward to all slices as mentioned above.
I’m a new Octatrack user so forgive me if this is a noob pitfall, but i’ve searched the forum and internet and found no mention of this! All of the YT videos I’ve seen on slicing work as expected, so I’m not sure what I’ve done wrong or if this is a bug.
I think that the behavior would be a little different but if the drum loops are samples which you added to the card and were not recorded directly into the machine, that it wouldn’t hurt to check whether or not your samples have the correct sample rate for the OT.
Hey all! thanks for the suggestions, I’ll try to run this to ground soon. There were no LFO’s assigned to sample params, only the default pitch assignments. It has been an odd problem. The samples were “loopmaster” drum loops that came on the CF card on my used unit, and were 16/44.1 samples. I tried dubbing the loop to a new flex track in the same project, and that one worked properly. I also tried other “anniversary edition” samples, and those worked properly too.
@sezare56 - I had tried creating a new project and using the same sample, and the problem persisted, so I wouldn’t guess it’s a scene assignment - I’ll need to learn more about assigning scenes to slots though! Maybe it was that.
When I browsed the CF card, I did notice an .ot file accompanying the .wav file in the directory, I deleted that - around the same time I did get the loop to work but not sure if that was the cause.
Lots to learn on the ol’ Octa! TBC… Thanks to all, you’re a very helpful bunch here!
The .ot file is where slices and other sample settings are saved. Deleting the file basically deletes all sample settings. Deleting all slices, creating a slice grid and switching on slices in source setup should be all that’s needed for proper slice playback…
I also have the Loopmaster samples…but I don’t know if it’s against copyright if you’d upload your sample with the .ot file. Then we could check if it works on our machines.
I already deleted the .ot file unfortunately. I suspect that maybe I had loaded the sample sometime at the start of my trying out the unit in a stupid way, instead of adding it to a slot, and it placed that file there, and then when I tried reloading it, it was reading that data? I think the first time I loaded it, I loaded it directly on a static track and tried slicing, which I have since learned is not the way to do it. I opened the file in text edit and it had maybe 12 chars in it, so perhaps that was just one slice.
is it normal for .ot files to be stored in the shared AUDIO folder of the set alongside the .wav files? it was the only one in there, though it was also the first audio file I loaded up. That .ot file seems like the most likely cause of the issue. I’m still wrapping my head around buffers, slots and how to manage audio files in a project.
The .ot files are saved alongside samples which is by default the Audio folder, so that’s normal.
I get that you deleted the original .ot file, but when you sliced it again and saved settings, a new .ot file was created and if I understood you correctly, the issue persisted.
But I don’t think the sample settings could cause such an offset anyway…it’s weird. an active scene would override slice selection completely (=it would always play the slice selected by the active scene).
An lfo could do that, I guess…are you 100% sure all lfo’s are set to zero or don’t modulate the sample start parameter? Also no scene active? Scenes can control lfos. (Function + Scene A or Scene B button to mute scenes)
I’ll try to get my OT to produce an offset on slices, maybe that helps finding out what’s going on.
Definitely 100% sure the LFO’s were not assigned to sample start, and pretty sure they were at zero too. they were in their default state.
let me see if I can reproduce this, I may have cleared out the problematic machine and saved the project. I’ll check the scene config too, that could be it.
If I have a sample that’s used in different projects and sliced differently though, it doesn’t save multiple OT files to the audio pool, does it?
I think there’s always only one .ot file for each sample (you can of course save copies and have different sample settings this way), but the slices are actually part of the slots I think, because you can load the same sample twice into different slots and even pre-slice slots so that a sample without slices gets assigned the slice grid of that slot…
@sezare56 Please help! My brain is turning into a pretzel Are slices saved in .ot files ot in slots?
Both ! With SAVE SETTINGS slices are saved in .ot files, but slots settings are maintained after changes, and can be saved with parts / banks / projects so they can be reloaded.
You can also reload .ot file settings in FILE menu. These settings are automatically loaded when you load a sample in a slot…
This sounds like what might have happened - try as I might, I can’t reproduce it now that the audio pool OT file has been deleted.
I did try setting a scene with STRT = SL1 and that just locked it to SL1 for all slices, no offset. I think it must have been overlapping slices, one that came from the .ot file in the audio pool, and then the set of slices I was trying to make. Odd that “clear slices” didn’t clear them all though, or maybe it gets reloaded.
I did find an interesting bug in the course of that though, if you set a scene on B with retriggers set to, say, 3, you get 2 retriggers on A no matter what. I even tried hard-setting retriggers to 1 on A’s scene but still got 2 retrigs.
Thanks all, I’ll reply here if I manage to hit it again in a way I can reliably reproduce!
Are slices saved in .ot files ot in slots?