I'm saying it's unlikely to change because it's been implemented the same way on multiple instruments. So, Dave is unlikely to change one instrument's operation, making it different from the others, and even less likely to make that change across multiple instruments because a handful of people would like it to work differently.
Sorry if my response sounded dismissive. The nature of forums is that things get repeated again and again and again. We've answered that question multiple times, and the answer remains the same so it'd be better for people to refer to the previous answer rather than asking again.
Features get added based on a number of things. In no particular order but not limited to, ease of implementation, available code space, popularity of feature, time available for OS updates. As a synth fanatic and fellow consumer, I empathize with your frustration and I completely understand how hard it is to be told "no, it won't happen" when it's seemingly such a simple thing. I repeatedly go through that process during the design phase of every synth we make, and without fail every time we update any OS. I am the customer's voice, and I push hard for features that are popular as well as features that I would like to see.
However, at the end of the day it's not up to me and there are many complex variables that go into the decision-making process behind the scenes. We're a small company with limited resources and that means not everything that people want will get done. We're not in a position to "just hire more programmers", "open-source the code", or any of the other common recommendations that follow that statement. You'll just have to trust that we are operating as efficiently as we can given the size of the market.
I will reiterate a point that has been made multiple times by DSI and other musicians; please do not purchase an instrument based on the features *might* be added in the future. That not is an expectation you should have, you should buy it for what is right then. It is reasonable to think that if something is broken and stifles workflow that it should be fixed, and we're good about that. But, as usual everyone's personal feature request is always "the most important one" so it's important to remember there's a lot of competition for that request. If you don't like how something is, do your homework and see if it's like that on any other instruments we make, because if so it's not likely to be changed in your instrument.
I know a synth is a big purchase. None of this is being said to minimize the money you've spent. Regardless of cost, feature additions in hardware synths should be looked upon as bonuses, not as expected because you bought a product. We don't run a subscription service and we're not selling software instruments. I know people have come to expect many rapid iterations of software releases as the norm, but that's not our business model.
Any OS changes take a lot of resources even for seemingly simple things. The older a synth or the more mature the OS is, the less likely it is to be updated with new features. The Prophet-6 has a fairly mature OS at this point, so knowing how the company operates it's easy for me to give an answer with a reasonable degree of certainty. I'm not expecting everyone to like the answer, but I'd rather have you guys know the real answer instead of promising something that may never come.
Also, the forum should never be treated as somewhere to make definitive feature requests or bug reports. We provide the forum first and foremost as a place for musicians using our gear to collaborate and discuss. It's also a place to interact with DSI, though on a more limited and irregular basis. The only decisive way to ensure your request or bug has been heard is to contact us directly. We'll give you feedback, let you know that you've been heard, and add your bug or request to the list.
18 Replies
8090 Views