Re: [linux-audio-dev] LADSPA + GUI?

2004-02-03 Thread Dave Robillard
> 'scuse my ignorance - but how does it work with VST plugins? > http://www.ohmforce.com/media/ss_OhmBoyz_funky.jpg !!! That's definately the most compelling reason I've ever seen why NOT to implement LADSPA GUIs -DaveR

Re: [linux-audio-dev] LADSPA + GUI?

2004-02-03 Thread Paul Davis
>In theory: > > VST provides a (cross-platform) library (libvstgui) that is used > to draw pixmap GUIs. The plugin code calls UI functions. > >In practice: > > Many plugins call OS specific drawing functions. > >I'm not sure how automation is handled, but I dont think UI controls

Re: [linux-audio-dev] LADSPA + GUI?

2004-02-03 Thread Steve Harris
On Tue, Feb 03, 2004 at 03:31:23 +0100, Dave Griffiths wrote: > > Its not finding a way thats the problem, its getting people to agree > > on one. > > This again :) > > 'scuse my ignorance - but how does it work with VST plugins? > http://www.ohmforce.com/media/ss_OhmBoyz_funky.jpg !!! In theor

Re: [linux-audio-dev] LADSPA + GUI?

2004-02-03 Thread Dave Griffiths
On Tue, 3 Feb 2004 14:18:59 +, Steve Harris wrote > On Tue, Feb 03, 2004 at 08:49:49 -0500, Dave Robillard wrote: > > On Tue, 2004-02-03 at 03:38, Uwe Koloska wrote: > > > Dave Robillard wrote: > > > > If you really want to make a custom GUI for your plugin, nothing's > > > > stopping you from

Re: [linux-audio-dev] LADSPA + GUI?

2004-02-03 Thread Steve Harris
On Tue, Feb 03, 2004 at 08:49:49 -0500, Dave Robillard wrote: > On Tue, 2004-02-03 at 03:38, Uwe Koloska wrote: > > Dave Robillard wrote: > > > If you really want to make a custom GUI for your plugin, nothing's > > > stopping you from writing a simple jack/ladspa host that just takes > > > input, r

Re: [linux-audio-dev] LADSPA + GUI?

2004-02-03 Thread Dave Robillard
On Tue, 2004-02-03 at 03:38, Uwe Koloska wrote: > Dave Robillard wrote: > > If you really want to make a custom GUI for your plugin, nothing's > > stopping you from writing a simple jack/ladspa host that just takes > > input, runs it through your plugin, and outputs via jack (this is really > > eas

Re: [linux-audio-dev] LADSPA + GUI?

2004-02-03 Thread Steve Harris
On Mon, Feb 02, 2004 at 02:25:54 -0600, Jack O'Quin wrote: > > If one does not use the GTK application, then all what is available > > are controls provided by the host. > > Nice. Personally, I think a socket interface would be better, though. OSC! that way you make LADSPA plugins inside hosts O

Re: [linux-audio-dev] LADSPA + GUI?

2004-02-03 Thread Uwe Koloska
Dave Robillard wrote: If you really want to make a custom GUI for your plugin, nothing's stopping you from writing a simple jack/ladspa host that just takes input, runs it through your plugin, and outputs via jack (this is really easy BTW) and putting whatever UI you want on it. Then your plugin w

Re: [linux-audio-dev] LADSPA + GUI?

2004-02-02 Thread Dave Robillard
On Mon, 2004-02-02 at 14:52, Juhana Sadeharju wrote: > What about the following idea? > > My LADSPA plugin would allocate a segment of shared memory from "/dev/shm". > That is possible because most likely all Linuxes have that device. > Then somehow I create a backdoor for LADSPA controls. The bac

Re: [linux-audio-dev] LADSPA + GUI?

2004-02-02 Thread Jack O'Quin
Juhana Sadeharju <[EMAIL PROTECTED]> writes: > What is "/dev/shm"? How it is used? "df" shows: > none 62812 0 62812 0% /dev/shm On many systems it is a mount point for a tmpfs filesystem. This is required by some POSIX shm implementations (shmopen(), etc.). I

Re: [linux-audio-dev] LADSPA + GUI?

2004-02-02 Thread Paul Davis
>My LADSPA plugin would allocate a segment of shared memory from "/dev/shm". >That is possible because most likely all Linuxes have that device. >Then somehow I create a backdoor for LADSPA controls. hosts are responsible for allocating memory for LADSPA controls.

[linux-audio-dev] LADSPA + GUI?

2004-02-02 Thread Juhana Sadeharju
Hello. What is "/dev/shm"? How it is used? "df" shows: none 62812 0 62812 0% /dev/shm What about the following idea? My LADSPA plugin would allocate a segment of shared memory from "/dev/shm". That is possible because most likely all Linuxes have that device. T