On Sat, 2003-01-25 at 20:06, Bob Ham wrote:
>
> I think there's some confusion here, so I'll be very specific. In the
> .so, the _init function would go through each patch file in each
> directory and extract the information about them (eg, name, port
> descriptors, etc) and build its list of lad
On Fri, 2003-01-24 at 13:03, Francois Dechelle wrote:
> > Could you not do something similar to the vst plugin? Ie, have an
> > LADSPA_JMAX_PATH, or something, that has directories containing patches,
> > and have the ladspa .so build its list of plugins from scanning these
> > directories? I do
On Thu, 2003-01-23 at 21:23, Bob Ham wrote:
> On Thu, 2003-01-23 at 18:02, François Déchelle wrote:
>
> > > I'm guessing that Paul was wondering how you tell the LADSPA plugin what
> > > jMax patch to load. Well, thats what I'm wondering anyway ;)
> >
> > If the patch is included in the .c, then
On Thu, 2003-01-23 at 18:02, François Déchelle wrote:
> > I'm guessing that Paul was wondering how you tell the LADSPA plugin what
> > jMax patch to load. Well, thats what I'm wondering anyway ;)
>
> If the patch is included in the .c, then you tell it when building the
> plugin.
Could you not
Steve Harris wrote:
The 2 questions are related.
Is the output a .c file that can be compiled to to make a LADSPA plugin
(presumably linked against FTS), or is there an uber plugin that can load
any jMax patch?
For former would be more interesting I think, but both are very cool.
My idea w
On Thu, Jan 23, 2003 at 05:39:27 +0100, Francois Dechelle wrote:
> > oh my. no string parameters, though, true?
>
> To run a patch as a LADSPA plugin, there will a generic jMax plugin that
> loads the patch and wraps the jMax calls inside LADSPA calls (mainly the
> . The LADSPA ports will be mappe
On Thu, Jan 23, 2003 at 11:15:27 -0500, Paul Davis wrote:
> >one month we should have both ladspa inside jMax and jMax inside ladspa
> >(running a patch as a plugin).
>
> oh my. no string parameters, though, true?
Is the output a .c file that can be compiled to to make a LADSPA plugin
(presumably
On Thu, 2003-01-23 at 17:15, Paul Davis wrote:
> >one month we should have both ladspa inside jMax and jMax inside ladspa
> >(running a patch as a plugin).
>
> oh my. no string parameters, though, true?
>
>
To run a patch as a LADSPA plugin, there will a generic jMax plugin that
loads the patch
>one month we should have both ladspa inside jMax and jMax inside ladspa
>(running a patch as a plugin).
oh my. no string parameters, though, true?
On Thu, 2003-01-23 at 00:20, Paul Davis wrote:
> >IMHO, a fancy GUI for a real time effect like this one is a bit of a
> >wasted effort. You typically use this thing from your geetar and a pedal
>
> geetar? don't got no steenkin geetar. jus me an' mah old iron ufo
> drum, the latest toy to spend t
On Thu, 23 Jan 2003 10:52:18 +, Steve Harris wrote
> On Thu, Jan 23, 2003 at 11:28:32 +0100, Dave Griffiths wrote:
> > > Spiral Loops is just the most natural way to work with synced loops.
> >
> > I can have a go at making them resizable if you like. I'm probably going to
> > write a new spir
On Thu, Jan 23, 2003 at 11:28:32 +0100, Dave Griffiths wrote:
> > Spiral Loops is just the most natural way to work with synced loops.
>
> I can have a go at making them resizable if you like. I'm probably going to
> write a new spiral loop plugin for ssm soon. The fltk widget can be released
> se
On Thu, 23 Jan 2003 09:43:01 +, Steve Harris wrote
> >It might be nice if this sort of functionality melded into ssm, where
> >you could see the loop displayed around the circle... There would be a
> >visual cue then for when the loop was about to repeat, which can be hard
> >to find when the l
>It might be nice if this sort of functionality melded into ssm, where
>you could see the loop displayed around the circle... There would be a
>visual cue then for when the loop was about to repeat, which can be hard
>to find when the loop is > 10s long...
Yes, this is like dream land. I've been t
>IMHO, a fancy GUI for a real time effect like this one is a bit of a
>wasted effort. You typically use this thing from your geetar and a pedal
geetar? don't got no steenkin geetar. jus me an' mah old iron ufo
drum, the latest toy to spend time here in the studio. the most fun
you can have with al
jfm3 wrote on Wed, 22-Jan-2003:
> IMHO, a fancy GUI for a real time effect like this one is a bit of a
> wasted effort. You typically use this thing from your geetar and a pedal
> board that sends program change messages.
I tend to agree with jfm3 here... the EDP featureset and interface was
IMHO, a fancy GUI for a real time effect like this one is a bit of a
wasted effort. You typically use this thing from your geetar and a pedal
board that sends program change messages. With the PD front end, you can
replace the pedal board with anything, including results of audio
analysis (i.e. "st
>The SooperLooper LADSPA plugin now comes with PD patches!
>
>For those that might not remember, SooperLooper is a LADSPA plugin that
>emulates the Gibson-Oberheim Echoplex Digital Pro looping sampler. Go get
yes, its totally awesome, as awesome as every automatically built GUI
for this plugin
Hi Jesse,
I've CC'd the pd list and I am going to include the patches in the
PD external CVS. Last time I tried to contact
Jarno Seppnen <[EMAIL PROTECTED]> the email bounced.
Anyone knows Jarno's new address ?
Sooperlooper looks cl :)
Greetings,
Guenter
On Wed, 22 Jan 2003, Jesse Chappell
The SooperLooper LADSPA plugin now comes with PD patches!
For those that might not remember, SooperLooper is a LADSPA plugin that
emulates the Gibson-Oberheim Echoplex Digital Pro looping sampler. Go get
more info and download it at its new address:
http://essej.net/sooperlooper/
See the
20 matches
Mail list logo
