Notifications
Clear all

Algorythmic perfomance on Unify (approaches)

13 Posts
6 Users
14 Reactions
892 Views
(@ro-mix)
Estimable Member
Joined: 4 years ago
Posts: 119
Topic starter  

Have a good time, all!
I`m pretty much understand now how i can change patterns and even record parts in standalone Unify (for that i use Reaktor Midi looper ensemble and Stochas vst). Next level of question arouse: how to program some events and buildups. For fluid performance.
When buildup starts, f.e drum part is off - ok, for that we can place all the drum parts in separate Unify layer and use Mono Latch mode, so when i trigger one part, another if going offline.
But i try to figure out, can i use Polybox (other midi stuff) to make automatic switch from beat to breakdown (buildup) and then turn on some beat again. Buildup probably should be oneshot loop or sample.

PS: I stopped to use DAW for composing for sometime now, because i feel that this algorithmic approach is very powerfull and i go this way πŸ™‚
So let`s discuss any approaches to programming performance scenarios inside one Unify instance, without loading additional patches.

This topic was modified 3 years ago 2 times by RO-mix

   
saif_sameer reacted
Quote
saif_sameer
(@saif_sameer)
Member
Joined: 4 years ago
Posts: 60
 

We are on the same boat, personally I mainly use Unify as standalone realtime music performance tool. And aside of BlueARP as a project got myself involved in since 2011 till this moment, there are potential exclusive tools in Unify Shane made (thanks to him) and he has a brilliant vision to implement some unique approach that sounds musical, non-robotic, creative & intuitive.

Β 

Btw, try testing latest version of BlueARP 2.3.2 (which is not included in Unify) it has new improvements. And if you would like to share your suggestions, ideas & opinions on BlueARP, check the links below:

BlueARP plugin thread on KVR

BlueARP desktop module discussion

"In heaven, all the interesting people are missing."
Friedrich Nietzsche


   
Bernd@PDX, mj_prod, RO-mix and 1 people reacted
ReplyQuote
JeremyH
(@zinct)
Member
Joined: 4 years ago
Posts: 514
 

@saif_sameer

Thanks for the information on BlueARP 2.3.2.Β 


   
saif_sameer reacted
ReplyQuote
saif_sameer
(@saif_sameer)
Member
Joined: 4 years ago
Posts: 60
 

@zinct my pleasure πŸ™‚

Please make sure to put new version in separate folder & to not overwrite the BlueARP version comes with Unify.

Preset made in v2.3.2 might not be compatible with 2.3.1

"In heaven, all the interesting people are missing."
Friedrich Nietzsche


   
mj_prod and RO-mix reacted
ReplyQuote
JeremyH
(@zinct)
Member
Joined: 4 years ago
Posts: 514
 
Posted by: @saif_sameer

@zinct my pleasure πŸ™‚

Please make sure to put new version in separate folder & to not overwrite the BlueARP version comes with Unify.

Preset made in v2.3.2 might not be compatible with 2.3.1

Thanks @saif_sameer 👍Β  Yes, I was careful to keep them separate.


   
saif_sameer reacted
ReplyQuote
(@ro-mix)
Estimable Member
Joined: 4 years ago
Posts: 119
Topic starter  

I don`t know why, i copyed plugin to my vst folder, scanned. It shows up but loads version 2.3.1 in Unify anyway...tried to rename dll.. same. In Reaper it loads newest version.

This post was modified 3 years ago 2 times by RO-mix

   
ReplyQuote
saif_sameer
(@saif_sameer)
Member
Joined: 4 years ago
Posts: 60
 

@ro-mix Yes true, it is due to Unify's way to handle plugin management, you can check plugins verified in Unfiy, there will be both BlueARPs, by right clicking on any of them, it is possible to locate folder it resides in. Then rename it.

Personally, I'd give green light to replace the previous version with the newest one, I've been testing regressing compatibility since August 2020 and all is fine. Will check with Shane about that.

"In heaven, all the interesting people are missing."
Friedrich Nietzsche


   
RO-mix reacted
ReplyQuote
(@ro-mix)
Estimable Member
Joined: 4 years ago
Posts: 119
Topic starter  
Posted by: @saif_sameer

@ro-mix Yes true, it is due to Unify's way to handle plugin management, you can check plugins verified in Unfiy, there will be both BlueARPs, by right clicking on any of them, it is possible to locate folder it resides in. Then rename it.

Renaming dll does not help. Unify loads embeded BlueArp anyway... will wait when unify team will include a new version.


   
ReplyQuote
Robert.P
(@robert-p)
Reputable Member
Joined: 4 years ago
Posts: 293
 
Posted by: @ro-mix

But i try to figure out, can i use Polybox (other midi stuff) to make automatic switch from beat to breakdown (buildup) and then turn on some beat again. Buildup probably should be oneshot loop or sample.

Β 

Hi, as for the drums I had some good results with NI Maschine running inside Unify:

  • it is possible to map up to 128 scenes (1 drum pattern per scene) to MIDI notes
  • the drum patterns can be triggered either by the MIDI keyboard/pad controller or
  • by MidiBox routed to Machine layer

   
RO-mix reacted
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4453
 

Unify's Known Plug-Ins list contains extra details like version numbers, which actually aren't important. If you replace a plug-in with a newer version, as long as the new file (e.g.Β .dll orΒ .vst) overwrites the old one, Unify will still load the newer one, because the older one is gone and the new one is at the exact same path. The Known Plug-Ins list will still display the old version number. If you want it to update, it's often best to delete the plug-in from the Known Plug-Ins list, then drag-drop the new one in (or use "choose plug-in file(s) to scan..." on Operations menu).

Much of the code behind the Known Plug-Ins list was inherited from an older example program. Eventually I will rewrite it all, but for now, at least it works, and I prefer not to take the risk of breaking it.


   
RO-mix and mj_prod reacted
ReplyQuote
 zimp
(@zimp)
Eminent Member
Joined: 3 years ago
Posts: 22
 

It would be nice if layers could have a "mode" switch. Like some layers for live playing, other layers that use arpeggiator and again other layers that triggers the Midibox.

As it is now when a layer or patch is loaded from the browser every setting that is made for that layer is overwritten. Not always what you want. Separation between modes (live/arp/midibox plus additional settings like zoning, panning, volume) and sounds (VST) looks to me a logical step.


   
ReplyQuote
(@ro-mix)
Estimable Member
Joined: 4 years ago
Posts: 119
Topic starter  

@zimp Hm... Mechanic a-la Ableton live with swap preset or device could be nice improvement for quick integration and patchΒ  preview .. Modes are two complicated.. and we already have midi layers separate for Arps etc..


   
ReplyQuote
saif_sameer
(@saif_sameer)
Member
Joined: 4 years ago
Posts: 60
 

@zimp possible, BlueARP can call "Empty dummy" arp preset that bypasses notes as they are without arpeggiating, so then the notes can go to MidiBox.

Another approach, is the newly added feature in PolyBox, it automates layer selection by assignable Midi controller / Macro. So then we can have two layers, (A) BlueARP driven, and (B) MidiBox driven, and PolyBox will alternate between the two based on assigned parameter.

If I'll have free time on weekend I will post a coupe of patches as example. Otherwise, wait till one of my Unify libraries be ready. (Okay time to get back to work πŸ˜€ )

"In heaven, all the interesting people are missing."
Friedrich Nietzsche


   
mj_prod reacted
ReplyQuote
Share: