Thank you Vesa for your quick response.

The accuracy problem could be solved IMHO if we would use a float instead
of an integer type for the percentage pitch value - this would also
increase the resolution of the minimum pitch value below one cent (but
don't know if the instruments could handle finer resolutions that 1 cent).
And if we would restrict the maximum resolution of this pitch float
percentage value to two digits after the comma (0.01), then the minimal
accuracy would be less than a quarter of a cent - even if you choose/select
the highest pitch range value (currently 24).

Your other concern with the exact pitch value is a valid point too. So
users with no mathematical background would need to use the calculator to
multiply the pitch with the range value.

But if we would leave the range control like it is, it would make
automation sense-less for this control (so we could actually disable the
Ctrl+Click drag and drop action for this control).



2014-06-05 8:27 GMT+01:00 Vesa <dii....@nbl.fi>:

> On 06/05/2014 02:37 AM, Andreas Ecker wrote:
> > I really enjoying heavily the new pitch range control on the LMMS
> > instruments - making frequency sweeps possible (like the rough
> > Shepard-Risset-Glissando in the attached project). Thank you so much
> > Vesa for your fresh ideas, your great inputs and the time and hard
> > work your investigating in lmms. Many thanks in general to __all__ the
> > lmms community!!! Your enthusiasm has again enlited my "inner fire"
> > and motivation to produce music - just for fun and experimentation.
> > Loving you all for that!!!
> >
> >
> > But one small proposal I would have for the pitch range control.
> > Currently the pitch knob values are in cents (100 cents == 1 half
> > tone). And the range value is changing the scale or range of the pitch
> > knob, but not directly the pitch of the sound.
> >
> >
> > Lets assume LMMS would instead use the pitch value as percentage value
> > within the selected range value. So the pitch value would be always
> > between -100% and 100%, and the resulting pitch change of the sound
> > would then be the pitch percentage value multiplied by the ptich range
> > value.
> >
> >
> > This would give the pitch range control a direct effect which could be
> > automated for example to speed up frequency sweeps by the current
> > range factor.
> >
>
>
>
> There's a few problems with the idea... firstly, if the pitch is always
> +/-100%, then the accuracy of the pitch adjustment will decrease when
> range increases. Currently, we always get 1 cent accuracy, by just
> increasing the range.
>
> Also, there's usability concerns in this - it's harder to get an exact
> pitch if you can't see the actual pitch value in cents.
>
> I'm not against the idea, but it seems kind of tricky to implement, and
> there are some problems that would need to be worked out.
>
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their 
applications. Written by three acclaimed leaders in the field, 
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel

Reply via email to