Bug #47

rampLib does not account for the clipmodes wrap and fold

Added by Trond Lossius about 9 years ago. Updated about 6 years ago.

Status:ClosedStart date:2009-05-24
Priority:NormalDue date:
Assignee:Nils Peters% Done:

100%

Category:-Spent time:-
Target version:core-maintenance-sprint
Branch: OS:

Description

imagine a message such as /rotate 370 ramp 2000

if the parameter rotate is defined with the @range/bounds 0 360
@range/clipmode wrap, it will stop ramping at 360 instead of wrapping
around.


Related issues

Related to Modular - Feature Request #1149: jcom.parameter & dataspace: Ramps should happen according... Closed 2012-05-19

History

#1 Updated by Pascal Baltazar about 9 years ago

actually, things don't happen exactly as described above...
ramping will stop somewhere after 360
e.g. in the example below, 362 works well most of the time
and the other ones are strangely behaving...
HTH,
pb
----------begin_max5_patcher----------
557.3ocyVF0biBBDG+YymBFm6wbI.FMw6o1OG2zoCQoIzQAGAaycc528CVwd
lKMcRzKs4Awwkkk+7agEeYRP3Z0NtND8CzOQAAuLIH.L4LD3+NHrjsKqfoA2
BK4ZMaCObZaeF9NCXedsxvLbTTxBTMqrBQwXbmWOnjFs32bmmD7Lr2bEyjsU
H2beMOyzJBJM11MJ14j00T3UxLL5N+XjMkpFSA2.xg3sJxAQnV+32IuMqs9Y
9UEuM1gguEEmfjrRnivaqErhtAUUy0bocoHTx95Jh3jxRpqE6a5KJgrSSTms
WmLw0L8+FUoihpDfpsrcPTM8h.UJ.0XxkApOTnrw37oUBHEJt2FwUGkUzCY0
pixJqhXlvonv0L4lSAb6w.xEXi02HmOehgsQKF9QzjKwlo3HPUeQGPoyNeNt
rkfKF9ox3KAHSR6IqufRcqvipTWDn6kCGpKFETGMej7msp3.77XlpbVEyRFt
gWi7v5lZagD970pFYtFgs2Sf6rkUHpJU4bzy0rJmwxp440hm3Hc1VddSgMJ2
3VbnR8l68UlZmzBgjmYCooeAtSOED4qYBuhhgSjzzilBhNLEPOdJXp+4yn34
GkJ11rd.2r.6JS8UNGvUKjOFLiAJvXgT++7+fv5vYeeRoUM0Ycyd2Odg96ZI
mqMBITbouS64yVQdNG5tCZkh7JkPZ7Z.c26l1NUIkd0onUmfhR9TUTxUGiVb
0oHxInH6cwHx.Uj8iWm7GP9CqbK
-----------end_max5_patcher-----------

#2 Updated by Nils Peters about 9 years ago

  • Target version set to 0.5

#3 Updated by Pascal Baltazar about 9 years ago

  • Target version changed from 0.5 to 0.5.1

#4 Updated by Tim Place over 8 years ago

  • Target version changed from 0.5.1 to 0.5.2

#5 Updated by Nils Peters over 6 years ago

  • Target version changed from 0.5.2 to 0.5.5

#6 Updated by Trond Lossius over 6 years ago

  • Status changed from New to Assigned
  • Assignee set to Trond Lossius

#7 Updated by Trond Lossius over 6 years ago

  • Target version changed from 0.5.5 to core-maintenance-sprint

#8 Updated by Trond Lossius over 6 years ago

Here's an updated patch illustrating how the problem remains.


----------begin_max5_patcher----------
631.3ocyWssjhBCD8Y3qHE09nql.BhySy9cr0VSEfnFKHgJDbb2ol+8MW.Wb
Ecb7xHOnToCoyoOcmSZdy0wKgukT4AdB7SfiyatNNFSZCNMic7JvaSywUlWy
iQdkmr1ajcJIYqzXtTPYxVqr5BdsLmHMKA1XsDKSWQYKeQPRk1sLHxeLbDve
dj9QvTy.3XH3WMqglY7tZG+Nxu08K3LICWPLS8CAEm2clJ5eLyfztdGdnrV3
fz1d20U+2nyLnKHUU3kjCh5IBtDKI.THDHvEkJvCg8yBnSvByC0ANBZheT.z
7HtCMX8i72kD6J775igBtMDj+cffBhld8DTn+0wOH3Plf7udBxe10QPyeb7y
hbtxG8G39GOvQPSrNEYpONT+3f3VsOXkNEvKAyV1KID+wjPIVkpHRh3EBCmj
S5px8njf9F5SW0zPdwV0mlhmOeUSzv8TEZbj53DL5RoFzbjkahuPtIb.q3De
CtyZ1Up3L8wwOGoQl0o7hw6NfCZHqm0ABHijRKv4fmEJwCxjDdMKqB.Uh2vV
ao4zxBdFA7p.WpMVTNISP2P.UoqHY04JeZstnlkJobFHmxHXQKPziRUNV1U4
a+zRvwSKyLMR4aqWCsUu51pNQZYTyu9ROOvVtNU5YUcxkdSAJvp1gl8w2UbT
ZAc6oEy1XR9+W23lPQaeetphWKRaAZSpBf1A1LRkjxv55qNuitEZv+B3UzrL
Bq6kWYzJ88YlHE1aR6bgCZucpe3DtGjumnY5YfFzWF2DMnPS7YflnuLzLePw
M5uXX.Amf6HZrBP3xxMDQUiKM.QIKulKzCiFYFRY1gFO5IHansuenq1au69W
lYMym.
-----------end_max5_patcher-----------

#9 Updated by Nils Peters about 6 years ago

  • Assignee changed from Trond Lossius to Nils Peters

#10 Updated by Nils Peters about 6 years ago

  • Status changed from Assigned to Closed
  • % Done changed from 0 to 100

Applied in changeset commit:2705ceafe60153ea6411ac68994724268de72b83.

Also available in: Atom PDF