ok how about this for editing the envelopes
when the cursor is over a draggable point (apex or curve fit) there should be some sort of change to indicate the user can select and drag that point
you could enlarge the shape or change the cursor so the user knows they're over a selectable area
once it's selected we've got that value box showing up. It's the step before that gives me trouble
i know that would help my clumsy mousing and feedback is always a good thing in the UI
Rhino features suggestions
-
- KVRAF
- 2217 posts since 15 Jul, 2003
-
- KVRAF
- 2217 posts since 15 Jul, 2003
re: user learn
why not default fill in the text field with the label of the parameter selected?
best of all would be drag and drop of the parameter to one of the six boxes, but that may be asking too much
why not default fill in the text field with the label of the parameter selected?
best of all would be drag and drop of the parameter to one of the six boxes, but that may be asking too much
-
- KVRAF
- 19818 posts since 16 Sep, 2001 from Las Vegas,USA
I've just found this thread so forgive me if this has been mentioned before.I would like the abiliity to turn off the sequencer for certain envelopes.Then you could have some env's running the seq and some doing other things like backgroung pads or sweeps. 
-
- KVRAF
- Topic Starter
- 3388 posts since 29 May, 2001 from New York, NY
Tek: Unfortunately that can't be done - the step seq triggers whole *notes* - that means all the envelopes of a note.
'Tick
'Tick
-
- KVRist
- 224 posts since 30 Jul, 2002 from Lancashire UK
1. No really a feature but more banks of CPU lite patches would be handy.
2. Wider range of waveforms - more human voice and synth style waveforms. And more thumping bass PPG style waves.
3. Obviously a multitimbral mode, if possible.
2. Wider range of waveforms - more human voice and synth style waveforms. And more thumping bass PPG style waves.
3. Obviously a multitimbral mode, if possible.
-
- KVRist
- 457 posts since 30 Jun, 2003 from cinci, oh
i would like to see 6 small toggle buttons under the osc envelope editing window. the button for the current osc is always on, but you can toggle one or more of the others to display a ghost image of its envelop behind the current (editable) one. a nice touch would be a knob to control the briteness (or translucency) of the ghost envelop(s); or perhaps even color coding them.
i am not a rhino owner (yet); i downloaded the demo the other day and i must say, this is one of about three synths on the entire kvr site that would truely add value over frooty's built in generators (of course, that is just my opinion). Heck, with the ability to read DX7 sysex and the feature mentioned above, i cannot afford to be without this synth.
i am not a rhino owner (yet); i downloaded the demo the other day and i must say, this is one of about three synths on the entire kvr site that would truely add value over frooty's built in generators (of course, that is just my opinion). Heck, with the ability to read DX7 sysex and the feature mentioned above, i cannot afford to be without this synth.
-
- KVRAF
- Topic Starter
- 3388 posts since 29 May, 2001 from New York, NY
Tim Conrardy (Mr DX7 man) is currently trying the DX7 import. Depending on his feedback, this feature could be in the next release....
'Tick
'Tick
-
- KVRAF
- 19818 posts since 16 Sep, 2001 from Las Vegas,USA
Well Bloody 'ell so much for that idea.I vote for more waveforms then.Big Tick wrote:Tek: Unfortunately that can't be done - the step seq triggers whole *notes* - that means all the envelopes of a note.
'Tick
-
- KVRist
- 255 posts since 10 Apr, 2003
newbie here again, so forgive me if this has be suggested already:
One feature I find lacking in most synths, is some sort of graphical tool for keyboard velocity maping... if that is the correct term..
I know a few have it.. NI's Absynth now has it and maz sounds VSampler has always had it....
This is a great feature I think for any vsti, because the nature of many patches is that the upper ranges on the keyboard just scream, while the lower ones are soft. So a feature like this would let one sculpt the keyboard response to a more balanced and more playable thing. I really love the way it's been implemented in Absynth so that one can just paint it... so nice! VSampler is less fun with vector line points and all but it still works...
Is this a possible additon to Rhino?
thanks for listening!
One feature I find lacking in most synths, is some sort of graphical tool for keyboard velocity maping... if that is the correct term..
I know a few have it.. NI's Absynth now has it and maz sounds VSampler has always had it....
This is a great feature I think for any vsti, because the nature of many patches is that the upper ranges on the keyboard just scream, while the lower ones are soft. So a feature like this would let one sculpt the keyboard response to a more balanced and more playable thing. I really love the way it's been implemented in Absynth so that one can just paint it... so nice! VSampler is less fun with vector line points and all but it still works...
Is this a possible additon to Rhino?
thanks for listening!
-
- KVRAF
- Topic Starter
- 3388 posts since 29 May, 2001 from New York, NY
Max,
So this would be an additional curve on the oscillators pages ? Where you would draw the velocity range across the keyboard ?
'Tick
So this would be an additional curve on the oscillators pages ? Where you would draw the velocity range across the keyboard ?
'Tick
-
- KVRist
- 255 posts since 10 Apr, 2003
ah good question... well I'm not a programmer at all and can only speak of what I've seen other places, so I'll try to do that...
The velocity curves in the various OSC's are one thing... understood.... but what I'm trying to explain is how a very few vsti's have an additonal function, using a little separate GUI window, and in that it sets the total output of the instrument across the keyboard...
the very best example of this I know of is NI's Absynth... it just gives you a picture that represents the range of the keyboard, and you can use the mouse to simply sculp that picture, as if it was putty or warm wax.... so for example then, the result could be that any range or even diff parts of the keyboard respond differntly when played.
so for example, the low range can be louder while the higher range, say from C4 up tapers to more quiet... you can sculpt it anyway you would like.
Now VSampler 2.7x had this also, but did it with vector lines that you could add a few points to... The Absynth way is much nicer IMHO...
so I don't know if I'm explaining this well... if you can get a look into Absynth 2.x, you can find the area I mean... if I can find a url about I'll come back with that.
thanks again...
---PS----- found it:
OK here is what I mean... sorry for the poor terminology... "key scaling" is the term used:
http://www.nativeinstruments.de/index.php?absynth2fx_us
you can see the picture at the bottom of this page..
but the result is what I have been trying to explain and this is what I've mentioned.
The velocity curves in the various OSC's are one thing... understood.... but what I'm trying to explain is how a very few vsti's have an additonal function, using a little separate GUI window, and in that it sets the total output of the instrument across the keyboard...
the very best example of this I know of is NI's Absynth... it just gives you a picture that represents the range of the keyboard, and you can use the mouse to simply sculp that picture, as if it was putty or warm wax.... so for example then, the result could be that any range or even diff parts of the keyboard respond differntly when played.
so for example, the low range can be louder while the higher range, say from C4 up tapers to more quiet... you can sculpt it anyway you would like.
Now VSampler 2.7x had this also, but did it with vector lines that you could add a few points to... The Absynth way is much nicer IMHO...
so I don't know if I'm explaining this well... if you can get a look into Absynth 2.x, you can find the area I mean... if I can find a url about I'll come back with that.
thanks again...
---PS----- found it:
OK here is what I mean... sorry for the poor terminology... "key scaling" is the term used:
http://www.nativeinstruments.de/index.php?absynth2fx_us
you can see the picture at the bottom of this page..
but the result is what I have been trying to explain and this is what I've mentioned.
-
- KVRist
- 143 posts since 28 Oct, 2002
An easy one: please make the button labels (load, save etc.) click-sensitive. It's sometimes difficult to hit the small squares.
Otherwise I'm still in the beginning of exploring all the possibilities. It's such deep instrument already.
Fette Töle
Otherwise I'm still in the beginning of exploring all the possibilities. It's such deep instrument already.
Fette Töle
-
- KVRAF
- Topic Starter
- 3388 posts since 29 May, 2001 from New York, NY
Yes. Another line in my todo list for 1.10Fette Töle wrote:An easy one: please make the button labels (load, save etc.) click-sensitive. It's sometimes difficult to hit the small squares.
'Tick
-
- KVRist
- 255 posts since 10 Apr, 2003
ah the todo list! well now, I think you mentioned there would be a prob with the new banks listing and saving and reloading in say SX or whatever... and surely there is...
this is a little nasty in the long run [unless I'm missing the point somehow]... It also shows up in Chainer which normally can save about anything as a chainer preset.
So just wondering if anything can be done about this in the future... maybe some way of having banks have a number and the pre's in each bank a sub number that can be saved? It surely would be nicer but don't know if it's possible without changing the basic way Rhino deals with banks and presets. Any thoughts?
this is a little nasty in the long run [unless I'm missing the point somehow]... It also shows up in Chainer which normally can save about anything as a chainer preset.
So just wondering if anything can be done about this in the future... maybe some way of having banks have a number and the pre's in each bank a sub number that can be saved? It surely would be nicer but don't know if it's possible without changing the basic way Rhino deals with banks and presets. Any thoughts?
-
- KVRAF
- Topic Starter
- 3388 posts since 29 May, 2001 from New York, NY
Well I think the best option would be to include the bank name along with the synth data. Thus the synth could switch to the proper bank when reloading.
However I'd rather give it a little bit more thought: I feel the real requirement here was only to have a "quick load" function for banks. This has turned into the disturbing notion of internal / read-only external banks, maybe it's time to simplify it all
'Tick
However I'd rather give it a little bit more thought: I feel the real requirement here was only to have a "quick load" function for banks. This has turned into the disturbing notion of internal / read-only external banks, maybe it's time to simplify it all
'Tick