LMMS / LMMS/lmms

Instrument Plugins Redesign

Open
#3,534 43 comments 7 reactions 0 assignees View on GitHub
enhancement gui meta
Dominant language
C++
Stars
10.4k
Forks
1.3k
Avg merge
2d 13h
Merged PRs (30d)
7

Description

We are going to be enhancing the instrument designs. I'm looking for a balance between an exciting ui (letting each plugin have its own unique style to represent and visually distinguish its sound) and good ux (maintaining some consistency so that the user does not become surprised/confused and understands that these plugins have relation to LMMS.

Bellow, I have listed all of the elements and design standards that will be need to be followed by the people contributing designs. If someone would like to contribute a design for one of the plugins, please inform me in the comments bellow so that two people do not accidentally redesign the same plugin.

**FONTS**
When working on the logos, you can pick the font of your choice as long as the font has proper licensing. Some safe places to find fonts are google.com/fonts and fontsquirrel.com. The fonts that we are currently using for LMMS include Orbitron in ALL CAPS, Titilliumm, Cabin and Open Sans. For best results when working with text, export your final SVG as a Cairo .png (I prefer to use the Save A Copy function here).

If the Cairo .png leaves some of the elements looking a bit too crisp, you can always export the text with Cairo and the background with Inkscape. Use the "Color to Alpha" option in GIMP to cut out the bg and then place it on the background. This is only necessary if you are creating a more complex graphic.

**BACKGROUND**
We want the background to have enough contrast, especially with the knobs.

**GRADIENTS**
Please note that your eyes follow the direction that a gradient is facing. For example, the gradient that I used in the LFO controller was linear so that your eyes would be drawn from the title down to the content of the plugin. If the gradient pointing at an odd angle, the plugin will be a bit less intuitive for the user. Gradients should be subtle when possible. This is not exactly a rule, but because many prefer flat design and many others don't I try to keep it somewhere in between.

**KNOBS**
Let's keep the design of the knobs the same throughout the instruments with the exception of choosing any of the colors in our palette.

**COLORS**
Unlike the effects plugins, which almost exclusively used the green, you can use any of the colors in this palette on the instrument designs.
![colors](https://cloud.githubusercontent.com/assets/7960169/25774982/36fcbd0e-324f-11e7-8c04-694a841c97af.png)

Please reference my source files in the [artwork repo](https://github.com/LMMS/artwork) for access to backgrounds, buttons, and icons that you can reuse.

Note: you can replace @mentions with PR # once ready.

- [ ] AudioFileProcessor
- [ ] BitInvader
- [ ] FreeBoy
- [ ] GIG Player
- [ ] Kicker
- [ ] LB302 (@Umcaruje)
- [ ] Mallets
- [ ] Monstro (@Texxiliator)
- [ ] Nescaline
- [ ] OpulenZ
- [ ] Organic (@IvanMaldonado)
- [ ] PatMan
- [ ] Sf2 Player (@Mark-Agent003)
- [ ] sfxr
- [ ] SID
- [ ] TripleOscilator (@LocoMatt)
- [ ] VesSTige
- [ ] Vibed
- [ ] Watsyn
- [ ] ZynAddSubFX
- [ ] Carla Rack
- [ ] Carla Patchbay
- [ ] Xpressive (when completed)

![shot-2017-05-06_11-22-38](https://cloud.githubusercontent.com/assets/7960169/25774938/216f8d8c-324e-11e7-8e3e-d878cf894cbc.png)

@Umcaruje @Mark-Agent003 @BaraMGB

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the referenced source files in the LMMS artwork repository and the listed instrument plugins. Check the comments to see which designs are already claimed or associated with pull requests, then choose a single unclaimed plugin and align its design with the stated font, background, gradient, knob, and color guidance. Done means a completed plugin design is submitted for review and the checklist is updated.

Written by the indexing model from the issue text.

Assessment

Domain
design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.