[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: starting audio applications via a common wrapper?



|--==> Eduardo Marcel writes:

  EM> On Tue, 2006-02-14 at 21:00 +0100, Free Ekanayaka wrote:
  >>I think it's a good idea, at least till a consensus  is reached in the
  >>Linux Audio community about how to manage the situation.
  >>If did something quite similar with the ALSA Modular Synth package (ams):
  >>
  >>http://svn.debian.org/wsvn/demudi/ams/trunk/debian/patches/11ams_launch_script.dpatch?op=file&rev=0&sc=0
  >>
  >>the wrapper detects if jack is running and changes the actual command
  >>line accordingly.

  EM> That's very much what I thought of doing, instead that I initially
  EM> devised writing this wrapper in C and actually trying to connect
  EM> to the daemons/drivers using their binary interfaces. 

  EM> Maybe that would be overkill and simply searching the running 
  EM> processes like you did would be sufficient  (and much simpler 
  EM> to do). The only disadvantage I see is when the sound server 
  EM> is running on a different host, like it would be the case with 
  EM> ESD or maybe MAS in a XDMCP environment.

If we found a way to detect this case  too with shell commands, then a
script would be enough for all situations.

  EM> Someone suggested we should limit the solution to jack 
  EM> applications, I think that we should always try to
  EM> solve the general problem, it's in the Debian tradition... ;)

Ok, let's respect the tradition then :)

  EM> Any thoughts on this? Shell/C program?

I'd go for shell, unless C is absolutely necessary.

Cheers,

Free



Reply to: