Back to search
Top Contributors
60
commits
36
commits
29
commits
27
commits
21
commits
13
commits
6
commits
5
commits
4
commits
1
commits
Windows Application Volume Control via MIDI
Stars
169
Forks
26
Watchers
169
Open Issues
31
Overall repository health assessment
No package.json found
This might not be a Node.js project
60
commits
36
commits
29
commits
27
commits
21
commits
13
commits
6
commits
5
commits
4
commits
1
commits
Ran into race condition when upgrading my pc. Fixing it here in the simplest way.
9a2298dView on GitHubMerge pull request #91 from nathanojb/use-top-row-knobs-as-volume-limiters
023ee00View on GitHubSaving the SubFader position to the config. If we did _not_ save the SubFader position, moving a main fader after program restart would take the default value of a float i.e. 0 when doing the multiplication. This would cause a sudden mute until the relevant SubFader is moved. Note that the main Fader position is not saved. That only poses a problem if, after the program restart, the SubFader is moved _before_ the main Fader. Given that the intention of the SubFader is as a cap, and the main fader as the actual volume control this strikes me as a rare occurance and not worth coding for.
bfd2f17View on GitHubInclude postion of SubFader into the volume calulation by multiplying it's position with the main Faders position *pre-logarithm*. This causes the subFader to cap the maximum volume of it's parent Fader.
f2caf08View on GitHubAdd SubFader concept to Fader.cs, and update all existing constructor calls to comply with the new parameter requirements. 'SubFader' is what I am calling the Knob above the sliding faders on the NanoKontrol2, EasyControl etc. Unfortunately I only own the NanoKontrol2 so cannot configure the other FaderDef's correctly.
26584d2View on GitHub