MXXX MultiParameter issues
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
It does, but it's not numbered
. Backward compatibility...
Basically originally only the first parameter's range was available for modulation/automation, but people asked for more, so now it's 4 I think, but the names have to stay the same for sake of backward compatibility. At least I think, I'll check if the " 1" could be added
.
- KVRian
- Topic Starter
- 1059 posts since 28 Jun, 2006 from Germany
A bit confusing okay. But in the end it's good that there is no bug after all, hehe! 
System: Win 10 64 bit / i9 9900K (8x 3.6 GHz) / 16 GB DDR4-3200 RAM / 1TB M.2 SSD + 2x 500 GB SSD / RME Babyface / Reaper
Tagirijus.de
Tagirijus.de
- KVRian
- 1094 posts since 23 Sep, 2006
Got another multiparameter bug:
Tried making a tremolo and freqeuency shifter with the same rate... you cant map a frequency shifter to a group (as it's not a 'rate' value but a 'shift' value), so i had to map both their rates to a multiparameter. When doing that, i set the tremolo to 'use first parameters range'.... so it mapped to the frequency shifters range... but it didn't, it was a much smaller range (and not the one that was disabled by enabling this option).
The work around is to obviously just type in the same range, but it's clearly a bug so I thought i'd write it up.
Thanks!
Tried making a tremolo and freqeuency shifter with the same rate... you cant map a frequency shifter to a group (as it's not a 'rate' value but a 'shift' value), so i had to map both their rates to a multiparameter. When doing that, i set the tremolo to 'use first parameters range'.... so it mapped to the frequency shifters range... but it didn't, it was a much smaller range (and not the one that was disabled by enabling this option).
The work around is to obviously just type in the same range, but it's clearly a bug so I thought i'd write it up.
Thanks!
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Nope it's not a bug
. Basically you need to have both parameters the same "kind of range". Frequency shifter is very specific, you might notice how different the range is. It goes to negative values and is more accurate near 0Hz. If you want to make the same frequencies (why btw?
), you'd have to simulate it using transformations for the parameters. You won't get and exact match though, that's impossible.
- KVRian
- Topic Starter
- 1059 posts since 28 Jun, 2006 from Germany
Haha, maybe I should call this thread "it's a bug, maybe! ... but possibly not after all". 
System: Win 10 64 bit / i9 9900K (8x 3.6 GHz) / 16 GB DDR4-3200 RAM / 1TB M.2 SSD + 2x 500 GB SSD / RME Babyface / Reaper
Tagirijus.de
Tagirijus.de
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
- KVRian
- 1094 posts since 23 Sep, 2006
OK, thanks Vojtech, I understand. Shame I can't match them but I get that it's an unusual match.
You asked why... Well, I was trying to match them because doing a 50% wet slow freq shift creates a super cool modulation effect and I was trying to pair that with a tremolo at the same rate... Then changing both mod speeds in sync, just to see what happens
Thanks!
You asked why... Well, I was trying to match them because doing a 50% wet slow freq shift creates a super cool modulation effect and I was trying to pair that with a tremolo at the same rate... Then changing both mod speeds in sync, just to see what happens
Thanks!
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Aaaha, interesting
. Well, I'm afraid a perfect sync will probably be impossible... 
