On Sun, Jan 03, 2021 at 11:25:16PM +0000, Filipe Coelho wrote: > jackpatch has a user-experience problem
Out of curiosity, what is the problem? I've been using it for over 6 years and it's always worked flawlessly here. > The things I would like to improve are in regards of user experience, the > protocol can stay intact. > But please understand, when you ignore or even attack back request to make > the experience better for new users, how are we supposed to act? You could accept the decision and move on. > An export/import option is not unreasonable, in my opinion (and several > others on the same github topic too). There is an 'import at mouse' option in each track menu. Unlike Ardour, non-timeline records multichannel tracks to multichannel files, which can be used as is, so no need for a separate export function. If further conversion is required it can be done with an existing program like sox. > You do not have a use for it, okay. So what is so bad if someone else tries > to do it? Nothing, in their own project. It should be obvious to anyone who reads the web site and/or looks at the source code that Non has been designed to give a high level of functionality from a tiny code base. It's also obvious (to me) that it's aimed at users familiar with traditional Unix command line tools. Why is a developer's choice to aim at a certain type of user so difficult to accept? It's extremely presumptuous to expect a project to abandon it's fundamental design philosophy because a self-appointed 'community' thinks it should change its target user base. The amount of passive aggression and gaslighting going on here makes me very sad. The community spirit that existed when I started using Linux for pro audio work 15 years ago seems to have been replaced by an intolerant mindset that expects everyone to conform to its own idea of how things should be. John
