![Smile :)](./images/smilies/icon_smile.gif)
to all.
![Cool 8)](./images/smilies/icon_cool.gif)
reteo wrote:Wow... such a lot of vitriol, for certain.
Are you referring to my comments re: Reaper ? Not very vitriolic, IMO, but I'm sure others are more sensitive to such estimations.reteo wrote:Wow... such a lot of vitriol, for certain.
No, it was the post right after the previous one I made, re: codec_spurt. He took my first sentence as a quote and called it insightful. I'm not sure if he was referring to the whole post I made, or was simply insulting me, but the rest of his post had the feeling of him calling me psychotic and masochistic. I could be wrong, but the language he used was pretty strong.StudioDave wrote:Are you referring to my comments re: Reaper ?reteo wrote:Wow... such a lot of vitriol, for certain.
Actually, LADI has nothing to do with Linux audio problems. It interfaces with Jack in order to give you the ability to:ret wrote:It really is a matter of opinion but I personally think these LADI-based session handlers just add yet another layer of complexity instead of solving the obvious underlying linux audio problems.
I probably used wrong words but in a nutshell what I meant is that there is linux audio base system, then there's jack and now add these LADI-based session handlers on top of that. It's a mess of way too many layers when compared to mac or windows. Why can't linux audio software be as simple as those other systems are? It just doesn't make any sense.reteo wrote:
Actually, LADI has nothing to do with Linux audio problems. It interfaces with Jack in order to give you the ability to:
1: Visually direct audio between applications (which include audio drivers) in an easy-to-understand way.
2: Save and restore application loadouts, including auto-launching apps and restoring the previously-saved connection.
3: Encapsulate layouts so that they can be re-used on different projects.
4: Provide centralized locations for each project to save its data.
Issues with Linux audio should be handled by the audio driver (ALSA/FFADO). Jack is not a driver, it's just the server that handles the connections. Either way, fixing sound problems may be important, but making the redirection of audio easier and more convenient should not be ignored, either.
Whew. Thanks. Sorry, I got a bit paranoid there.reteo wrote:No...StudioDave wrote:Are you referring to my comments re: Reaper ?reteo wrote:Wow... such a lot of vitriol, for certain.
I imagine it depends on the kind of project you usually work on and your preferred approach to working with tools. If you'll adapt the problem to the tools you have, then you can often get by without learning anything new. If you love learning new things, you'll find a reason to even if there's no need. Different strokes...ret wrote:I doubt that other than some very specific situations there is no need for jack kind of routing on windows or mac.
© KVR Audio, Inc. 2000-2024
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement