Re: [PD] polyWaveSynth issue
Patrice Colet wrote: Mathieu Bouchard a écrit : On Sun, 9 Sep 2007, Kyle Klipowicz wrote: Yes, I can understand how that might be frustrating. That's why I really enjoy keeping my personal settings in the .pdrc file on OS X or Linux. With windows, this isn't an option, but a .bat file works well. With windows we can change options with editing the registry. and a .bat doesn't work well because of the interfering registry entries. does the -noprefs flag not work on windows? fmasd.r IOhannes ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] polyWaveSynth issue
IOhannes m zmoelnig a écrit : Patrice Colet wrote: Mathieu Bouchard a écrit : On Sun, 9 Sep 2007, Kyle Klipowicz wrote: Yes, I can understand how that might be frustrating. That's why I really enjoy keeping my personal settings in the .pdrc file on OS X or Linux. With windows, this isn't an option, but a .bat file works well. With windows we can change options with editing the registry. and a .bat doesn't work well because of the interfering registry entries. does the -noprefs flag not work on windows? fmasd.r IOhannes Yes it works, I just forgot this option, thank you for reminding me this usefull one. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] polyWaveSynth issue
Hallo, Luigi Rensinghoff hat gesagt: // Luigi Rensinghoff wrote: i was curious to check out that synth, but i get this error. the screenshot i from ubuntu, but it was the same on OS X. You can fix this by adding your polyWaveSynth directory to your pd-path or copy over poly*.pd to that director.y As polypoly.pd lives in a different directory from polyWaveSynth, it cannot find the objects it creates dynamically. (I'm not sure, if it *should* see them, though, i.e. if this is a bug in Pd.) Ciao -- Frank Barknecht _ __footils.org_ __goto10.org__ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] polyWaveSynth issue
Hi Phil~ Perhaps you could repackage the polyWaveSynth with the required abstractions included, since they are very small in size to make much of a difference? This might eliminate much of the frustration that seems to be plaguing some people. ~Kyle On 9/9/07, Frank Barknecht [EMAIL PROTECTED] wrote: Hallo, Luigi Rensinghoff hat gesagt: // Luigi Rensinghoff wrote: i was curious to check out that synth, but i get this error. the screenshot i from ubuntu, but it was the same on OS X. You can fix this by adding your polyWaveSynth directory to your pd-path or copy over poly*.pd to that director.y As polypoly.pd lives in a different directory from polyWaveSynth, it cannot find the objects it creates dynamically. (I'm not sure, if it *should* see them, though, i.e. if this is a bug in Pd.) Ciao -- Frank Barknecht _ __footils.org_ __goto10.org__ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list -- - - - -- http://perhapsidid.wordpress.com http://myspace.com/kyleklipowicz ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] polyWaveSynth issue
Hi Kyle, I thought of doing that, but reconsidered because it seems like it might lead to versioning problems, namespace clashes, multiple copies of objects and possibly, dogs and cats sleeping together. Or am I over-thinking it? Phil Kyle Klipowicz wrote: Hi Phil~ Perhaps you could repackage the polyWaveSynth with the required abstractions included, since they are very small in size to make much of a difference? This might eliminate much of the frustration that seems to be plaguing some people. ~Kyle On 9/9/07, Frank Barknecht [EMAIL PROTECTED] wrote: Hallo, Luigi Rensinghoff hat gesagt: // Luigi Rensinghoff wrote: i was curious to check out that synth, but i get this error. the screenshot i from ubuntu, but it was the same on OS X. You can fix this by adding your polyWaveSynth directory to your pd-path or copy over poly*.pd to that director.y As polypoly.pd lives in a different directory from polyWaveSynth, it cannot find the objects it creates dynamically. (I'm not sure, if it *should* see them, though, i.e. if this is a bug in Pd.) Ciao -- Frank Barknecht _ __footils.org_ __goto10.org__ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] polyWaveSynth issue
Hallo, Phil Stone hat gesagt: // Phil Stone wrote: I thought of doing that, but reconsidered because it seems like it might lead to versioning problems, namespace clashes, multiple copies of objects and possibly, dogs and cats sleeping together. I've found an easier solution: add [declare -path .] to polyWaveSynth.pd. Or was it PolyWaveSynth.pd? PolyWavesynth.pd? I think all lowercase names are easier to remember hint,hint. ;) Ciao -- Frank Barknecht _ __footils.org_ __goto10.org__ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] polyWaveSynth issue
Frank Barknecht wrote: Hallo, Phil Stone hat gesagt: // Phil Stone wrote: I thought of doing that, but reconsidered because it seems like it might lead to versioning problems, namespace clashes, multiple copies of objects and possibly, dogs and cats sleeping together. I've found an easier solution: add [declare -path .] to polyWaveSynth.pd. That requires 40.0, right? Also, there doesn't seem to be a help patch for [declare] -- I've seen it mentioned here on the list, but is it documented anywhere? It looks like it would add [polyWaveSynth]s folder to PD's path -- but how would PD find [polyWaveSynth] to load it in the first place? Plus, does this really avoid any problems from including dependent objects (possibly creating multiple copies) inside abstraction folders? Or was it PolyWaveSynth.pd? PolyWavesynth.pd? I think all lowercase names are easier to remember hint,hint. ;) i'llconsiderthatforthenextrelease. :-) Phil ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] polyWaveSynth issue
Phil~ I don't think it would cause problems if you keep them in a subdirectory and addressed the abstractions with abs/foobar.pd type naming. Does Pd search the patch's folder first for all non-native objects before parsing the path? Also, this will all become resolved once Pd-extended moves forward to including more recent abstractions in its releases (i.e. Pd-extended-0.40 or however it will be branded). Until then, we just can't really expect the same crowd that Pd-extended is marketed for to know much about cvs and setting up the paths and stuff. It's better to take the high road and avoid elitist isolationism and make things easy as possible for new users to dive into: Pd needs adherents to thrive and become a serious competitor of similar commercial options. I think that this object will be a great selling point for new Pd users, especially because of the polyphony. Polyphony management is one of the most annoying things for new (and more seasoned) users to deal with in Pd. Your synth (combined w/ Frank's freaking awesome abstractions) has a great possibility for becoming a template for many awesome modifications and enhancements down the line. ~Kyle On 9/9/07, Phil Stone [EMAIL PROTECTED] wrote: Hi Kyle, I thought of doing that, but reconsidered because it seems like it might lead to versioning problems, namespace clashes, multiple copies of objects and possibly, dogs and cats sleeping together. Or am I over-thinking it? Phil Kyle Klipowicz wrote: Hi Phil~ Perhaps you could repackage the polyWaveSynth with the required abstractions included, since they are very small in size to make much of a difference? This might eliminate much of the frustration that seems to be plaguing some people. ~Kyle On 9/9/07, Frank Barknecht [EMAIL PROTECTED] wrote: Hallo, Luigi Rensinghoff hat gesagt: // Luigi Rensinghoff wrote: i was curious to check out that synth, but i get this error. the screenshot i from ubuntu, but it was the same on OS X. You can fix this by adding your polyWaveSynth directory to your pd-path or copy over poly*.pd to that director.y As polypoly.pd lives in a different directory from polyWaveSynth, it cannot find the objects it creates dynamically. (I'm not sure, if it *should* see them, though, i.e. if this is a bug in Pd.) Ciao -- Frank Barknecht _ __footils.org_ __goto10.org__ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list -- - - - -- http://perhapsidid.wordpress.com http://myspace.com/kyleklipowicz ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] polyWaveSynth issue
Hallo, Phil Stone hat gesagt: // Phil Stone wrote: That requires 40.0, right? Also, there doesn't seem to be a help patch for [declare] -- I've seen it mentioned here on the list, but is it documented anywhere? It looks like it would add [polyWaveSynth]s folder to PD's path -- but how would PD find [polyWaveSynth] to load it in the first place? Uhm, I don't really know, when declare was introduced, may indeed be with 0.40. Anyway, adding the directory of pWS to the path will make polypoly.pd find the objects it needs to create copies from. One can either add the directory using pd -path ... or using [declare]. However there are still some problems with that, which I will post in a separate mail. Ciao -- Frank Barknecht _ __footils.org_ __goto10.org__ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] polyWaveSynth issue
Kyle Klipowicz wrote: Phil~ I don't think it would cause problems if you keep them in a subdirectory and addressed the abstractions with abs/foobar.pd type naming. OK, I think it's starting to sink in. I can keep private abstraction libraries inside my abstraction. Another advantage to this is that I can control the versioning of these libraries -- only updating them when I know they don't break [polyWaveSynth]. (Man, I wish the whole PD namespace thing weren't such a ball of confusion, to me at least. I guess it's a natural consequence of the organic growth of PD, though.) Does Pd search the patch's folder first for all non-native objects before parsing the path? I was wondering that same thing. If not, this method wouldn't work very consistently. Also, this will all become resolved once Pd-extended moves forward to including more recent abstractions in its releases (i.e. Pd-extended-0.40 or however it will be branded). Yes. (Hans? Frank?) please add sssad and polypoly to Pd-extended! Until then, we just can't really expect the same crowd that Pd-extended is marketed for to know much about cvs and setting up the paths and stuff. It's better to take the high road and avoid elitist isolationism and make things easy as possible for new users to dive into: Pd needs adherents to thrive and become a serious competitor of similar commercial options. Agreed. I just want to make sure I don't screw up the user's namespace, though. That sort of thing will lose adherents in a hurry. :-) I think that this object will be a great selling point for new Pd users, especially because of the polyphony. Polyphony management is one of the most annoying things for new (and more seasoned) users to deal with in Pd. Your synth (combined w/ Frank's freaking awesome abstractions) has a great possibility for becoming a template for many awesome modifications and enhancements down the line. What a nice thing to hear! Thanks, Kyle. Phil ~Kyle On 9/9/07, Phil Stone [EMAIL PROTECTED] wrote: Hi Kyle, I thought of doing that, but reconsidered because it seems like it might lead to versioning problems, namespace clashes, multiple copies of objects and possibly, dogs and cats sleeping together. Or am I over-thinking it? Phil Kyle Klipowicz wrote: Hi Phil~ Perhaps you could repackage the polyWaveSynth with the required abstractions included, since they are very small in size to make much of a difference? This might eliminate much of the frustration that seems to be plaguing some people. ~Kyle On 9/9/07, Frank Barknecht [EMAIL PROTECTED] wrote: Hallo, Luigi Rensinghoff hat gesagt: // Luigi Rensinghoff wrote: i was curious to check out that synth, but i get this error. the screenshot i from ubuntu, but it was the same on OS X. You can fix this by adding your polyWaveSynth directory to your pd-path or copy over poly*.pd to that director.y As polypoly.pd lives in a different directory from polyWaveSynth, it cannot find the objects it creates dynamically. (I'm not sure, if it *should* see them, though, i.e. if this is a bug in Pd.) Ciao -- Frank Barknecht _ __footils.org_ __goto10.org__ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] polyWaveSynth issue
Kyle Klipowicz a écrit : Until then, we just can't really expect the same crowd that Pd-extended is marketed for to know much about cvs and setting up the paths and stuff. It's better to take the high road and avoid elitist isolationism and make things easy as possible for new users to dive into: Pd needs adherents to thrive and become a serious competitor of similar commercial options. ~Kyle My one half cent, everytime I give some try to a new pd-extended it messes up all my pd stand-alone applications because of the freaking pdsettings, that is installed by default, without giving user choice for installing this evil file or not. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] polyWaveSynth issue
On Sun, 9 Sep 2007, Kyle Klipowicz wrote: Yes, I can understand how that might be frustrating. That's why I really enjoy keeping my personal settings in the .pdrc file on OS X or Linux. With windows, this isn't an option, but a .bat file works well. I definitely agree that the settings department is in need of some revision, it's just a matter of someone with the know-how, free time and determination to set it right. We don't even agree on what is right. Some want it more platform-dependent, some want it more platform-independent. Some are ok with path dialogs that require people to type full folder names and won't allow more than 10 folders... some are not ok with that... etc _ _ __ ___ _ _ _ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] polyWaveSynth issue
Mathieu Bouchard a écrit : On Sun, 9 Sep 2007, Kyle Klipowicz wrote: Yes, I can understand how that might be frustrating. That's why I really enjoy keeping my personal settings in the .pdrc file on OS X or Linux. With windows, this isn't an option, but a .bat file works well. With windows we can change options with editing the registry. and a .bat doesn't work well because of the interfering registry entries. I definitely agree that the settings department is in need of some revision, it's just a matter of someone with the know-how, free time and determination to set it right. Some are able to compile after getting knowledge about the configure options and then have severe chances of having a well configured software, some doesn't want to use a compiler for installing, and have a lot of chances to miss a lot of features proposed by the software, through different kinds of installing processes. We don't even agree on what is right. Some want it more platform-dependent, some want it more platform-independent. An optimized plateform-dependent version would implie the use of different application programming interfaces (eg: gtk for gnome, qt for kde, cocoa for OSX, etc...), anyone would like to go on that way? Some are ok with path dialogs that require people to type full folder names and won't allow more than 10 folders... some are not ok with that... etc I guess that's why many different softwares proposes different options during the install process. Also I don't know how these choices could be implemented through an installer. My point is that pd is necessarily messing with configuration files like pdrc or pdsettings that are inevitably interfering between different pd versions, and making impossible the clean and easy development of stand-alone applications. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] polyWaveSynth issue
Hi pdlers i was curious to check out that synth, but i get this error. the screenshot i from ubuntu, but it was the same on OS X. Bild 3.png Description: application/applefile inline: Bild 3.png i am sure you know the trick, thanks luigi___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] polyWaveSynth issue
Hi Luigi, This is a happening in [polypoly] where it replicates the [polyWaveVoice~] objects. I can't figure out what the problem is just from a screen shot, though. Did you get all the dependencies? It looks like you have at least some of the polypoly objects, but something like this is often a path problem: all the dependencies, as well as the polyWaveSynth archive, have to be in PD's path. Sorry if I'm suggesting obvious things to you, but I can't think what else this would be. Anyone else having the same trouble? Phil Luigi Rensinghoff wrote: Hi pdlers i was curious to check out that synth, but i get this error. the screenshot i from ubuntu, but it was the same on OS X. i am sure you know the trick, thanks luigi ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
