+- 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] Velocity values from Variable A : wierd behaviour (/showthread.php?tid=1913)
[FIXED] Velocity values from Variable A : wierd behaviour - Martineh - 01-06-2025
Hello Thomas,
First of all, happy new year
Here is an issue I encountered, I may have found a bug.
I followed your instructions found on this thread : https://forum.xor.eu/showthread.php?tid=1712&pid=11215#pid11215 #67 in order to control the velocity values of a midi pattern with an I2C fader.
I expected the velocity to be 127 when the variable is 4095, and that it would decrease regularly with the variable, down to minimal values.
Here is how it actually behaves :
VAR A = 4095 : Velocity is 127 (as expected)
4059 < VAR A < +-2000 -> no midi note. No output at all.
1680 <VAR A < 1360 : midi notes output again, but the velocity increases when VA decreases (which is very unexpected).
Here is a short video to show you. It was filmed with V2.01A, but I updated to V2.02 before posting this thread and exactly the same problem occurs.
Also, this relationship between velocity and variable A is not random, it's always identical. Same behaviour when using another variable (B).
You hear Nerdseq controlling a bitbox micro in the video, but I also sent midi straigh into my DAW and it's exactly the same problem.
All the best,
Martin
RE: Velocity values from Variable A : wierd behaviour - XORadmin - 01-06-2025
Thanks. I just checked the code and found the issue. That'll be fixed with the next maintenance update soonish.
Workaround: Use a random range for the velocity and change the range in the mapping based on the variable.
RE: Velocity values from Variable A : wierd behaviour - Martineh - 01-07-2025
(01-06-2025, 08:19 PM)XORadmin Wrote: Thanks. I just checked the code and found the issue. That'll be fixed with the next maintenance update soonish.
Workaround: Use a random range for the velocity and change the range in the mapping based on the variable.
Thanks to you !!!
Seriously, you rule.
EDIT : Following your suggested workaround, I managed to configure one fader to set the velocity and a second fader to set the amount of randomness added, using two variables and two random ranges.
It may seem insignificant, but for me it's a new step forward in my understanding of the mapping screen