mindbuffer / cohen_gig Goto Github PK

I just pulled down the latest master and got it working after a really long build process. The nannou windows then opened and I could see the visualisation going on.

I then navigated to the shader/src/lib.rs file and tried mutiplying the uniforms.time varibale by 0.0 to see if I could freeze time. After saving I could see it compiling and trying to hot reload but the visualisation stayed the same. I tried manipulating other parameters as well but seemed the changes were making no effect.

I then closed the window, reset all of my changes in the shader/src/lib.rs file and went to run the cohen_gig again, and cargo is now trying to rebuild all 345 crates from scratch again.... Are you seeing this bahviour as well @mitchmindtree ?

May have to thread the DMX sources and send the colours via a channel.

At the moment, each shader has a params struct that contains all of the shaders tweakable parameters. For example, the gilmore acid shader has a params struct like below:

struct Params {
    speed: f32,
    displace: f32,
    colour_offset: f32,
    grid_size: f32,
    wave: f32,
    zoom_amout: f32,
    rotation_amount: f32,
    brightness: f32,
    saturation: f32,
}

It would be nice to be able to tweak these values during the show. Currently, the way i've mapped the midi controller is I can tweak the 2 most fun params for each shader. In this instance though, the gilmore acid shader has 7 more variables that aren't able to be tweaked, and since my mac cant hot-reload I will be unable to 'live code' during the performance.

I was thinking it would be awesome if somehow, when a shader is selected via the Drop Down Menu, the params associated with that shader showed up as sliders.... I haven't been sure about the best way to auto-populate this with out some crude hand coded solution for each shader... maybe there is a nice dynamic way of achieving this?

GUI Example (would be nice is the sliders were named after the params they were controlling)

MIDI MAPPINGS

Just a heads up for future reference as it's never a good idea to match on strings for a couple of reasons:

1. More expensive to match on every character in a string rather than a single enum value.
2. Easy to make typos that won't get caught at compile time.

Currently, it looks like the wash_colors and led_colors are being packed into the same dmx buffer. We will need to be able to send 2 unique lines of dmx, one to the LED's and one to the house lighting console which will control the house wash lights and 2 spot lights.

This is the artnet wiring diagram that Jobe has put together. Would be good to hard code this into the software.

The Vertex input should look something like this:

struct Vertex {
    position: Point3,
    light: Light,
}

enum Light {
    Wash {
        index: usize,
    },
    Led {
        index: usize,
        row_col: [usize; 2],
        normalised_coords: Point2,
    }
}