Steps to reproduce

• Add an animation to a scene
• Start the timeline
• Add the scene to the timeline
• Remove the animation from the scene

Expected

The properties that are changed because of the animation are reset to 0

Actual

The properties that are changed because of the animation are still there with the last value the animation gave them

It is not possible to create a custom property for an instance of a dom-repeat element: Polymer/polymer#3534

A computed property can't be used, because we only know the ID inside the dom-repeat and as far as I know I can't pass arguments into a computed property:

  getScene(sceneId) {
    return this.sceneManager.filter(scene => scene.id === sceneId)
  }

  static get template() {
    return `
      <template is="dom-repeat" items="{{scenes}}" as="sceneId">
        {{getScene(sceneId)}}
      </template>
    `
  }

If it would be possible to create a custom property inside dom-repeat, I would not have to call getScene(sceneId) all the time to retrieve the data for the scene.

In order to activate a specific MIDI button without the actual MIDI controller being connected, it would be nice to trigger the MIDI event that is associated with a MIDI button by using the UI.

selectors.getScenes(getState()).map(scene => {
      if (scene.fixtures.indexOf(fixtureId) > -1) {
        dispatch(removeFixtureFromScene(scene.id, scene.fixtures.indexOf(fixtureId)));
      }
    });

-> scene.fixtures.indexOf

When a scene is stopped, the last values of that scene are still in the global array of DMX values.

Do we want that? Does this make sense? Or should we reset the values to a configurable default value after the scene is not active anymore?

• Remove observers,
• calculate properties in plain JS
• then write into state
• then change properties in component (if that is needed at all)

When interpolation between a "static" value, the value jumps to a lower value even when nothing should be changed at all.

Example

0: {
  dimmer: 255
},
1: {
  dimmer: 255
}

Expected result

No change in the value

Actual result

Value is jumping from 255 to 254 and back to 255:

Components / Modules

• Keytime
• universe-manager
• timeline-manager
• timeline-animation

The state is saved into localStorage for the universe, but the properties of the DMX fixtures are not set based on their values from the corresponding universe.

Problem

• We have 2 fixtures: Fixture A (FA) at address 1 and Fixture B (FB) at address 10
• We have a scene for FA and another scene for FB
• We activate the scene for FB, but FA gets the properties that are changed as part of the scene for FB

This would be useful when going into a venue and trying to play with the fixtures and creating keyframes based on the values of the fixtures.

Related to #50

The port in main.go is hard coded to 1337, but it should be configurable trough the bash via a -port cmd argument.

In order to control the VisionLord fixtures directly from Dekk, we need to create an API that works via WebRTC.

Keeping the strobe in sync on all fixtures (hardware) is really difficult, because all of them have different frequency ranges. That's why it would be cool to have a strobe that is the same on all devices.

ALSO it would be nice to have the strobe in sync with the music.

Instead of just showing a number, the degree should be of type "slider".

Issue description

When removing a fixture from a scene the corresponding values in the universe are not reset. Instead the last values for that fixture are still in the universe.

Steps to reproduce

• Add a scene with an animation & fixture to the timeline
• Start the timeline
• Remove the fixture from the scene
• Open "universes" and see that the properties are still present

Versions

1. Browser: Chrome 68
2. luminave: 3.0-dev

It would be nice to use the see the color that gets transmitted by modV to luminave in the UI, so that someone can check if everything is working.

When using libs/abcq/uuid.js it is possible that the same UUID is returned multiple times. This only happens in combination with a persisted state (e.g. localStorage), because the generated UUID is saved and loaded when the application is reloaded.

Saving the last UUID into localStorage could be an option, but because we are using the UUID also in https://github.com/NERDDISCO/VisionLord/blob/feat/redux/src/constants/index.js, it is not possible to access the localStorage at this point. Also adding a new constant would mean that everything that was added afterwards (e.g. a universe or fixture) is not unique again.

Ideas

Two instances

• Use a separate instance for constants and for the the components
• Persist the latest UUID for the components into state and reset it when the frontend is loaded

Random UUID

• Use a module that creates random UUIDs

When you attach the MIDI controller via USB, you get a input connected and a output connected event. If you reload the page, you only get the input connected event and not the output connected again.

This might cause problems when we want to use the output to send data back to the MIDI controller.

When scenes are added to the timelineManager with addSceneToTimeline only the sceneId is used.

If the same scene is added x times to the timelineManager, it's impossible to remove the scene that was added by a for example MIDI controller input.

Load all DMX fixtures by using dynamic imports: https://developers.google.com/web/updates/2017/11/dynamic-import

Expected

When resetting the timeline-manager all scenes are removed and the attached fixtures are reset as well.

Actual

When resetting the timeline-manager all scenes are removed but the fixtures still have all their properties with the last value.

Integrate modV 1.0 so that every color property can be overridden by the color that was transmitted by modV.

At https://github.com/Polymer/pwa-starter-kit you can find the PWA Starter Kit and it has some awesome things to kickstart an application:

• Views / Routes
• lit-element
• unit & integration tests
• Redux store
• build

and much more.

Use https://github.com/FloEdelmann/open-fixture-library instead of hard coded fixture objects.

Create a WebSocket connection to the fivetwelve-bridge in order to send the universe to dmxpen.

A connection was hacked into VisionLord for JSConf Budapest 2017 in https://github.com/NERDDISCO/VisionLord/tree/feat/fivetwelveWebsocketLink

When you load VisionLord with the state live set to true, the universe-manager is not instantiated and therefore can't update the existing universes.

Workaround

After a page load switch from live to edit to live mode.

Group buttons / scenes in groups, so that they can react to changed in the same group

Deactivate others in group when another element gets activated

• Button A is in a group with Button B
• Button B is activated (pressed)
• Button A gets pressed
• All buttons in the same group are inactivated (Button B is inactive)

Same applies for Scenes in the Timeline.

The fixtures can only be removed when they are re-triggered in the order they were added via the MIDI controller:

Reproduce

• hit button 1, button 2, button 3 to add the scene
• hit button 2 to remove the attached scene
• Removes scene attached to button ?

Problem

The dmx-properties are not correct after a fixture was removed

Steps to reproduce

• Add any fixture (for example "ADJ Starburst")
• And another fixture (not the same as before, for example "CameoPixBar600PRO")
  
• Remove the firstly added fixture

Expected result

• The second fixture has it's dmx-properties

Actual result

• The second fixture has the dmx-properties of the removed fixture
  

Instead of rendering a input type=range for a MappedParam, it would be awesome to see the different mappings, maybe in a select?

In order to use luminave in other browsers, we have to add a transpiler like webpack to get an ES5 version.

Even if the other browser doesn't support WebUSB, you can use the other integrations.

Expected

When using play then pause then play the progress should continue where it left of the last time.

Actual

The progress resets itself after the second play

• Set the properties of a fixture
• Convert those properties into a keyframe

• Add support for the WebAudio API
• Choose an audio source
• Use the frequency data to dynamically add scenes to the timeline
• Use https://github.com/meyda/meyda for extended audio processing

Instead of having a WebSocket connection it would be nice to use a ReadableStream to improve the performance of sending data to fivetwelve.

There are a lot of ideas currently living inside ideas.js, which should be issues on GitHub. Also some classes have Todos which are also issues.

When the timeline-manager is started it will update all fixtures that are defined in VisionLord, instead of just the ones that are a part of a scene.

Expected

Only the fixtures that are part of a scene get updated.

Actual

All fixtures are updated when the timeline is running.

Additional info

I guess this is happening because the dmx-fixture itself is listening to changes to the timeline-manager: https://github.com/NERDDISCO/VisionLord/blob/feat/redux/src/components/dmx-fixture/index.js#L62-L66

When using another browser and reusing a configuration, the status of the USB connection might be connected, even when the device was never paired.

When pausing the timeline the animation loop is still triggered one more time.

Expected

When I pause the timeline it stop immediately

Actual

There is at least one more frame being executed

Interpolate between values if you have something like this:

• keyframe 1: strobe(80)
• keyframe 2: strobe(120)

Instead of just using the string as we do right now.

The PixBar 600 PRO has a 12 LEDs and all of them have their own sub-property:

// ...
      params: {
        dimmer: new RangeParam(1, { min: 0, max: 255 }),
        strobe: new RangeParam(2, { min: 0, max: 255 }),

        led1: {
          color: new RgbParam([3, 4, 5]),
          white: new RangeParam(6, { min: 0, max: 255 }),
          amber: new RangeParam(7, { min: 0, max: 255 }),
          uv: new RangeParam(8, { min: 0, max: 255 })
        },

        led2: {
          color: new RgbParam([9, 10, 11]),
          white: new RangeParam(12, { min: 0, max: 255 }),
          amber: new RangeParam(13, { min: 0, max: 255 }),
          uv: new RangeParam(14, { min: 0, max: 255 })
        },
// ...

Right now this is not handled so it's not possible to set a color

Problem

When attaching the USB DMX controller to the computer and opening VisionLord, all attached DMX fixtures go cray cray and show random stuff

Temporary fix

Send the universe from VisionLord to the USB DMX controller by starting the timeline

Additional info

• This might happen because when the USB DMX controller is attached to the computer and it is starting the loop (because it's an Arduino) it send an empty array into the DMX512 network which causes this shit (JUST AN IDEA)

Add a filter to the scene-manager to be able to filter scenes by name and assigned fixtures.

Maybe even create a search component that can be used in other *-manager as well 😎

Steps to reproduce

• Add a scene to the timeline
• Start the timeline
• Change the keyframe of the animation that is attached to the scene that is currently running

Expected

The animation is using the updated keyframes

Actual

The animation is using the old keyframes

Use Polymer 3 and lit-element instead of the old pre-release of Polymer and the Polymer Element.

• Change @polymer/[email protected] to @polymer/[email protected]
• Change @polymer/[email protected] to @polymer/[email protected]
• Use @polymer/[email protected] instead of polymer-element
• Use polymer serve

In order to plan in advance where the fixtures are in a specific venue, it would be nice to have a VenueManager

Concept

• Create the venue in a 2D space
• Set the position of the fixture in the room
• Visualize the current properties of the fixtures based on the scene
• Create a grid that represents the venue with slots to put fixtures to
• Assign fixtures to slots
• Assign modV-colors to slots
• Create animation + scene based on the assignments (Prefix: Name of the venue + slot-name)
• Add animations to slots (Those animations have to be added to the assigned scenes)
• Show the modV manager and make it possible to change the modV grid based on input values, so we can see the current mappings without modV running
• Create a new fixture when creating a slot
• Move the edit into the sidebar, so that the grid is not resized when editing
• Tests

Data

{
    "venueManager": [{
        "id": "uuid",
        "name": "hall",
        "width": 5,
        "height": 10,
        "slots": [{
                "id": "uuid",
                "name": "washer 1",
                "x": 1,
                "y": 4,
                "fixtures": ["uuid", "uuid"],
                "animations": ["uuid", "uuid"],
                "sceneId": "uuid",
                "modV": 40
            },
            {
                "id": "uuid",
                "name": "spot 1",
                "x": 3,
                "y": 4,
                "fixtures": ["uuid"],
                "animations": ["uuid", "uuid"],
                "sceneId": "uuid",
                "modV": 20
            }
        ]
    }]
}

From time to time (after a few refresh) it is not possible to control the fixtures anymore. The animation fires, but the lights don't do anything.

Workarounds

1. Sometimes it just starts to work again after a refresh.
2. And sometimes a refresh is not enough, so I have to remove the paired Arduino from the Browser, refresh and connect again.
3. And if 2. is not working: Remove the paired Arduino from the Browser and restart the Browser and connect again

🤔

When you set the property of a dmx-fixture and the timeline is paused, the value gets not updated in the universe.

This was done because of performance problems when updating too many devices + properties in an animation loop.

Expected

The value gets updated in the universe

Possible solution

• Create a component that can "flush" all properties into the universe

When I attach a MIDI controller via USB, the input connected is fired twice.

When I refresh the page with the MIDI controller already attached, the input connected is fired once as expected.

Component: midi-controller

For example the position and rotation for Moving Head should have an initial value.

Maybe having a default scene is already enough? Not sure yet.