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

[Dave Robillard]

On Thu, 2005-20-10 at 13:19 +0200, Antonio wrote:
> 2005/10/20, Dave Robillard <address@hidden>:
[snip]
> > > 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).
> 
> I've set the environment variable DSSI_PATH (it was empty before) and
> now om see the dssi plugins! Note that om didn't complain about
> DSSI_PATH not being set.

Strange... thanks for the info, I'll check it out.

[snip]
> > 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
> 
> The port exist. I can connect my midi keyboard to the whysynth midi
> input via qjackctl or aconnect.

Hm.  I guess I'll have to get whysynth one of these days and check it
out.  Seems /very/ strange that xsynth works but whysynth doesn't.

> Many thanks so far! I will begin to play with whysynth inside om now ;-).

Apparently there's an issue with the module being so incredibly massive
it doesn't fit on the canvas.  Have fun. :]

-DR-