-
assigned issue to
Delay10 - Maximum Delay Time Resets to Zero
Issue #24
resolved
The Delay10 maximum delay time is 1500 samples. When this value is reached (by Control knob for example) the delay time should clip and remain at 1500. Instead, the delay time appears to go to zero.
This does not occur in the Delay8 block.
Example patch: AAIAAAF4eJxNkE9Kw0AUh39jp/MiGhG8gLlAmcQkproqFhctRaEnSEgCgdAEmwG78DriAdx5gB7GpRsXQn1JU3RmHgyPj+/9AdRWfWF/drv2Hb6w7qpV81SVa8hcRwGg6J1iHOvb/XWFgA0MJmkKOc6jCJiTQ35HjIKWEYAjQNOsjDeuhozcgCmiF/qEzQatW1FPDgROJyYtqssH09SmYfw6TjlPxrr5K6s5s4hrSC9sZTZ90BvOu4baCDulxz4SGC7rsmBREI9dYKa+6RXUa47YA24OGD6acp3xDFmSA1O64I2csWzkBYearJsDclmsmPPzJAHu1ZZCnPi+/gc5vLaFKZuiLjeQbnLFZR31Q8+wXB63p2b4BasdSCc=
Comments (3)
-
-
- changed status to resolved
Fixed in forthcoming release.
-
Fixed issue 24 by reordering the read/write ops
→ <<cset 6202642b904b>>
- Log in to comment
This appears to be a fencepost error, or maybe I can correct it by re-ordering the read and store operations.