Difference between revisions of "Newsoundslider"
Jump to navigation
Jump to search
Fcartegnie (talk | contribs) (Created page with '== new sound slider proposals == File:Newslider_010210.png * Pros ** Combines two modes * Cons ** Undefined behaviour between Normal sound state & boosted sound state ** B...') |
Fcartegnie (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | == new sound slider proposals == | + | == new sound slider proposals == |
| − | [[ | + | [[Image:Newslider 010210.png]] |
| − | * Pros | + | *Pros |
| − | ** Combines two modes | + | **Combines two modes |
| − | * Cons | + | *Cons |
| − | ** Undefined behaviour between Normal sound state & boosted sound state | + | **Undefined behaviour between Normal sound state & boosted sound state |
| − | ** Boost mode should be dBA values | + | **Boost mode should be dBA values |
| + | |||
| + | == new implementation == | ||
| + | |||
| + | Current implementation is using library variables & functions within widgets itself. | ||
| + | Sound values changes if in hardmix mode and depends on global defines & lib max values. | ||
| + | No real split between values and representation then. | ||
| + | |||
| + | New implementation requires and interface layer/adaptor between UI & library. (wraps C or use existing C++ wrappers) | ||
| + | Sound is 0-100%. UI doesn't have to care about library values. | ||
Revision as of 18:49, 8 February 2010
new sound slider proposals
- Pros
- Combines two modes
- Cons
- Undefined behaviour between Normal sound state & boosted sound state
- Boost mode should be dBA values
new implementation
Current implementation is using library variables & functions within widgets itself. Sound values changes if in hardmix mode and depends on global defines & lib max values. No real split between values and representation then.
New implementation requires and interface layer/adaptor between UI & library. (wraps C or use existing C++ wrappers) Sound is 0-100%. UI doesn't have to care about library values.
