here we go again ... i can't get it installed correctly (i thought i had it earlier...but i guess not). Granted i could just run the compiled version but i want to know how to do this. When i download load the source files for pd 0.39 and i double click on the pd icon the program runs fine..... but this is running without officially being compiled .... what am i missing by running pd this way. When i do try to compile i get this error....
cd ../extra/bonk~;make pd_darwin
make[1]: Nothing to be done for pd_darwin'. cd ../extra/choice;make pd_darwin make[1]: Nothing to be done forpd_darwin'.
cd ../extra/expr~;make pd_darwin
make[1]: Nothing to be done for pd_darwin'. cd ../extra/fiddle~;make pd_darwin make[1]: Nothing to be done forpd_darwin'.
cd ../extra/loop~;make pd_darwin
make[1]: Nothing to be done for pd_darwin'. cd ../extra/lrshift~;make pd_darwin make[1]: Nothing to be done forpd_darwin'.
cd ../extra/pique;make pd_darwin
make[1]: Nothing to be done for `pd_darwin'.
install -d //usr/local/lib/pd/bin
install: mkdir //usr/local/lib/pd: Permission denied
make: *** [install] Error 71
this was trying the "make install" method so i can just type pd and the program starts. does this error mean i'm not signed on as the superuser? When i try make and make depend i get this: As the only user of my computer i'd think i'm by default the superuser.
(src) 27 % make depend
make: Nothing to be done for depend'. (src) 28 % make cd ../extra/bonk~;make pd_darwin make[1]: Nothing to be done forpd_darwin'.
cd ../extra/choice;make pd_darwin
make[1]: Nothing to be done for pd_darwin'. cd ../extra/expr~;make pd_darwin make[1]: Nothing to be done forpd_darwin'.
cd ../extra/fiddle~;make pd_darwin
make[1]: Nothing to be done for pd_darwin'. cd ../extra/loop~;make pd_darwin make[1]: Nothing to be done forpd_darwin'.
cd ../extra/lrshift~;make pd_darwin
make[1]: Nothing to be done for pd_darwin'. cd ../extra/pique;make pd_darwin make[1]: Nothing to be done forpd_darwin'.
What is goin' on here .... i'd really appreciate tha help.
thanks, matt
Matthew Williams wrote:
install -d //usr/local/lib/pd/bin install: mkdir //usr/local/lib/pd: Permission denied make: *** [install] Error 71
this was trying the "make install" method so i can just type pd and the program starts. does this error mean i'm not signed on as the superuser?
yes
When i try make and make depend i get this: As the only user of my computer i'd think i'm by default the superuser.
no. the power of superuser has nothing to do with the number of people using a computer. "root" (as the superuser is normally called on unices) is an administrative account, while your normal user account is a, well, user account.
but why? to prevent people who don't know what they are to do any damage. just imaging you (as the only user of your machine) would do "cat /dev/null > /dev/sda" (try it as normal user; then try it as super user; then don't blame me for an unusable computer! (so don't try it out))
so the conclusion is: yes you need to be su to modifiy certain parts of the file system in order to protect you from yourself.
mfg.asdr. IOhannes
IOhannes m zmoelnig wrote:
Matthew Williams wrote:
install -d //usr/local/lib/pd/bin install: mkdir //usr/local/lib/pd: Permission denied make: *** [install] Error 71
this was trying the "make install" method so i can just type pd and the program starts. does this error mean i'm not signed on as the superuser?
yes
oh and i forgot: you don't necessarily have to "make install" in order to run your self-made pd. so you don't need to be superuser.
just start it with "../bin/pd" and you should be fine
mfg,.asd.r IOhannes
Matthew Williams wrote:
install -d //usr/local/lib/pd/bin install: mkdir //usr/local/lib/pd: Permission denied make: *** [install] Error 71
this was trying the "make install" method so i can just type pd and the program starts. does this error mean i'm not signed on as the superuser?
You can usually do "sudo make install" and give _your_ password and it will work as though you were the daemon root itself.
Martin
Hi Matthew,
You can just run the compiled version. If you are on OSX, extracting the pd-0.39-1.mac.tar.gz file creates a clickable application. (Download it from http://www-crca.ucsd.edu/~msp/software.html)
Doubleclick and Pd should start up. If this is not the case let us know (and provide information about your system).
For the beginning don't care about externals, as you probably won't need them. When teaching Pd I always tell my students to use Millers version, because as soon as they realize that there might be an external that solves their problem, they go crazy and search for externals and try to compile them instead of thinking about how to solve their problem .. and fail to learn Pd and to get anything going.
So my advice: If you want to start with Pd, study it without externals, use Millers version, and give feedback about problems before trying to compile your own or searching for externals. Always prefer solutions without externals, because this shows up the weaknesses and makes it possible to fix them in Pd itself instead of using some external hacks.
Cheers,
Guenter
On Tue, 25 Oct 2005, Matthew Williams wrote:
here we go again ... i can't get it installed correctly (i thought i had it earlier...but i guess not). Granted i could just run the compiled version but i want to know how to do this. When i download load the source files for pd 0.39 and i double click on the pd icon the program runs fine..... but this is running without officially being compiled .... what am i missing by running pd this way. When i do try to compile i get this error....
cd ../extra/bonk~;make pd_darwin make[1]: Nothing to be done for
pd_darwin'. cd ../extra/choice;make pd_darwin make[1]: Nothing to be done forpd_darwin'. cd ../extra/expr~;make pd_darwin make[1]: Nothing to be done forpd_darwin'. cd ../extra/fiddle~;make pd_darwin make[1]: Nothing to be done forpd_darwin'. cd ../extra/loop~;make pd_darwin make[1]: Nothing to be done forpd_darwin'. cd ../extra/lrshift~;make pd_darwin make[1]: Nothing to be done forpd_darwin'. cd ../extra/pique;make pd_darwin make[1]: Nothing to be done for `pd_darwin'. install -d //usr/local/lib/pd/bin install: mkdir //usr/local/lib/pd: Permission denied make: *** [install] Error 71this was trying the "make install" method so i can just type pd and the program starts. does this error mean i'm not signed on as the superuser? When i try make and make depend i get this: As the only user of my computer i'd think i'm by default the superuser.
(src) 27 % make depend make: Nothing to be done for
depend'. (src) 28 % make cd ../extra/bonk~;make pd_darwin make[1]: Nothing to be done forpd_darwin'. cd ../extra/choice;make pd_darwin make[1]: Nothing to be done forpd_darwin'. cd ../extra/expr~;make pd_darwin make[1]: Nothing to be done forpd_darwin'. cd ../extra/fiddle~;make pd_darwin make[1]: Nothing to be done forpd_darwin'. cd ../extra/loop~;make pd_darwin make[1]: Nothing to be done forpd_darwin'. cd ../extra/lrshift~;make pd_darwin make[1]: Nothing to be done forpd_darwin'. cd ../extra/pique;make pd_darwin make[1]: Nothing to be done forpd_darwin'.What is goin' on here .... i'd really appreciate tha help.
thanks, matt
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
For the beginning don't care about externals, as you probably won't need them. When teaching Pd I always tell my students to use Millers version, because as soon as they realize that there might be an external that solves their problem, they go crazy and search for externals and try to compile them instead of thinking about how to solve their problem .. and fail to learn Pd and to get anything going.
thats a really good point!!!! But to be honest i'm a little scared i'm not going to have the patients (or brains) it'll take to make the sort of things i want. Basically i want a some sort of midi patches where i can turn knobs and restructure rhythms in realtime. Sort of like the buffer override (but affecting midi instead of audio), and more coherent . I'm know people have created these things, but like you said it's just not the same as figuring it out yourself. One i'm thinking of in particular is the "glitch" vst plugin. But it's sorta lame to just use a plugin built by someone else, although it does sound tight .. i won't use it besides it's not for os x anyway. So thats my main goal for the moment. Since you teach pd, and have seen lots of different types of people use pd... what is the learning curve for someone of average intelligence. Is it the kind of thing where like one day it'll click and i'll be able to do any sort of thing i can think of. Because at the moment i have to go over tutorials 3 times before i really grasp what tha hell is actually going on. Even then i don't feel like i could create anything from what i've learned... but then again i'm only 1/2 through the control samples so it's a little to soon to tell if i really can "get it". Do you have text book for you're class? Or a syllabus i could look at? Anyway.... thanks for the advice!!!
matt
Hallo, Matthew Williams hat gesagt: // Matthew Williams wrote:
But it's sorta lame to just use a plugin built by someone else, although it does sound tight .. i won't use it besides it's not for os x anyway. So thats my main goal for the moment. Since you teach pd, and have seen lots of different types of people use pd... what is the learning curve for someone of average intelligence. Is it the kind of thing where like one day it'll click and i'll be able to do any sort of thing i can think of.
It's very similar to learning an old fashioned real instrument like the piano or saxophone: It won't make click one day, but if you listen to stuff you recorded while rehearsing two months ago, the difference will be huge. The same can happen, if you look at your patches from weeks or even years ago. You will think: "Man, today I would do this much cleaner, faster and simpler. However I still had great fun back then."
Because at the moment i have to go over tutorials 3 times before i really grasp what tha hell is actually going on. Even then i don't feel like i could create anything from what i've learned... but then again i'm only 1/2 through the control samples so it's a little to soon to tell if i really can "get it".
I'd say that's perfectly normal. And it's good that you really go through the control examples. It's tempting to skip them, because doing audio may be so much cooler, but the control stuff is very important. It's also good to re-read the html-manual several times. It's very concise and it's easy to miss stuff if only reading it once.
The two most important things to learn IMO are [trigger] and the flow of execution in a Pd patch and later the role abstractions and their arguments play. This will make it much easier to understand and read patches by other people.
Reading a good introduction to sound synthesis is very helpful, too. Of course Miller's book comes to mind, however for a more "friendly" introduction try to get a copy of Dodge/Jerse: "Computer Music".
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
Hallo, gÃŒnter geiger hat gesagt: // gÃŒnter geiger wrote:
For the beginning don't care about externals, as you probably won't need them. When teaching Pd I always tell my students to use Millers version, because as soon as they realize that there might be an external that solves their problem, they go crazy and search for externals and try to compile them instead of thinking about how to solve their problem .. and fail to learn Pd and to get anything going.
So my advice: If you want to start with Pd, study it without externals, use Millers version, and give feedback about problems before trying to compile your own or searching for externals. Always prefer solutions without externals, because this shows up the weaknesses and makes it possible to fix them in Pd itself instead of using some external hacks.
Amen!
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
-
Frank Barknecht -
günter geiger -
IOhannes m zmoelnig -
Martin Peach -
Matthew Williams