Hi,<br><br>I&#39;ve been trying to come up with a nice program architecture for a live performance tool (Audio looping etc),<br>and I&#39;ve kind of hit a wall:<br><br>Input will be taken via OSC, the &quot;engine&quot; will be written in C++, and the GUI is up in the air.<br>
<br>I&#39;ve written most of the engine, (working to a degree needs some bugfixes), and now I&#39;ve started implementing<br>the GUI in the same binary. Ie: its all compiled together, double-click it and it shows on screen &amp; loads JACK client.<br>
The GUI code has a nasty habit of segfaulting.. which is also killing the engine. That&#39;s a no-go for live performance.<br>The engine is rock solid stable. So its the fact that there&#39;s the GUI thread running around that&#39;s segfault-ing things.<br>
<br>So I&#39;m wondering if it feasible to keep the audio/other data in SHared Memory, and then write the GUI in Python reading<br>from the same memory? Is this concidered &quot;ugly&quot; design? I have no experience with SHM, so I thought I&#39;d ask.<br>
<br>The other option I was concidering is writing the front-end GUI part using only info obtained from OSC, but that would<br>exclude the waveforms of the audio, and lots of other nice features...<br><br>Help, advice, laughter etc welcomed  :-)  -Harry<br>