Finally done with my new Digitakt live set, so I’ve been excited to dive back into the XY even though I know it’s got some bugs to sort out still. Started a couple tracks last night on the XY I was super happy with, so I woke up early to keep plugging away at them. Turned on the XY and immediately got the crash below. Songs gone, samples gone, preferences all reset. Sigh…
1 Like
Damn. I’m sorry that happened to you! I’ve been pretty frustrated with my XY too… deal-breaking bugs aside, it’s missing so many essential features. Here’s to hoping they come out with a Hail Mary update soon lol.
4 Likes
damn that really is a huge bummer. everyone should just return their op-xy and buy an op-z instead. i say this partially in jest but im confident a majority of folks would be able to do everything they need musically on the opz.
1 Like
Have been using mine daily since released and only crash I’ve come across is when using CM-15 via USB. Are you confident something isn’t going on with your hardware or default project at boot?
Thanks for posting about this. Losing work is so dispiriting.
I have been using my XY every day, a lot, and I haven’t gotten any crashes. It makes me nervous, though.
Can you remember what you were doing before you shut down? I recall you mentioned using the Scramble feature may have altered something. I appreciated that information and so have not touched Scramble.
The other thing I haven’t done is load any of my own samples. I intend to, but I thought I would wait to see if they re-work the sample menu section, add nested folders, etc.
I wonder if crashes are related to either of those things. It’s very helpful when users who have had crashes post about what they think is going on with their XY. I hope TE post an update soon.
I have had it crash a few times but I haven’t lost anything. I have heard this can happen when you load too many custom samples (whatever that means). Did you load a lot of custom samples?
I’m pretty sure it has something to do with loading my own samples on it, it crashed right when I usually see the init file system message upon turning it on. It’s weird though as I loaded these samples on it last week and it’s been fine every time I try and use it until today.
No idea if it’s hardware or not at this point, too hard to pinpoint. I didn’t get a single crash at all the first three weeks I had it, but since 1.0.15 came out it seems to happen frequently. Supposedly there’s a new OS about to drop shortly, really hoping this finally makes things stable or I’m going to contact TE and return it. I’ll just keep using my OP-Z until I feel confident I can actually use my XY without losing work over and over.
2 Likes
It also happened to me 2 weeks ago when I was only loading 4 drum samples less than 1MB in total, which doesn’t seem that excessive to me.
I’ve just contacted TE to initiate a return, I’m out of patience at this point and I’d rather get my money back and wait until I know I can actually even finish ONE song on the device before I lose my work.
Super bummed, the XY is amazing on paper and I was more excited about it than an other piece of gear that’s come out in a long time.
For sure, the OP-Z is amazing and I’ve used it extensively since it came out. I was just really looking forward to the added functionality the XY was bringing to table. Oh well, maybe in a few months.
1 Like
I’m pretty sure they will fix these issues but since this is so expensive and there’s no guarantee they will that makes sense. I was looking forward to hearing your OP-XY set. I listened to your OP-Z set and it was awesome.
I’m hopeful they will fix the issues sooner rather than later too. I had a lot of ideas for the live set I wanted to make on it that I’d still like to pursue.
At the same time it’s been two and half months since it was released, and this is a lot of money to leave tied up in a device that doesn’t work as intended with no public acknowledgement of the issues. It’s easy for me to defend what the OP-XY costs, but. only if it actually works.
Ok, I’ll stop ranting now. Happy some people are having fun with it and being productive. Keep posting your work, I’ll be following along.
3 Likes
The only excuse I can think of is that it was released at the end of the year and a lot of their staff have been on holiday. But now that it’s past the holiday season they should be able to release a fix soon.
I was having this same issue last night, it was when I was copying and pasting a step. I had some chord changes I wanted on some additional steps, and it was working for most of the steps, but for whatever reason when I tried to copy to the 15th step it would crash the device every time.
Sorry dude
1 Like
I have had my OP-XY for a week or so and have experienced the power on crash only once (so far). It occurred on a freshly reset environment before I had done any work. Looking at the display that the OP posted, it looks the same as mine did. As a retired software engineer having done many years of embedded work, it looks to me as if the CPU/boot code is trying to access a resource (memory, a register, etc.) that has not yet been initialized. In other words, a timing issue that results from a piece of code being run before the code that should do the initialization that this piece of code needs done before executing. I believe TE will be able to find the root cause and fix it, but it won’t be easy since it can’t be readily reproduced through a fixed set of steps beyond powering the unit on. I am confident, based on TE’s history, that they will continue to release firmware updates that will both add features and fix bugs, though adding features can certainly introduce new bugs too.
1 Like
My op-1 field does crash too (it’s pretty rare though). I get what you are saying about a possible explanation but how/why would that result in losing all of your files for projects, samples etc? I have never worked with any kind of system that would do that upon crashing.
Without seeing the code and the power up initialization process, I could answer that. I can say that I didn’t lose anything, probably because I didn’t have any work on it yet.
I’ve had a few crashes too. One where you get a screen full of error messages on booting the unit, but when I switch it off then on again it is fine. This has happened a few times.
Twice I’ve had it crash during a session, but luckily it has auto saved the project and I’ve not lost anything.
I’ve got quite a few user samples loaded. Most in their own folders, such as a kick folder (900+ kicks, too many I know), snares folder etc.
I also use the scramble feature quite a lot. When it did crash I wasn’t using scramble.
Since I saw people saying they’ve had crashes causing work to be lost, I’ve started making backups of my OP-XY.
I wonder if it could be due to certain audio formats, bit rates, etc not being fully supported? I bought the two Rephazer sound packs and I have had the exact same issues as you: it’s crashed quite a few times (especially on boot) but I have never lost any data.
It could be. I might trawl through my samples and see if I have any corrupted ones or ones that have incorrect bit-rates.
2 Likes