This week I looked into the Max [nodes] object. Haven't confirmed exactly how I want to use it for my coloured objects but more generally, every object in Node Mode would be an effects unit. The proximity the the centre of each node (each nodal object) would have effects on the strength of that effect unit (e.g. greater room size or decay time on a reverb effect unit). That's the #goal anyway.
So let's jump into [nodes]!
Some new [objects] and terms I played with and learned today:
[nodes] - visualizes nodes in a 2D display and calculates the distance of those nodes from a point (called a knob). There are SO MANY attributes and parameters to control for [nodes]. Here are some I've decided to use for CHIMIRA:
nodenumber - the number of nodes
active - the active state of a node can be set on or off which can be handy if I want an effects unit turned off at specific times
setnode - sets the x and y positions of a node with its index. My coll data will definitely go towards a setnode so that the nodal positions are controlled by my physical coloured objects! There's also messages including xplace and yplace that can be sent to [nodes].
setsize/nsize - sets the size of a node. I'm not sure how to map this yet but I could have specific nodes with preset sizes (e.g. reverb fx units could be larger in size to affect more of the surface and be present more than an fx unit like pitch shifting. This way, when my knob/sample is "out of the range" of my node, then I only have pitch shifting effects when I'm much closer to the object/colour with pitch shifting effects).
appearance - there are so many fun things to customize! These include the colours of the background (bgcolor), node text (textcolor), knob color (knobcolor), centre of the nodes (pointcolor), and the first node (nodecolor). #Unfortunately, I haven't been able to find a way to #target specific nodes and change their colors yet.
[Nodes] has a candycane attritube that can alternate the colours of nodes with a predetermined set of colours. So, if there are a total of 6 nodes, and if candycane2 colour is red, then every second node would be red. This is a neat feature but I'm not sure if it's what I want as it'd be more useful if the nodes represented the colours that my objects were. Similar to how I've set up my [jit.lcd] dot display (link coming soon!).
Things to think about...
No data: what should my nodes do when there is no data? The absence of data should trigger that index to be turned off in its active state.
Knobs or Nodes: I currently don't know how to determine which object seen by MIRA is a knob or a node. Should I have a separate colour dedicated to be a knob and only a knob (e.g. only black objects are seen as a knob; only 1 black object would be allowed to be detected; black objects do not have nodal effects)? I could route black colour data and represent it as a knob. But my previous Sample Player has assigned samples per colour. I think I'll need to create a #selector for what mode I'm in. Currently that would allow either a Sample Playing or Nodal mode but not both simultaneously. Then my "black knob" idea could work.
Blobs: what about blobs of the same colour? Do they do the same thing? e.g. All red blobs affect a sample's pitch shifting with the proximity of the sample knob with the individual red blobs. How do we target those nodes to display the colour of that object?
Text: How do I manipulate the numbers displayed to represent the index system I've made with my tracker? e.g. Can I put the numbers '11' to represent blob 11 (second blob in tracker 1) and '23' to represent blob 23 (fourth blob in tracker 2) even if there aren't numbers between 12-19? For it to be more user friendly and intuitive to interpret, I might need to use another [jit.lcd] for the final #visualization that interprets data from this [nodes] object.
Коментарі