From: Chris C. <ca...@al...> - 2009-07-03 06:45:42
|
On Thu, Jul 2, 2009 at 8:31 PM, D. Michael McIntyre<ros...@gm...> wrote: > Looking at that script, there is nothing in there to make TiMidity send its > audio through JACK. In fact, now that I think about it, for this to work, > JACK would also need to be run as a fake daemon process, and it would need to > be started *before* TiMidity in order for TiMidity to communicate with it. These days, the JACK client library will automatically start the JACK daemon if it isn't already running, when an application tries to connect to JACK. There are some exceptions -- e.g. an application can ask for this not to happen, and it won't happen with RG 1.7.x because that uses an older JACK client API. I don't know about Timidity; this might not be what is actually happening there, it's just a thought. And of course it only works if starting JACK without any particular configuration and with the default audio device happens to work for you on your hardware. Chris |