On Tue, 2 Sep 2014 19:42:16 +0100 Harry van Haaren <harryhaaren@xxxxxxxxx> wrote: > On Mon, Sep 1, 2014 at 6:44 PM, J. Liles <malnourite@xxxxxxxxx> wrote: > > This is something that would go into the .desktop files of > > applications as a capability > > Cool: then its time to make it work in the UI, and after that > bug-report every app that is useful with NSM and doesn't have it in > its .desktop. Agreed, I think it's doable. It is little work per-program. I think it would be sensible to check how real the performance issue is, but the mtime check Len suggested plus some caching would take care of it most of the time if the performance issue is real at all. > > Certainly I have no intention of adding any qjackctl like > > configuration features. > Which also isn't what I'm suggesting I agree here too. All I imagine is something that is able to start jack before everything else, nothing more than that. On the UI side it could be a simple field where you enter the jackd command you want to use for this session. > > Just create a ~/.jackdrc and you're done. > That doesn't work per session, and mixing / live-performance have a > need for very different JACK settings, perhaps even different > interfaces. > > It could be discussed to "highjack" ~/.jackdrc by copying an NSM > sessions .jackdrc to ~/ although a hack solution for a power-user, > I think its not a good way to go for beginners. We need something to > fix this... ideas? For my taste this solution is far too hackish. I would not expect or want any program to modify my ~/.jackdrc. If jack is already running when the programs start then the ~/.jackdrc is irrelevant. I'm still in favor of a simple jackstart program (generic if possible or especially for jack). The only issue I see with such a program is that it may be hard to tell when jack is actually started. Maybe I'm wrong and there is an easy way to tell that I'm not aware of. Maybe something in the jackd API would help? Would jackctl_server_start() work? http://jackaudio.org/api/group__ControlAPI.html#ga0ee7d8a3386503ce677f1adbd206e971 Regards, Philipp _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
