I'm trying to add that reverb in to my own patch. I simply copied and pasted the "pd reverb" subpatch in to my own. The "reverb-echo" abstraction isn't being found by my own patch (it shows up with a red outline, and an error in the console: "reverb-echo ... couldn't create".
The example patch works fine, loads that abstraction no problem. But it doesn't work in my own patch.
I tried loading a different abstraction in to my own patch, and it loads just fine.
Any ideas what's going on here? How can I get better debugging information than "couldn't create"?
thanks!
-Morgan
2011/2/15 Morgan Packard morgan@morganpackard.com
I'm trying to add that reverb in to my own patch. I simply copied and pasted the "pd reverb" subpatch in to my own. The "reverb-echo" abstraction isn't being found by my own patch (it shows up with a red outline, and an error in the console: "reverb-echo ... couldn't create".
The example patch works fine, loads that abstraction no problem. But it doesn't work in my own patch.
I tried loading a different abstraction in to my own patch, and it loads just fine.
Any ideas what's going on here? How can I get better debugging information than "couldn't create"?
The reason is that the abstraction 'reverb-echo.pd' is not in a location where your pd goes looking for possible abstractions (search path, see File
Path...), and is also not in the same directory as your own patch in which
you want it to be loaded. Quick and easy solution: copy the file 'reverb-echo.pd' to the same directory as where your own patch is located and then try again. gr, Tim
thanks!
-Morgan
--
Web: http://www.morganpackard.com
Music/Art: Latest album: Moment Again Elsewherehttp://www.anticipaterecordings.com/releases/ANT_011/index.php iOS app Thicket http://itunes.apple.com/us/app/thicket/id364824621?mt=8available on iTunes store . ================================
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hi,
On Tue, Feb 15, 2011 at 03:43:35AM +0100, tim vets wrote:
Quick and easy solution: copy the file 'reverb-echo.pd' to the same directory as where your own patch is located and then try again.
Even quicker would be to use one of the three builtin reverbs by Miller in the "extra" dfirectory: [rev1~], [rev2~] or [rev3~]. [rev2~] is similar to the docs example.
Ciao
Frank Barknecht Do You RjDj.me? _ ______footils.org__
I don't entirely follow what is happening with your files. But in order to access abstractions they need to have a file path, which you can setup via the preferences menu>>>Path. I don't know if you are aware of this or not.
I put all mine in a folder called "abstractions" which I have set up a path to.
On Tue, Feb 15, 2011 at 1:33 PM, Morgan Packard morgan@morganpackard.comwrote:
I'm trying to add that reverb in to my own patch. I simply copied and pasted the "pd reverb" subpatch in to my own. The "reverb-echo" abstraction isn't being found by my own patch (it shows up with a red outline, and an error in the console: "reverb-echo ... couldn't create".
The example patch works fine, loads that abstraction no problem. But it doesn't work in my own patch.
I tried loading a different abstraction in to my own patch, and it loads just fine.
Any ideas what's going on here? How can I get better debugging information than "couldn't create"?
thanks!
-Morgan
--
Web: http://www.morganpackard.com
Music/Art: Latest album: Moment Again Elsewherehttp://www.anticipaterecordings.com/releases/ANT_011/index.php iOS app Thicket http://itunes.apple.com/us/app/thicket/id364824621?mt=8available on iTunes store . ================================
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Why not always put your abstractions in the same directory as the patch? (Or in a subdirectory if you want to organize them that way.) It makes things more modular: e.g., you can just compress the containing directory and shoot it off rather than sending a separate attachment for abstractions and have them copy your manually-entered search patch settings (which most likely will not be the same across platforms).
Additionally, the patch directory is searched first (at least according to the manual), so you're less likely to run into name clashes that way. (And then you can guarantee no nameclashes by prefixing your abstractions with a "./" like [./my-abs].)
-Jonathan
--- On Tue, 2/15/11, Richie Cyngler glitchpop@gmail.com wrote:
From: Richie Cyngler glitchpop@gmail.com Subject: Re: [PD] noob question: trying to repurpose the G08.reverb.pd example To: "Morgan Packard" morgan@morganpackard.com Cc: "pd list" pd-list@iem.at Date: Tuesday, February 15, 2011, 3:45 AM
I don't entirely follow what is happening with your files. But in order to access abstractions they need to have a file path, which you can setup via the preferences menu>>>Path. I don't know if you are aware of this or not.
I put all mine in a folder called "abstractions" which I have set up a path to.
On Tue, Feb 15, 2011 at 1:33 PM, Morgan Packard morgan@morganpackard.com wrote:
I'm trying to add that reverb in to my own patch. I simply copied and pasted the "pd reverb" subpatch in to my own. The "reverb-echo" abstraction isn't being found by my own patch (it shows up with a red outline, and an error in the console: "reverb-echo ... couldn't create".
The example patch works fine, loads that abstraction no problem. But it doesn't work in my own patch. I tried loading a different abstraction in to my own patch, and it loads just fine.
Any ideas what's going on here? How can I get better debugging information than "couldn't create"? thanks! -Morgan
On Tue, 15 Feb 2011, Jonathan Wilkes wrote:
Why not always put your abstractions in the same directory as the patch? (Or in a subdirectory if you want to organize them that way.) It makes things more modular: e.g., you can just compress the containing directory and shoot it off rather than sending a separate attachment for abstractions and have them copy your manually-entered search patch settings (which most likely will not be the same across platforms).
But sending a separate attachment also makes things more modular, as it allows using the exact same abstraction collection over several different patches. As those object-classes (abstractions) become more familiar, they become something that doesn't have to be relearned per-project and it becomes a common vocabulary across projects.
It's two different kinds of modularity.
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
-
Frank Barknecht -
Jonathan Wilkes -
Mathieu Bouchard -
Morgan Packard -
Richie Cyngler -
tim vets