I’ve been on the early beta team for many many music products over the years, and even with very knowledgeable and experienced testers there’s always things that you can’t account for. Different use cases, different sample types each prefer, different computers being used to interface with the gear, hardware issues that don’t happen to each unit, component changes in manufacturing that don’t get communicated properly to the developers, unknown regressions in certain software updates, what color socks you have on, etc.
Plus sometimes end users just come up with workflows you never even considered while testing, musicians tend to think outside the box a lot
It is a little strange that so many people are having issues with sample management and transfer though on the XY. And just how difficult it’s been to replicate those issues even when you have access to the exact same samples. Hopefully they’re getting close to sorting out these bugs soon.
I just finished my first full song on the XY. I actually first sequenced it on the Z a few months back and eventually moved it onto my XY, where I was able to bring it much further along than I could with my Z.
I did ~10 vocal takes, made a processed composite track in Logic Pro, then ran the processed vocals back through the XY.
It was quite the learning process!
The result isn’t a masterpiece but it really reflects the direction I want my music to go: loud messy drums, layered synths, and mopey vocals.
The only problem with creating Software and Hardware products are the Users.
If there were no Users, there would be no problems.
I hope TE fixes their Bugs, cause I really want to feel like the OPxy was a good investment now that my return window has passed.
. Where’s our Sample Slicing/Chopping
. Where are my nested Folders of my onDevice Sample Library
. Where is my Stable File Transfer UX
. Where is my faster loading Samples and MultiSamples
. Where is my Stability on device when using longer Samples and Multi-Samples
. Where’s my Bluetooth stability to insure connections to iPadOS remain locked and sustained
. Where’s my proper ADSR on a Per Sample Basis in the DrumKits (Global ADSR…really?)
. Where’s my SAMPLE CHOP Instrument (maybe a better solution to doing it in the DrumKit)
. Where’s my Hope?
. Where is Waldo?
No but clearly I’m here because I’m looking to see if it’s time to upgrade. That answer is a hard nope. I am trying to figure out how so many issues could have slipped through. Like you and @Tarekith I have been a part of a couple beta’s and have never seen something as bad as this.
I own quite a bit of gear, and if I am being honest, the OPxy release has probably been the worse experience I’ve had with new gear.
I’m not sure how such basic things like Sample Slicing, Sample Library Management and overall stability slipped thru the cracks on this device. I’m a pretty basic user who has mastered doing a lot with a little, and the fact that I am encountering bugs and crashes is just mind boggling to me.
I am hopeful that TE fixes all of these issues, as I truly see the potential in this device.
But it was a rather bitter pill to swallow, forking over, over 2K from something that shouldn’t have shipped until it was more stable.
TE needs better QC and QA when it comes to testing…or stop trying to do too much with the little resources you have…because ‘ugly’ issues are materializing for us, your customers.
Honestly, I think the S-4 release was abysmal… after almost a year it still says “coming soon” when you press certain buttons.
But fair point, the device was not ready for prime time, TE took a hard decision.
In my daily work I work as a mechanical engineer and I can tell you that delaying start of production is devastating for a product release, millions of dollars in the trash… TE probably had already set out a start of production when releasing it for Beta testing and delaying that release would probably cost them millions…
the OP-Z was delayed by 2 years if I’m not mistaken and that really put a dent in them.
I fully agree with most of your points. The main issue is though that us as consumers still purchase devices even when they’re in a state like this and the manufacturer gets rewarded either way. Same as pre-ordering games, etc. The XY was selling like hotcakes before Christmas. I’m sure some people in TE will have some nice fat bonuses coming up.
Either way there was a deadline for the device launch and it was launching without being fully ready, or even with a manual. People then buy the device anyway. I do think that over the next six months we’ll see a much more stable device with a few more features, but tbh even as it is, it’s very immediate and fun to use. My Field is looking very lonely lately.
The problem with them is they don’t communicate properly either.
For the KO 2, @tedavid joined the thread a couple of times, worse… he made some promises (resampling) and then silenzio stampa.
They should address this, and if you ask me, at this premium price where everything was expected to be flawless, they should offer something in exchange. Dunnow… here’s a voucher because you’re unwillingly a beta tester. A token of trust. Or smth.
When I got my Omega Speedmaster after years of debating and stuff, it worked as advertised. And for that amount I wasn’t expecting less.
Yeah absolutely. Not equally enough as delaying a full launch. Just keeping a manufacturer on hold costs a fortune, because they are expecting an ROI of the investment in tooling, assembly stations etc.
Then you have sales, logistics, marketing etc. all being put on hold.
Not sure how TE actually works but I’m assuming the software should’ve been written way before production of the actual hardware and tested internally in a simulator or on a hardware prototype.
Most of the issues are software bugs.
Edit: I was contemplating returning it too. Not sure if Thomann will accept it though. It’s a flawed product. Even if software only.
Not necessarily. Most people I’ve seen complain about issues ended up returning devices within a shops return window. These devices are going to be sold as B stock usually, but not returned to TE with issues. TE isn’t loosing any money there as the devices would have been sold wholesale to the shop.
I’ll have to revisit how the ADSR works in the DrumKit. I’ve put the XY on the shelf because of its poor Sample playback abilities and lack of Sample Library management. FieldKit crashes almost routinely when transferring Samples to the XY.
I get frustrated whenever I hear Popping on my Samples during Playback even when I adjust the the Attack to resolve these pops.
The fact that Samples continue to POP on my manual chops is just maddening to my ears.
Im not sure about this myself. The Blackfin processors are very specialised and even though I work in software development, I’m not sure it would be possible/practical to fully emulate the device for development and testing.
Fair enough. At the same time if you’re going to release a device you know isn’t 100% stable or ready to be used on a stage, you need to let people know that some how. I get not having all features included early in a release, but the device shouldn’t lock up, crash, or erase your data either.
Anyway, I’ll bow out again and not let this get me worked up. I already voted with my wallet and returned mine. Just annoyed as I love the XY if it was just stable enough to use.
