I would like to present these results directly to the Polyend Team. Specifically to @Mitch.
I would like to avoid free-text possibilities as they usually just causes too much noise.
Hence i’ll gladly take any improvements or additions or even entire polls that you think would be useful.
I’m sorry if it sounded offensive. I’m not trying to step on anyone’s toes - i swear 
.
As i said, i’m just looking at it objectively and logically.
And if you do that, you have to admit that you could easily dismiss this discussion as a minority complaining. Let me be clear: i don’t want to do that, which is why i’m asking for your help 
(which is what i also stated in the paragraph after that).
Also i’m not a native english speaker (i’m from switzerland), so maybe sometimes i end up phrashing things more offensive than they are meant. Germanic languages do have a tendency to be a bit harsh 
All these arguments distilled into polls l. I say no, let the people of polyend read what we say!
Make the polls if you want, but you should know that people who vote might come from the professionals, the power users, the hobbieists, the rich who 1200 euros mean nothing, poor people that gave a good portion of their money, people who care and people who don’t care.
And your poll proposals are not good I think…
We want all! Is there a priority on these?
Cynically I could argue.
I honestly get folks frustrations here, I was an OG Play customer then the Play+ and I get where folk come from in terms of the delays to bug fixes and updates, but the personal attacks to the devs ain’t on, we can have a discussion without hurling insults guys.
I love to bash out ideas on the Play, especially rhythm parts which it personally gets used for the most, I got frustrated with both the OG Play and the Play+ but have since made peace and just accepted it for what I think it’s best at.
Personally, looking back, I don’t think the wish list was or is a good idea, having wishes accepted by Polyend and then voted on by the community, just gives the impression that the top voted wishes are going to be implemented and we know thats not happening, Sample Slicing has been the most requested since Feb 2023 and nearly 2 years later there is no hints to it being implemented, the Midi performance feature feels like it’s been coming since the OG Play was released and i’m assuming this has taken up alot of the Play’s development resources.
Hopefully the Play update gets released soon, people are losing their sh!t in here 
1st world problems and all that 
Just like i could argue that you are cherry picking the things i say and not taking into account that i repeatedly offer to help and ask for help to find a path forward.
Without insulting or disrespecting anyone, for me the problem is that Play+ is not finished.
It is normal that there are some bugs at the start, but that months and months later we still have no corrections is enough to be quite upset.
And even though only 0.5% of us complain here, it doesn’t mean anything. The thing is that only one person, who is the moderator, is the only one who is not upset about the issue, so that is a bad percentage. I don’t see anyone else asking for patience and understanding… the rest are angry and rightly so.
In my case I bought Play+ because I wanted to prepare some live shows with it, and I have it in a closet, barely used because the equipment right now is defective, NO ONE would dare to do a live show with it.
tbh I wish they’d shelve the midi performance idea. I can imagine it’s pretty tricky to implement n personally I’m never going to use it.
I know I’m just 1 person so maybe it’s a highly requested feature, but I’d far prefer to get bug fixes firstly, and then after that stuff like a better synth edit UI, and sample slicing / editing. meat & potatoes stuff.
That logic seems to be incorrect. Most users don’t even bother to post on the forum. Out of overall 9.5k members, it might be that only about 100 are aware of this topic and have read it. You should have compared those 20 with the number of active forum members who visit the forum and post regularly. And that’s like, I don’t know, 100 or 200 maybe?
I’m disappointed by the slow development as well. I think the device is underdeveloped and its potential is not fully implemented. I’ve been following this thread since its creation and I was silent till today when I saw this message that I wasn’t able to not to reply to.
I still hope for the best tho. I believe the update is delayed because the development team is aware of the issue(s) and is trying hard to do something about it. There may be some severe complications with firmware development and debugging, idk. I am a software dev myself and realize that it’s not always as easy as it might seem to people who are not engaged in the development process.
Then please make a better suggestion.
What i’m trying to achieve… and what will help us all… is to have hierarchical data so it can’t be ignored. I want the voice of the overall community.
It clearly indicates the overall community sentiment and leads the way for further discussion. And then you’ll have their ear (or eyes in this case) to hear/read what the community says in detail.
Nothing is stopping us from pointing to those posts (or this post) once we have that.
It helps to reinforce your points.
But that’s democracy. You can’t expect companies (any of them) to distinguish between their customers. That’s not how the world works and definitely not how companies work in general.
We could break this part into 4 different questions. Where each one could be given a priority between 1 - 5 or 1-10 ? How does that sound?
I want to make something clear here though: i 100% agree that bugs should always have the outmost priority, especially ones that prevent you from using the product as it was intended from the start.
But new features are always a nice to have and never something you should expect. It’s a problem i see across all gear communities. People are never satisfied with what they purchase. Always wanting more. And that just not realistic.
And before you rip me apart again 
. Let me be clear:
I personally expect that the functionality that a device promises when it hits the market, to work… and if there are any bugs… that they’ll be squashed in a timely manner. And if that is not the case, i wish for open and transparent communication.
I really hit a nerve with that number haven’t i?
I am well aware of how flawed it is. It was supposed to be an example, that if we want to affect meaningful change, we need to get a more meaningful, overall sentiment from the community. And we have the means to do it. 
Again, i apologize for anyone who i have offended with it. As i stated. It is not my intention to minimize the frustration that people are feeling at all. As i have stated and tried multiple times here, i’m trying to find a way so we can be heard.
You assume i am not upset or frustrated. You couldn’t be more wrong . I am very frustrated that the devices that i love are causing frustration among it’s user base. And yes, some of these bugs have driven me nuts. If i wasn’t upset i wouldn’t post detailed bug reports. I personally want them to do well and i want them to flourish.
So if you want to accuse me of anything, then let it be that i maybe care too much
I’m not asking for patience and understanding. All i’m been asking is for a civil discussion and for us to come together to bring meaningful data/change that represents all of us.
Again - if you have a better idea than those polls (or have suggestions on how to improve them) and posting them everywhere so we can get as much representative data as possible. I’m all ears.
I don’t think it makes a ton of sense to argue about what percentage of users are complaining about bugs, etc. It’s clear that this type of topic has been one of the most active types of discussion on this forum for months.
Basically everyone I’ve talked to who has owned a Play has experienced some level of bugginess. I love the device and I have a great time making music on it, but wouldn’t dare try to use it in a live setting. Many of the crashes result in really loud glitchy buzz noises that would absolutely ruin a live performance.
I don’t think the problem is with developer competency per se. In the beginning of my career I worked on VERY small dev teams (2-5 people) on some really badly-written (by me) software. Even then, we were able to push bug fixes in 1-2 months max while continuing feature development and making quarterly releases. Delays for the main releases were common.
It’s got to be a problem with prioritization or release strategy or some other weird internal conflict. It’s baffling that no crash fixes have been released after almost a year if development has been active this whole time.
I do want to recognize that there has been SOME level of communication. The community mods have always been open about providing the approximate timeline that they have been told. Very likely all that they are permitted to say.
At this point why not just have an open beta? Or make some sort of statement and actually commit to a release date for bug fixes, regardless of whether other features are complete.
I won’t, you don’t deserve this. We don’t share the same views and it is ok. I don’t want to cherry pick on what you say. I’m trying to make my self helpful to my fellow, dissatisfied and not, owners of play(+).
Polyend should pay you for your services, they should pay some people to help with the code.
Users are not beta testers, and companies should not be run by volunteers.
The only thing I can propose to help you is to let the company, who ever is responsible read all these.
And I can help you (or better l, help polyend) by explaining the difference of midi a and b to @cjclip.
I will stop here. I love polyend stuff, I really do. Seeing my play collecting dust because there is no sufficient support just is frustrating. That’s it.
Over n out.
Does anyone knows when Elektron would fix any outstanding bugs on the DT2 or any of the announced but missing features? That’s right, no-one knows but them.
I think that one of the issues with Polyend is their openness (which I love BTW). People tend to react very badly when their expectations are not met so setting expectations just plays badly in the long run.
My advice to the Polyend team would be to avoid any future timeline promise and focus in meeting their internal deadlines and objectives. Of course you could communicate that you are working on X or Y…but I would avoid to give any hint around when it could be ready.
If the team is already pushed hard (as it seems by some of the latest releases) I would say that this strategy will be even better as it will take pressure and when updates arrive the overall reaction will be positive.
Any new updates coming to the devices will always have a negative component related to the delivery delay.
I’m not sure polls or surveys are a good thing in the music gear arena, have you been over to Native Instruments forum lately, folk are losing their sh!t on the Maschine+ forums too, NI have sent surveys and polls for the past few years asking folks opinions yet still to see the fruits of any of the surveys done
Man, I would not want in any of these guys shoes, it gotta be a stressful balancing act with a number of products to support… oh and customers
Just something in regards to wish lists, I get that some features will not be acceptable due to technical constraints on the device, but a response that probably bugs me most (sorry) is: Unfortunately, the wish doesn’t fit our current product design direction.
We don’t know where Polyend wants to take Play or the direction they’re going with it and it’s not for us to know, at the end of the day it is Polyends product and vision, but maybes the wish voting system should be scrapped and the wish list just renamed to feature requests, which the user can still create and the community can still comment on and like, as it still allows Polyend to track feature requests, but Polyend refrain from commenting as to whether the feature is accepted, a technical restraint or does not fit the product direction.
That way if new features are introduced into firmware updates they are a welcome addition to the product instead of the hope that a users accepted wish is going to be an added feature in the future.
Just my 2 cents…
I actually never been there as i don’t use NI products myself (or atleast anymore…had a 88 keys controller in the past), so no i had no idea
Regarding polls/surveys:
You miss 100% of the shots you don’t take. - Wayne Gretzky
(yes i’m a hockey fan )
If the community wants their voice heard, i think it’s a valid and productive option.
But that’s also why i feel it would be important for such a survey to be representative of what the communities concerns are. Hence why i’d like the survey questions to be created by the community.
TLDR: i’m willing to put such a survey together, but i’d like everyone’s help in shaping it, because else it is pointless.
In my opinion this survey would be a win-win from both vantage points:
Of course, what is done with the data afterwards, is up to Polyend and based on good faith.
The problem I see with that is that people are going to complain about how their request/wish didn’t make it but X did. Then again, people are happily gonna complain regardless. You’re of course free to disagree with Polyend’s view of the product direction, but when it comes down to it - you bought the product for what it is not what it can be. Would it be cool to have LSDJ style tables in the Tracker? Sure. But I get if Polyend doesn’t wanna do it for whatever reason.
One thing I think this thread as made incredibly obvious is that people run into bugs but don’t seem to report those. Maybe because it takes time and they are lazy, or they just expect things to magically solve themselves.
I’m not a member of the beta testers so I don’t know how it works behind the scenes, but I would prefer if Polyend focused on fixing bugs first, features are of course nice and all - but not as important in my eyes.
You don’t see people reporting bugs because they’ve been reported for months.
Another aspect, which could maybe be reconsidered is the option to Open Source the OS, if the developer(s) don’t have the resources to manage and maintain the project: