im trying to build a system so i can integrate my analog rytm better into my workflow with push. the problem: overbridge lists over 2000 parameters (i don
t need all of them, but most…), so creating an ø.param object for each of this would take days of work.
i already have all parameters listed and organized in the correct osc format, but i don`t know that much about scripting.
could someone help me out, with an example? i could send a part of the patch.
anyway:
will ossia work with so many parameters, or should i forget about this idea and look for another solution
(that would be very bad, as this patch is only a small part of a bigger intermedia-performance-system, which would benefit from ossias feature set immensely)
thx in advance