Some guy in the MAX/MSP facebook group was able to reverse engineer and find the formula.
It's [expr out_low + (out_high-out_low) * exp(-1 * (in_high-in_low) * log(power)) * exp(($f1 - in_low) * log(power))], and it seems to just WORK PERFECTLY!! A few more test, and I can get on to cloning it... the formula in the reference was just a lot of bull crap... cheers 2015-06-20 16:37 GMT-03:00 Alexandre Torres Porres <[email protected]>: > > compatibility also means keeping (functionality) bugs. > > Yes it does! But, anyway, the point is that I do not really see a "bug" > here... > > 2015-06-20 15:51 GMT-03:00 IOhannes m zmölnig <[email protected]>: > >> On 06/20/2015 03:55 AM, Joel Matthys wrote: >> > I just don't see the value of trying to make it compatible with broken >> > code in Max. >> >> the sole purpose of cyclone is to provide compatibility with max: if you >> have a max(<5) patch, it makes it trivial to port it to Pd. >> >> compatibility also means keeping (functionality) bugs. >> >> if you don't care about compatibility, there are plenty of other >> externals out there, that might fit your bill. >> >> >> gfdsamr >> IOhannes >> >> >> _______________________________________________ >> [email protected] mailing list >> UNSUBSCRIBE and account-management -> >> http://lists.puredata.info/listinfo/pd-list >> >> >
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
