Re: [PD] bendin bug (?)

; > > > Best, > > Giulio > > > > -- > > *From:* Alexandre Torres Porres <por...@gmail.com> > > *To:* Giulio Moro <giuliom...@yahoo.it> > > *Cc:* Miller Puckette <m...@ucsd.edu>; "pd-list@lists.iem.at"

Re: [PD] bendin bug (?)

ha! good point!there goes my argument. From: Alexandre Torres Porres <por...@gmail.com> To: Giulio Moro <giuliom...@yahoo.it> Cc: Miller Puckette <m...@ucsd.edu>; "pd-list@lists.iem.at" <pd-list@lists.iem.at> Sent: Monday, 12 September 2016, 2

Re: [PD] bendin bug (?)

turbance. > > Best, > Giulio > > -- > *From:* Alexandre Torres Porres <por...@gmail.com> > *To:* Giulio Moro <giuliom...@yahoo.it> > *Cc:* Miller Puckette <m...@ucsd.edu>; "pd-list@lists.iem.at" < > pd-list@lists.

Re: [PD] bendin bug (?)

ulio From: Alexandre Torres Porres <por...@gmail.com> To: Giulio Moro <giuliom...@yahoo.it> Cc: Miller Puckette <m...@ucsd.edu>; "pd-list@lists.iem.at" <pd-list@lists.iem.at> Sent: Monday, 12 September 2016, 20:34 Subject: Re: [PD] bendin bug (?)

Re: [PD] bendin bug (?)

Couldn't you simply open older patches with an older version of pd? Even gcc over time requires changes to the source that uses deprecated API. Best, -- Ivica Ico Bukvic, D.M.A. Associate Professor Computer Music ICAT Senior Fellow Director -- DISIS, L2Ork Virginia Tech School of Performing

Re: [PD] bendin bug (?)

2016-09-12 16:14 GMT-03:00 Giulio Moro : > > As far as intuitiveness is concerned, -1 to 0.999878 is the most intuitive > range for me. > You'll be glad to know that the update in cyclone will include also the -1 to 0.999878 range for you in midiformat/midiparse. I didn't

Re: [PD] bendin bug (?)

por...@gmail.com> To: Miller Puckette <m...@ucsd.edu> Cc: "pd-list@lists.iem.at" <pd-list@lists.iem.at> Sent: Monday, 12 September 2016, 20:01 Subject: Re: [PD] bendin bug (?) 2016-09-12 15:31 GMT-03:00 Miller Puckette <m...@ucsd.edu>: In fact I though

Re: [PD] bendin bug (?)

> > 2016-09-12 15:31 GMT-03:00 Miller Puckette : > > Yet another idea would be to make a new object name (pitchbendin/out) > just tell us please if you plan to do this for the next release and when do you think a 0.47-2 version might come out ;) maybe before the pdcon16? thanks

Re: [PD] bendin bug (?)

2016-09-12 15:31 GMT-03:00 Miller Puckette : > In fact I thought there already was one in Cyclone. > The one in cyclone is [xbendin] and [xbendout] and they both go from 0 to 1383. I find this pair of objects quite obsolete and I don't know why they were put in cyclone, as they

Re: [PD] bendin bug (?)

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.

Re: [PD] bendin bug (?)

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

Re: [PD] bendin bug (?)

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

Re: [PD] bendin bug (?)

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 signature.asc Description: OpenPGP digital signature

Re: [PD] bendin bug (?)

On Sep 11, Alexandre Torres Porres wrote: > But in pd it is 14-bits already > > It's just that both counterparts are not in the same standard, a bug as i > see it (bendout is -8192 to 8191 & bendin is 0 to 16383) - bendout is what > I consider the usual way to deal with pitch bend, where 0 is no

Re: [PD] bendin bug (?)

But in pd it is 14-bits already It's just that both counterparts are not in the same standard, a bug as i see it (bendout is -8192 to 8191 & bendin is 0 to 16383) - bendout is what I consider the usual way to deal with pitch bend, where 0 is no bend up/down. cheers 2016-09-11 8:15 GMT-03:00

Re: [PD] bendin bug (?)

Hello, Well, that's basically what Max does. It defaults to the original 0-127 and then you can specify a "hires" mode to use all 14-bits rather than just 8-bits like 0-127 did. We just implemented this for midiparse and midiformat in cyclone, the current version only had the 0-127. So yes, it'd

Re: [PD] bendin bug (?)

2016-09-07 16:30 GMT-03:00 Billy Stiltner : > > > On Wed, Sep 7, 2016 at 2:48 PM, Alexandre Torres Porres > wrote: > >> ok, somebody told me it was only 7 bit back in the day >> >> when 850 AD? > https://www.midi.org/articles/the-history-of-midi > no

Re: [PD] bendin bug (?)

On Wed, Sep 7, 2016 at 2:48 PM, Alexandre Torres Porres wrote: > ok, somebody told me it was only 7 bit back in the day > > when 850 AD? https://www.midi.org/articles/the-history-of-midi ___ Pd-list@lists.iem.at mailing list

Re: [PD] bendin bug (?)

ok, somebody told me it was only 7 bit back in the day 2016-09-06 20:37 GMT-03:00 Alexandre Torres Porres : > 2016-09-06 9:17 GMT-03:00 Simon Iten : > >> not sure why max would only allow 0-127, maybe you can get float values >> from it ? :) >> > > nope...

Re: [PD] bendin bug (?)

2016-09-06 9:17 GMT-03:00 Simon Iten : > not sure why max would only allow 0-127, maybe you can get float values > from it ? :) > nope... you need an extra object (xbendin/out) to use 14 bits - silly as f*ck ___

Re: [PD] bendin bug (?)

7 bits. (mm) are the >>> most significant 7 bits." >>> >>> >>> >________________ >>> > From: Alexandre Torres Porres <por...@gmail.com> >>> >To: Giulio Moro <giuliom...@yahoo.it> >>> >

Re: [PD] bendin bug (?)

__ >> > From: Alexandre Torres Porres <por...@gmail.com> >> >To: Giulio Moro <giuliom...@yahoo.it> >> >Cc: "pd-list@lists.iem.at" <pd-list@lists.iem.at> >> >Sent: Sunday, 4 September 2016, 19:33 >> >Subject:

Re: [PD] bendin bug (?)

> From: Alexandre Torres Porres <por...@gmail.com <javascript:;>> > >To: Giulio Moro <giuliom...@yahoo.it <javascript:;>> > >Cc: "pd-list@lists.iem.at <javascript:;>" <pd-list@lists.iem.at > <javascript:;>> > >Sent: Sunday, 4 September 2

Re: [PD] bendin bug (?)

I agree with Alexandre about what seems sensible, but introducing a change like this will break existing patches. Is it possible (for all changes like this) to introduce a compatibility mode to get the old behavior? Yes, any seasoned Pd hacker will know how to fix the scaling. I'm just imagining

Re: [PD] bendin bug (?)

rres Porres <por...@gmail.com> >To: Giulio Moro <giuliom...@yahoo.it> >Cc: "pd-list@lists.iem.at" <pd-list@lists.iem.at> >Sent: Sunday, 4 September 2016, 19:33 >Subject: Re: [PD] bendin bug (?) > > > > > > > >2016-09-04 13:35 GMT-03

Re: [PD] bendin bug (?)

2016-09-04 13:35 GMT-03:00 Giulio Moro : > Is this a [bendin] or a [bendout] bug? > > [bendin]'s current implementation is closer to the actual MIDI messages > being transmitted. > but in actuality, the not raw standard is from -8192 to 8191 right? I just care they both

Re: [PD] bendin bug (?)

6, 17:26 Subject: [PD] bendin bug (?) so, bendout takes from -8192 to 8191, but bendin will receive from 0 to 16383, which is inconsistent with the bendin message, can it be considered a bug and fixed? cheers ___ Pd-list@lists.iem.at mailing list U

[PD] bendin bug (?)

so, bendout takes from -8192 to 8191, but bendin will receive from 0 to 16383, which is inconsistent with the bendin message, can it be considered a bug and fixed? cheers ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management ->