![]() |
|
[FIXED] Strange/unexpected behaviour of ^46 on CV16 - Printable Version +- XOR Userforum (https://forum.xor.eu) +-- Forum: Products (https://forum.xor.eu/forumdisplay.php?fid=3) +--- Forum: NerdSEQ (https://forum.xor.eu/forumdisplay.php?fid=6) +---- Forum: Nerdseq issue / bugreport (https://forum.xor.eu/forumdisplay.php?fid=8) +----- Forum: Beauty and less important bugs/glitches (https://forum.xor.eu/forumdisplay.php?fid=16) +----- Thread: [FIXED] Strange/unexpected behaviour of ^46 on CV16 (/showthread.php?tid=1181) |
[FIXED] Strange/unexpected behaviour of ^46 on CV16 - mgd - 08-23-2021 Hi! I'm making progress w/r to shaping the trigger/gates of the CV16 to my liking. I now have the following problem or at least unexpected behaviour: I currently mostly use ^40 (envelope 4 as AR envelope) for my notes and with proper settings for Attack and Release that sounds ok and looks fine on my scope. I also have a couple of ^46 spread where there were longer notes that I wanted to end at the time I placed the ^46. What I see on the scope and also hear is that the ^46 creates a short spike/trigger although the envelope is already at 0. That is unexpected as I had expected ^x6 essentially ends/stops the current modulator (in case of an envelope sends it to 0). Is there a reason for this spike/trigger or is that a bug? Kind regards, Michael RE: Strange/unexpected behaviour of ^46 on CV16 - XORadmin - 08-23-2021 I think (can confirm tomorrow) that the stop command releases the modulator and sets the voltage back to the original value (being a note or pitch). Depending on add/pure and a finished envelope there should be no change when executing the stop RE: Strange/unexpected behaviour of ^46 on CV16 - XORadmin - 08-27-2021 I finally checked this with a scope and indeed the stop modulator command generates a spike sometimes (either with and without a running modulator). This is in the CV16 expander, so I got to check in there what is going on. Will be moved to bugs. RE: [FIXED] Strange/unexpected behaviour of ^46 on CV16 - XORadmin - 12-28-2022 Fixed with CV16 Firmware V1.2 |