yeah, it changes your music production game into a more complicated one.
i can already layer synths to make every sound imaginable in my daw.
yeah, it changes your music production game into a more complicated one.
As can I. However, it certainly makes everything much easier if you work in multiple DAWS as I do. In addition, it is a great instrument in itself with a great and growing library. That is a big part of why it was developed.
You can already have midi effect chains within midi layers.WatchTheGuitar wrote: ↑Sat Jul 04, 2020 4:06 pm Feature request : Allow MIDI Effects to have other MIDI Effects as a Source
I can work around this by using the calling MIDI effect in the main Unify instance and have the receiving MIDI effect in the MIDI layer of a child Unify instance as an instrument, but it'd be a lot less hassle to be able to do it all in one Unify instance.
What I was working on (which works fine via the work around) is a MIDI effect listening on MIDI channel 1 (which my main keyboard uses) that changes scale (midiScaleChanger) and sends the result on MIDI Channel 9, then the 'listening' MIDI effect contains ChordPotion and then sends to instruments I've set up to receive on MIDI Channel 2,3,4 and 5.
And those instruments are all Unify instances with their own MIDI scale changers.
Gets a bit Inception like without the ability to set up the MIDI routing in one Unify instance.
Wasn't working for me when I tried it. The order I put things in made no difference, it didn't seem to take the output of one item and push it into the next, instead all seemed to fire off at once.DrMEM wrote: ↑Sat Jul 04, 2020 5:58 pmYou can already have midi effect chains within midi layers.WatchTheGuitar wrote: ↑Sat Jul 04, 2020 4:06 pm Feature request : Allow MIDI Effects to have other MIDI Effects as a Source
I can work around this by using the calling MIDI effect in the main Unify instance and have the receiving MIDI effect in the MIDI layer of a child Unify instance as an instrument, but it'd be a lot less hassle to be able to do it all in one Unify instance.
What I was working on (which works fine via the work around) is a MIDI effect listening on MIDI channel 1 (which my main keyboard uses) that changes scale (midiScaleChanger) and sends the result on MIDI Channel 9, then the 'listening' MIDI effect contains ChordPotion and then sends to instruments I've set up to receive on MIDI Channel 2,3,4 and 5.
And those instruments are all Unify instances with their own MIDI scale changers.
Gets a bit Inception like without the ability to set up the MIDI routing in one Unify instance.
You can also load the free Kushview Element as a midi effect to contain other midi effects if you need to do some crazy midi splitting and routing stuff in an easy-to-visualize way.
Dat Sine Wave though
I'm curious why you say that. Perhaps we're not doing a good enough job of explaining what Unify is.
© KVR Audio, Inc. 2000-2024
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement