I'd second that. I was aware of the bug for many years (although I erroneously thought it was the hardware which was buggy) and adopted my patches to that. I'd prefer not having to deal with broken patches, having to figure out on which pd Version it'll run correctly.
-- Orm
Am Montag, den 12. September 2016 um 14:31:19 Uhr (-0400) schrieb Miller Puckette:
Yet another idea would be to make a new object name (pitchbendin/out) with the correct behavior. (In fact I thought there already was one in Cyclone.)
cheers M
On Mon, Sep 12, 2016 at 03:28:45PM -0300, Alexandre Torres Porres wrote:
or might also be a valid point of view, I'm in favor of fixing inconsistent things like this even if it means going through a lot of hassle fixing my patches - but william huston proposed this backwards compatibility flag, which is a neat solution
cheers
2016-09-12 9:22 GMT-03:00 IOhannes m zmoelnig zmoelnig@iem.at:
On 2016-09-12 11:25, Derek Kwan wrote:
i think it'd be fine to outright change one and break backwards compat
that's most likely because you don't have accumulated a lot of patches that rely on the old behaviour.
fgmasdr IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list