You don't need to mess with any CVS files to get it to compile, and ideally you should just be able to tye "make", then "make install". Also take a peak in the make file to be sure it is looking in the right directory for the files it needs. particularly 'm_pd.h'
However, I just reinstalled everything on my mac, and upgraded to 10.3, and now I can't get zexy to compile!! so, I'm probably doing something wrong too.
I've realized that my above response is slightly off, the "abs~", should be a "wrap~" sorry.
also, take a look at a basic looper I've made, it may help you out if you haven't figured it all out already...
I'm not sure how to best explain this, but I'll give it a shot now, and I'll upoad a patch later today...
I'm sure you've got a "phasor~" which is driving the "tabread4", what you need to do is connect a "snapshot~" to the output of the "phasor~" which, when banged, captures the current value, then subtracts it from the output of the phasor. run that through an "abs~" and you'll be good.
(except abs~ might be in the zexy external.... but hey, you should get that anyhow.)
| \ <bang>
| \ |
| <<snapshot~ >>
<< -~ >>
I hope that helps. ...and I may have the inputs to "snapshot~" switched, I can't remember exactly how that goes off the top of my head.
what's happening is this;
when a note is hit a message is sent with the note number, velocity, channel, etc..., and when when it is released all of the same information is sent again, with the important difference that the velocity is zero.
In your current patch the velocity is used to trigger the envelope, regardless of its value. To stop the double notes you need to filter out any velocities whose value is zero.
A easy way to do that is with the "select" (or "sel") object.
connect the second output of your "notein" with the first input of a "select 0", then connect the second output of the "select 0" to the "t" message box.
(also check out the trigger object box, it will work better and be more flexible that the "t" message box that your patch currently uses)
hope that all helps.
now I've never tried it but...
As I understand it the compiler that comes with cygwin is a spits out regular .exe files that *should* run outside of the cygwin environment.
Cygwin runs normal windows executables in a environment thats more familiar to us 'nix geeks. At least thats how I understand it.
I have compiled PD on Mac OS X, and had no problems, but on windows I understand that it is a little more difficult.
what happened when you tried to compile it?