Notifications
Clear all

Using a single instance of Unify, vs multiple instances  

  RSS

mschiff
(@mschiff)
Estimable Member
Joined: 5 months ago
Posts: 109
October 5, 2020 4:58 am  

What do you recommend, and what would be the most efficient?

A. A single instance of Unify with multiple instruments with some on the same midi channel, and others on different channels for different midi tracks.

B. Multiple instances of Unify, each on its own midi channel, with single or multiple patches in each?

I noticed that John did this in the last livestream, and was wondering why he changed his mind mid-way and went from A to B.

-- Martin


Quote
Leszek 1953
(@leszek-1953)
Member
Joined: 1 year ago
Posts: 172
October 5, 2020 9:06 am  

(@mschiff)

Hi Martin

Maybe he wanted to evenly load the computer's CPU. (use more CPU threads)
 
Les.

ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 1 year ago
Posts: 1606
October 5, 2020 3:53 pm  

@mschiff

There isn't a huge efficiency difference among the various possibilities.

Some of John's methods are just things he got used to with older plug-ins, but he may have specific reasons in some cases. I've asked him to cover this in a future livestream.


ReplyQuote
SSquared
(@ssquared)
Member
Joined: 1 year ago
Posts: 89
October 5, 2020 6:56 pm  

@mschiff

Some of this is based on what makes the best sense for you and your needs.  For example:

  • For live use, it may make sense to use standalone Unify (single instance) and assign MIDI channels to different Unify layers.
  • On the other hand, if you are recording, you may find creating a separate Unify per track works best (multiple instances).
  • There may be different ways of doing things and sometimes it comes down to what makes the best sense to how you work.

I can't recall when John may have used different MIDI Channels.  It is possible he was showing Unify's PolyBox tool which requires you to assign different MIDI Channels per layer.  That is specific to how the tool works.  Other times, he has shown recordings of how a demo track was made, or is creating a new recording during a livestream and will use separate Unify instances per track.

Do you recall the video(s) and time stamps?

Ableton Live 10, Omnisphere, Native Instruments, Diva, SynthMaster, Alchemy 1.55, Addictive Keys, Unify


ReplyQuote
mschiff
(@mschiff)
Estimable Member
Joined: 5 months ago
Posts: 109
October 5, 2020 9:47 pm  

@ssquared

It was at 1:07 of the Livestream from last Saturday (10/3).

-- Martin


ReplyQuote
SSquared
(@ssquared)
Member
Joined: 1 year ago
Posts: 89
October 6, 2020 1:24 am  

@mschiff

I see.  Thanks.  Maybe John will need to explain specifically why he chose a different MIDI Channel in this particular case.  I understand wanting to separate out the first 7 tracks (BPM drums) from the last two (BPM drums with a pad), but if the first seven are responding to all MIDI channels, I'm curious to know what MIDI Channel 2 did.  And if he was switching his keyboard MIDI channel as well.

It's possible it was for recording purposes.

Now you have me curious as well.  😀 

Ableton Live 10, Omnisphere, Native Instruments, Diva, SynthMaster, Alchemy 1.55, Addictive Keys, Unify


ReplyQuote
PlugInGuruForums
(@pluginguruforums)
Owner/Guru Admin
Joined: 1 year ago
Posts: 134
October 6, 2020 8:06 pm  

I needed to play a different sound independent of the first big drum groove so I used a different MIDI Channel. Logic automatically changes MIDI Channel if you assign a track to a specific MIDI channel. I didn't touch my keyboard since it's braindead (touch screen doesn't work). MIDI Channel 2 allowed me to play the BPM Key patch over the sequenced drum groove.

Life is Sound / Sound is Divine
www.pluginguru.com


mschiff and SSquared liked
ReplyQuote
SSquared
(@ssquared)
Member
Joined: 1 year ago
Posts: 89
October 11, 2020 5:43 am  

Thanks @pluginguruforums.

Ableton Live 10, Omnisphere, Native Instruments, Diva, SynthMaster, Alchemy 1.55, Addictive Keys, Unify


ReplyQuote
Share: