Trigger a long evolving pad and play through it with my guit... hmmm....
I guess this would be done having one OSC with the capability to have 'audio in' as a wave source... but am I off into fantasy land here?
Rhino features suggestions
-
- KVRer
- 23 posts since 3 Jan, 2003 from Somewhere in my bedroom under a pile of midi cables
I'd love to be able to play my guitar through Rhino...
Trigger a long evolving pad and play through it with my guit... hmmm....
I guess this would be done having one OSC with the capability to have 'audio in' as a wave source... but am I off into fantasy land here?
Trigger a long evolving pad and play through it with my guit... hmmm....
I guess this would be done having one OSC with the capability to have 'audio in' as a wave source... but am I off into fantasy land here?
SR Misc Synthz/Where Is Wookie
Fame at last in SR Sonic Station
-
- KVRAF
- Topic Starter
- 3388 posts since 29 May, 2001 from New York, NY
That's possible in theory - but you won't be able to apply FM to your audio input oscillator. I need to re-read the vst sdk manual to see how to do that.
'Tick
'Tick
-
Stupid American Pig Stupid American Pig https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=4753 - KVRAF
- 7065 posts since 25 Nov, 2002 from not sure
I like the idea of using the Rhino as an Efx unit. the onboard efx are pretty good, and using the onboard step sequencer and modulation could make things even more interesting...
-
- KVRAF
- Topic Starter
- 3388 posts since 29 May, 2001 from New York, NY
Good one krhen. I left it out to save some cpu cycles, but I too think it's a must-have...
'Tick
'Tick
-
- KVRist
- 138 posts since 8 Jul, 2003
Correct me if I'm wrong but there's no way to use an LFO osc to modulate a Filter cutoff (or res for that matter). Am I missing something there? You could make an lfo out of a filter envelope, but then you can't do things like track the keyboard or modulate the LFO with the waveshaper etc.
Additional cool feature: MIDI control of waveshaper amount (from 1:1) much like WS amt can be modulated by vel/at.
One more: Ability to make our own waveforms (.vfs) for the \waves directory - is this a standard format? What about a .AIFF/.WAV to Rhino \waves converter?
Additional cool feature: MIDI control of waveshaper amount (from 1:1) much like WS amt can be modulated by vel/at.
One more: Ability to make our own waveforms (.vfs) for the \waves directory - is this a standard format? What about a .AIFF/.WAV to Rhino \waves converter?
-
- KVRAF
- 7936 posts since 18 Feb, 2003 from out there somewhere
Can you enhance Rhino so that it will drive my car to work, spend 8 or so hours in the office doing a passable impression of me and then bring the car home again, thereby freeing up my time to make music?
-
- KVRian
- 966 posts since 28 Sep, 2002 from UK
All together now
ASIO for standalone, ASIO for standalone, ASIO for.....
ASIO for standalone, ASIO for standalone, ASIO for.....
-
- KVRist
- 138 posts since 8 Jul, 2003
In a situation where you're using Rhino/any VST as a standalone MIDI-controlled soundsource, OR inside a VST host but still mainly controlling via MIDI (in my case, I have a sequencing PC (controlling hardware synths as well as soft) separate from my Rhino PC (running V-Stack), with MIDI between), one thing that I wish ALL VSTis would implement is a way to automate a bank load via MIDI.
Off-hand, I'd say have the VSTi recognize a MIDI universal sysex string that contains a string of the path/filename of the bank to load. This way, one could embed that sysex string in the sequencer track (or, say, on a Peavey PC1600x button) WITH the filename of the bank to load, and control such remotely/automatically. Universal sysex means no registering with MMA, standard, allowing for variable data, and easily implementable.
(of course this would be most useful if the ASIO microhost is implemented
Off-hand, I'd say have the VSTi recognize a MIDI universal sysex string that contains a string of the path/filename of the bank to load. This way, one could embed that sysex string in the sequencer track (or, say, on a Peavey PC1600x button) WITH the filename of the bank to load, and control such remotely/automatically. Universal sysex means no registering with MMA, standard, allowing for variable data, and easily implementable.
(of course this would be most useful if the ASIO microhost is implemented
-
- KVRist
- 138 posts since 8 Jul, 2003
Oooh ooh here's another one. Dunno based on your implementation if this is possible. On the Kawai K5000 there's a knob that control the levels of even and odd harmonics in the additive oscs. Makes for some nice evolving control of sound. If you could a) allow for MIDI/slider control over this/these (0 to max set) and b) add two envelopes for these (one for even level and one for odd level), that would be IMMENSELY cool (well, at least useful
Its not quite an envelope on EACH harmonic like the K5000 but it adds another level of realtime change that IMO should be inherent in an additive synth.
Its not quite an envelope on EACH harmonic like the K5000 but it adds another level of realtime change that IMO should be inherent in an additive synth.
-
- KVRAF
- Topic Starter
- 3388 posts since 29 May, 2001 from New York, NY
krhen: shouldn't this be straightforward to do with 2 oscs and the additive editor ? Then you'd have separate envelopes and level output for both odd and even harmonics...
'Tick
'Tick
-
- KVRist
- 138 posts since 8 Jul, 2003
um yeah (duh) - well... though in some sense it'd easier rather than trying to get the levels proper between two oscs, esp. without being able to have them both on screen at the same time. Perhaps to facilitate, there could be some funtions added to the additive editor to REMOVE EVENS, REMOVE ODDS, (and I'm sure I can think of a few more) on a context menu? That would solve it. I'd hate to make a basic add waveform, then copy it to two oscs, and then tweak by hand to remove the even and odd components from each just to obtain the effect
Though in the perfect world, there would be an envelope on EACH harmonic - but I can only imagine the CPU power needed?
Though in the perfect world, there would be an envelope on EACH harmonic - but I can only imagine the CPU power needed?
-
- KVRer
- 3 posts since 30 Jul, 2002 from Lausanne Switzerland
Hi,
First of all, Rhino is a wonderful instrument. Congratulations and thank you for providing us with such a beast!
A request for a next update. Maybe I ask for the moon but it would be great to be able to see every envelopes, or key tracking, or level curves at once for a given oscillator.
I picture it so: little windows for each item you can open (and edit) and close at will, or otherwise a dedicated page like the one in Absynth.
Hey, does it sound good?
Thanks
Phil
First of all, Rhino is a wonderful instrument. Congratulations and thank you for providing us with such a beast!
A request for a next update. Maybe I ask for the moon but it would be great to be able to see every envelopes, or key tracking, or level curves at once for a given oscillator.
I picture it so: little windows for each item you can open (and edit) and close at will, or otherwise a dedicated page like the one in Absynth.
Hey, does it sound good?
Thanks
Phil
-
- KVRist
- 138 posts since 8 Jul, 2003
You did a great job with this on Angelina where there is a tab/button for the three envs and one is 'highlighted' while the non-selected ones are ghosted. Of course getting past three, this may get quite cluttered, BUT would be very useful in sync'ing up envelope movements if you could, say, select WHICH three or four envelopes are visible at any one time (one active and the others ghosted)
-
- KVRAF
- 2217 posts since 15 Jul, 2003
of the suggestions so far
I like the idea of being able to import DX7 sysex files (but wait a while cause otherwise I'll never really learn FM synthesis, I'd just get lost downloading and trying presets out with diffrnt waveforms and Fx.)
doesn't Angelina have an Fx package? I think the suggestion to split off Rhino's sequencer and Fx section as an Fx is top drawer.
as long as the CPU usage is optimized. I would prioritize that. I added a Rhino track to a crowded field and blew my P-4 2.4 gHz into overload.
some manner of ghosting osc envelopes for evolving pads would be very nice if it could be navigated easily ( and to be honest my mouse and I haven't quite figured out how to efficiently modify envelopes. I keep accidentally resizing when I mean to move, so I'm constantly selecting 'fit')
I don't have any suggestion there just saying that so far it's a troublesome are for my clumsiness. --
and being new to the interface and since I tend to skip things in the manual since I don't think I need to know that yet, I was pretty much lost for an intuitive way to get controls down to automation. I'm sure it's all in there. It's just not so intuitive for those of us who set aside the manual and start tweaking to figure out how things work.
altogether a wonderful piece of work and what's best about that is whatever little frustrations come up are overcome by a desire to figure this out since it sounds so fabulous.
I like the idea of being able to import DX7 sysex files (but wait a while cause otherwise I'll never really learn FM synthesis, I'd just get lost downloading and trying presets out with diffrnt waveforms and Fx.)
doesn't Angelina have an Fx package? I think the suggestion to split off Rhino's sequencer and Fx section as an Fx is top drawer.
as long as the CPU usage is optimized. I would prioritize that. I added a Rhino track to a crowded field and blew my P-4 2.4 gHz into overload.
some manner of ghosting osc envelopes for evolving pads would be very nice if it could be navigated easily ( and to be honest my mouse and I haven't quite figured out how to efficiently modify envelopes. I keep accidentally resizing when I mean to move, so I'm constantly selecting 'fit')
I don't have any suggestion there just saying that so far it's a troublesome are for my clumsiness. --
and being new to the interface and since I tend to skip things in the manual since I don't think I need to know that yet, I was pretty much lost for an intuitive way to get controls down to automation. I'm sure it's all in there. It's just not so intuitive for those of us who set aside the manual and start tweaking to figure out how things work.
altogether a wonderful piece of work and what's best about that is whatever little frustrations come up are overcome by a desire to figure this out since it sounds so fabulous.