A) Usine V5 versions (pro VSTI, easine VSTI and their VST versions) allows you to insert usine directly as an audio vst in your live setup.
pros: integrated with host, perfect synchro link, all settings saved/recalled in live projects, easy route audio or remote parameters like standart vsts.
cons: it's not Hollyhock, so only V5 patches/workspace will work
B) Hollyhock. Here both app will run independantly standalone, it have to 'manually' be setuped to comunicate sync, audio, midi, and transport.
pro: it's hollyhock and up to date.
cons: have to handle two projects on the different apps and maintenance them all separately, harder to get perfect sync (still doable), need external things to be installed to communicate:
MIDI : midi datas can go from/to usine/live and vice versa using a virtual midi port (ie LoopBe, MidiYoke..) that wirtually acts as physical intefaces, so one daw port out emmit to the other port in.
Audio: Virtual audio ports exists as well (Jack, AsioLinkPro..) and will make virtual in/outs, same going from one daw to another.
transport/sync: man won't be able to perfectly jump in a project position transport, but the MTC make one daw master and the other slave (ie live emits timming on midi port and usine syncs).
Parameters: have to be dealt with midi then , eventually OSC if using M4L, but much harder imo to maintenance (ie loading snapshot refreshs) than vst versions, so personally i stick with VST versions..Statistics: Posted by 23fx23 — 20 Apr 2017, 13:16
]]>