On 05/15/2014 05:31 PM, Vesa wrote:
> So I've come up with some ideas on solving this dilemma.
>
> 1. Interpolate all volume controls (and others where similar issues
> exist) - so that volume transitions would always be smooth and not
> sudden: when the volume is changed, it slides from oldvalue to newvalue
> in the time of one period. The problem is, the behaviour and quality of
> the controls will still be dependent on period size ("buffer size" in
> settings). Regardless, this could still be a good idea to do because we
> don't always get sample-exact data, and this way we could smooth the
> changes in automations as well.
>
> 2. Make the step size only affect the knobs, and possibly the automation
> grid, but allow the actual values of the model to also go between steps.
> Maybe make this behaviour configurable per-model, add a flag or
> something that determines how step size is used. A boolean member could
> be named "strictStepSize" or something, and it determines whether the
> step size applies only on the knob or will it be "strictly" applied to
> the values of the model.
>
> 3. Add a second "step size" property, so that there's two of them: one
> that gets used by the widget (knob), and one that actually determines
> the internal step size of the model.
>
Toby, do you have an opinion on what would be the best solution here?
For the step size problem I mean...
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel
