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

From: Paul Coccoli <pcoccoli@email-addr-hidden>
Date: Mon Dec 27 2010 - 22:32:33 EET

On Sat, Dec 25, 2010 at 8:05 PM, Harry Van Haaren <harryhaaren@email-addr-hidden> 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.
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-dev
Received on Tue Dec 28 00:15:01 2010

This archive was generated by hypermail 2.1.8 : Tue Dec 28 2010 - 00:15:01 EET