Would a similar enhancement be possible to extend Unify from the already supported NI Symphony Essentials towards the full NI Symphony Series?
Unify by PluginGuru; The next big thing?
-
- KVRAF
- 5622 posts since 23 Aug, 2014 from Boston/Cambridge
DiscoverStation is simply wonderful and even allows us to Unify BBCSO Pro, not only Discover or Core. Kudos
Would a similar enhancement be possible to extend Unify from the already supported NI Symphony Essentials towards the full NI Symphony Series?
Would a similar enhancement be possible to extend Unify from the already supported NI Symphony Essentials towards the full NI Symphony Series?
-
- Banned
- 1646 posts since 4 Aug, 2017
Cameron did a great job of this video:
-
- Banned
- 1646 posts since 4 Aug, 2017
I agree!
-
- KVRist
- 230 posts since 9 Mar, 2017
Probably. I think one of the Unify users is interested to try this. Check our Forum in this section: https://forums.pluginguru.com/unified-libs/Fleer wrote: Sun Apr 04, 2021 1:54 am DiscoverStation is simply wonderful and even allows us to Unify BBCSO Pro, not only Discover or Core. Kudos
Would a similar enhancement be possible to extend Unify from the already supported NI Symphony Essentials towards the full NI Symphony Series?
-
- KVRAF
- 4340 posts since 8 Mar, 2005
Couldn't you do most of this with Maschine plugin inside your host?
-
- KVRAF
- 3735 posts since 17 Sep, 2016
Say what? Not sure if you are joking! If you were, that's a good one!
Unify Standard comes with 400 ready to play sounds, a mix of sampled and synthesizer layers, plus effects.
Have you installed the free Spitfire Audio LABS sounds and the Unified LABS presets yet? There's a lot in there for free! https://labs.spitfireaudio.com/
There are also free Unified libraries for the free synths Surge and Pendulate. Nice!
Plus there are quite a few other free Unified libraries for various paid commercial synths. You might already own some of these synths, so then it's just a matter of adding that free Unified library to Unify.
Windows 10 and too many plugins
-
- KVRAF
- 5622 posts since 23 Aug, 2014 from Boston/Cambridge
Hell yeah, those included Unify sounds are some of the best PlugInGuru ever made. Over 3 GB of them. And indeed, add Spitfire LABS to those, free as well as the accompanying Unify patches, and you’re set for a looooooong time.
-
- Banned
- 1646 posts since 4 Aug, 2017
You can add all kinds of free synths to Unify other than the ones included (for example: u-he, TAL, Surge, Vital, Full Bucket) and have an incredible instrument for very little $$$.Fleer wrote: Fri Apr 09, 2021 1:28 am Hell yeah, those included Unify sounds are some of the best PlugInGuru ever made. Over 3 GB of them. And indeed, add Spitfire LABS to those, free as well as the accompanying Unify patches, and you’re set for a looooooong time.
-
- KVRist
- 230 posts since 9 Mar, 2017
You probably could, and if Maschine is your thing (especially if you use a Maschine controller), you may want to stick to what you know. Patch loading is faster in Unify, and I'm not sure if the Maschine plug-in supports multi-threading; if not, you will run into CPU limits very quickly.keyman_sam wrote: Fri Apr 09, 2021 12:46 am Couldn't you do most of this with Maschine plugin inside your host?
However, Unify is itself a plug-in, so if you want you can use it inside Maschine. One of our users is taking a deep look into this right now.
-
- KVRist
- 283 posts since 6 Aug, 2017
Is it possible to set up keyswitches to drive inputs to different layers (or sets of layers) in Unify?
I'm thinking something like this:
I set up a keyswitch range from C0 to B0. If I hit C0 it sets all further midi note messages outside the keyswitch range to channel 1, and every layer in Unify that listens to channel 1 receives note messages, until I hit another keyswitch. Then if I hit C#0, it sets all further midi note messages outside the keyswitch range to channel 2, and every layer in Unify that listens to channel 2 receives the note messages.
This would be useful for setting up keyswitches for libraries that don't have keyswitches already, or for creating keyswitched layered Unify-ed instruments.
If this isn't possible yet, and you would consider implementing it, here are some considerations I've thought of:
-When a keyswitch is hit, any note-on's currently playing should wait until the corresponding note-off is received to change the channel that particular note is sent on. (This is to prevent hanging notes).
-Mod wheel, pitch, and other cc messages should probably be sent to all channels regardless of which keyswitch is active.
I'm thinking something like this:
I set up a keyswitch range from C0 to B0. If I hit C0 it sets all further midi note messages outside the keyswitch range to channel 1, and every layer in Unify that listens to channel 1 receives note messages, until I hit another keyswitch. Then if I hit C#0, it sets all further midi note messages outside the keyswitch range to channel 2, and every layer in Unify that listens to channel 2 receives the note messages.
This would be useful for setting up keyswitches for libraries that don't have keyswitches already, or for creating keyswitched layered Unify-ed instruments.
If this isn't possible yet, and you would consider implementing it, here are some considerations I've thought of:
-When a keyswitch is hit, any note-on's currently playing should wait until the corresponding note-off is received to change the channel that particular note is sent on. (This is to prevent hanging notes).
-Mod wheel, pitch, and other cc messages should probably be sent to all channels regardless of which keyswitch is active.
-
- KVRist
- 230 posts since 9 Mar, 2017
Some great thoughts here, @DrMEM, thank you.DrMEM wrote: Sat Apr 10, 2021 3:20 am Is it possible to set up keyswitches to drive inputs to different layers (or sets of layers) in Unify?
I'm thinking something like this:
I set up a keyswitch range from C0 to B0. If I hit C0 it sets all further midi note messages outside the keyswitch range to channel 1, and every layer in Unify that listens to channel 1 receives note messages, until I hit another keyswitch. Then if I hit C#0, it sets all further midi note messages outside the keyswitch range to channel 2, and every layer in Unify that listens to channel 2 receives the note messages.
This would be useful for setting up keyswitches for libraries that don't have keyswitches already, or for creating keyswitched layered Unify-ed instruments.
If this isn't possible yet, and you would consider implementing it, here are some considerations I've thought of:
-When a keyswitch is hit, any note-on's currently playing should wait until the corresponding note-off is received to change the channel that particular note is sent on. (This is to prevent hanging notes).
-Mod wheel, pitch, and other cc messages should probably be sent to all channels regardless of which keyswitch is active.
Unify currently has three distinct ways of setting up MIDI control. The newest one, "MIDI Controller files" (https://pluginguru.net/unify/manual/dok ... ller-files), allows defining responses for specific controllers in the stand-alone Unify app only. (In a DAW, it's not possible to tell multiple controllers apart except by MIDI channel.) In a MIDI Controller file, you can use note-on events to trigger parameter changes and actions, so some of what you ask is possible already.
I'm doing my best to make it clear to everyone that Unify's MIDI control features are still embryonic and subject to LOTS of change. I wasn't sure how much user interest there would be, but since we've made even these preliminary features available, response has been huge.
Are you a member of our PlugInGuru Forums? If not, please join, and post some of these ideas in the Live Performance part of the forum at https://forums.pluginguru.com/unify-live/.
-
- KVRian
- 754 posts since 27 Nov, 2011
Hi there, first I want to say thank you for making Unify. It is allowing me to do something that I've never really been able to do before - create synth patches and easily sync them between my two machines. It's a simple thing, but letting me set the library path, and saving each patch as a separate file, means I can just store it all in Dropbox and it just works. And it's built so well for working quickly and simply, it's just a lot of fun.
I do have a few requests
First is an FX version (which I believe may be on the to-do list). One of the great powers of Unify for me is syncing patches between computers. Of course I would also like to do that with FX devices... so please just count this as a vote for that feature.
Second is to have an option for the patch browser to exclude patches that use any plugins I don't have installed. So I'm building patch libraries across my two machines, and I have most of the same plugins on both machines. But there are some plugins I only have on one machine. The automatically-generated "Instruments" section is super cool. It would be great if I could set Unify to only show patches that use plugins I have on that machine, and hide any patches that use plugins I don't have.
Third is a layer preset browser, with next / previous to cycle through layer presets. This would be similar to the "Source" browser in Omnisphere, and would make it a lot easier to try out layer combinations quickly.
I do have a few requests
First is an FX version (which I believe may be on the to-do list). One of the great powers of Unify for me is syncing patches between computers. Of course I would also like to do that with FX devices... so please just count this as a vote for that feature.
Second is to have an option for the patch browser to exclude patches that use any plugins I don't have installed. So I'm building patch libraries across my two machines, and I have most of the same plugins on both machines. But there are some plugins I only have on one machine. The automatically-generated "Instruments" section is super cool. It would be great if I could set Unify to only show patches that use plugins I have on that machine, and hide any patches that use plugins I don't have.
Third is a layer preset browser, with next / previous to cycle through layer presets. This would be similar to the "Source" browser in Omnisphere, and would make it a lot easier to try out layer combinations quickly.