Yes I do. When I build liquidsoap to enable jack audio recognition, it needs soundtouch.
I don't mind that I have to custom build it, and that I might not get the same support that others who don't use it might get, but when I am told to do a custom build myself and the packages don't include it it doesn't exactly make one feel all happiness and joy. I make all my apps jack-aware so that I can easily swap feeds in a graphical patchbay rather than having to code or use telnet to make changes. Using different sinks and sources and crosspatching them is a lot easier using jack. It also works for recording streams that one can connect to, if the app that is the source happens to be showing in the patchbay it is a simple drag and drop to record it. Romain Beauxis wrote: > Hi! > > Do you need soundtouch? It used only for very specific operators.. If > not then simply disable it :) > > R. > > 2011/6/22 VE4PER/ Andy<[email protected]>: > >> >> Those are the two I used previously Romain, and both caused liquidsoap final >> install to fail the final make install due to "missing soundtouch" all the >> included libs etc and soundstrectch were installed but a file the liquidsoap >> install was looking for ( being "soundtouch") was missing. >> >> I tried both soundtouch files twice and both attempts on both files , both >> the deb and orig packages showed a successful soundtouch package completion, >> but caused liquidsoap install to fail due to the missing 'soundtouch' file.. >> >> >> -----Original Message----- >> From: Romain Beauxis<[email protected]> >> To: VE4PER / Andy<[email protected]> >> Cc: Brandon Casci<[email protected]>; savonet-users >> <[email protected]> >> Sent: Wed, Jun 22, 2011 4:56 pm >> Subject: Re: [Savonet-users] making a .deb package >> >> Hi Andy! >> >> 2011/6/22 VE4PER / Andy<[email protected]>: >> >>> I have limited experience with the PACKAGES file as I need to use it to >>> enable the inclusion of JACK AUDIO CONNECTION KIT. >>> The packages file sets up the options one wants installed then the >>> bootstrap incorporated the changes and the configure, make,& make >>> install after that did the normal install, as long as all the >>> dependencies were found. I don't know why all the options aren't >>> included as default, if one doesn't use them it is only a bit of extra >>> disk space used. If one was in a position where one had to remove >>> something then they could go through a custom build. >>> >> Custom builds of liquidsoap are generally quite tricky, in particular >> for users that just want to enable one feature.. >> >> We generally believe that, when building a custom liquidsoap, it is >> good to only enable the features that you want to use. First, it >> reduces the install/build complexity by reducing the dependencies you >> need to install and second it makes it easier to debug and report >> issues in case of issues. >> >> >>> Did you happen to find a source of 'soundtouch' when you did the pakages?? >>> >> Do you mean the sources of the C soundtouch library? For this one, as >> for all other external dependencies, we the developpers use mostly >> debian. Thus, the sources of those dependencies can always be found by >> looking at the corresponding debian package. In this case here: >> http://packages.debian.org/source/sid/soundtouch >> >> Have great day! >> Romain >> >> ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
