Slices changing position after setting?

Is this a known bug? When I am editing my slices start and end points I do a few (maybe 8 or so?) and then when I go back those start and end points have changed? Maybe I’m unintentionally hitting a button or something?

1 Like

Okay no, it’s way worse than I thought. I will place the slice then go to the next and place that one, then when I go back to check my previous one it is all changed around. Do they react to each other when they are being placed or something?

As I work I"m using FUNC+YES to preview the slice sounds. Not sure if that is causing this?

No.

Slice order can change if you delete a slice, or add a slice before another one.

No reason slices change randomly.

User error.
If you describe step by step how do you proceed maybe we can find out…

This is so bizarre, and perhaps the worst bug I’ve encountered on the Octatrack (I’ve been using it for over 10 years).

Doing some research on fixing this I stumbled on OctaChainer and used that to create the slices. When I loaded the file with the new slices they were accurate up to about halfway through the file then started going awry. I also tried editing those but kept running into the same issue with them moving around. At some point the audio file stopped playing back but only on certain parts of the .wav! Very strange behavior.

I just updated to the latest OS hoping that fixes it. Another possibility is that perhaps it is running out of RAM? It’s a long wav file (8 min?) in an already pretty stocked project file (64 sample slots used).

Going to try the new OS then also try the slices in a new project file.

If all these things don’t work I’m going to get a video capture of the bug. I hate bugs like these that literally make me feel insane.

Static or Flex track?

1 Like

Static

Is the “!” icon flashing?

I’ve had glitches with Static tracks in the past when pushing slices too far. RAM access (Flex tracks) is much faster than SD card access (Static tracks).

Issues with direct playback?
Same behavior with plocked slices ? (A sequence)

Flex are better to manipulate slices live.

The sample is too large for Flex

Possible to load up to 8m28s (16 bit) in a fresh project.

The idea is to decipher if there is Static playback problem, as you say there is a bug. Maybe a problem to read that sample directly from your card.

So if you sequence your slices with that Static, what is the behavior ?

So update…

Sorry I got tired of trying to repro this and after updating my OS I reloaded my samples that I had made slices with OctaChainer and the slices worked! I didn’t have to edit slices and deal with the bugs of doing that. So last night I was just fucking around with my noise mangler a bit but I will probably come back to this because at some point I’m going to want to make manual slices again.

1 Like

Expressive setup ! :content:

Glad to know it seems to work well now ! Personally with slices mangling with crossfader or random slices I mostly use Flex, because with Static you get clicks unless you plock slices (OT has to know which slice to pick on the card before to avoid clicks).

But with Static you can get rid of clicks using longer attack, so it can work in certain conditions…
Or just add distortion and noisy sounds. ; )

Thanks for all your help. I haven’t noticed any clicks but that’s something I’ll listen for.

Yea learning the intricacies of this method I think it’s a matter of refining my approach to both the sample prep and execution.

But I’m still perplexed by that bug. I just got that gooseneck camera holder setup so I will capture that slice bug if I encounter it again and post here.

1 Like

With weird Static slices issues, I’d also consider the CF Card quality, if it is almost full, if many files have been deleted, added…(defragmentation)

So I wouldn’t recommend Static for heavy mangling of slices, but I could play a 1h30m Shostakovich piece sliced loops with timestretch without issues…

Or 4 several minutes recordings of Hydrasynth, recorded with OT, sliced and randomly played…with longer attack to avoid clicks.

Yes please…

1 Like

My card is 64GB! I have lots of space on it. I was getting a “this card is corrupt” message on my PC though but then scandisk supposedly fixed it… so I don’t know. haha

1 Like

Just talking about my experience with original OT MKI first generation Kington 16Gb. Several previous owners. It got full, crashed, I lost everything. Worked like a charm after.

So as Static play directly from card, I’d also consider card problems.
(And compare with Flex if possible within 8m28s 16 bit limit !)

Missed your track earlier. Good stuff! Got a cosmic horror vibe.

1 Like

:smile: I guess I wasn’t in a good mood…

But I found the principle interesting to remix longish files randomly. 4 long samples, 2 tracks per sample, crossfading each other with using slides on vol, random lfo on slices. Fades in / out avoiding usual clicks with random slices.

Probably a 64 steps pattern.