Coarse Probability ...

Coarse Probability Adjustments  


New Member
Joined: 3 weeks ago
Posts: 1
05/02/2020 7:01 pm  

Currently the Eloquencer only allows coarse adjustment to the probabilities. For instance there is only 8 increments for values for CV Variation Probability. Is there an option to switch the Eloquencer to allow more fine grained probabilities similar to Pamela's New Workout (which allows 1-100)?

Here's several ideas for how this could be accomplished:

  1. While editing CV Variation (or any other variation % setting): Pressing in the encoder toggles between fine and coarse adjustment modes
  2. Pressing in and holding in the encoder while turning allows fine adjustments
  3. Global menu setting to allow changing the behavior to fine vs coarse adjustment
  4. Config file edit to change the behavior to fine vs coarse adjustment

Eloquencer is a great module!

Thank you,

Member Admin
Joined: 10 months ago
Posts: 187
11/02/2020 9:59 am  

Hi @wizardofzot!

Thanks for your feedback.

The limitation of fine values in the step parameters is more related with memory than with interface.
Let's take CVP as an example. As you know CVP has 8 possible values, that means that in the internal memory it takes 3 bits 2^3=8.
In a project context that means 3 bits / step --> 48 bits/track --> 384 bits/pattern --> 24576 bits /project
This is the amount of data that needs to be stored in volatile memory in relation with CVP. We also have to store data for CVR, GL, GLP, GLR, R, RP, RVP and CV (that uses much more bits),

If we increase the amount of data related with CVP to have , let's say, 128 values ( it is always good to have numbers that are power of 2 (2^n)) we will need to use 7 bits for this parameter.  That's a subtancial increment. If we apply that increment to all step parameters will probably increase the volatile memory used like 2 or 3 times, so the volatile memory usage will be critically close to its limits, I mean there will be enough memory but won't let us to add things in the future or have the security margin in memory use.