Having been a software programmer and developer for over 30 years in a number of usage domains, I can see a lot of reasons why the Renoise developers would, for the most part, discontinue active development. I also understand dedicated users who wish to see programs continue to evolve, have new features added, gain market share, enhanced community involvement and growth and so on.
So, you are an IT pro of around the same vintage as myself. Nice! You would be acutely aware of scope-creep then when it comes to software. It’s generally a hard thing to push back against - though the Renoise developers have certainly got that under control.
By and large, I think we’re pretty much in agreement on these points so there’s not much I have to add to your last post.
You do mention the software developers “needs requirement” which I would call their overarching goals or remit for their product. But there in part lies the problem with Renoise, we are in an information vacuum and we as paying customers don’t know even in a vague sense what the developers want to take this software - though the lack of updates or communication is probably a pretty good sign of that.
We seem to focusing in on new features for Renoise but that is not the entire story either. Even if the Devs see it in some way as being feature complete, there’s the fact that computers are changing and Renoise isn’t keep up and that can take it into obsolescence. For example, nowadays, all my screens are HiDPI and Renoise is looking terribly ‘squinty’ on these screens. I know there are work-arounds for this particular problem such as changing resolution or zooming DPI but they are nonetheless workarounds that come with a downside such as all my apps I have running while Renoise is open are affected and issues such as that.
So even current usability seems to be under threat. Also, we may reach a point where core OS-Level libraries such as LibSTDC may change to a point where breakage is inevitable. I don’t know. This 2nd example is a little over simplified and a tad alarmist, I know but the first example of DPI holds true today.
Plus, Renoise isn’t bug-free. No software is. At least other software (DAWs in this case) I have some confidence that their bugs will be remedied. With Renoise, it’s feeling a lot like “You’ve got what you’ve been given” and you’re lucky to get anything more. I know some fixes have happened but its that damn information vacuum that is killing me.
It’s not like I’ve totally given up on Renoise. There’s still many things I appreciate about it. For me, Redux is how I’m now using Renoise but that makes it more a supplementary than a primary tool.
I got one board with Tracktion with Waveform 8. Waveform 8 without Redux would not have been worth the switch over to it as W8 didn’t offer some key fucntionality that I was getting with Renoise/Redux.
Then Waveform 9 came out with a kick-arse Multi-sampler. I stull use Redux for some certain modulations and effects but largely its W9 on its own.
I can foresee when Waveform 10 arrives next year (yes major revision every year), even those edge cases that I rely on Redux for will most like have gone away and so my need for Redux could disappear.
This is part of it. as other DAWs grow, Renoise/Redux is just going to feel longer in the tooth. To me, at least.
Fun times. Renoise has been good to me. I still love it just the same.