DIVA GUI Suggestions
-
- KVRAF
- 2686 posts since 5 Feb, 2004 from Nevada City, California
-
- KVRAF
- 5913 posts since 17 Aug, 2004 from Berlin, Germany
What would be the unit when voice modulates the tune (while stacking) and every stacked voice should be detuned by 24 semitones? The "tune mod depth" goes to +/-24 but this are not semitones?Urs wrote:Actually, the values pretty much always mean something. Any tuning is always in semitones or even MIDI Note Number, such as filter cutoff. Any volume is in linear percent, any gain is in dB. Any modulation is usually in the same unit as the parameter, but most of the time in twice the range (bipolar then)
| Links-
- u-he
- 30222 posts since 8 Aug, 2002 from Berlin
Hmmm... the Voice modulator goes from -1 to +1, so it's either 1 or -1/+1 or -1/0/+1 or -1/-0.33/+0.33/+1, depending on voice number. I'd rather use it for panning and filter modulations.
For proper intervals I think that the Voice Map is the better suited modulator.
(I'm also contemplating to bing back the individual stack voice tuning of ACE... what do you think?)
For proper intervals I think that the Voice Map is the better suited modulator.
(I'm also contemplating to bing back the individual stack voice tuning of ACE... what do you think?)
-
- KVRAF
- 5913 posts since 17 Aug, 2004 from Berlin, Germany
The individual stack voice tuning of ACE is IMO better and easier to use.Urs wrote:Hmmm... the Voice modulator goes from -1 to +1, so it's either 1 or -1/+1 or -1/0/+1 or -1/-0.33/+0.33/+1, depending on voice number. I'd rather use it for panning and filter modulations.
For proper intervals I think that the Voice Map is the better suited modulator.
(I'm also contemplating to bing back the individual stack voice tuning of ACE... what do you think?)
Btw. it would also a good idea to provide switchable units where it makes sense (herz, semitones, cent, sync to host,...) this would make some things a bit easier.
| Links-
- KVRAF
- 2065 posts since 14 Sep, 2004 from $HOME
My 2 cents on the GUI:
The text labels are sometimes really hard to decipher at first glance, at least for me:
* font in uppercase is always harder to read
* too much smoothing, thus way too fuzzy
* maybe you could use another font in the OSC section, this one seems a bit unfitted for screen reading (Der Schriftsetzer in mir würde sagen : "zugelaufene Punzen")
* and: why the mix of the two fonts, even in one section?
I don't mind the unit display that much, I mean, you can always just go by ear, but I am alway irritated by the different behavior of the mouse wheel on different knobs:
* on the OCSs detune , it goes in steps of .40, so going from 0.0 to 1.0 (one semitone) is not possible with the wheel. Why not in .50 steps?
* on the Waveform knobs in goos in steps of .20
* on other knobs, in steps of .20
Also, on the detune knobs, using the mouse, it doesn't make a difference whether you hold the shift key or not. On nearly all other knobs, w/o shift means going in bigger steps, and holding the shift key means finetuning.
May seem a bit nitpicking, but those are just the things that are bugging me...
All the best,
F.
The text labels are sometimes really hard to decipher at first glance, at least for me:
* font in uppercase is always harder to read
* too much smoothing, thus way too fuzzy
* maybe you could use another font in the OSC section, this one seems a bit unfitted for screen reading (Der Schriftsetzer in mir würde sagen : "zugelaufene Punzen")
* and: why the mix of the two fonts, even in one section?
I don't mind the unit display that much, I mean, you can always just go by ear, but I am alway irritated by the different behavior of the mouse wheel on different knobs:
* on the OCSs detune , it goes in steps of .40, so going from 0.0 to 1.0 (one semitone) is not possible with the wheel. Why not in .50 steps?
* on the Waveform knobs in goos in steps of .20
* on other knobs, in steps of .20
Also, on the detune knobs, using the mouse, it doesn't make a difference whether you hold the shift key or not. On nearly all other knobs, w/o shift means going in bigger steps, and holding the shift key means finetuning.
May seem a bit nitpicking, but those are just the things that are bugging me...
All the best,
F.
-
- u-he
- 30222 posts since 8 Aug, 2002 from Berlin
Thanks F.
Well, the two fonts are easily explained: Some labels are not yet planted into the background graphics - thus we have to draw them on top, with the built-in font rendering. This will naturally change in time for the final version. It'll be all one font.
I agree about the Punzen. However I tried a lot. More space between labels means either bigger gui, or smaller knobs, or smaller fonts. Neither of these seemed favourable.
However, I do hope to add some functionality to my gui framework next year. Which may hopefully be useful to create sharper text, better resize and instantly more readability.
Well, the two fonts are easily explained: Some labels are not yet planted into the background graphics - thus we have to draw them on top, with the built-in font rendering. This will naturally change in time for the final version. It'll be all one font.
I agree about the Punzen. However I tried a lot. More space between labels means either bigger gui, or smaller knobs, or smaller fonts. Neither of these seemed favourable.
However, I do hope to add some functionality to my gui framework next year. Which may hopefully be useful to create sharper text, better resize and instantly more readability.
-
- KVRist
- 69 posts since 24 Dec, 2008
Hi Urs,
I'm curious: what's the reason for putting the filterfm, resonance, feedback, and noise/crossmod modulations on the modification page? It seems like it would be clearer to put them in the same section as what they control.
Thanks!
Ben
PS Dive sounds amazing! I've been making an ipad controller for it which is super fun.
I'm curious: what's the reason for putting the filterfm, resonance, feedback, and noise/crossmod modulations on the modification page? It seems like it would be clearer to put them in the same section as what they control.
Thanks!
Ben
PS Dive sounds amazing! I've been making an ipad controller for it which is super fun.
-
- KVRAF
- 2336 posts since 13 Oct, 2002 from Terra Firma
Could we have a pop out preset page so that we can browse presets and tweak at the same time?
Also x/y controllers so we can assign and mix sounds and parameters in real time would be fun.
Also x/y controllers so we can assign and mix sounds and parameters in real time would be fun.
-
- KVRAF
- 4197 posts since 23 May, 2004 from Bad Vilbel, Germany
Not using wheel: Triple Osc "Range" switches require too much mouse movement, the "Waveform" knobs require too little...fschattschneider wrote:I don't mind the unit display that much, I mean, you can always just go by ear, but I am alway irritated by the different behavior of the mouse wheel on different knobs...
Using wheel: They both feel OK.
-
- u-he
- 30222 posts since 8 Aug, 2002 from Berlin
The reasons is that these are less common targets. I did not want them to cause distraction from what Diva is about: A rather basic synth that's reminiscent to some oldtimers. These oldtimers never had any of those modulations available, hence we made them an "add on", just like the modifiers.benj3737 wrote:Hi Urs,
I'm curious: what's the reason for putting the filterfm, resonance, feedback, and noise/crossmod modulations on the modification page? It seems like it would be clearer to put them in the same section as what they control.
Thanks!
Ben
PS Dive sounds amazing! I've been making an ipad controller for it which is super fun.
-
- KVRAF
- Topic Starter
- 4081 posts since 28 Jan, 2011 from MEXICO
Could the presets navigation buttons (forward/back) be midi mapped?
dedication to flying
-
- u-he
- 30222 posts since 8 Aug, 2002 from Berlin
One can not load a file upon a MIDI event directly. It has to be buffered in a timer driven loading facility. Which I have never gotten around to doing... but which is high up on my list of things I want to change next year.rod_zero wrote:Could the presets navigation buttons (forward/back) be midi mapped?