![]() controlling bits with notes on channel 1, pitch on channel 2, programs on channel 3. Would having the different modes active simultaneously on different MIDI channels be another solution to your problem? E.g. So basically in order to be able to control all operands i must be in "bit" mode and use midi notes. Reaktor doesn't hosts plug-ins at all, i can use both bidule or logic to map any midi cc to any automation, with bidule i can map only midi cc, while with logic i can map almost everything but it's a pain. There is definitely room for improvement here.) I am not very familiar with Reaktor tbh and I feel I first have to ask you, isn't it possible to control VST parameters directly via Reaktor? Do you have to control everything through MIDI? (Permut8's MIDI implementation is as you can see very sparse. Sounds like a very interesting Reaktor project. ![]() Normally, clicks and aliasing is something you avoid like the plague as a dsp developer, but this time I decided to view it as a feature. That's what you get with primitive hardware. I am aware of the clicks in Permut8, and not only with program changes. send a program change to Permut8 #1, then next time to #2 and quickly crossfade, and then next time back to #1 again. Basically every permut8 will set the incoming step anticipatedly and then i will crossfade when is the time.ĭo you mean you will e.g. it doesn't work properly with AU's in Live. It's kind of "dangerous" to have one VST parameters that can change others, as I learned with the morph parameter in MicroTonic 3. If by automation you mean exposing every single bit as its own VST parameter I did actually try this once, but it didn't work very well with certain hosts. 2 - enable an automation for every operand switch (32 automations) in addition to the grouped ones (4 automations), this will allow the ability to map each operand to a midi CC, else as alternative the ability to map 2 midi ccs to each operand group se we will be able to make all the combinations using midi. This is an idea that I've had for a while. Smoothly changing the clock frequency just wouldn't work in synced mode otherwise. The reason the pitch wheel only works in "freq" mode is because it only works when a key is held, and the reason for that is that Permut8 temporarily disables it's phase lock with the host song position (if Permut8 is in synced mode that is). There is definitely room for improvement here.) 1 - allow pitchbend always to act like when midi control is set to "freq", this will allow to use "freq" feature while we are in bit mode, also allow the ability to map a midi cc to be used as "freq" mode while we are in other midi control modes so we can play notes using that midi cc like when you play midi notes when is in "freq" mode. Great fx by the way, finally something different. Basically every permut8 will set the incoming step anticipatedly and then i will crossfade when is the time. What i'm missing the most is a sequencer, i've tried using program change but everytime i change i get tons of clicks, what i'm thinking to do with reaktor is to control multiple istances of Permut8 so every step change i will make a crossfade between istances elimitating clicks. ![]() I know i can set midi control to "bits" but in this case i lose the ability to use it as Freq, so here's a couple of suggestion for the next update:ġ - allow pitchbend always to act like when midi control is set to "freq", this will allow to use "freq" feature while we are in bit mode, also allow the ability to map a midi cc to be used as "freq" mode while we are in other midi control modes so we can play notes using that midi cc like when you play midi notes when is in "freq" mode.Ģ - enable an automation for every operand switch (32 automations) in addition to the grouped ones (4 automations), this will allow the ability to map each operand to a midi CC, else as alternative the ability to map 2 midi ccs to each operand group se we will be able to make all the combinations using midi. What i'm missing right now is about operands, as you know there are 256 steps for each operand group so it's not possible to map a standard midi cc as the lower operand never activates. Hi everyone, i'm still playing with the demo and i'm trying to make a sort of sequencer for Permut8 using Reaktor (+bidule).
0 Comments
Leave a Reply. |