I’ve been playing around with some sample chains i downloaded but i’m getting a recurring problem.
The Octatrack locks up and I have no idea what is causing it. Each time it happens, i have just been messing with a sample chain and selected a slice to play with, then got sidetracked playing about with effects etc. Then at some point, the whole lot just freezes and it takes a reboot to fix it.
As with most of the problems i have encountered on this machine, i’m probably doing something wrong!
Any thoughts on this? Or maybe someone else gets this behaviour too?
I’m on OS 1.25D. Just trying to recreate the problem again but it hasn’t happened yet.
When i say the Octatrack freezes, i mean literally everything freezes. The screen will not change from whatever it was displaying, the buttons have no effect, and the only thing that fixes it is switching it off and back on again.
I’m using Inspektor Gadjets single cycle sample chains, which i think are popular and other people have been using without any issues.
I guess the only thing i can do is report back when the problem occurs again.
[quote=“” djenzyme""]
I’m on OS 1.25D. Just trying to recreate the problem again but it hasn’t happened yet.
When i say the Octatrack freezes, i mean literally everything freezes. The screen will not change from whatever it was displaying, the buttons have no effect, and the only thing that fixes it is switching it off and back on again.
I’m using Inspektor Gadjets single cycle sample chains, which i think are popular and other people have been using without any issues.
I guess the only thing i can do is report back when the problem occurs again.
[/quote]
Same here. On 1.25D and my OT freezes up in exactly the same way often when I scroll through and audition samples from that waveform collection during playback on the same track. It seems to happen less when I scroll and audition at a slower pace. I’m using the CF card that came with my OT, and haven’t tried using another one or looked into which samples in particular are most likely to trigger the issue.
I don’t know if I am having the same issue or I am just a noob but I started a new project and when I tried to change track level, the value does not change and a small dot appears on the top left hand corner above the bpm number, when I turn the level knob.
Same for me, got OT recently and updated to last firmware.
I’ve tested CF card which I received with the unit with https://github.com/AltraMayor/f3 tool and found a few corrupted sectors,after 7 erase in OSX they dissapeared.
But anyway after some experiments I got freeze.
Finaly I’ve bought brand new pristine card, tested it, it seems ok.
And after a few hours it got stuck again.
Freezes on loading sample during playback.
I happens on one of my set but in different folders.
I can easily reproduce it few times with fast samples changing – normal worklow choosing what to load.
Probabbly it is happen in folders with large files amount but not fully sure.
So sad
P.S. Yeah just tested again about 15-20 changes in a row and got stuck.
P.P.S Usually it is ‘loading’ stuck screen but few time I’ve got exceptions.
I’ve had this happen too, changing samples on a slot that is playing. It doesn’t always cause an error, but sometimes it does… hasn’t happened to me in a while. Maybe send your project file to elektron with a bug report.
I guess it could be corrupt sectors on the card that cause this too… who knows, maybe elektron will be able to figure it out!
One famous comrade Pavel from Russian comunity supposed it is a bug in 1.25E, I managed to rollback to 1.25B. And no frezzes yet for a while, can’t reproduce it with a lot of sample changing in a row as well (knocking on wood) yey!
glad to hear this is just a bug in the os
i’ve been having this problem ocassionally since the first week i got mine and i thought i was going to have to send it back
Tested a bit more and i can recreate this 100% of the time simply by playing a pattern then deleting one of its samples from the flex list… instant freeze!
Im really hoping this is a bug related to the one that is already being mentioned here, I’ve been away from the Octatrack for a good few weeks now and I’ve come back to this nonsense!
[quote=““Pinwale Sounds””]
I don’t know if I am having the same issue or I am just a noob but I started a new project and when I tried to change track level, the value does not change and a small dot appears on the top left hand corner above the bpm number, when I turn the level knob.
[/quote]
The small dot appears whenever your OT is transmitting MIDI. Have you checked the settings for Audio CC Out which you´ll find under project => MIDI?
If set to Ext, your knobs will just transmit the CC# they are assigned to. But not alter any parameter internally in your OT.
I’m glad you managed to fix it, however sample reloading crash still here. Actually 1.25E was my first OS, so I have no old OS created projects, and I’ve tried all kind of manipulations with CF. Finally support confirmed bug, I’m only worry they already closed ticket, but issue was not resolved. I’m developer myself and this support workflow confusing me.
