Open darwingrosse opened 8 years ago
I can't find the cause of this, but I managed to fix it on my computer by twiddling around a bit. Can you try the latest commits and see if that fixes it for you?
I've seen this parameter confusion before, but I've been unable to find a consistent recipe to duplicate it. I just tried your example and it works for me. Wouldn't this be a Max issue and not a Beap issue? I would LOVE to see it resolved.
I'll raise the issue with engineering. Thanks for looking.
[ddg]
On Tue, Dec 8, 2015 at 5:41 AM, Matthew Davidson notifications@github.com wrote:
I've seen this parameter confusion before, but I've been unable to find a consistent recipe to duplicate it. I just tried your example and it works for me. Wouldn't this be a Max issue and not a Beap issue? I would LOVE to see it resolved.
[image: screen shot 2015-12-08 at 7 41 06 am] https://cloud.githubusercontent.com/assets/422217/11655873/1572cefa-9d7f-11e5-8b76-50ce4aed955e.png
— Reply to this email directly or view it on GitHub https://github.com/stretta/BEAP/issues/56#issuecomment-162868725.
Also, regarding envelope timings, would it be feasible to standardize the durations to a longer time than 4 seconds? My preference is for at least 10 seconds with an exponential scaling. That gives sufficient precision for low values but provides room to grow. (And in general anywhere we have a timing control it should probably be exponentially scaled)
PM On Dec 8, 2015 10:03 AM, "darwingrosse" notifications@github.com wrote:
I'll raise the issue with engineering. Thanks for looking.
[ddg]
On Tue, Dec 8, 2015 at 5:41 AM, Matthew Davidson <notifications@github.com
wrote:
I've seen this parameter confusion before, but I've been unable to find a consistent recipe to duplicate it. I just tried your example and it works for me. Wouldn't this be a Max issue and not a Beap issue? I would LOVE to see it resolved.
[image: screen shot 2015-12-08 at 7 41 06 am] < https://cloud.githubusercontent.com/assets/422217/11655873/1572cefa-9d7f-11e5-8b76-50ce4aed955e.png
— Reply to this email directly or view it on GitHub https://github.com/stretta/BEAP/issues/56#issuecomment-162868725.
— Reply to this email directly or view it on GitHub https://github.com/stretta/BEAP/issues/56#issuecomment-162908491.
FWIW, I too have seen it, and I believe this might be something that can/will be fixed for Max 7.1.1. Once Max 7.1 is out the door, we can start looking at this and some other parameter-related issues that likely affect BEAP.
-Ben
On Tue, Dec 8, 2015 at 7:09 AM, petermcculloch notifications@github.com wrote:
Also, regarding envelope timings, would it be feasible to standardize the durations to a longer time than 4 seconds? My preference is for at least 10 seconds with an exponential scaling. That gives sufficient precision for low values but provides room to grow. (And in general anywhere we have a timing control it should probably be exponentially scaled)
PM On Dec 8, 2015 10:03 AM, "darwingrosse" notifications@github.com wrote:
I'll raise the issue with engineering. Thanks for looking.
[ddg]
On Tue, Dec 8, 2015 at 5:41 AM, Matthew Davidson < notifications@github.com
wrote:
I've seen this parameter confusion before, but I've been unable to find a consistent recipe to duplicate it. I just tried your example and it works for me. Wouldn't this be a Max issue and not a Beap issue? I would LOVE to see it resolved.
[image: screen shot 2015-12-08 at 7 41 06 am] <
https://cloud.githubusercontent.com/assets/422217/11655873/1572cefa-9d7f-11e5-8b76-50ce4aed955e.png
— Reply to this email directly or view it on GitHub https://github.com/stretta/BEAP/issues/56#issuecomment-162868725.
— Reply to this email directly or view it on GitHub https://github.com/stretta/BEAP/issues/56#issuecomment-162908491.
— Reply to this email directly or view it on GitHub https://github.com/stretta/BEAP/issues/56#issuecomment-162909854.
Thanks Ben.
Peter - I'm for longer envelope segments (and expo scaling). I agree 10 seconds is better.
Looks like the parameter business is cleaned up. I'll leave this open for the envelope segment time issue...
Have a saved BEAP-based patch with an ADSR envelope in it. Delete the ADSR and drag in an AHD envelope. The Hold parameter will be renamed "Sustain", causing much confusion. See tomorrow's newsletter video for an example...
:-(