Originally Posted By: Rustyspoon#
Musocity,
Most developers, when come up with a new feature that supersedes existent, get rid of previous method. In my view, redundancy is the biggest issue with BIAB. They spend enormous resources of time tackling bugs, many of which are related to redundant methods, instead of spending that time focusing on coherency and workflow.

That's an interesting hypothesis. I think limitation of the core functions is the biggest issue, followed by user interface issues, but I do agree with you that BIAB creates new ways of doing things and does not remove the old. The only positive I could say about that is that we know users here have very different skills and goals and prefer all different kinds of workflow. Taking away something that they are familiar with and that they rely upon, even if for a better feature, might be unnecessarily difficult for them. Those of us who are active here and discuss the features that are needed may not be the best judge of that question. I think I would settle for making everything work, even if there is redundancy, but I do value your point.

BIAB 2025 Win Audiophile. Software: Studio One 7 Pro, Swam horns, Acoustica-7, Notion 6, Song Master Pro, Win 11 Home. Hardware: Intel i9, 32 Gb; Roland Integra-7, Presonus 192 & Faderport 8, Royer 121, Adam Sub8 & Neumann 120 monitors.