Request: Automate-able shift value / Inertia parameter for midi values
-
- KVRAF
- 2623 posts since 20 Oct, 2014
Hi,
I tried to do a exact frequency matching by the played synth note in MEqualizer. This worked in Renoise using custom formula thru the Renoise Formula Device. But since this kind of stuff is not possible in any other DAW.
It turns out that midi note input->frequency is already possible in all melda plugins (thx @ jmg8), but it seems to lack of the following features, which I would like to suggest:
- Automate-able shift value: doesn't seem to appear in the automation list!
- An inertia mechanism, so you could use the band shifting for fancy filter effects!
I would like to suggest to include a midi input to all frequency related Melda plugins, e.g. MEqualizer, MFilter, Mbandpass or Mcomb + a note->frequency translator in the modulator section. I hope you get the idea. So it was possible to do exact note frequency matching + some offset frequency...
What do you think about it?
Thanks for consideration.
I tried to do a exact frequency matching by the played synth note in MEqualizer. This worked in Renoise using custom formula thru the Renoise Formula Device. But since this kind of stuff is not possible in any other DAW.
It turns out that midi note input->frequency is already possible in all melda plugins (thx @ jmg8), but it seems to lack of the following features, which I would like to suggest:
- Automate-able shift value: doesn't seem to appear in the automation list!
- An inertia mechanism, so you could use the band shifting for fancy filter effects!
I would like to suggest to include a midi input to all frequency related Melda plugins, e.g. MEqualizer, MFilter, Mbandpass or Mcomb + a note->frequency translator in the modulator section. I hope you get the idea. So it was possible to do exact note frequency matching + some offset frequency...
What do you think about it?
Thanks for consideration.
Last edited by Hanz Meyzer on Mon Apr 10, 2017 10:53 am, edited 1 time in total.
-
- KVRist
- 206 posts since 17 Mar, 2013
+1
If that would be too problematic it would be nice to at least have a transpose parameter for all frequency bands at once, to achieve the same effect, and probably actually work better when sliding.
The audio pitch follower already has a transpose but it transposes from that audio pitch, it would be nice not to have to have the audio analysed in the first place as proper midi data is already available, which reduces artefacts, decreases processing etc.
If that would be too problematic it would be nice to at least have a transpose parameter for all frequency bands at once, to achieve the same effect, and probably actually work better when sliding.
The audio pitch follower already has a transpose but it transposes from that audio pitch, it would be nice not to have to have the audio analysed in the first place as proper midi data is already available, which reduces artefacts, decreases processing etc.
- KVRAF
- 2702 posts since 9 Jul, 2015 from UK
Code: Select all
78DABD565D6FDB3A0C7DEFAF30F4DE58923FE40071866EB7BE1DD0ACDD52ACF73E6AB1120B55AC54969776BF7E946C174ED6160356CC4060E9983C24E5433AB3770F5B157C17A691BACE11996014887AA54B596F72D4DAF56986DECD4F668BF3FB962BF9030C85B5F0B0093EE8DA1AAD1440E735FFA6449923F0AEB85A6FB8ACFDE6F2CB72A7A4B5C22CC197E428C9E8314A731481E9823F5C1657EF955EDD391440B0FCA4AD782E0E41C18E1BBE15C0518A9DAD0EA1A7F84FC852AFED92DBD670EB0BC5683EFBD7F05D359FEDB4AC6D70EF8BF7170AECE30E12B816FC0E05FFE5884E62C2D22449688AA728F83F47596F3A4DA29401D505375B5DCB5513CE67A1271CF1D2977919C9D22989139C30CF7BCA26537F253422E9ABC4E333872078C23023983D1324C95216C7342351E683E037E18D269824114918866CDF94378EA32C63906D42FF9CF7426EAA6525D4BA27CF188D932C4959FF265F220F3B759CCCCE8CE08D53A7DC822CBFE87DE3B416BA2735578FD011C199DA55DC85867318C00F15AF6BA116BA842416F2011D24DAAD6F2B515FC8B2149D5897BA352BB086AA6F655DEAFD4D5701104192D746ACA5022943F305FF18BE877BC7EE4AB8F6675128BE69DE437E3174C38353748409A64E4F690A39BF60161F9B85E3602EB45E89A6D10643D32B6D2024C667242E8A5155405548A5FCE20A068A91A5E8AD0171AFD71F5CB0ACF4DEE35FB96A4587DD547275E70A0947C1C82BC1F073319E65A16FC212BD094BFC272C4B5DEB0D4CB3416DE4C0190CBC5BD385C03E463F753C4206241B10DA2145E1F2F048E490A270BF1E8973E4F61E71BA18D40DEA1F8D65D70C47937A7E04E003A14037F9B7EFDB95454936653165309D3A415FEA0D37D2565BB9EA3E01600F7E38EB776EB8D31844354CF74F70CBD1F9E78004A74161C47D0BDFB0C700223D8581A14018759D9F26B1ABE5303FF277F2A307F951D70D726DC197BE966A787CB8F03D6E95954FFCFE0D2CFC6A3EFB582FC0E7AAB5EE762B4B5B2D9C7ADC6C09C67DDDCB261C4CC063D7DABDDBDD0C4275E2E8E4F0553612CEA777FA5883E9C82A8D5FB4DAF3EF62ADCDF6663426C7C21CB987431207F13B811E32F7B9FE0675EFEF0AED0FE80456BFFC9B999FFC04DB7DBCF7Jason @ Melda Production
-
- KVRist
- 206 posts since 17 Mar, 2013
Heh, I didn't know that, I see the trick was to set the correct min and max values. Thanks!
A shame Shift can not be directly automated, but indirect means seems to be sufficient.
A shame Shift can not be directly automated, but indirect means seems to be sufficient.
Last edited by pone on Mon Apr 10, 2017 10:52 am, edited 4 times in total.
-
- KVRAF
- Topic Starter
- 2623 posts since 20 Oct, 2014
@jmg8: Thanks a lot, did not realize that!
What I am now still missing is:
- Automate-able shift value: doesn't seem to appear in the automation list!
- An inertia mechanism, so you could use the band shifting for fancy filter effects!
I did now change the topic accordingly.
What I am now still missing is:
- Automate-able shift value: doesn't seem to appear in the automation list!
- An inertia mechanism, so you could use the band shifting for fancy filter effects!
I did now change the topic accordingly.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
I'll check about the shift value, BUT you can already do that using multiparameters - instead of accessing the target parameter directly, attach a multiparameter to the MIDI and then you can freely transform it in many ways. It could be problematic to make it work "by semitones", but considering the situation it probably even isn't the case.
As for "intertia" - what do you mean??
As for "intertia" - what do you mean??
-
- KVRAF
- Topic Starter
- 2623 posts since 20 Oct, 2014
Oh nice.
I mean a crossfade, which is variable in speed. I guess thats possible with a multi parameter, too?MeldaProduction wrote:As for "intertia" - what do you mean??
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Yes! That's exactly what these things are for
. I think just the defaults will be suitable and set the Speed at will
.
-
- KVRAF
- Topic Starter
- 2623 posts since 20 Oct, 2014
Surely I did something wrong: If I setup a midi settings/note->multiparam1/value1 route and then change the "speed" setting in multiparam1, nothing will change, it's still an abrupt change...MeldaProduction wrote:Yes! That's exactly what these things are for. I think just the defaults will be suitable and set the Speed at will
.
So that speed setting seems to apply only on the multiparam master value, which seems not to be targetable.
So if I am right, I would like to request that either the midi note dialogue gets such a speed section, or the multi parameter itself was targetable...
Or the speed was applied to the sub parameters instead the master value...?
-
- KVRAF
- 10375 posts since 2 Sep, 2003 from Surrey, UK
I'm sligllty lost.
Could you describe, in small steps, what you want to do?
-
- KVRAF
- Topic Starter
- 2623 posts since 20 Oct, 2014
Hi,
I want to do a midi note->frequency follower, but on change of a note I want the frequency to fade in between, so the frequency changes only slightly over time.
I want to do a midi note->frequency follower, but on change of a note I want the frequency to fade in between, so the frequency changes only slightly over time.
- KVRAF
- 2702 posts since 9 Jul, 2015 from UK
Code: Select all
78DADD585B53E336147EE75768FC1E22DFE26426C94EB87861862C29A6D03EAAB1126B702423CB84ECAFEF912C07E742CBB6FBD0023324FA7474EE3AE788E197D7558E5EA82C99E023C73DC50EA27C2E52C69723A7528B4EDFF9323E194E279512171B4E566C7EF95C52A580A044E722CF4951D2546F5F3ECF08A7397071DE36CE084F4B8B638D7325610F045E72F2474E53035FB16536236579BF29E8C8B99A21D773D08D58BF613716BB4B8A9C294565C2BE5377E4447EB08F7A23C7079E53F27A13DF9EE562FEA45100E1FCB4CA159B11495614A8CBAD9A468B6F42D1630A823D4573E482162ADB85BE12C6CDF91DE4B652BBA0B6B1538041DACD3E76B137180CC25EAF4502165B8AE01D8A722584968F4F71D88213B15009519524CAC4113BE3E157498A6C3C2C04E30AD9D095A74946B43B93E78A489A3AA81D8567CD37C2918B2307A9DAED629D64345F5CDD3AE8B703C57FAF255D11B9121CB877C7432B487BC088421792AC2157A622A535F5CC2814E764599E01C7C075BAC740F46ABCBCD17F81A0BBCF182063DABFB57046C993B5AD0FB6F57018F838F864B679266E3EC65E1844FF13DBFEDA9E4188FBBD7ECF733DF793C5CA6F6215865EF4E96CB377CCF5BD4F72C774596F97C8E0BF5822BB753338194E2425A56E8D6C053DF14EACCBFA30EC70926FBE53899A2FE719E1D0B66BADA6ECB5E509B7F9FE98517EC5D29472DB40E58AE4A6D9C2EA8E9622AF74434A41E1CE00A0C4B42F4E758BAB5B58222A39A786E523E3A958DB1100646B4748BA6039343870CF47DC643CB21380771D17EC9375DBC2B46831073D85C47A9811520F1567B18FE378D711B7303C4996524B04489289B5593D90BCA265CCF2DC4668CBD36D78623C39C7BB3CF1319EF7199B3FE9BD3617AFE1A279FC632E7EC3258AF5EFDFDAD73E1BB43508273FA64122B858C20083267991915656A596C01C2B6B1158FBAAFE716AC46D907E837835121B1B0CE26B248E6BDF182418397A6D101DF426DBF50D30336C651218AE414A0A9DBB937C292453D96AE45CD00581F9D18C96CDF619917A5C83DCA760EC640573E862638CAF33DBF02F59096719B76EB9277249D5919DB1D5E192BFD05CFCC4CAB0CB16C458ED63499F2B98F73753C6D18B4E57E8ADC6F78714E4F58D42474147B020737ACDA138DC403D51CD7E27B0F16D3BE0476C3ABCC6DA944EADD93E3936E4DEFB5BFE478B801152EBDE3DAEFCD695364B206BE08D51EAFAD97A38E8E5DE5B62BC07E09D3B56FBE2462C89C9343677D0F68DF20D3EA083EA25AA83B9CF1A5E67BBAF9AF11E80D1D75FAF2F53A684AC25D575BA91DBAC92826A7DE095F450C7119FF6FA6E0FE6AC1E746DDFC2F5991905EF7055EAF03562505CE5F91DE14B6A2E0424CC964F14F9617F10055ED43F30EDF21714A00EDA261A0A5A0A40AB75232FEC4378C20084FDDC86D974C9AD46F07DCF750788F6F764AED80B857E010F61745E4909AE6863D77C21468E736CABB6D974DCA90D165C207D5BA04EEA4F7837EA8F4796AA6CDA5C22D4EE4DB63A761B123851546AAD57F74D3DD635B0AE7A0FAC649068F6D03507D216552F78976A4D5EE80252E3BEA9CFF8346CD7DFD671ABFE3C83C9A3C51CE35E70C87C4BF911019645B7B172C7C0BAD0EF72B7CEF8006B7B5E7B72DA04B67BFCFF1CE3933F0197BB5F85Jason @ Melda Production
-
- KVRAF
- Topic Starter
- 2623 posts since 20 Oct, 2014
Hm, maybe a problem in 10.07 and you are using another version? I just see a dry/wet <- note connection and no transition / inertia....
-
- KVRAF
- 10375 posts since 2 Sep, 2003 from Surrey, UK
^^^
I think that you are right; I'll guess that jmg8 did that in the v11 beta. In the MIDI /Note Controllers, try changing the Dry/Wet target to "MultiParameter 1".
I did something similar to jmg8's approach:
-- Multiparameter 1 controls the EQ's Band 4 Frequency, with a Speed of 2000ms (to transition the complete frequency range),
-- MIDI Note Controller 1 controls the Multiparameter 1 value,
-- you could change the MP1 Speed to 2667 for a speed of 250ms / octave
-- or even use a different MIDI Note Controller to control the Speed!

I think that you are right; I'll guess that jmg8 did that in the v11 beta. In the MIDI /Note Controllers, try changing the Dry/Wet target to "MultiParameter 1".
I did something similar to jmg8's approach:
-- Multiparameter 1 controls the EQ's Band 4 Frequency, with a Speed of 2000ms (to transition the complete frequency range),
-- MIDI Note Controller 1 controls the Multiparameter 1 value,
-- you could change the MP1 Speed to 2667 for a speed of 250ms / octave
-- or even use a different MIDI Note Controller to control the Speed!

