Problem building Pluggos as per the tutorial

Sep 28, 2006 at 10:40pm

Problem building Pluggos as per the tutorial

I’m having problems building Pluggos using the tutorials provided as part of the Pluggo Development kit.

I’ve worked my way through the first tutorial and reached the point of file>build collective/application, i’ve selected pluggo (.dll) from the options and clicked build.

The collective build window is there and there’s a message which says: Starting Build for TutorialP1.pat-build

It says the same in the Max Window, but it’s been 30 minutes now and it’s still not progressed and there’s no pluggo in the place i’ve tried to save it.

How long should it take?
Presumably not that long!

I’m running Max/MSP+Jitter 4.5.?, (I bought it a couple of months ago if that helps), on Windows XP.

I’m assuming it’s a simple thing i’m doing wrong but after scanning the Pluggo Development .PDF i still can’t find the problem…so any help or advice would be massively appreciated.

Thanks in advance,
John

#27871
Sep 28, 2006 at 10:59pm

it should take about 1 second.

Something is jammed up on your system. Quit it and try again. If you are still having problems, let us know about it.

Cheers

Andrew

#84849
Sep 28, 2006 at 11:52pm

Hi Andrew, thanks for replying so quickly!

I’ve quit and retried it a few times, all with the same results unfortunately :(

Can you suggest any settings i can try changing or things that might be causing the problem?

Thanks again,
John

#84850
Sep 29, 2006 at 8:31am

Ok…So far i’ve tried rebooting Max and also rebooting my PC, all to no avail.

Should i now try reinstalling Max and see whether that works or is there something i’ve over looked?

Before i try that though, can someone tell me if the same Challenge/Response i used to authorise it last time will work again?
It’ll be on the same computer and the same version of Windows as it was loaded on to last time.

If that doesn’t work, should i try reinstalling Windows?
I’d be using Norton Ghost to recreate a version of the disk image, although i’ll have to use an image from prior to installing Max…so the same question applies as reinstalling Max, ie will my Challenge/Response still work?
Again, it’d be installed onto the same computer although i’m not sure if the Windows would have the same installation codes and therefore whether the Challenge/Response would still work.

Any advice appreciated, thanks in advance
John

#84851
Sep 29, 2006 at 5:28pm

Ok…so i’ve now uninstalled and re-installed Max, still no joy!

I then formatted my C: drive, reinstalled Windows XP, Max/MSP+Jitter and everything else…still nothing!
(although fortunately my old challenge response worked)

For the record it’s Max/MSP 4.5.7 & Jitter 1.5.2.

I’m sure it’s not me doing anything wrong now, i also can’t get my copy to build either Collectives or Applications from any of my patches (including demo patches, tutorials etc etc).

Same message in the Collective Window and the Max Window, but nothing else.

Any help would be appreciated, thanks again
John

#84852
Sep 29, 2006 at 5:39pm

It certainly does sound like you have done everything right.

We’re gonna resolve this in support…

-A

#84853
Sep 29, 2006 at 5:45pm

Thanks Andrew,

I was just emailing support as we speak but i’ll hold off for a bit now…unless you think it’s appropriate.

Would a list of all the applications on my system, (and attached devices), help?

#84854
Sep 29, 2006 at 9:47pm

Thankfully Andrew managed to solve the problem, so here’s a follow up for the knowledge base.

The problem was that for some unknown reason Max wasn’t compiling Collectives (.mxf), Applications (.exe) or Plugins (.dll) from the “build” option in the File menu on my computer.

Bizzarely this also occurred on a fresh install of Max/MSP 4.5.7, downloaded from the Cycling 74 site (not from my original CD), on a seperate computer also running XP home SP2!

The solution, for anyone who has the same problem in the future, was as simple as adding the specific file extension when naming the file…for example: “myplugin.dll” (for a plugin), “mycollective.mxf” (for a collective) or “myapp.exe” (for an application).

He also pointed out that when creating an application, (.exe), it is essential to only use one period (.) in the file name and that should be the one followed by exe!

I hope this information goes some way to furthering the Max/MSP knowledge base and helps anyone who ever finds themselves with a similar problem in the future.

Thanks so much Andrew, your help was invaluable :-)

#84855
Sep 29, 2006 at 10:05pm

No worries mate.

BTW, the “multiple periods in the standalone file name” bug is fixed in MaxMSP 4.6.2 for Windows.

-A

#84856
Sep 29, 2006 at 10:35pm

this is a problem for XP which I Haven’t addressed.

What you need to do is…

Go to control panel, open folder options, then under the view tab, uncheck “hide extensions for known file types”

now, when you build a collective as a pluggo plugin, you need to remove the “.pat-build” at the end and replace it with “.dll”……

–=–=——=–=——=–=—-

So, the reason why it wasn’t building was because the extension at the end was incorrect and windows wasn’t displaying that information back to you.

Took me weeks to figure out lol…

James

#84857
Sep 30, 2006 at 4:12am

Well, I hope I can piggy-back on this thread and get some help myself. I too have been working through the Pluggo tutorials, which I found this evening by searching the forum archives – http://homepages.gold.ac.uk/ems/pdf/PluggoDevGuide.pdf – and I have been using the example to convert my delay patcher into a VST (.dll)….well, no problems building the .dll (thank something or someone for that!), but the issue for me is when I load the plug up on my MAX host. The plug loads fine, and even it’s window looks fine, but as soon as I touch the damn thing in order to tweak a parameter, MAX crashes and shuts down instantly.

I have copied my delay patch below. Any suggestions? One question I have is whether it is necessary to create that loop between the float number box and the pp object. Can I leave this out? I’m afraid that in reading the tutorial and trying to build my patch into a plug that I may have neglected to do something really important or critical.

Kris

#P toggle 128 458 15 0;
#P window setfont “Sans Serif” 9.;
#P window linecount 1;
#N pp 5 Mix 0. 100.;
#P newobj 15 130 75 9109513 pp 5 Mix 0. 100.;
#N pp 2 DelayTime 0. 1000. ms;
#P newobj 499 56 127 9109513 pp 2 DelayTime 0. 1000. ms;
#N pp 1 DelayTime 0. 1000. ms;
#P newobj 498 29 127 9109513 pp 1 DelayTime 0. 1000. ms;
#N pp 3 Feedback;
#P newobj 515 90 70 9109513 pp 3 Feedback;
#N pp 4 Feedback;
#P newobj 517 115 70 9109513 pp 4 Feedback;
#P newex 234 454 43 9109513 plugout~;
#P newex 239 490 28 9109513 dac~;
#P newex 119 55 37 9109513 plugin~;
#P newex 119 27 28 9109513 adc~;
#P window setfont “Fixedwidth Serif” 10.;
#P newex 192 328 32 9240586 *~ 1;
#P newex 272 328 32 9240586 *~ 1;
#P newex 435 328 36 9240586 *~;
#P newex 355 328 36 9240586 *~;
#P user hslider 101 245 12 76 101 1 0 0;
#P newex 102 260 43 9240586 * 0.01;
#P window setfont “Proportional Serif” 10.;
#P comment 102 231 23 9175050 Dry;
#P comment 173 231 22 9175050 Wet;
#P window setfont “Fixedwidth Serif” 10.;
#P newex 102 285 68 9240586 expr 1-$f1;
#P window setfont “Proportional Serif” 10.;
#P comment 367 292 67 9175050 L Delay Level;
#P window setfont “Fixedwidth Serif” 10.;
#P flonum 381 310 35 10 0. 1. 3 141 0 0 0 221 221 221 222 222 222 0 0 0;
#P flonum 461 310 35 10 0. 1. 3 141 0 0 0 221 221 221 222 222 222 0 0 0;
#P window setfont “Proportional Serif” 10.;
#P comment 447 292 67 9175050 R Delay Level;
#P comment 282 292 67 9175050 R Direct Level;
#P window setfont “Fixedwidth Serif” 10.;
#P flonum 294 310 35 10 0. 1. 3 141 0 0 0 221 221 221 222 222 222 0 0 0;
#P flonum 214 310 35 10 0. 1. 3 141 0 0 0 221 221 221 222 222 222 0 0 0;
#P window setfont “Proportional Serif” 10.;
#P comment 200 292 67 9175050 L Direct Level;
#P window setfont “Fixedwidth Serif” 10.;
#P newex 455 255 33 9240586 *~;
#P window setfont “Proportional Serif” 10.;
#P comment 464 220 75 9175050 Right Feedback;
#P window setfont “Fixedwidth Serif” 10.;
#P flonum 479 236 35 10 0. 1. 3 141 0 0 0 221 221 221 222 222 222 0 0 0;
#P flonum 288 237 35 10 0. 1. 3 141 0 0 0 221 221 221 222 222 222 0 0 0;
#P window setfont “Proportional Serif” 10.;
#P comment 276 223 62 9175050 Left Feedback;
#P window setfont “Fixedwidth Serif” 10.;
#P newex 264 255 34 9240586 *~;
#P newex 311 433 32 9240586 *~ 1;
#B color 5;
#P newex 174 432 32 9240586 *~ 1;
#B color 5;
#P window setfont “Proportional Serif” 10.;
#P comment 232 414 60 9175050 Output Level;
#P window setfont “Fixedwidth Serif” 10.;
#P flonum 369 147 60 10 1. 1000. 3 141 0 0 0 221 221 221 222 222 222 0 0 0;
#P window setfont “Proportional Serif” 10.;
#P comment 360 133 80 9175050 Right Delay Time;
#P window setfont “Fixedwidth Serif” 10.;
#P flonum 289 147 60 10 1. 1000. 3 141 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 434 199 74 9240586 tapout~ 1.;
#P newex 352 199 74 9240586 tapout~ 1.;
#P newex 434 174 73 9240586 tapin~ 1000;
#P newex 352 174 73 9240586 tapin~ 1000;
#P window setfont “Proportional Serif” 10.;
#P comment 284 133 73 9175050 Left Delay Time;
#P connect 38 0 14 0;
#P connect 14 0 16 1;
#P connect 22 0 31 1;
#P connect 28 0 25 0;
#P fasten 28 0 23 0 107 281 351 281 351 306 386 306;
#P fasten 28 0 22 0 107 281 351 281 351 306 466 306;
#P fasten 4 0 16 0 439 220 460 220;
#P fasten 4 0 31 0 439 220 440 220;
#P connect 2 0 4 0;
#P fasten 7 0 4 0 374 165 428 165 428 195 439 195;
#P fasten 16 0 2 0 460 276 536 276 536 169 439 169;
#P connect 35 1 32 0;
#P connect 35 1 2 0;
#P connect 23 0 30 1;
#P connect 41 0 7 0;
#P fasten 3 0 11 0 357 220 269 220;
#P fasten 3 0 30 0 357 220 360 220;
#P connect 1 0 3 0;
#P fasten 5 0 3 0 294 165 348 165 348 195 357 195;
#P fasten 11 0 1 0 269 276 259 276 259 169 357 169;
#P connect 35 0 33 0;
#P connect 35 0 1 0;
#P fasten 31 0 10 0 440 359 316 359;
#P fasten 32 0 10 0 277 349 316 349;
#P connect 19 0 32 1;
#P fasten 25 0 18 0 107 306 219 306;
#P fasten 25 0 19 0 107 306 299 306;
#P connect 40 0 5 0;
#P connect 13 0 11 1;
#P connect 39 0 13 0;
#P connect 10 0 37 1;
#P connect 37 1 36 1;
#P connect 43 0 36 0;
#P connect 37 0 36 0;
#P connect 9 0 37 0;
#P connect 18 0 33 1;
#P fasten 30 0 9 0 360 354 179 354;
#P fasten 33 0 9 0 197 349 179 349;
#P connect 34 1 35 1;
#P connect 34 0 35 0;
#P connect 29 0 28 0;
#P connect 42 0 29 0;
#P window clipboard copycount 44;

#84858
Sep 30, 2006 at 4:21am

the loop is necessary. Without the loop the contents of plugconfig [which wasn't included] will not be updated. Each pp is like a CC. If the value doesn’t go back into pp, then no preset can exist because nothing has been stored.

#84859
Sep 30, 2006 at 4:30am

Quote: DrSbaitso wrote on Fri, 29 September 2006 22:21
—————————————————-
> the loop is necessary. Without the loop the contents of plugconfig [which wasn't included] will not be updated. Each pp is like a CC. If the value doesn’t go back into pp, then no preset can exist because nothing has been stored.
—————————————————-

Okay, thanks. I guess I misinterpreted: “Now let’s look at how a pp object is connected to other objects. First, you’ll notice a curious circular connection between the float number box and the pp object. This is purely for the convenience of the plug-in developer for creating effect programs.”

I took the “purely for the convenience” clause to suggest it was not necessary, but I will make the connections now. So I need to add plugconfig too, then? Why does the tutorial before the one that introduces plugconfig go through the build process…doesn’t this imply that the plug could be build without it? It falls under the Improving the User Experience section. This is confusing. I’m not even concerned about storing any presets at this point, just getting the plug to work in its barest sense. Excuse my lack of understanding…I’m just taking it one step at a time here.

Kris

#84860
Sep 30, 2006 at 4:33am

The float/numberbox is the conveinant part…

#84861
Sep 30, 2006 at 9:12am

> So I need to add plugconfig too, then?

> Why does the tutorial before the one that introduces
> plugconfig go through the build process…doesn’t this
> imply that the plug could be build without it?

> I’m not even concerned about storing any presets at
> this point, just getting the plug to work in its barest sense.

note that plugconfig also contains prefs for things
like window size and such, which are required for any
plug-in.
yes i know, it does not even have a helpfile, but you?ll
find almost anything about it in the MSP reference .
yes, inMSP. :)

and always take care that you do not have more than one
plugconfig object in a plug-in, and also make sure thatyou use unique ID?s for differetn plug-ins.
otherwise these two errors might also cause that your biuld
doesnt show up in your host.

-110

#84862
Sep 30, 2006 at 4:55pm

The unique ideas that the .toast extension using Roman is refering to is in regards to messages and arguments which begin [as a symbol] with a string of 3 characters “—”. When the plugin is loaded the — will turn into a progressively linear number making sending to alternative instances impossible.

So, if you have…

send —matrix_point

when you load the plugin the object will become….

send 001matrix_point

for the life of the plugin, while the next time you load the plugin as another instance somewhere in your project, it’ll take it’s own number, 002 in this case, or higher if you have loaded other plugins.

DS

#84863
Sep 30, 2006 at 5:32pm

Okay, I rebuilt my entire stereo delay patch from scratch, following the tutorial example, adding the plugconfig, etc. Great. The plug loads up fine and it doesn’t crash when I click on it. Perfect. But now all I see in the plug window is a bunch of wires and objects, just a peep hole into my larger patch screen. Now I guess I need to take a look at that plugconfig object and see what I need to change to fix this. I even tried to arrange my sliders in a similar position as the tutorial example, but no such luck in seeing them. I just saw the note from Dr. Sbaitso on on his hidden objects for sizing a plugin…I’ll experiment with those I guess.

Do I need to hide on lock everything but my faders?

Kris

Quote: Roman Thilenius wrote on Sat, 30 September 2006 03:12
—————————————————-
> note that plugconfig also contains prefs for things
> like window size and such, which are required for any
> plug-in.
> yes i know, it does not even have a helpfile, but you?ll
> find almost anything about it in the MSP reference .
> yes, inMSP. :)
>
> and always take care that you do not have more than one
> plugconfig object in a plug-in, and also make sure thatyou use unique ID?s for differetn plug-ins.
> otherwise these two errors might also cause that your biuld
> doesnt show up in your host.
>
>
> -110
>
—————————————————-

#84864
Sep 30, 2006 at 5:36pm

You can do what you want in regards to hiding stuff. I mean, if the faders are the area that’s going to be what the user sees, it’d probably be nicer. Check out my abstraction, but you’ll need jasch and lobjects to make it work. It’ll size it perfectly ;)

#84865
Sep 30, 2006 at 5:42pm

Eeeek…more stuff to learn. Quick question. in useviews, does that first 0 need to be 1 to see my faders? I see now what defaultview and setsize are doing, I think, so I need to tweak those. I take it 550 220 0 means that I am setting the top edge of my plug’s interface 550 pixels over from the top left of my patche’s edit screen, 220 down, etc.

Kris

#C useviews 0 1 1 1;
#C numprograms 8;
#C preempt 1;
#C sigvschange 1;
#C sigvsdefault 32;
#C setsize 220 130;
#C defaultview Interface 550 220 0;
#C dragscroll 1;
#C noinfo;
#C setprogram 1 ‘Program 1’ 0 0.232283 0.228346 0.103 0.1496 0.15 0.15;
#C setprogram 2 ‘Program 2’ 0 0.232283 0. 0.292 0.677165 0.05 0.05;
#C setprogram 3 ‘Program 3’ 0 0.232283 0.110236 0.143 0.07874 0.15 0.15;
#C uniqueid 128 221 227;
#C initialpgm 1;

Quote: DrSbaitso wrote on Sat, 30 September 2006 11:36
—————————————————-
> You can do what you want in regards to hiding stuff. I mean, if the faders are the area that’s going to be what the user sees, it’d probably be nicer. Check out my abstraction, but you’ll need jasch and lobjects to make it work. It’ll size it perfectly ;)
—————————————————-

#84866
Sep 30, 2006 at 10:57pm

Okay, I’m making tremendous progress here, relatively, and even if this plug is utterly basic. Thank everyone for the help! Once I get this nacked, I can generalize my learnings and build other plugins. I have the thing working now for the most part and all my faders shows nice and neat in the plug window. However…

Can someone provide some tips on the values I should use with the binop1 boxes conaining * 127. and / 127. for the feedback fader? My code is below. Basically, I can only move my feedback fader about 25% across the width of the fader, then the feedback is at 100%. What values should I be using to change this? The delay time works fine, and the output, dry, and wet mix faders work fine as well (though the output seems a bit low, which I can fix). What has me curious is why I would come out of the pp object and go to a * 127 binop1, yet come out of the fader with a / 127 binop1. Isn’t this a wash? I don’t understand this.

Thanks / Kris

#P window setfont “Sans Serif” 9.;
#P window linecount 1;
#P hidden newex 486 419 39 9109513 * 127.;
#P hidden newex 814 182 38 9109513 / 127.;
#P comment 497 167 53 9109513 Delay Time;
#P comment 606 31 100 9109513 Parameter definition;
#P message 906 432 49 9109513 recall $1;
#P number 906 412 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
#P message 878 384 35 9109513 set $1;
#P number 878 363 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
#P number 837 412 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
#P message 837 432 55 9109513 capture $1;
#P button 837 373 27 0;
#N plugconfig;
#C useviews 0 1 1 1;
#C numprograms 8;
#C preempt 1;
#C sigvschange 1;
#C sigvsdefault 32;
#C setsize 350 200;
#C defaultview Interface 400 100 0;
#C dragscroll 1;
#C infopict delayhelp.pic.pct 2;
#C setprogram 1 “Program 1″ 0 0.232283 0.228346 0.103 0.149606 0.15 0.15;
#C setprogram 2 “Program 2″ 0 0.232283 0. 0.292 0.677165 0.05 0.05;
#C setprogram 3 “Program 3″ 0 0.232283 0.110236 0.143 0.07874 0.15 0.15;
#C uniqueid 128 221 227;
#C initialpgm 1;
#P newobj 891 454 53 9109513 plugconfig;
#B color 15;
#P comment 911 345 51 9109513 Programs;
#P comment 829 357 35 9109513 Store!;
#P comment 918 364 115 9109513 Store Program Number:;
#P comment 946 413 114 9109513 Recall Program Number:;
#P comment 499 231 53 9109513 Feedback;
#P comment 564 249 26 9109513 long;
#P user hslider 487 248 17 58 1000 1 0 9;
#N pp 6 Feedback 0. 1.;
#PP text “Sets the delay time in milliseconds”;
#P newobj 494 383 110 9109513 pp 6 Feedback 0. 1.;
#P comment 449 248 32 9109513 short;
#P hidden newex 957 253 38 9109513 / 127.;
#P hidden newex 904 58 39 9109513 * 127.;
#N pp 5 “Output Level” 0. 1.;
#P newobj 903 33 118 9109513 pp 5 “Output Level” 0. 1.;
#P window linecount 2;
#P comment 674 156 35 9109513 Output Level;
#P user uslider 684 186 18 62 128 1 0 2;
#P window linecount 1;
#P comment 562 188 26 9109513 long;
#P user hslider 486 186 17 58 1000 1 0 9;
#N pp 4 Delay-R 0. 1000. ms;
#PP text “Sets the delay time in milliseconds”;
#P newobj 579 49 113 9109513 pp 4 Delay-R 0. 1000. ms;
#P comment 449 187 32 9109513 short;
#P comment 564 211 26 9109513 long;
#P user hslider 486 209 17 58 1000 1 0 9;
#N pp 3 Delay-L 0. 1000. ms;
#PP text “Sets the delay time in milliseconds”;
#P newobj 578 85 113 9109513 pp 3 Delay-L 0. 1000. ms;
#P comment 449 211 32 9109513 short;
#P hidden newex 844 270 38 9109513 / 127.;
#P hidden newex 772 93 39 9109513 * 127.;
#N pp 2 “Dry Level” 0. 1.;
#P newobj 771 74 105 9109513 pp 2 “Dry Level” 0. 1.;
#P hidden newex 802 270 38 9109513 / 127.;
#P newex 729 54 39 9109513 * 127.;
#P window linecount 2;
#P comment 631 158 32 9109513 Dry Level;
#P user uslider 639 186 18 62 128 1 0 2;
#P user uslider 597 186 19 62 128 1 0 10;
#P window linecount 1;
#N pp 1 “Wet Level” 0. 1.;
#P newobj 729 33 105 9109513 pp 1 “Wet Level” 0. 1.;
#P window linecount 2;
#P comment 589 158 32 9109513 Delay Level;
#P toggle 129 373 15 0;
#P window linecount 1;
#P newex 231 376 43 9109513 plugout~;
#P newex 240 405 28 9109513 dac~;
#P newex 228 68 37 9109513 plugin~;
#P newex 233 35 28 9109513 adc~;
#P window setfont “Fixedwidth Serif” 10.;
#P newex 108 297 32 9240586 *~;
#P newex 360 290 32 9240586 *~;
#P newex 280 295 36 9240586 *~;
#P newex 192 297 36 9240586 *~;
#P window setfont “Proportional Serif” 10.;
#P comment 180 278 67 9175050 L Delay Level;
#P comment 265 277 67 9175050 R Delay Level;
#P comment 345 277 67 9175050 R Dry Level;
#P comment 93 278 67 9175050 L Dry Level;
#P window setfont “Fixedwidth Serif” 10.;
#P newex 315 248 33 9240586 *~;
#P window setfont “Proportional Serif” 10.;
#P comment 297 228 75 9175050 Right Feedback;
#P comment 137 229 62 9175050 Left Feedback;
#P window setfont “Fixedwidth Serif” 10.;
#P newex 191 248 34 9240586 *~;
#P newex 312 348 32 9240586 *~;
#B color 5;
#P newex 175 347 32 9240586 *~;
#B color 5;
#P window setfont “Proportional Serif” 10.;
#P comment 226 340 60 9175050 Output Level;
#P window setfont “Fixedwidth Serif” 10.;
#P newex 262 192 74 9240586 tapout~ 1.;
#P newex 174 192 74 9240586 tapout~ 1.;
#P newex 254 127 73 9240586 tapin~ 1000;
#P newex 173 127 73 9240586 tapin~ 1000;
#P connect 20 0 18 0;
#P hidden connect 33 0 18 1;
#P connect 20 0 0 0;
#P connect 7 0 0 0;
#P hidden connect 40 0 2 0;
#P connect 0 0 2 0;
#P connect 18 0 5 0;
#P connect 15 0 5 0;
#P connect 2 0 7 0;
#P connect 2 0 15 0;
#P hidden connect 46 0 5 1;
#P hidden connect 66 0 7 1;
#P hidden connect 30 0 15 1;
#P connect 19 0 20 0;
#P connect 5 0 22 0;
#P connect 23 0 21 0;
#P connect 22 0 21 0;
#P connect 20 1 1 0;
#P connect 10 0 1 0;
#P connect 19 1 20 1;
#P connect 22 1 21 1;
#P hidden connect 36 0 3 0;
#P connect 1 0 3 0;
#P connect 6 0 22 1;
#P connect 3 0 16 0;
#P hidden connect 30 0 16 1;
#P connect 17 0 6 0;
#P connect 16 0 6 0;
#P connect 3 0 10 0;
#P hidden connect 46 0 6 1;
#P hidden connect 66 0 10 1;
#P connect 20 1 17 0;
#P hidden connect 33 0 17 1;
#P hidden fasten 39 0 40 0 584 224 491 224;
#P connect 40 0 36 0;
#P hidden fasten 35 0 36 0 583 253 491 253;
#P hidden connect 48 0 67 0;
#P hidden connect 67 0 49 0;
#P hidden connect 66 0 48 0;
#P hidden fasten 36 0 35 0 491 304 569 304 569 75 583 75;
#P hidden fasten 40 0 39 0 491 264 569 264 569 48 584 48;
#P hidden connect 29 0 26 0;
#P hidden connect 32 0 27 0;
#P hidden connect 45 0 42 0;
#P hidden fasten 30 0 25 0 807 298 875 298 875 40 734 40;
#P connect 25 0 29 0;
#P hidden fasten 33 0 31 0 849 302 891 302 891 77 776 77;
#P connect 31 0 32 0;
#P hidden connect 26 0 30 0;
#P hidden connect 49 0 66 0;
#P connect 61 0 59 0;
#P connect 57 0 59 0;
#P connect 59 0 58 0;
#P hidden connect 27 0 33 0;
#P connect 60 0 61 0;
#P connect 63 0 56 0;
#P connect 58 0 56 0;
#P hidden fasten 46 0 44 0 962 261 1023 261 1023 36 908 36;
#P connect 44 0 45 0;
#P connect 62 0 63 0;
#P hidden connect 42 0 46 0;
#P window clipboard copycount 68;

#84867
Sep 30, 2006 at 11:00pm

Oh, and please excuse the rat’s nest of wires and connections in the patch. it looks like a nightmare without any connectionn bending, but it’s functional nonetheless.

K-

#84868
Oct 1, 2006 at 5:51pm

I just thought I would follow up with this and say that someone on the Pluggo list helped me solve the problem. The problem is that in my pp object argument for delay feedback, I was using 0. and 1000. as my min. and max. values, but should have been using 0 and 1000. I changed that, and it worked like a charm in the plug. I’m off to the wonderful world of building my own plugins now. :)

Thanks to all again,

Kris

#84869
Oct 1, 2006 at 6:12pm

Quote: info@krispenhartung.com wrote on Sun, 01 October 2006 11:51
—————————————————-
> I changed that, and it worked like a charm in the plug. I’m off to the wonderful world of building my own plugins now. :)
> Kris

vst-mac.info is eagerly awaiting your first public release.

#84870
Oct 1, 2006 at 6:16pm

Uh oh…but I’m using XP. Can an XP MAX user build a plug to work on mac? / K

Quote: Roman Thilenius wrote on Sun, 01 October 2006 12:12
—————————————————-
> Quote: info@krispenhartung.com wrote on Sun, 01 October 2006 11:51
> —————————————————-
> > I changed that, and it worked like a charm in the plug. I’m off to the wonderful world of building my own plugins now. :)
> > Kris
>
>
> vst-mac.info is eagerly awaiting your first public release.
—————————————————-

#84871
Oct 1, 2006 at 6:19pm

In a word no, but I’m sure someone would compile the plugin for you on a mac.

#84872
Oct 1, 2006 at 6:24pm

—————————————————-
> Uh oh…but I’m using XP. Can an XP MAX user build a plug to work on mac? / K

there are several people currently working on implementing
“plug-in distribution including source” as the regular
form of releasing plug-ins. some people already started it
doing with their own software and i will join too on my
next website update.

#84873
Oct 1, 2006 at 6:49pm

hello

recently i changed some things in my web site. among them, some max
patches and externals were included. for instance, some
implementations of daubechies wavelettes transform, stocastic
distributions and other things, as closed works. in all cases, source
code in max or c is provided.

http://www.sonoscop.net/jmb/ –> cosas de max

for spanish readers, some new texts have been added. they discusses
about listening and the uses of “real time” term in non technological
musical contexts.

jmb

jose manuel berenguer
jmbeal@telefonica.net +34932857046 +34696538403. http://
http://www.sonoscop.net/jmb/
jmberenguer@sonoscop.net +34933064128. http://www.sonoscop.net/
caos->sonoscop. cccb. montalegre, 5. 08001 barcelona
spain

#84874
Oct 1, 2006 at 9:15pm

Quote: Roman Thilenius wrote on Sun, 01 October 2006 12:24
—————————————————-
> there are several people currently working on implementing
> “plug-in distribution including source” as the regular
> form of releasing plug-ins. some people already started it
> doing with their own software and i will join too on my
> next website update.
>
—————————————————-

This is great. I am a member of the Reaktor library, and I really like the way that tool is constructed, and the availability of ensembles is massive. Hence, a centalized respository for MAX/MSP patches and/or plugs would be outstanding, or even a few de-centralized sites. The more the better. And of course, I more interested in those for live performance, especially guitar.

My plans for my utterly simple minded delay patch/plug is to build on it and create an approximation of a patch I have on my Boss VF-1 processor. It is essentially two pitch shifters and two delays that feed the pitch back in on itself, thus allowing ascending and descending octave arpegiation; but the most interesting effect for me is when you crank the feedback up with some higher delay times…makes some really rich and twisted pad-like sounds…anyway, I’m sure someone has already created a MAX/MSP patch like that, but is more of the principle of doing it myself.

Kris

#84875
Oct 1, 2006 at 9:30pm

shucks,

There are lots of max sites….. nothing like the Reaktor ensemble library though. Probably a good thing =/ There are some pretty crazy reaktor ensembles.

There’s the user pages here and all that. There’s a listing of 3rd party externals for windows too somewhere [besides maxobjects.com]

gee willickers

#84876
Oct 1, 2006 at 9:40pm

I think the power of MAX/MSP and what people can do with it, is what makes searching for what I want difficult. At the Reaktor library, if I want effects for live performance, I can easily find them…modulation, delays, pitch, multi-effects, experimental effects, and so on. When I start Googling for MAX/MSP patches, I usually end up finding a site of patches that are not at all useful for live performance on the guitar, but do all sorts of crazy and unbelievable things like computations, synthesis, vistual effects, etc. It would be nice to find a MAX/MSP patch library just for performing musicians….of course, it may very well be out there if I search long enough. And then there is the issue of pay-only pathches…and some sites, like on the maxobjects site take me to places where I have no idea what I’m looking at…a MAX patch that will turn my coffee maker on in the morning? :)

Kris

Quote: DrSbaitso wrote on Sun, 01 October 2006 15:30
—————————————————-
> shucks,
>
> There are lots of max sites….. nothing like the Reaktor ensemble library though. Probably a good thing =/ There are some pretty crazy reaktor ensembles.
>
> There’s the user pages here and all that. There’s a listing of 3rd party externals for windows too somewhere [besides maxobjects.com]
>
> gee willickers
>
>
>
—————————————————-

#84877
Oct 1, 2006 at 9:44pm

Yeah, Reaktor is much better for that sort of thing =/ The way it’s structured and the caps it has on philosophy and lack of dependencies upon “other resources” all make it easier to pick and combine things. After all, you can chain like 2-3 high level concepts together in Reaktor and the structuring from the get-go will result in that as being apart of the outcome. Not so in Max. Max is too open ended with everything. From usage, to patch structure, to using abstractions… it all makes it very difficult. Maxers are much more unique in that patches wind up much more unique than Reaktor users. Good or bad, well, both…, really.

#84878
Oct 1, 2006 at 9:51pm

Also, I don’t think I’ve ever really found much use for another maxers patch/collective. They just don’t ever make sense to me. Even pluggo plugins.

My idea of sharing in max is building a set of intermediate abstractions or lower level externals to share with the community. Right now I have like 650 3rd party externals [.mxe] files in my search path. To me, another persons idea of efficiency while working with in Max is the real way things are shared around here.

#84879
Oct 1, 2006 at 10:00pm

I was just thinking, if reaktor ever built in the capability to convert their ensembles to vst plugins, I’d be in heaven. I already run Reaktor inside of MAX, but it’s just a bit funky with all the snaps and everything..not as easy to control as with VSTs and presets.

Kris

Quote: DrSbaitso wrote on Sun, 01 October 2006 15:44
—————————————————-
> Yeah, Reaktor is much better for that sort of thing =/ The way it’s structured and the caps it has on philosophy and lack of dependencies upon “other resources” all make it easier to pick and combine things. After all, you can chain like 2-3 high level concepts together in Reaktor and the structuring from the get-go will result in that as being apart of the outcome. Not so in Max. Max is too open ended with everything. From usage, to patch structure, to using abstractions… it all makes it very difficult. Maxers are much more unique in that patches wind up much more unique than Reaktor users. Good or bad, well, both…, really.
—————————————————-

#84880
Oct 1, 2006 at 11:37pm

Well, that would be nice, I must admit. NI is retarded. Synthedit/Synthmaker/Pluggo will have to suffice ;)

#84881
Oct 2, 2006 at 3:22pm

Wow, i’ve been away for a few days and after checking my emails I see this thread’s come alive!

Some interesting info on the basics of Pluggo development too, which is nice to read. I’ve actually come to a few problems myself but whilst trying to work out how best to explain them i’ve actually stumbled on the solution, which has been poetry in motion.

My first pluggo’s been an attempt to make a multiband delay using the FFT object to split the signals into seperate frequency bands and then delaying each of them by different factors. Mainly because the use of [FFT~] is something I really need to brush up on, but also because i thought it’d make an interesting basis for applying more complex effects to later. So far the signs are good and i’ve managed to make some interesting rhythms by applying a single looped drum hit to it…but there’s still quite some distance to go with it yet.

Kris: I took a look at your patch, (the real rats nest one), and can i suggest you try right clcking on your connections and then selecting align, it’s a very usefull trick for patch intelligibility. Also when you’re looping your connections back round to the [pp] objects, if you hold down ctrl it’ll let you make “segmented patch cords” without having to have them selected permanently, (which really annoys me). By doing that you can fold them back round segment by segment and make your connections go round corners, if that makes sense. Sorry I can’t be of more help to you yet, (and even more sorry if that seems patronising because it’s not intended to be)…just some very small bits of wisdom from one Pluggo newbie to another :)

Roman: If i’ve understood what you’re saying, that you’re working on a way of cross comaptibility between Plugs compiled on different platforms being interchangable, that’d be an excellent development…especially for us XP users because there’s so many good looking Pluggos out there that are Mac only :(

DrSbaitso: NI is retarded, you’ve got that right, and most of their plugins are chronic CPU hogs too! ;)

#84882
Oct 6, 2006 at 8:25pm

Krispen Hartung wrote:
> Uh oh…but I’m using XP. Can an XP MAX user build a plug to work on
> mac? / K

I can build it for you… ;-)

I still didn’t release my nice pluggos to the public…

Stefan


Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com

#84883

You must be logged in to reply to this topic.