Pre-sliced recorder buffer issue 1.25H

Elektron Gear Octatrack
#1

So I finally upgraded to os H from E and my pre sliced buffers are gone. In the slice editor there is one line with start and end on it, but it’s not even a slice, it has no length. If there were no slices the OT would fall back to start points but this anomaly makes all my trigs locked to slices play silent, and in the editor it shows any slice lock triggers the non slice anomaly, which is silent…
So, deleted all slices and resliced which worked until powering off and back on, slices gone, one line anomaly back.
Next went for empty reset and created some sliced buffers and saved new project. Power off, on: anomaly back…

Anyone else seen this behavior?
I should add that I’m using the create 64 slice option and not defining them myself…

Small OS tweaks
Octatrack freezes when left alone for a while
What is Assign to Self used for?
#2

Ensure that you clear the slot, and that you don’t have a settings (OT) file sitting there, does the issue still exist?

#3

Tried that first, no dice…
Also did empty reset and new project, same same…

#4

Can you replicate in a new Project?

#5

Not trying to be rude but I’ve said twice already:
Empty reset, new project, new set even.
Replicated…

#6

Ah, sorry, I missed that, not enough coffee!

Want to ping me over that new project, and/or I’ll dig out my v1.25H machine and see if I can replicate / test / answer.

#7

Thanks Rusty, I’m all hopped up on siberian ginseng myself! I’m deep in the lab right now and don’t wanna switch out my usb’s, but when I’m done jammin I’ll make an extraction from the OT…

If you feel like it, all you gotta do is make a new project, assign a flex machine to a recorder buffer, make a recording, slice to 64… Save project…
Now either reload project or power cycle,
No more slices except a no length ghost slice…

#8

I feel like you guys are so close to describing a weird issue that pops up for me. for me, it occurs (seemingly at random) when I’m dealing with flex machines. usually when I decide to grab a quick loop of whatever I’ve been sequencing. I’ll assign a flex machine to one of the 8 tracks, but when I go to choose a record buffer, I get a frowning face icon at the bottom along with details about available memory. at least I think that’s what it’s saying. anyways, result is, the flex machine WILL NOT sample.

so I go to the memory settings, increase the available memory (I think that’s how I’d describe it), and try again. nothing.

I clear the recorder slot. nothing.

so I just end up scrapping whatever I’m doing, starting a new project and then of course it works fine. but how did I get to the point where I see that damn frowning face? what am I not understanding??

please tell me that we have some overlap here.

#9

Hi Open_Mike,

Just thought I’d give your recipe a try to see if I could recreate your issue, but wasn’t successful. The 64 slices remained as expected.

Here’s the actual list of steps I took, as there was one vital action missing from your list:

  1. make a new project
  2. assign a flex machine to a recorder buffer
  3. make a recording
  4. slice to 64
    *****4a. File > Save and Assign Sample
  5. Save project
  6. reload project or power cycle,
  7. No more slices except a no length ghost slice

Is there something different in my actions/results?

1 Like
#10

So I don’t save and assign sample because I would like there to be an empty recorder buffer that is already sliced and waiting for recording…
Out of curiosity, on your test did you end up with a sliced empty buffer or the recording you had made and sliced?
Thanks for testing…

#11

Sorry buddy but I don’t think these issues are related…
Does sound like something with the memory config or the memory could be full if you have lots of samples loaded? Dynamic recorders may be your friend…

#12

Hi Open_Mike,
I should be able to test this today. Now I understand what it was that you were trying to accomplish. I’ll run the steps again and send back my answers hopefully tonight.

#13

I’ve got some answers.

First of all, if I do not Save and Assign the Sample but simply Save the Project, I DO experience the same symptom as you: an empty recording buffer and no slices. Oddly, I was able to take a series of steps that resulted in a single S0 0-length slice, but now cannot recreate. Regardless, there was never a pre-sliced buffer after restart or Project reload.

But when I saved and assigned the sample, I was greeted with a sliced grid and sample as expected.

Does that match with you? I have never tried to save a pre-sliced buffer, so never ran into this issue.

1 Like
#14

Hey y’allzz,
Been busy runnin sound for a small festival in northern Cal, the Fractal Lake Gathering…
Haven’t slept much, good times.
I’ll get back to this soon, thanks for your replies…

#15

So, been busy lately and haven’t dove back into this, but it seems like Ritual Audio has confirmed my dilemma. Slight difference in that I always get the 0 length slice which results in silence and no defaulting to start points.
Guess I’ll file a support ticket.
For what it’s worth I’ve been moving to use start points instead of slices for live audio to deal with tempo changes and resampling, but it still would be nice to know I can pre slice a buffer if I want to.

#16

hey I just decided to look into this. When you save and assign the sample in a recorder buffer and choose “to SELF” then yes it does reload with the sample content, but it can still be used as a track recorder - albeit with whatever name you gave it rather than “RECORDING 8” or whatever.

The big plus is that the slices are still there, so it serves as workaround.

I guess that slices can only exist within content - & that’s why you just get that annoying ‘ghost’ slice when you reload a project, with its emptied recorder buffers.

I’d prefer a different kind of behavouir where the slice grids stay intact. As things stand you really have to be vigilant about this. Projects using sliced recorder buffers (which must be very common, no?) will always be broken when you return to them. Definitely not safe to rely on the working autosaved version - and the user save doesn’t help either!

Did you raise the issue as a support ticket? I’d be interested in the response.

2 Likes
#17

Hey, honestly I moved to start points and forgot about this. I’ll check if I filed a support ticket but I don’t think I did. Interesting work around, thanks for looking into this. On the E version of the os, you wouldn’t have to save sample settings or anything, you just sliced the recorder buffer and it would remain through power cycles. My project would use that as a main feature and it would always be there every time I powered up the ot. I’m now using start points because I always slice evenly anyway and they keep in time with tempo changes, so it’s actually better for me.

1 Like
#18

Checked my support log, I did not file a ticket. I’ll do it sometime soon…

2 Likes
#19

Support ticket filed, I’ll report back when I hear something…

5 Likes
#20

Confirmed as a bug by Elektron. Was recommended to downgrade to E if really needing this, first making sure to backup to a computer. No mention of if it will for sure be fixed or timeframe. I’m gonna stay on H with fingers crossed for a few more bug fix updates…

I encourage all OT users to narrow down bugs(especially with pickups) and file support tickets cause maybe if they get enough we can get some more bugs squashed before we reach legacy land…

4 Likes