pluggo vst parameters


    Aug 28 2006 | 2:47 pm
    Di't really get any response on this on the max list. Maybe here...?
    I have a problem with pluggo plug-ins in vst~ (in MaxMSP). Parameter values are not reportet to the 4th outlet of vst~, IF you call a program by a message into the vst~ inlet, AND the vst~ window is not open. If the window is open values are reportet.
    This patch should show the behavior:
    /J

    • Aug 28 2006 | 2:59 pm
      There isn't really enough information in your email to give you an answer. What versions of Max and Pluggo are you using? What platform are you on? Is overdrive on? Is audio on? Do these things make a difference if they are switched? etc...
      -Tim
      Jakob Riis wrote: > Di't really get any response on this on the max list. Maybe here...? > > I have a problem with pluggo plug-ins in vst~ (in MaxMSP). Parameter > values are not > reportet to the 4th outlet of vst~, IF you call a program by a message > into the vst~ inlet, AND the vst~ window is not open. > If the window is open values are reportet. > > This patch should show the behavior: > > #P window setfont "Sans Serif" 9.; > #P window linecount 1; > #P message 284 53 26 196617 plug; > #P message 602 267 30 196617 open; > #P newex 349 247 27 196617 + 1; > #P newex 289 231 32 196617 print; > #P newex 349 185 78 196617 prepend append; > #P user ubumenu 349 219 100 196617 0 1 1 0; > #X add "Phasy Breakup"; > #X add "Nasal Chorus"; > #X add "Mixexpressed Anxiety"; > #X add "Yeah Yeah"; > #X add "Rubber Stadium"; > #X add "Watery Flange"; > #X add "Polite Twister"; > #X add "Chorus of Flappers"; > #X add "Some Short Echoes"; > #X add "Punchy Zzzzz"; > #X add "Broken Flanger"; > #X add "Decaying Bub Chor"; > #X add "Unstable Friends"; > #X add "High School Football"; > #X add "The Phasing Effect"; > #X add "Bam! Pow! Zap! Check?"; > #X prefix_set 0 0 0; > #P message 441 183 33 196617 clear; > #P message 45 115 56 196617 pgmnames; > #P newex 45 89 27 196617 b 2; > #N vst~ loaduniqueid 1024132096; > #P newobj 284 153 79 196617 vst~; > #P newex 84 50 162 196617 loadmess plug "Average Injector"; > #P newex 44 192 31 196617 dac~; > #P newex 44 164 111 196617 loadmess startwindow; > #P window linecount 4; > #P comment 479 204 158 196617 when changing the preset program here , > no parameter values are printet unless the vst~ window is open; > #P window linecount 1; > #P comment 455 221 27 196617 > #P connect 2 0 3 0; > #P connect 6 0 7 0; > #P connect 4 0 5 0; > #P connect 4 0 6 0; > #P connect 14 0 5 0; > #P fasten 7 0 5 0 50 141 289 141; > #P fasten 12 0 5 0 354 268 263 268 263 148 289 148; > #P fasten 13 0 5 0 607 302 245 302 245 144 289 144; > #P connect 5 3 11 0; > #P connect 5 5 10 0; > #P connect 10 0 9 0; > #P connect 8 0 9 0; > #P connect 9 0 12 0; > #P fasten 6 1 8 0 67 110 446 110; > #P window clipboard copycount 15; > > /J > >
    • Aug 28 2006 | 4:02 pm
      28/08/06, kl. 16:59 +0200 , skrev Tim Place:
      >There isn't really enough information in your email to give you an >answer. What versions of Max and Pluggo are you using? What platform >are you on? Is overdrive on? Is audio on? Do these things make a >difference if they are switched? etc...
      OK - good answer :-) Here's the deal:
      Alubook 1.33 Ghz, Mac OS X 10.4.7, MaxMSP 4.5.7, Pluggo 3.5.4. Pluggo plug-ins in vst~. If you call a program by a message into the vst~ inlet, and the vst~ window is not open, parameter values are not reportet to the 4th outlet of vst~. If the plugin-window is open values are reportet.
      This is true for all combinations of audio - and overdrive on/off.
      This patch illustrates the problem:
      /Jakob
    • Aug 28 2006 | 4:31 pm
      Okay - I see the behavior you describe. Thanks for the additional info. While we look into it, you can work around this by using a bunch of get messages to get the values after the preset has changed. It's not pretty, but hopefully it will get you by until we are able to release a fix.
      best, Tim
      Jakob Riis wrote: > 28/08/06, kl. 16:59 +0200 , skrev Tim Place: > >> There isn't really enough information in your email to give you an >> answer. What versions of Max and Pluggo are you using? What platform >> are you on? Is overdrive on? Is audio on? Do these things make a >> difference if they are switched? etc... > > OK - good answer :-) Here's the deal: > > Alubook 1.33 Ghz, Mac OS X 10.4.7, MaxMSP 4.5.7, Pluggo 3.5.4. > Pluggo plug-ins in vst~. If you call a program by a message into the > vst~ inlet, and the vst~ window is not open, parameter values are not > reportet to the 4th outlet of vst~. If the plugin-window is open values > are reportet. > > This is true for all combinations of audio - and overdrive on/off. > > This patch illustrates the problem: > > #P toggle 121 357 15 0; > #P button 22 334 15 0; > #P window setfont "Sans Serif" 9.; > #P user umenu 22 378 44 196647 1 64 394 0; > #X add Off; > #X add On; > #P window linecount 1; > #P newex 22 356 89 196617 adstatus takeover; > #B color 5; > #P window linecount 2; > #P comment 70 378 126 196617 Turns "Scheduler in Audio Interrupt" mode on/off; > #P comment 39 328 115 196617 report "Scheduler in Audio Interrupt" mode; > #P toggle 124 261 15 0; > #P button 24 239 15 0; > #P user umenu 23 282 44 196647 1 64 298 0; > #X add Off; > #X add On; > #P window linecount 1; > #P newex 24 261 94 196617 adstatus overdrive; > #B color 5; > #P window linecount 2; > #P comment 71 283 88 196617 Turns Overdrive mode on/off; > #P window linecount 1; > #P comment 40 240 125 196617 report Overdrive mode; > #P toggle 49 164 15 0; > #P message 215 68 26 196617 plug; > #P message 533 282 30 196617 open; > #P newex 280 262 27 196617 + 1; > #P newex 220 246 32 196617 print; > #P newex 280 200 78 196617 prepend append; > #P user ubumenu 280 234 100 196617 0 1 1 0; > #X add "Phasy Breakup"; > #X add "Nasal Chorus"; > #X add "Mixexpressed Anxiety"; > #X add "Yeah Yeah"; > #X add "Rubber Stadium"; > #X add "Watery Flange"; > #X add "Polite Twister"; > #X add "Chorus of Flappers"; > #X add "Some Short Echoes"; > #X add "Punchy Zzzzz"; > #X add "Broken Flanger"; > #X add "Decaying Bub Chor"; > #X add "Unstable Friends"; > #X add "High School Football"; > #X add "The Phasing Effect"; > #X add "Bam! Pow! Zap! Check?"; > #X prefix_set 0 0 0; > #X pattrmode 1; > #P message 372 198 33 196617 clear; > #P message 45 115 56 196617 pgmnames; > #P newex 45 89 27 196617 b 2; > #N vst~ loaduniqueid 1024132096; > #P newobj 215 168 79 196617 vst~; > #P newex 84 50 162 196617 loadmess plug "Average Injector"; > #P newex 49 193 31 196617 dac~; > #P window linecount 4; > #P comment 410 219 158 196617 when changing the preset program here , > no parameter values are printet unless the vst~ window is open; > #P window linecount 1; > #P comment 386 236 27 196617 > #P fasten 24 0 23 0 27 397 9 397 9 354 27 354; > #P connect 25 0 23 0; > #P connect 23 0 24 0; > #P connect 23 1 26 0; > #P fasten 18 0 17 0 28 302 11 302 11 259 29 259; > #P connect 19 0 17 0; > #P connect 17 0 18 0; > #P connect 17 1 20 0; > #P connect 3 0 5 0; > #P connect 3 0 4 0; > #P connect 14 0 2 0; > #P fasten 5 1 7 0 67 110 377 110; > #P connect 8 0 11 0; > #P connect 7 0 8 0; > #P connect 9 0 8 0; > #P connect 4 5 9 0; > #P connect 4 3 10 0; > #P fasten 12 0 4 0 538 317 176 317 176 159 220 159; > #P fasten 11 0 4 0 285 283 194 283 194 163 220 163; > #P fasten 6 0 4 0 50 141 220 141; > #P connect 13 0 4 0; > #P connect 5 0 6 0; > #P window clipboard copycount 27; > > /Jakob > > >
    • Aug 28 2006 | 5:44 pm
      28/08/06, kl. 18:31 +0200 , skrev Tim Place:
      >Okay - I see the behavior you describe. Thanks for the additional info. > While we look into it, you can work around this by using a bunch of >get messages to get the values after the preset has changed. It's not >pretty, but hopefully it will get you by until we are able to release a fix.
      Yes I was thinking about that as well. But then the next problem occur: If the plugin window is open I will get these messages twice, and since the idea is to transmit the data over a network, to interact with other users sending and receiving data as well, I would like to reduce that dataflow as much as possible. So it would be great if I somehow could determine whether the vst-window is open or not - I can't really get my head around that one.... So maybe it's one more 'not so pretty' solution.
      Cheers, /Jakob
    • Aug 28 2006 | 5:55 pm
      In my test, the values were never transmitted regardless of whether the window was open or closed.
      Could you use change objects to filter out values? If you need to filter lists that are the same you could also use the jmod.change object from jamoma.org. -Tim
      Jakob Riis wrote: > 28/08/06, kl. 18:31 +0200 , skrev Tim Place: > >> Okay - I see the behavior you describe. Thanks for the additional info. >> While we look into it, you can work around this by using a bunch of >> get messages to get the values after the preset has changed. It's not >> pretty, but hopefully it will get you by until we are able to release a fix. > > Yes I was thinking about that as well. But then the next problem occur: > If the plugin window is open I will get these messages twice, and since > the idea is to transmit the data over a network, to interact with other > users sending and receiving data as well, I would like to reduce that > dataflow as much as possible. So it would be great if I somehow could > determine whether the vst-window is open or not - I can't really get my > head around that one.... So maybe it's one more 'not so pretty' solution. > > Cheers, > /Jakob > > >