Hi Georg, the concept is comparable albeit a bit different. Unix pipes are usually established between two end-points. Say you're piping the output of one application to another.
With jack each application registers as many inputs from and outputs to the jack daemon as it needs and simply uses them. Without knowing where data really comes from and where it goes to. That decision is completely up to jack and thus to the user. You could connect one application's output to three other inputs. Or you could connect four outputs to one input. Also you could include your sound card as just another source or sink. I think the concept is pretty easy to grasp when seen on a small Screenshot: http://ncc-1701a.homelinux.net/~dennis/jack-example.png Yours sincerely, Dennis Schulmeister -- Dennis Schulmeister - Schifferstr. 1 - 76189 Karlsruhe - Germany Tel: +49 721/5978883 - Mob: +49 152/01994400 - eMail: [EMAIL PROTECTED] Now moved to the corridor: Hermes! (http://ncc-1701a.homelinux.net) (mostly German) http://www.denchris.de - http://www.audiominds.com http://www.motagator.net/bands/65 <GunPG KeyID: B8382C97> On Fri, 2008-06-20 at 21:32 +0200, Kurt Georg Hooss wrote: > Thank you. That was enlightening to me. At least, i believe so... > is it right that signal flow through jack is in some sense > similar to data flow in unix pipelines? > > sorry for this rather basic question. it would help me understand. > cheers > georg > > > > On Friday 20 June 2008 20:33:06 Dennis Schulmeister wrote: > > Hi, > > > > in my opinion the very purpose of audio-jack is equally both: to provide > > access to the sound hardware and to enable inter-application routing. > > That's because it has originally been an integral part of Ardour's audio > > engine before both were split. > > > > Within the audio domain jack plays an integrating role. First of all > > does it simplify application development because it provides an > > efficient and easy to use API. > > > > Secondly it makes sure that all jackified applications play together > > (literally). There's no problem at all to create complex signal flows > > between as much applications (and hardware) as the CPU can handle. Also > > there's no problem to have the applications synchronized to a common > > clock. > > > > Thinking about it if Linux video is really missing something than it is > > wide adoption of video-jack. > > > > > > > > Yours sincerely, > > Dennis Schulmeister _______________________________________________ Cinelerra mailing list [email protected] https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
