42low wrote:Why should you use that ladish? Especially if is said it's old and no more supported. Keeping such software running is asking for problems.
Ladisch? Sound routing? Why not use Jack? Or simply alsa?
I plug in my midi-keyboard. And dedicate it to a wanted track within DAW and other music software. That's all i do and it all works fine out off the box.
That's why i never understand why some have to explore all kinds off deep technical ways and a lot off hard coding and so on. I almost always plug in en never hardcode and it works. I really don't understand.
I think that if you experiment to much it eventually will disturb somewhere. But that is/was with win to.
This is a good question. The short answer is: because things are confusing. Documentation is all over the place, there's a lot of dead projects that you don't even realize are dead, there's a lot of overlap between programs that you might think serve different purposes; there's a lot of programs that people swear by and I think "oh neat I should try this out" but then I can't even figure out what it's for or how to use it; there's a lot of confusing names.
But your steps confuse me. You say "why not use jack or simply alsa".
Well first: I am using jack, but you need a way to interact with it. I assumed that cadence and qjackctl were the two main ways to go about it. I can't, as you say, "just plug and it works out of the box", I need to set up jack, I need to tell jack what plugin to connect with the keyboard, etc. Ladish was just a tool in cadence that looked the most comfortable for the job.
So for example, you plugin and turn on your midi keyboard, and you want to play around with synth sounds. How do you tell the synth which device to use?
I recently reinstalled arch so I'm going to use this as an opportunity to have a clearer understanding and a more comfortable setup.