Difference between revisions of "Newsoundslider"
Jump to navigation
Jump to search
Fcartegnie (talk | contribs) |
|||
| Line 18: | Line 18: | ||
New implementation requires and interface layer/adaptor between UI & library. (wraps C or use existing C++ wrappers) | 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. | Sound is 0-100%. UI doesn't have to care about library values. | ||
| + | |||
| + | [[Category:Dev Discussions]] | ||
Latest revision as of 14:41, 1 October 2013
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.
