I needed these features and created patches for my own use. However, I believe they may be of general interest.
I am attaching the patches (only drumkv1) in case they are useful as a reference, even if only for testing the features and determining whether they make sense.
SpinBox increments by units + CTRL/SHIFT = FINE/COARSE STEPS
Tenths are too fine-grained for adjustment. In most cases, whole units are the optimal setting.
At present, changing the value by one unit requires a very large movement—ten mouse-wheel steps—which makes editing extremely cumbersome.
Keyboard modifiers, CTRL and SHIFT, can be used to access fine adjustments (tenths) and coarse adjustments (tens).
My patch has one limitation: it does not affect the OFFSET spinboxes. For consistency, they should also use Shift to activate the coarse adjustment instead of Ctrl, which is their current behavior.
Apart from that, it works well, also distinguishing integer-valued spinboxes, which do not have a fine-adjustment step.
Improvements to Random
Creating a preset from scratch is similar to the work of a painter.
Generating random configurations, recognizing potential in one of them, and then shaping it further is similar to the work of a photographer.
Replace the warning dialog with a percentage-configuration dialog
This would provide full control over the randomization at any time, directly at hand, without having to change the main configuration.
For example:
If I am looking for something different—fresh or unexpected—from which to create something meaningful, 20% is a good starting point. That is also the most commonly used setting and should be the default.
However, on other occasions, you may only want variations of an instrument that has already been built.
In that case, you need to make continuous adjustments to find the most suitable percentage.
Why should the main configuration have to be changed? Why should you have to leave the editing environment?
Random values rounded to integers
This creates less visual noise and therefore makes it easier to understand why the instrument sounds the way it does.
I leave this for your consideration.
re. Feature Request for Vee One Suite...
I don't really buy onto this, sorry.
Why not stick to the current (and old) covenant to have Ctrl to all course increments (units instead of tenths where applicable) ?
That's a good idea, but why...
?
cheers
re1. Feature Request for Vee
I should have implemented the example in SynthV1, where these improvements are much more evident.
1_ SpinBox increments by units
The units are optimal for parameter adjustments. Tenths fall short—something you notice when creating presets from scratch.
As I said, I chose a poor example of implementation, because for drumkV1, tenths are sufficient in most cases.
VeeOne forces the user to rely on a default scale that isn't optimal for editing, making the editing process cumbersome.
Try creating a snare from scratch using SynthV1... and you'll see for yourself. It’s a fact, not just a perception.
You’ll immediately ask yourself: why am I moving in increments of ten when I want to move in increments of one?
__
2_percentage-configuration dialog
Here’s an example.
There are hardly any "libre" electronic percussion samples available.
Since the latest VeeOne was released... there is now an infinite source. (Although a "how-to" guide would be needed to demonstrate this).
Take SynthV1, go to the Drum bank, select the instrument (for example, a snare) you want new samples for, and apply a percentage variation ranging from 2% to 10%.
I invite you to try it out... you automatically get interesting variations of the instrument that still retain the snare's family identity.
For this type of use, constantly navigating to the settings to change the percentage becomes cumbersome.
But this approach applies to any other instrument as well.
It’s a workflow similar to a photographer's: as I mentioned, you look for that interesting shot among many, and then refine its form from there...
__
3_Random values rounded to integers
... And it is much easier refine when working with whole numbers rather than decimals. And as I noted, decimals create visual and mental clutter. Why? Too many imprecise values, too much information. It is easier to process visually:
10.0 · 6.0 · 4.0 · 22.0 · 54.0
than
10.4 · 6.2 · 4.8 · 22.7 · 54.3
In short, while having fine-tuning with decimals is useful, the optimal working value is the whole number.
__
Perhaps these improvements only count as such from a very personal perspective.
That’s how I see it... but we don’t have to agree :)
re2. Feature Request for Vee...
as said you already have this for long: just press Ctrl key while using the mouse-wheel or the up and down arrow buttons.
there's no need to invert or overengineer on this.
already agreed with this, let's move on
but not on this, sorry.
really can't see how this alleged noise is an issue--it's all random generated numbers after all :)
true ;)
anyway, at least one of your suggestions will pervade into the gang, so thanks!
cheers
ps. next time you could make it as a PR (preferably to develop) right?
re. PR (preferably to develop)
I'm not familiar with the terminology; I'll do it that way next time.
As always, thank you very much for listening to us and for your patience.
Add new comment