vst~ inside a standalone
Dear Collective Wisdom,
has anyone succeeded in building a Standalone with a vst~ object
included?
I have a working patcher that makes use of vst~ to talk to NI
softsynths (FM7/8 and Kontakt). Works well enough running in Max/MSP
but the standalone produces a steady stream of "error: vst~:
midievent: effect doesn't want events" messages. Audio is running.
What I've found in the docs and on the list is all about building VST
plug-ins, not about using the vst~ object inside a collective. I have
some ideas to try, but if someone has a cookbook recipe that would be
very helpful.
Thanks,
Peter
-------------- http://www.bek.no/~pcastine/Litter/ -------------
Peter Castine +--> Litter Power & Litter Bundle for Jitter
Universal Binaries on the way
iCE: Sequencing, Recording &
Interface Building for |home | chez nous|
Max/MSP Extremely cool |bei uns | i nostri|
http://www.dspaudio.com/ http://www.castine.de
At 4:45 PM +0100 12/22/06, Peter Castine wrote:
>Dear Collective Wisdom,
>
>has anyone succeeded in building a Standalone with a vst~ object included?
>I have a working patcher that makes use of vst~ to talk to NI
>softsynths (FM7/8 and Kontakt). Works well enough running in Max/MSP
>but the standalone produces a steady stream of "error: vst~:
>midievent: effect doesn't want events" messages. Audio is running.
I've found that I tend to receive these error messages if I send midi
messages to the vst~ object, before it has loaded a vst plugin. I
may be wrong, but I also thought that sometimes I might have gotten
the message if I sent midi note on messages or similar to an effect
plugin (rather than instrument plugin) that didn't recognize those
messages.
Dan
--
Dan Nigrin
Defective Records
202 Hack / PC-1600 User / VSTi Host / OMS Convert / Jack OS X
http://www.defectiverecords.com
http://www.jackosx.com
On 22 Dec 2006, at 17:09, Dan Nigrin wrote:
> At 4:45 PM +0100 12/22/06, Peter Castine wrote:
>> Dear Collective Wisdom,
>>
>> has anyone succeeded in building a Standalone with a vst~ object
>> included?
>
> Yes - http://www.defectiverecords.com/vstihost
hi dan,
out of curiosity, i just had a quick go on this myself and built a
simple standalone with vst~ and something to generate midinotes. to
my surprise i couln't load any pluggo plugins. got a lot of "error:
pp: no such object" etc. meaning that the standalone can't find the
externals... used in the plugin. (other plugins, no pluggos, work fine).
if i include the original max-patch from which i've built the vst-
pluggo, in the standalone, everything works fine.
i can also send midievents to the plugin.
i guess i'm missing to include some library to be able to load pluggo
plugins into a standalone, no?
>
>> I have a working patcher that makes use of vst~ to talk to NI
>> softsynths (FM7/8 and Kontakt). Works well enough running in Max/
>> MSP but the standalone produces a steady stream of "error: vst~:
>> midievent: effect doesn't want events" messages. Audio is running.
>
> I've found that I tend to receive these error messages if I send
> midi messages to the vst~ object, before it has loaded a vst
> plugin. I may be wrong, but I also thought that sometimes I might
> have gotten the message if I sent midi note on messages or similar
> to an effect plugin (rather than instrument plugin) that didn't
> recognize those messages.
yes, happens in both situations. but this is not limited to
standalone use of vst~.
also applies to normal max use and seems like the correct behaviour
to me.
i had situations when once accidentally i've sent midievents to a
'wrong' vst plug, i couldn't get away from the "error: vst~:
midievent: effect doesn't want events" anymore, even after loading a
vst~ that could definitely handle midievents.
i had to reinstatiate the vst~ object to get it working again.
maybe this is what peter is seeing.
greetings,
volker.
On 22-Dec-2006, at 17:40, vb wrote:
> i had to reinstatiate the vst~ object to get it working again.
> maybe this is what peter is seeing.
Reinstantiating an object inside a standalone (or any kind of
collective) is a little tricky.-
I'm releived to know that it can work and, indeed, I relaunched my
standalone after reinstalling FM8 and, Lo! Hark! Choirs of heavenly
voices with reverb and overdrive...
There may be some unpredictables in the mix, but it can work.
It's now time to pack so I'll take this opportunity to wish everyone
who wants it a Merry Christmas.
-- Peter
-------------- http://www.bek.no/~pcastine/Litter/ -------------
Peter Castine +--> Litter Power & Litter Bundle for Jitter
Universal Binaries on the way
iCE: Sequencing, Recording &
Interface Building for |home | chez nous|
Max/MSP Extremely cool |bei uns | i nostri|
http://www.dspaudio.com/ http://www.castine.de
>>>has anyone succeeded in building a Standalone with a vst~ object included?
>>
>>Yes - http://www.defectiverecords.com/vstihost
>
>hi dan,
>out of curiosity, i just had a quick go on this myself and built a
>simple standalone with vst~ and something to generate midinotes. to
>my surprise i couln't load any pluggo plugins. got a lot of "error:
>pp: no such object" etc. meaning that the standalone can't find the
>externals... used in the plugin. (other plugins, no pluggos, work
>fine).
>if i include the original max-patch from which i've built the
>vst-pluggo, in the standalone, everything works fine.
>i can also send midievents to the plugin.
>i guess i'm missing to include some library to be able to load
>pluggo plugins into a standalone, no?
hi Volker,
I got the following back from someone at Cycling (I've forgotten who
now, just saved the text clipping, sorry!) about this issue:
"There is however currently an issue with Pluggo plugins running in
applications built wiith MaxMSP with Pluggo version 3.5.4 and
greater. Because Pluggo plugs use the MaxMSP search path when they
are running inside of MaxMSP ( instead of their own search path ), if
they do not find all the externals and resources they need in the
collective or application bundle they will not load correctly. You
can get around this in 2 ways.
1. Add C74 Plug-in Support to your application's search path using
the filepath object.
2. Include the C74 Plug-in Support folder in your application."
Hope this helps!
Best,
Dan
--
Dan Nigrin
Defective Records
202 Hack / PC-1600 User / VSTi Host / OMS Convert / Jack OS X
http://www.defectiverecords.com
http://www.jackosx.com
Does your vst~ have an argument to load a plug on start-up?
I experienced similar problems with plugs not wanting midi events, exactly
as you describe, then someone suggested using a dummy plug to load at
start-up and the problems went away,
cheers
On 22/12/06 15:45, "Peter Castine" wrote:
> Dear Collective Wisdom,
>
> has anyone succeeded in building a Standalone with a vst~ object
> included?
>
> I have a working patcher that makes use of vst~ to talk to NI
> softsynths (FM7/8 and Kontakt). Works well enough running in Max/MSP
> but the standalone produces a steady stream of "error: vst~:
> midievent: effect doesn't want events" messages. Audio is running.
>
> What I've found in the docs and on the list is all about building VST
> plug-ins, not about using the vst~ object inside a collective. I have
> some ideas to try, but if someone has a cookbook recipe that would be
> very helpful.
>
> Thanks,
> Peter
>
>
> -------------- http://www.bek.no/~pcastine/Litter/ -------------
> Peter Castine +--> Litter Power & Litter Bundle for Jitter
> Universal Binaries on the way
> iCE: Sequencing, Recording &
> Interface Building for |home | chez nous|
> Max/MSP Extremely cool |bei uns | i nostri|
> http://www.dspaudio.com/ http://www.castine.de
>
>
On 22 Dec 2006, at 18:12, Peter Castine wrote:
> On 22-Dec-2006, at 17:40, vb wrote:
>
>> i had to reinstatiate the vst~ object to get it working again.
>> maybe this is what peter is seeing.
>
> Reinstantiating an object inside a standalone (or any kind of
> collective) is a little tricky.-
oh really?
hm, i'm sure _you_ will find a way.
>
> I got the following back from someone at Cycling (I've forgotten
> who now, just saved the text clipping, sorry!) about this issue:
>
> "There is however currently an issue with Pluggo plugins running in
> applications built wiith MaxMSP with Pluggo version 3.5.4 and
> greater. Because Pluggo plugs use the MaxMSP search path when they
> are running inside of MaxMSP ( instead of their own search path ),
> if they do not find all the externals and resources they need in
> the collective or application bundle they will not load correctly.
> You can get around this in 2 ways.
>
> 1. Add C74 Plug-in Support to your application's search path using
> the filepath object.
> 2. Include the C74 Plug-in Support folder in your application."
ok, thanks, i found the thread. but then i noticed i'm still running
pluggo 3.5
i know, it's time to upgrade.
v
When I try to include the folder c74 plug-in support, i click choose, but it doesn't show up on the collective editor window!
any ideas?
ok Spotlight was tripping me up...
Still haven't got my standalone working yet though :(
.
you need to go inside your cycling74/external folder and add all the
files starting with plug to your collective. It should work :-)
are you on mac?
p
On 01/03/07, Philip Reeder wrote:
>
> ok Spotlight was tripping me up...
> Still haven't got my standalone working yet though :(
> .
>
Ok - so this is how i got it working in case it helps anyone else.
You need to add every folder in the c74 pluggo support folder.
I stupidly thought it would add all folders within the one folder.
It didn't for me.
live and learn...
Thanks for the help all.
I
> may be wrong, but I also thought that sometimes I might have gotten
> the message if I sent midi note on messages or similar to an effect
> plugin (rather than instrument plugin) that didn't recognize those
> messages.
>
> Dan
i vaguely remember that this is what the collective wisdom found
out about it a few years ago.
then again, i wouldnt be surpised if there are new problems
with those NI v. 4 instruments!