aroffringa / glight Goto Github PK
View Code? Open in Web Editor NEWDMX controller software for live control of stage lighting
License: GNU General Public License v3.0
DMX controller software for live control of stage lighting
License: GNU General Public License v3.0
Currently there's only a 'new faders window' button in the menu. The menu should include a submenu with a list of fader windows.
Dry mode currently crashes because of the folder changes.
For most controls, a larger fading slider is not necessary, and only an "on / off" check box should be enough (in combination with fading).
The number of presets reaches unmaintainable counts quite easily. Having maps/groups/directory-like structures to cluster them is necessary.
Part of #37 . To store in class structure & savefile.
Organising objects is a bit hard right now, as you can't move them around after creating -- but you often don't know how to organise when creating. #27 should be merged first.
When setting 20+ lights, it can be handy to be able to take one light as prototype and copy that colour/pulse/... setting to a number of other selectable lights.
The "sequence" object is now just an intermediate step with not much value -- one would barely ever a sequence object in a second chase for example.
Now that dependencies are much less of an issue, it should also be possible to change sequences after they are constructed. It would be easier to create an empty chase, and add the items one by one after that.
This should take into account that time sequences are going to be added as well ( #54 ).
The bottom frame is too large, and chases should be allowed to be renamed.
When opening a saved configuration, currently all sliders are unset.
It would be useful to give the setup of sliders a name and be able to recall a given setup. These can then be included in the save files.
BeatFinder is currently unconditionally created in management class.
Add a button 'Set' to the configuration window and when pressed, open a window where the user can type in a new DMX start address.
This would set all lights to different colours, and rotate those colours to the right, left or randomly.
An effect that takes four values as input: a master channel and three colour channels, and that outputs the three colours scaled with the master channel.
This makes it possible to have a moving chase that is changeable in colour.
Currently all fixtures are shown as circles from left to right. It would be useful to be able to drag them around to more closely represent the room and setup.
This would be an interesting to effect, possibly also implementing more complex light curves.
This would change the type without removing dependencies
When pressing 'assign' in the controlwindow, only unassigned presets should be assigned.
Make it easy to program a few default chases, e.g.:
Fader labels can change place between even and odd fader numbers, such that they can extend a bit below faders.
These would be similar to chases, but (optionally) only play their sequences once when started, and allows setting the time per sequence item.
Should buffer the input signal, and output the input signal after some selected duration.
Current control widgets directly set values according to their sliders. A 'fade time' slider should be added to the control window. The control widget should keep track of fading and set the value during every update-interval. Later, sliders could be reworked to give visual feedback of current 'true' level.
The tree gets quite busy: I think it is better to have a folder selection button which selects an 'current' directory, and a list shows items in that direction. It also makes more sense that operations then are performed in that directory.
Implement a way to program the lights (preset, chases, ...) while continuing to run the lights uninterrupted.
This is already possible with chases, but it could make designing strobes or 'warning' flashing lights easier.
It could also implement a one-time pulse/flash action without repeating the action.
Old name is kept, only updated after chosing a different fader.
Object lists should optionally have an extra column with the type. Can be a letter at first, an icon later would be nicer, along with an icon giving the average colour of the object.
The current chase creation scheme won't work for #75. A solution would be to have a 'create chase' button, and when pressed open a modal window in which the user sees a standard object list and an add button to create the chase.
Current buttons take too much space. Some of them can be hidden in menu's, e.g. the fade in and out speed, which will also allow further options for the fade window.
Includes a white channel
Part of #37 .
Currently they are always stored in the root.
List all 'objects' in one list and when one selected, show a type-specific frame (dockable? window?) that allows changing that object.
Button is there but doesn't do anything.
Effect that flashes ~two times with random timing, is on for 20% power for half a sec before fully turning on.
When an object instead of a folder is selected, new objects can currently not be created. However, it would be easier to be able to make multiple objects in a row if the new objects would be placed in the parent folder of the selected row.
Not sure if this would be useful, but could have applications.
Should also check dependencies
In the configuration window, dmx channels are sorted by value. When they wrap around 512, that's confusing. E.g.: a fixture might use channels "0, 1, 512". Better would be "512, 0, 1".
Ticket #23 added a fade effect. Some more advanced fading can be interesting, e.g. curves.
Default chases are directly applied to fixtures. Selecting any controller is a bit more complicated, e.g. to determine colour and from multiple directories, etc. To determine colour might take some slight internal restructuring.
Currently, only effects are calculated through for dependencies. However, a chase can include an effect that again controls a chase, hence an effect-only dependency trace in which control to calculate first is not correct.
Currently the fastest speed is somewhat arbitrary set, and when the dmx device updates slower it can cause skips. For slower fades or chases this is not visible, but for a strobe effect it would be nice to be able to set the trigger time to the update speed.
An effect has itself controllable functions and can control other functions. Ideas for effects are fading, delay, invert, threshold, audio input, pulse/strobe.
The 'delete' button in the chases window is currently not working.
Like the dry mode, it would be useful to disconnect a single faders window and show a copy of the current state in the visualization window, until the window is reconnected. When reconnected, fading settings of that frame would also be applied.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.