[LAD] Program design: C++ -> SHM -> Python

Paul Coccoli pcoccoli at gmail.com
Mon Dec 27 20:32:33 UTC 2010

On Sat, Dec 25, 2010 at 8:05 PM, Harry Van Haaren <harryhaaren at gmail.com> wrote:
> So I'm wondering if it feasible to keep the audio/other data in SHared
> Memory, and then write the GUI in Python reading
> from the same memory? Is this concidered "ugly" design? I have no experience
> with SHM, so I thought I'd ask.
> The other option I was concidering is writing the front-end GUI part using
> only info obtained from OSC, but that would
> exclude the waveforms of the audio, and lots of other nice features...

If you only run the GUI on the same machine as the engine, you buffer
your samples (via rungbuffer) to a non-RT thread that writes them to
disk.  Then use OSC to send the file name to the GUI.

More information about the Linux-audio-dev mailing list