As one of Vuo's developers, I work on Vuo's engine (the thing that makes compositions run), work on nodes, and write documentation. You'll see me on the forums answering people's questions about Vuo.
I've been developing apps and frameworks for several years (since I was in college). Pre-Vuo projects include Kineme Quartz Composer plugins, iOS apps for education, an app that analyzes photographs of tomato slices, and software to help people with disabilities use talking keyboards.
I enjoy using Vuo to make live music visuals. My hope for Vuo is that it will grow into a community of people of diverse backgrounds and identities making lots of different artistic, useful, unique, goofy, beautiful, crafty, wonderful compositions.
One reason that you might see banding is if your monitor supports fewer colors. If that's the problem, adding some noise (as in the attached composition) should help.
To check if you really are getting an 8bpc image, you can open it in an image editing application and check the number of unique colors. For example, in Photoshop, go to Image > Mode > Indexed Color. The maximum unique colors you could see with 8bpc is 256. If you see slightly fewer than that (like 246), it's fine. If you see a lot fewer, there's a problem.
Sure, a Change Items in List node — like the existing Change Item in List, but inputting multiple Positions and multiple New Items — sounds good. Opened for voting.
@Bodysoulspirit or @Xavier dev, did you have a specific example in mind where the Change Item Ranges in List node would be useful? Unless you do, we plan to skip this node and just add the Change Items in List node. Since a Change Item Ranges in List node would have several input ports that you'd have to coordinate to make sure the data is entered consistently in all of them (correct number of list items, etc.), we're thinking the complexity of the ports would outweigh the convenience of being able to use ranges.
We're continuing to make progress on working around this GPU driver bug. We had suspected that certain changes to the graphics system (eliminating the use of OpenGL shared contexts) would fix the crashes/hangs, and we confirmed that they do.
We've started using computers with AMD GPUs more frequently, and have also observed similar system-wide hangs when using Final Cut Pro X on those computers (without any Vuo compositions running). And other people have reported issues using Photoshop's GPU acceleration with AMD GPUs. So this seems to be a fairly widespread AMD driver issue :^/