VST creation crashes.
More questions in my continuing struggle to jump into the deep end in MAX.
I’m working on some very complex set-ups with the intention of turning them into VST instuments. I’ve found something that reoccurs and I’m wondering if it’s something that I’m doing wrong, or if there is a bug or OS compatiblitly issue.
The problem: I’ve built a complex set-up that uses patches within patches (i.e. Encapsulated thingies). When I convert it to a VST, the plug in will crashes the host. IF I de-encapsulated everything, it works fine. So, I’m thinking, obviously this has to do with building the VST instrument properly, but after looking at the tutorials, and searching here, I haven’t found an answer.
Could someone clearify the right way to build a VST that uses Encapsulated Patchers? I’ve tried saving the Encapsulated Patches as seperate programs and "Including" them; I’ve also tried Including the folder that contains them, and both get the same crash response.
bpatcher and abstractions will include them selves when a plugin is Build… I have had no problems so far including all kinds of material inn my pluggos…. the only thing i found to be very buggy in plugins is the Ubumenu…
could you post an example, showing the problem ? so we can reproduce ?
I seem to remember reading somewhere that ubumenu is not supported in
Pluggo’s because of that "thou shalt open no other window but me" thing that
is written into the vst standard,
> The problem: I’ve built a complex set-up that uses patches within
> patches (i.e. Encapsulated thingies). When I convert it to a VST,
> the plug in will crashes the host. IF I de-encapsulated everything,
> it works fine. So, I’m thinking, obviously this has to do with
> building the VST instrument properly, but after looking at the
> tutorials, and searching here, I haven’t found an answer.
A crash always points to some kind of bug… Its maybe not your fault.
But as it seems, you can reproduce it. Then its time to send the whole
patch to firstname.lastname@example.org. And give clear instructions how to
reproduce the crash. If you have different hosts, let them know if the
problem occurs everywhere or not.
They will look into your patch and maybe find a way to at least prevent
Just encapsulating portions of a patch should not lead to crashes, it
might change the way the patch works, if you use some sophisticated
pattr addressing, but that would only render the patch non-functional…
Or did you encapsulate a thispatcher object? Just leave it out…
Usually it should not change anything.
   
\ /|() ()|
))))) )| | |( \
/// _/)/ )))))
14, Av. Pr. Franklin Roosevelt,
94320 Thiais, France
Phone at CCMIX +33-1-57 42 91 09
Is there a way you could zip the patch and make it downloadable somewhere?
Ummm – definitely change all the umenus so that they are in scroll mode.
Send us more details – platform, hosts etc. You also do not need to loadbang the windowsize message into plugconfig, it is saved in there after the first time you do it.
Ah… yes, sorry about that. Here…
and follow the link to ‘Client Access’.
Type in ‘maxhelp’.
That should open a window that gives you the option to download the Max patch as a text file. Let me know if you have any troubles downloading.
SOOOO one more thing… a drag down menu is a dangerous idea? I didn’t encounter any problems exporting the ‘umenu’ (pop up) items. They actually seemed to work fine. But, they might be part of the bigger complication.
My main system is a Mac G5 Quad running OSX 10.4.5 but I’ve had the same problem on my cute little G4 laptop running 10.3.9. The host is Plogue Bidule (www.plogue.com).
Thanks again all. This is what the internet was meant for.
Don’t confuse umenu with ubumenu; umenu (the one you’re using) is safe for
use in Pluggo’s – it’s ubumenu (the square cornered one) that’s a problem in
And in answer to your question about using pcontrol to open a sub-patch;
probably not a good idea, though I think I’m right in saying that it depends
on the host, so if it works for you in your host, then no worries (unless
you intend to share the plug, or course – in which case it would be polite
to at least add a caveat…)