Re: [linux-audio-dev] LCP v0.1.0

New Message Reply About this list Date view Thread view Subject view Author view Other groups

Subject: Re: [linux-audio-dev] LCP v0.1.0
From: Paul Davis (pbd_AT_Op.Net)
Date: Mon Dec 10 2001 - 15:59:04 EET


In message <3C14ADA5.DDD5B6D0_AT_boosthardware.com>you write:
>Could someone explain in simple english how these apps are intended to
>work together please?
>
>Do I just run one version of jack and then lcp, ardour, alsaplayer,
>spiral loops, timidity, glame, pd and anything I do will be at low
>latency and ardour can record everything I play without dropouts? Can I
>tell ardour to seperate the streams into multiple tracks or do I tell
>jack and ardour just "listens" to jack?
>
>In other words what is the expected order of events in laymans terms.

1) start up a JACK server with your chosen driver (right now, just
      the ALSA audio i/o driver)
2) start up any or all JACK-aware applications
3) LADSPA hosts load LADSPA plugins
4) LADSPA hosts optionally start standalone GUI processes to
      control LADSPA plugins, communication via LCP (or http; to be decided).
      Remember: they don't have to do this. They could use no GUI
      at all, or build their own.

Every audio stream is a mono 32 bit IEEE floating point data stream
that can be shared with and tapped into by any or all JACK participants.
To record the output from SpiralLoops in Ardour, you'd just click on
the input button for the DiskStream, select "SpiralLoops-L" or
whatever SpiralLoops called its left output stream, and voila. This
audio stream is completely independent from all others. It doesn't
show up at the outputs of your audio interface unless you connect it
to a port that ultimately routes data to an audio i/o port.

--p


New Message Reply About this list Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : Mon Dec 10 2001 - 15:58:46 EET