Re: Insight needed: Perl, C, Gtk2, Audio, Threads, IPC & Performance

I tried to use Perl for audio but did not get the performance I was looking for, so I switched to C++. I noticed that a lot of my C++ code was repetetive, so I used perl to generate the C++ code using templates.

For my C++ generation code, the perl functions specify a signal-processing netlist. I used the graph modules to solve the dependencies in the netlist, so that the C++ code came out in the correct order. It works great, and the generated code is clean. It looks like it was typed in by a very patient programmer! A typical example is a 51 line perl program that turned into a 9102 line Jack application.

It should work perfectly the first time! - toma

Comment on Re: Insight needed: Perl, C, Gtk2, Audio, Threads, IPC & Performance - Oh My!

Replies are listed 'Best First'.
Re^2: Insight needed: Perl, C, Gtk2, Audio, Threads, IPC & Performance - Oh My! by Joost (Canon) on Jun 02, 2006 at 00:43 UTC
That sounds very interesting. Do you have any code lying around that I can take a look at? :-) At the moment, the graph I'm dealing with is a net of connected plugins that are mostly written in C (LADSPA plugins). I just calculate the right order once it's needed (in perl, using the Graph modules) and cache that until the the network is changed. After that the speed is acceptable - not great, but good enough for small experiments at least - since all I do is call one method for each plugin to generate a partial stream of X samples. The rest is normally handled in C. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]
Re^3: Insight needed: Perl, C, Gtk2, Audio, Threads, IPC & Performance - Oh My! by toma (Vicar) on Jun 02, 2006 at 07:10 UTC
I don't have anything that I can post right now. I used HTML::Template on the C++ code, and I was in the process of switching to Text::Fillin when I stopped working on it. My code is from the early days of Jack when it was a moving target. I hope to get back to it someday and publish it in an updated form. Our approaches are somewhat similar, and they are also similar to the PD (Pure Data) approach. The difference is that we like perl code, and PD uses a GUI instead. I don't know if you are using the low-latency linux patches, etc, but if you are not, you should visit Planet CCRMA at home. The PlanetCCRMA web site and mailing list is a great place to find help and advice on linux audio development! It should work perfectly the first time! - toma	[reply]