Morphine Feature Requests....
-
- KVRist
- 401 posts since 29 Mar, 2006 from The Grim North (well, Yorkshire)
Hi Maxx, I have version 1.1.5 of Morphine --- I'm sure you're snowed under with feature requests but maybe someday you could implement the following:
1) Patch Changing / Patch Automation
Currently there's no way to change a patch without clicking on the "Program" selector
(On the AEffect class, numPrograms is set to zero)
Obviously this means there's no way of changing the selected patch using automation
Also, I'm working on a simple host that lets you assign a patch to a midi controller button - this won't work either.
2) Some of the Knob values just show a percentage when you change them
Some show sensible values (Chorus Rate in Hz, Delay Time in ms, Master Level in Db)
A lot of the others don't (ie Reverb Decay, Hi-Cut, Attack time etc)
Should be an easy fix!
1) Patch Changing / Patch Automation
Currently there's no way to change a patch without clicking on the "Program" selector
(On the AEffect class, numPrograms is set to zero)
Obviously this means there's no way of changing the selected patch using automation
Also, I'm working on a simple host that lets you assign a patch to a midi controller button - this won't work either.
2) Some of the Knob values just show a percentage when you change them
Some show sensible values (Chorus Rate in Hz, Delay Time in ms, Master Level in Db)
A lot of the others don't (ie Reverb Decay, Hi-Cut, Attack time etc)
Should be an easy fix!
-
- KVRist
- 151 posts since 5 Jul, 2004
Hi, thanks for your suggestions...
1) Well, it's VST. What means there is no (official at least) way to let a host know when program is changed inside the plugin editor. No information about the preset can be passed to the host.... Steiny maybe know how to do that, but that's top secret of them
Actually, program change via midi works here (as well as bank change). Are you using program change midi messages or are you assigning CC to program number obtained from VST? (in the second case it won't work indeed).
2) Well, yeah, that's easy... but I don't think it really matters... Reverb Decay which you used for an example must be in percents, coz actually in any reverb decay time is infinite, just the level of the reverb tail is trying to reach zero but never reaches (in theory, but in practice it's limited by float values resolution which cannot be used as end point as human ear stops hearing the sound way earlier before zero). And many parameters which display values in percents are supposed as "empirical". I mean - you adjust it by ear, because seeing for example "Attack time is 0.57 seconds" doesn't help you to make a sound at all... that's what I honnestly think
you just listen to it and estimate by ears (yeah, I'm known for telling that since Toxic first version, hehe
).
1) Well, it's VST. What means there is no (official at least) way to let a host know when program is changed inside the plugin editor. No information about the preset can be passed to the host.... Steiny maybe know how to do that, but that's top secret of them
Actually, program change via midi works here (as well as bank change). Are you using program change midi messages or are you assigning CC to program number obtained from VST? (in the second case it won't work indeed).
2) Well, yeah, that's easy... but I don't think it really matters... Reverb Decay which you used for an example must be in percents, coz actually in any reverb decay time is infinite, just the level of the reverb tail is trying to reach zero but never reaches (in theory, but in practice it's limited by float values resolution which cannot be used as end point as human ear stops hearing the sound way earlier before zero). And many parameters which display values in percents are supposed as "empirical". I mean - you adjust it by ear, because seeing for example "Attack time is 0.57 seconds" doesn't help you to make a sound at all... that's what I honnestly think
-
- KVRist
- Topic Starter
- 401 posts since 29 Mar, 2006 from The Grim North (well, Yorkshire)
Thanks Maxx
1) I have been using the effSetProgram opcode, ie:
pEffect->dispatcher( pEffect, effSetProgram, 0, prog, NULL, 0 );
...I could always send the MIDI program change instead I suppose - however there's no way as it stands to get a count of how many programs are available or to display the patch names without opening the GUI.
2) The tips aren't that important really!
...oh, and thanks for another nice synth
1) I have been using the effSetProgram opcode, ie:
pEffect->dispatcher( pEffect, effSetProgram, 0, prog, NULL, 0 );
...I could always send the MIDI program change instead I suppose - however there's no way as it stands to get a count of how many programs are available or to display the patch names without opening the GUI.
2) The tips aren't that important really!
...oh, and thanks for another nice synth
-
- KVRist
- 151 posts since 5 Jul, 2004
Thanks for that... I will try to think about programs also. Tricks are always possible, indeed 
Author and support for ToxicIII, Morphine and PoiZone VSTi's.
-
- Banned
- 1966 posts since 2 Mar, 2004
well, I put my feature requests also here:
1. midi learn
2. ability to automate the morph mix
3. animation of morph mix and morph path position (similar to cube), in order to give a visual feedback of what sound mix one is hearing at the moment
4. mirotuning support (with scala or tun files)
the implementation of this in an update would be really great.
thanks for listening. cheers, akj
1. midi learn
2. ability to automate the morph mix
3. animation of morph mix and morph path position (similar to cube), in order to give a visual feedback of what sound mix one is hearing at the moment
4. mirotuning support (with scala or tun files)
the implementation of this in an update would be really great.
thanks for listening. cheers, akj
-
- KVRist
- 151 posts since 5 Jul, 2004
midi learn and microtuning suggestions I like
Probably will add that in one of the future updates.
You can automate morphing path btw, but only with MIDI CC's...
You can automate morphing path btw, but only with MIDI CC's...
Author and support for ToxicIII, Morphine and PoiZone VSTi's.
-
- KVRist
- 151 posts since 5 Jul, 2004
well, you may route any CC, or pitch wheel/aftertouch, etc (as well as with built-in additional envelopes) to MorphX and MorphY on Modulation page... checkout modulation matrix.
Author and support for ToxicIII, Morphine and PoiZone VSTi's.
- KVRAF
- 5542 posts since 26 Apr, 2007 from Noosphere
Hi to all! I dont know is it possible or not, but i think it would be great if each generator has a bottom DRIVE separately. And one thing as well-for example, we have two generator i use.Wnen we in MORPH window trying to morph them(first generator 50%, second 50%) what we have?-We have just two signals mixed.Its mean that these two signals(waves better) playing together-one near other)but not really morphed into one hybrid wave.So is it possible to create this new function.Sorry,maybe im crazy:)Thnx
-
- KVRist
- 151 posts since 5 Jul, 2004
Actually, when you morph 4 generators - they are not really "mixed". It means - there are no 4 generators internally, only one. When you morph, amplitudes/detunes of 128 harmonics are interpolated according to morphing path.Igr0 wrote:Hi to all! I dont know is it possible or not, but i think it would be great if each generator has a bottom DRIVE separately. And one thing as well-for example, we have two generator i use.Wnen we in MORPH window trying to morph them(first generator 50%, second 50%) what we have?-We have just two signals mixed.Its mean that these two signals(waves better) playing together-one near other)but not really morphed into one hybrid wave.So is it possible to create this new function.Sorry,maybe im crazy:)Thnx
>We have just two signals mixed
it's opposite, and it already works as you requested... if I understand you right
Author and support for ToxicIII, Morphine and PoiZone VSTi's.
- KVRAF
- 5542 posts since 26 Apr, 2007 from Noosphere
Thnx for the answer Maxx.Ill try to understand it better.But what about Drive function separately for every generator.
It would be very useful to give different value of DRIVE for every generator.I understand, that this feature is a big deal 
-
- KVRist
- 151 posts since 5 Jul, 2004
Thanks alot Igr0!
Naah... drive per generator is impossible because of that reason. To overdrive a generator, you need render each generator separately, what will lead to 4x bigger CPU usage. It's very major change to the engine, and if I do so - it will be just another synth
Naah... drive per generator is impossible because of that reason. To overdrive a generator, you need render each generator separately, what will lead to 4x bigger CPU usage. It's very major change to the engine, and if I do so - it will be just another synth
Author and support for ToxicIII, Morphine and PoiZone VSTi's.
