I have a launch unit with no hardware issues, though an LCD with bright corners on a $2300 device instead of an infinite black OLED for a monochromatic UI is a suspect choice. OLED does have wear issues but it’s a replaceable part and likely negligible in cost difference. Cheap.
Software is still beta at best. Huge issues with multisamples and synth presets causing what I suspect to be memory buffer issues causing repeatable hard crashes
Is it possible to use the op-xy like a looper? Kind of ableton style, to record synth lines as samples and after recording seamless playback? Or at least quantized sample recording?
Not in its current state. That’s a huge letdown for me, and hopefully will be updated soon with a firmware upgrade. It’ll be great to be able to sample to a fixed length and with timestretch to go with it. It has three sample engines but as it is now, the sampling features are not quite there yet.
Done a lot of ranting on here but not shared anything I made yet so here’s a little jam I made on the train in about 15-20mins. Such a fast machine to work on!
https://on.soundcloud.com/NL5AiBawH1ygeFtD8
Just recorded straight onto phone muting things in and out.
Thanks for comprehensive reply.
I’m wondering how many of you are satisfied with your purchase.
Same here…I want to want this thing, but am scared of headaches if I pull the trigger.
There’s nothing like it but the pricing is out of touch with the current market. I’d honestly feel more connected to it if it was a better value or the firmware was as polished as the hardware, features, and workflow. A beautiful unique $3800 CAD premium boutique device that has the illusion of perfection ruined by frequent system crashes. Still, when I jam on it I smile like a dummy. If it was $999, everyone who jams would own one. At its current price, it’s almost embarrassing to justify.
@DigitalDruid i think its extremely YMMV.
not 100% sure, but it seems like everyone who is reporting crashes are users who put a lot of samples on the device from their collections. personally, i have not had a crash in a long time. never had a crash at all with 1.0.25. most of the sampling that i’ve done has been on the device itself, though i have loaded some samples from my collection.
and yea it is a very inspiring device, but even without any recent crashes, i find some of the sequencer bugs i run into very frustrating, but i am also very diligent about documenting and reporting them, trying to keep faith that TE is going to fix them all.
but then there are also some things that seem like bugs to me that might be an unfortunate choice by TE… like try using a synth engine in legato mode and tie one note to another lasting just one step.
the first note lasts 2 full steps and the note it is tied to lasts half the step it is on so you’ll hear it go back to the original note, instead of doing a glide to a a short step. its sounds really bad and its the kind of thing i can imagine TE shrugging on. could be resolved if we could adjust individual lengths of notes, but i’m not holding my breath on that one 
Wait what? You cannot adjust length of individual notes?
no… there is a per-pattern setting “length” that defaults to 50 (as in 50%) that will be used for any step you place on the step keys.
when you live record, it uses whatever length you played, but when strictly step sequencing it just uses the “length” setting and there is no way to dial it in for individual steps. let’s hope they add that because it would be extremely easy. right now holding a step and tapping the -/+ keys nudges the steps start time. they could make holding a step+shift and the -/+ keys adjust the length and it would solve it!
To be clear, I believe my crashes are from 3rd party multisampler patches and synth presets, not my painstakingly curated and modified to spec sample library.
Isn’t the PPQN resolution like 8092? Can’t you hold the note on the sequencer, and then tap the note where you want it to end (length) and then using microtiming (note + plus/minus octave keys)?
I checked, you absolutely can via microtiming.
So you cannot trig lock the note length after it’s been recorded? Really?
Are you absolutely sure that there are no options like that already? That doesn’t make any sense to me.
i would love it if there was, but i’m 99% sure there isn’t. also just tried holding a step, then holding the bar button (which brings up the screen that has the “length” setting) and tried turning it down, but it effects all notes placed with a step button, pattern-wide. based on how other p-locks work, i would think this would be the most likely way.
live-recorded notes don’t respond to changes with the “length” setting.
This is insanely disappointing
oh and in the process of doing that, i discovered a bug lol!
i had put a note on each beat (1, 5, 9, 13) and when the length parameter was set to something below 5, half the steps didn’t even trigger at all 
sadly, i stumble into these kind of bugs kinda frequently. will report it!
Read my above comment, you definitely can set a notes length and exactly where in the individual step it ends with 1/8092th precision using microtiming (or with less resolution if you extend the pattern past 64 steps)
@everbong i’m trying and all i can get it to do with the -/+ is change when the note starts, not when it ends. can you elaborate?
@everbong i think we’re either having a miscommunication or i’m being dense. i know you can change the microtiming of when a step begins and i know you can extend a step to other steps, but no combination of holding different buttons that i’ve tried has let me adjust any microtiming of the end of a note, which is handily visualized on the bar screen.
i tried pushing and holding the 1st step, and while still holding it down, pressing the 4th step to extend the note to the 4th and then with both of those steps held, adjusting the -/+, but it only adjusts the start time…