Thing is its really not that easy with a large code base to add anything in an hour. Bug fixes go quicker because the code is already in place and unless it was a major cockup it can be alot quicker to fix since its usually just some re-arranging of code or fixing a few lines here or there once you track down the actual problem.LawrenceF wrote:You're welcome. Now for some off topic stuff...agit wrote:thanks did not know that
Take Reaper for example. It does a ton of things that S1 cannot do... which shouldn't eliminate the developer saying ... "Hmmm... that's a nice little bit, I'll add that in, might take a hour at most."
Honestly, for someone with the actual source code how long would it actually take to do that? It puzzles me. If I were an audio workstation developer I'd have a running list of "little easy things" like that organized by inverse level of apparent difficulty and I'd copying them into my app left and right... weekly.
They'd be calling me "Jack The Ripper".
Unfortunately, it seems that many developers kinda live in their own little bubble, some not really even looking at others work or ideas except when it's something really big or flashy that can't be ignored.
Completely new features require underlying code changes, gui changes, testing, regression testing, all sorts of things that usually span many dev and testing groups within a single company, its rarely one single dev doing everything. Whole new features even tiny ones, can still be a large amount of work. Thats also without knowing how their code is actually structured, something that may have been easy to add in one daw may be a pain in the other.
Then you also have to run it through management. They may have an entire list of new features that they require have higher priority than what some dev thinks is important based on the higher level view of where they want the product to go. If they let the devs run off and start adding every little thing they want willy nilly then they will never get done the actual new features they had planned that may differentiate themselves from competitors. They may also have contractual deadlines if they are bringing in some third party support like soundcloud, melodyne, nimbit, whatever, where they are required to have certain functionality in by a certain release date. Those would definitely have to take precedence over some side project a single dev wants to do