midiwhale

If you're intolerant to newbie questions, please just skip by.....

When I build collective as VST the final dll plug-in interface screen size (in pluggo 3.6) is some arbitary small value (80 x 200 ?)). I can shrink the window, but never expand or maximise it.

I have tried various things, pcontrol, fpic, include as background, including background pic within path, loadband-display-thispatcher, window size x y thispatcher, etc. and none of them seem to have any impact.

The manual mentioned standalone, but there did not seem to be a section on make VST, or any similar interface guide for a plug-in.

The standalone mentions screen coords for the graphic (window size) but never seems to define what the 4 points actually are!!

(I have assumed they were top left x/y and bottom right x/y - hope that is correct).

Logically I just expected the screen area I could see to become a plug-in, or the alternative plug-in wondow size to be VERY obvious :-(

Did try forum search
Did hard skim pdf
Did try for 3 hours

The manual mentioned standalone, but there did not seem to be a section on make VST, or any similar interface guide for a plug-in.
The standalone mentions screen coords for the graphic (window size) but never seems to define what the 4 points actually are!!
(I have assumed they were top left x/y and bottom right x/y - hope that is correct).

Any help/pointers much appreciated!
Thanks.


newbie-make-vst-letterbox-interface-size

Window size and view offsets are all set in your plugconfig script.

>If you're intolerant to newbie questions, please just skip by.....

>When I build collective as VST the final dll plug-in interface screen size (in pluggo 3.6) is some arbitary small value (80 x 200 ?)). I can shrink the window, but never expand or maximise it.

>I have tried various things, pcontrol, fpic, include as background, including background pic within path, loadband-display-thispatcher, window size x y thispatcher, etc. and none of them seem to have any impact.

>The manual mentioned standalone, but there did not seem to be a section on make VST, or any similar interface guide for a plug-in.

>The standalone mentions screen coords for the graphic (window size) but never seems to define what the 4 points actually are!!

>(I have assumed they were top left x/y and bottom right x/y - hope that is correct).

>Logically I just expected the screen area I could see to become a plug-in, or the alternative plug-in wondow size to be VERY obvious :-(

Chris Muir | "There are many futures and only one status quo.

cbm@well.com | This is why conservatives mostly agree,

 | and radicals always argue." - Brian Eno

At 8:05 PM +0000 12/27/06, peter wrote:
>If you're intolerant to newbie questions, please just skip by.....
>
>Did try forum search
>Did hard skim pdf
>Did try for 3 hours
>
>When I build collective as VST the final dll plug-in interface screen size (in pluggo 3.6) is some arbitary small value (80 x 200 ?)). I can shrink the window, but never expand or maximise it.
>
>Hence I get a letterbox view of my gui.
>
>I have tried various things, pcontrol, fpic, include as background, including background pic within path, loadband-display-thispatcher, window size x y thispatcher, etc. and none of them seem to have any impact.
>
>The manual mentioned standalone, but there did not seem to be a section on make VST, or any similar interface guide for a plug-in.
>The standalone mentions screen coords for the graphic (window size) but never seems to define what the 4 points actually are!!
>(I have assumed they were top left x/y and bottom right x/y - hope that is correct).
>
>Logically I just expected the screen area I could see to become a plug-in, or the alternative plug-in wondow size to be VERY obvious :-(
>
>Any help/pointers much appreciated!
>Thanks.

-- 
Chris Muir           | "There are many futures and only one status quo.
cbm@well.com         |  This is why conservatives mostly agree,
http://www.xfade.com |  and radicals always argue." - Brian Eno


So you just add an OBJECT box with the name PLUGCONFIG and then right mouse click and do GET INFO (&/or help)

I'd love to believe that is in the manual.....

But it seems to be in the Pluggo3 manual, which is NOT part of the default MAX/MSP documentation install ?!

I'd love to believe that is in the manual.....
But it seems to be in the Pluggo3 manual, which is NOT part of the default MAX/MSP documentation install ?!

yes indeed it is hard to find information about

[plugconfig] - because it is in the MSP reference pdf

(and not in the MAX reference) for a reason nobody knows.

read up on plugconfig in the MSP reference, the thing is

i recommend not to use "size auto;" but pixel values.

yes indeed it is hard to find information about
[plugconfig] - because it is in the MSP reference pdf
(and not in the MAX reference) for a reason nobody knows.

read up on plugconfig in the MSP reference, the thing is
easy to understand.

i recommend not to use "size auto;" but pixel values.


http://www.creativesynth.com/MAXMSP/001-SynthBuildingMSP/sbm_07.html

I am extremely grateful to all the users who have helped to answer this!

Once you know, it isn't a problem. But if I released a product in this state I would be shot!

Compile as plug-in is not some tack-on optional feature (any more). It is one of the 3 major options on the compile project drop-down. 

Users should be armed with sufficient tools to make them work, without experiencing such frustration. Why on earth it would default to an arbitrary letter box size, instead of the current view, totally escapes me.

1) On compile it should check if the correct objects are inserted in the project (ie plugin for plugins and standalone for standalones presumably) and notify the user of WHAT is missing if so.

It shouldn't be hard to check for such "seminal" dependencies.

2) It should have a chapter, at least a page in the MSP Tutorial (as well), or a reference pointer to the other (MAX) tutorial manual.

As VST plug-in are by-an-large "audio" devices, it really should be in the (audio related) MSP manual. The ratio of MIDI only plug-in to audio included ones is pretty wide.

As PDFs are electronic and can be edited (no really they can), I can't quite see why it can't be amended/updated or minimum a separate addendum document created.

The pluggo manual is not installed by default and some of the information in that is irrelevent nad hence confusing, while some of it is essential reading.

If this is typical of an academic project gone commercial, and the lack of care and customer focus provided.....It shouldn't be up to the user base, to define/salvage a product. This should be a mature product by now. It was 15? years ago when I last used it.

Sorry to have a cow, but there is no excuse for what I can only describe as this sort of corporate "apathy".

Also the show meters and swirl options on the plugin device, are neither compiled nor remembered. I'm sure there's a reason and I'm not even surprised it doesn't work. I won't hold my breath looking for it in the manual/tutorial/integrated-help-system - LOL.

Constructive Complaints:
Compile as plug-in is not some tack-on optional feature (any more). It is one of the 3 major options on the compile project drop-down. 
Users should be armed with sufficient tools to make them work, without experiencing such frustration. Why on earth it would default to an arbitrary letter box size, instead of the current view, totally escapes me.

1) On compile it should check if the correct objects are inserted in the project (ie plugin for plugins and standalone for standalones presumably) and notify the user of WHAT is missing if so.
It shouldn't be hard to check for such "seminal" dependencies.
As they are seminal, I see no excuse!

If this is typical of an academic project gone commercial, and the lack of care and customer focus provided.....It shouldn't be up to the user base, to define/salvage a product. This should be a mature product by now. It was 15? years ago when I last used it. 

Also the show meters and swirl options on the plugin device, are neither compiled nor remembered. I'm sure there's a reason and  I'm not even surprised it doesn't work. I won't hold my breath looking for it in the manual/tutorial/integrated-help-system - LOL.


Newbie - make VST - letterbox interface size