Statistics: Posted by 23fx23 — 31 Dec 2010, 17:35
]]>
But in Usine, when a VST is added on a patch a map file is created in the /temp/ folder. Actually this map is very simple but it will be improved in the future.
Statistics: Posted by senso — 31 Dec 2010, 11:28
]]>
But I'm no master so who knows...
Statistics: Posted by gurulogic — 31 Dec 2010, 02:44
]]>
i wondered if Vsts could provides their natives CCs to parameters assignations and if we could somehow get those infos.
for example on this vst cutoff is 74, res75 this one 21 ect
what im after is using usine multiples advantages relating automations, but i dlike to be able somehow to export the midi clip
i would have reced with usine, and import it in ableton (or could be extended to other daw).
if we could rec the same cc lane in the midi clip than the native one the vst react by default to, when reimporting the automation would be working in any other daw natively. it could also have some kind of "automap" features applications,
like we move a knob on a vst, and it's cc is scanned, then we move a hardware knob, and some patch maps the datas
so the cc in is straight converted and controls the vst. dk if see what i mean.
no worries if complex, there are workaround, for example iml for the last thing, or manually create maps.
but before i make a manual database of all my vsts cc nb and param names
i was wondering if the master didn't have any magic pgming trick possible
Statistics: Posted by 23fx23 — 31 Dec 2010, 02:29
]]>