LTT recently did a video about deej in their recent cheap gadgets video. https://youtu.be/8BxVi6YiicQ
[0] https://www.aliexpress.com/item/1005005589381790.html (a chinese clone of the korg nanoControl 2, the original korg aren't that great quality, but they work, the clones are 'just as good', or you can pay more for korg or another brand)
Well making it yourself would allow it to customize it to your needs. I though about creating something to hang below my monitor. That way it will not take any desk real-estate.
If you buy a chip with pins you don't even need to solder, just use female to female dupont.
Of course buying a midi controller is a valid option. I would just not say there is "no way" creating it yourself is not worth it.
It's a neat product, but a completely different market.
Worth mentioning about the NanoKontrol2, it is quite a beast to use well. To get control over the LEDs you need to send a variety of sysex midi messages. In general I found the midi control to be pretty daunting when trying to talk to mine. There was a lot more going on than I expected: https://cdn.korg.com/us/support/download/files/aeb2862daf0cb...
What happens if you change the levels through software and your faders do not move?
I would just have used rotary encoders.
Most schemes involve scaling the available fader travel to the "available" software travel.
Ex: Fader at 40%, software at 60%. Fader motion "up" between 40-100 moves software "up" between 60-100. Fader motion "down" between 40-0 moves software "down" between 60-0.
There are various other schemes, including multiple regimes and nonlinearity. Programmable synthesizers have dealt with this for many years. See pp13-14 of this manual for an example: https://www.davesmithinstruments.com/wp-content/uploads/2015...
[1]: https://www.adafruit.com/product/5466
[2]: https://eu.mouser.com/c/passive-components/potentiometers-tr...
Rotary encoders are just not as good for controlling volume as faders.
I've been thinking about using a rotary encoder for lights to deal with this problem specifically (light state being out of sync with a fader/pot). I figure I'll just have software figure out the new state based on the user interaction.
There are a number of ways to handle the knob or fader's physical position not matching the current value:
* As soon as the control is touched, it becomes "live" and the value jumps to wherever it is. This is the simplest, but most disruptive approach because a value can jump abruptly.
* When the control is moved, it has no effect on the value until it physically reaches where that value is. This avoids any disruptive jumps, but can be confusing because a control feels "dead" until you reach the right point to get it alive again.
* I think there are other approaches where moving the control starts interpolating the live value to where it is.
There's no perfect solution, but it's tractable and not a huge issue in practice. Motorized faders are nice but very expensive and have shorter life spans.
For knobs, you can more easily avoid it by using endless encoders instead of potentiometers and then interpret its current location as the current value. (For example, Elektron hardware and the Hydrasynth take this approach.) But you lose the nice tactile affordance of having the knob stop at either end of its extent.
And yes by rotary encoders I meant those that rotate indifinitely. And I miss my Elektron Model:Sample, too bad it lacked the sampling function otherwise I would have kept it.
But like the others said, Soft-takeover has been a thing for many many years.
I would use the pots, you still have software vs hardware problem, but don't need to fiddle with small sliders when you just want to change the volume a tiny bit.
Wouldn't your software changes are overwritten by the absolute values from the Deej? That wouldn't be a surprise.
I haven't dug through the code for the app, so I don't know if it monitors the levels in software and immediately corrects them with the hardware values, if it loops at a specific interval, or only triggers on significant hardware value change.
But if not monitored, I can't imagine it would be an insurmountable task to add.
But https://hackaday.com/ features sometimes nice DIY project, I often also see them popping up on youtube. But you might be able to find some if you search on 3D printing websites such as https://www.printables.com/
…hang on a minute, it already (kind of) exists: https://www.elgato.com/us/en/p/stream-deck-plus-black
newKeys conf@(XConfig {XMonad.modMask = modm}) = [
((modm .|. shiftMask, xK_m), spawn "easyeffects -l music"),
((modm .|. shiftMask, xK_v), spawn "easyeffects -l video")
]
In this (contrived) example you'd press SHIFT-L_ALT-m to enable the 'music' profile, SHIFT-L_ALT-v for the 'video' profile.You can also make a script which cycles through available plugins and bind that to a key, showing which plugin is activated when the key is pressed. There are many ways which lead to this version of Rome, choose the one you like best.
If you're using Gnome there is an extension which does most of the work:
https://github.com/wwmm/easyeffects/wiki/Preset-Selector-GNO...
(quote) It basicly adds a button to your top panel. Then you can click on it to see your available presets and click one to activate it without opening EasyEffects window. It also adds keyboard shortcuts to cycle through available input and output presets. Those can be set from extensions preferences window. Default keybindings are Ctrl + Super + o for output and Ctrl + Super + i for input presets.
A: Hey, somehow it is super loud when I use this to regulate volume. How come yours is set so high?
B: Ha, that's because you are regulating volume on Windows, where it maps 1 to 1 to the software volume mixer!
A: frustrated stare at their screen showing a Windows desktop
B: Having fun with volume regulation going wuuuuiii
I keep 50 "normal max" because sometimes I can be useful to be able to quickly go temporarily to 80-100 for really weak sources, without fiddling with the application or volume mixer.
That said, I have experienced what you mention when using an external headphone DAC/amp combo where there's been a mismatch between the output impedance of the DAC/amp and the headphones, and no option to adjust output impedance. But that's hardly Windows' fault.