Re: [Om-synth] om, patchage and whysynth

[Dave Robillard]

On Thu, 2005-20-10 at 09:43 +0200, Antonio wrote:
> Hi Dave,
> 
> 2005/10/20, Dave Robillard <address@hidden>:
> [cut]
> > > 1) In om_gtk, when I create a new patch, how can I add a dssi plugin?
> > > Using the menu Add-> Plugin... I see only the internal om plugins and
> > > the ladspa plugins, no dssi plugin is listed. I want to use whyshynth
> > > through om ;-).
> >
> > Sounds like your Om wasn't built with DSSI support (it's optional at
> > compile time).  Either that or you've installed your DSSI plugins
> > somewhere that Om can't find them - the console output from Om will give
> > you all the information you need on this.
> 
> As said, the configure script has found the dssi header. I've tried
> also to use --enable-dssi to be sure (but accordingly to the configure
> --help this should be the default) but the dssi are not found. The
> console output of om and om_gtk don't mention dssi while starting. How
> can I specify a path for the dssi plugins in om?

It only prints something if DSSI_PATH is not set, so I guess this means
you /do/ have DSSI_PATH set (or DSSI isn't compiled in, but apparently
it is).

Check your DSSI_PATH environment variable.  ('echo $DSSI_PATH' to see
it, and 'export DSSI_PATH="/foo:/home/bar"' to set it).

It would maybe be a good idea for me to print out where plugins are
being located in all cases....

> > > 3) If I launch whysynth with jack-dssi-host, I can't see in patchage the
> > > midi input (I mean, there's no green box on the whysynth box). There is
> > > something I can do to made the midi connection?
> >
> > Sounds like maybe your patchage wasn't built with alsa MIDI support (or
> > maybe it's so old it's not even in that version)?  Does anything have a
> > MIDI port at all?
> 
> Yes I've compiled the midi support. And lash_synth (for example) shows
> the midi input, but I want to use WhySynth ;-). The patchage vesion is
> the last tarball 0.2.3.

Try refreshing?  It does happen sometimes that patchage doesn't receive
notification of new port creations.

If it still doesn't show up, you might want to check with another patch
bay (qjackctl, alsa-patch-bay, or aconnect which you're guaranteed to
have) to see if the port actually exists.  If the port doesn't exist,
something is wrong with the jack-dssi-host/whysynth combo

-DR-