On Sun, 2004-08-08 at 01:04, Russell Hanaghan wrote:
> On Sat, 2004-08-07 at 18:16, Dave Phillips wrote:
> > Russell Hanaghan wrote:
> >
> > >>Also, please give me some more detail about how you're launching the plugin.
> > >>
> > >>
> > >
> > >vsti, namely Hyper Canvas, is in /usr/lib/wine directory. Name had a
> > >space in it so I truncated it because clearly fst want's it that way.
> > >Then with Wine running, from a shell as user "jack_fst HyperCanvas"
> > >Jack_fst is responding...If jack isn't running, it complains.
> > >
> > Okay, a few things:
> >
> > Are you starting jack_fst from /usr/lib/wine, i.e., from the same
> > directory as the plugin ?
> > I removed the spaces too, it works fine.
> > You don't need to start Wine. These applications (jack_fst, vsti) make
> > use of libwine's functions, you don't need to run Wine before starting
> > jack_fst.
> >
> > Try these steps:
> >
> > Make sure Jack is running (I use Rui Nuno Capela's qjackctl).
> > Open a terminal, enter this command from your home directory prompt:
> >
> > jack_fst /usr/lib/wine/HyperCanvas
> >
> > Let me know what happens.
>
> I use qjackctl too..currently 2.9. Couldn't live without it!
> Yep..tried using the full path to the plugin in about round 2. Does the
> same thing.
>
> I had to break down my system for a gig tonight but when I boot it up
> tomorrow or the next day, I will do as you suggested previously and pull
> the Wine hairball....yes...thats "hairball" {'cause that name just seems
> more appropriate with Wine) of the same version you have and try to
> compile it. Seems logical that if I use it, that narrows down what it
> _isn't_ that is causing the problem. {if that makes sense}.
>
> Oh...and Thanks one more time for persisting with assisting! One of the
> many things I like about Linux AND it's users!
{sharpening up the knife with which I intend to plunge into my heart} :)
So I built the version of Wine from Kjetil's site that you are using.
All went pretty smooth. Wine works...at least with the usual
Minesweeper, etc.
I then rebuilt fst and Jack_fst against the new install of Wine. Moved
my HyperCanvas Dll into the new Wine directory which is now
/usr/local/lib/wine. Fired up Jack with high hopes and {make fast
deflating balloon noise here} Fubar! Same thing...
$oz@fx jack_fst /usr/local/lib/wine/HyperCanvas.dll
Can't load plugin HyperCanvas
All the builds were clean with minimal probs...had to set
PKG_CONFIG_PATH for jack_fst to configure...
Anymore suggestions before I book my room with the rubber wallpaper at
the silly farm? :)
R~
>
> R~
>
> >
> > >Dig it! I wasn't slamming you or the quick toot...and I think you know
> > >that...and I am greatful it was there at all because frankly, it's the
> > >ONLY reference material for any of the vst implementations out there!
> > >Just saying it would be nice to cover the stuff like "oh...BTW, here's
> > >what the hell ./mkdirectories, or whatever it was, means and it's bloody
> > >well not there! :) That one cost me an hour!!!
> > >
> > No slam taken, I think you're being pretty patient with the whole thing.
> > I'd have given up a while ago... ;)
> >
> > The tutorial should be wiki-ized. I wrote it testing libfst 1.5, the
> > mkinstalldirs bug's in 1.6. I do try to be specific about version
> > numbers tested, but I don't have time to keep the tutorial up to date.
> > There is a small but very active community of VST/VSTi plugin testers,
> > and I would rather see the users keep the tutorial current. Wikis seem
> > like a good way to maintain things like the toot.
>
> Agreed. IF I ever get this blasted thing working, I'll be at least able
> to share my experiences on MDK and how I got it to
> work....See...OPTIMISM! :)
>
> R~
>
> >
> >
> >
>
