Statistics: Posted by ceasless — 05 Jan 2014, 19:57
]]>
]]>
Any thoughts on my proposed system? It would _really_ change the game of interfacing in Usine.
Statistics: Posted by ceasless — 05 Jan 2014, 19:26
]]>
]]>
However, this does not resolve the situation that in polyphony there is only one "copy" of the bus, so choosing a color on any of the voices will change that color for all voices.
Is there a way around this?
Statistics: Posted by ceasless — 05 Jan 2014, 18:57
]]>
what you see in the first wire is the real color value, then to transport those values, Usine need to translate them in numeric ones, but at final, you'll have the good result..
Statistics: Posted by nay-seven — 05 Jan 2014, 17:01
]]>
You can see that Usine reports the color on the wire going in to the bus. The next picture shows the stream for the FOREGROUND bus instead, but I assure you it is the same.
Am I missing something simple? I haven't really done much with buses yet because I've been focusing on making instruments more than workspaces as yet. I've played around with them before and they all worked exactly as expected until now.
How I'd ideally like to see colors work in Usine (I quote "bus" because I may be meaning something different?):
Be able to create a color "bus" that can be easily selected through a new fader, but for color "buses". This fader would show the list of these "buses" that have currently been patched in the rack. There would be another new module (like the color picker) where you could choose "buses" from 'rack', 'top-parent patch', 'parent patch', etc. These would be displayed in a 'triangle browser' view and would allow you to easily create colors that persist across an entire patch, have one simple interface for changing them, and then turn on polyphony and now have it for X voices. Interface elements within these voices can be controlled by rack level "buses" independently.
Since it is something like color, maybe it doesn't seem like such a big deal. But when I'm trying to keep everything looking how I want it it becomes a nuisance quickly and makes my patches very messy (and heavy!! cpu can go crazy!). As it is just as simple as color (which I doubt one would ever change during a live set without there being a technical reason for it like color blindness), it feels to me like maybe there is a way to create a new "bus" that doesn't care about latency just consistent routing for the color events that are (rarely) sent to modules.
Statistics: Posted by ceasless — 05 Jan 2014, 16:39
]]>