Abstracting and Building Coll Data
We've got some x, y locations but what about using it now? Dr. Hamel and I previously discussed some of our options:
using the locations as a node for each
dividing the surface into a grid for applications like a step sequence (this would provide less sensitivity to the actual positioning of the colour since it is generalized into an area rather than a point)
there was another one but it's escaping me at the moment...
OH. Also, we want to accurately present when a colour ISN'T there. Otherwise, that's a lot of colour data left inside our tracker that just isn't there! So let's start with that...
![](https://static.wixstatic.com/media/b40f49_808c7935c25a4331b6e6cd6b1d51f162~mv2.jpg/v1/fill/w_980,h_822,al_c,q_85,usm_0.66_1.00_0.01,enc_auto/b40f49_808c7935c25a4331b6e6cd6b1d51f162~mv2.jpg)
This turned out to not be too difficult. Since our Tracker patch produces -1 values when the colour isn't present (which was simply selected out), we can use sel -1 to produce some message that the colour simply isn't present! Location (-100, -100) is now sent out when there colour isn't there. Done.
Now to make a Coll Grid Data Structure! This way we'll have an index of different colours and their respective live locations to use for musical applications!
![](https://static.wixstatic.com/media/b40f49_762047236b214c59a1813cc0953266a3~mv2.jpg/v1/fill/w_401,h_833,al_c,q_80,enc_auto/b40f49_762047236b214c59a1813cc0953266a3~mv2.jpg)
new: [uzi]
flashback to MUSC 320 [coll]
Comments