41–50 of 57 posts
You can buy premade MIDI faders for about $25 [0], there's no way that the hardware aspect of this project is worth making over that. The software is the only real issue, at a quick glance, [1] appears to be relatively equivalent for generic MIDI fader support, perhaps with a few more bells and whistles available. [0] https://www.aliexpress.com/item/1005005589381790.html (a chinese clone of the korg nanoControl 2, th…
I need this for Mac!
Earlier quoted context omitted.
What happens when software is at 0%, your slider is at 100% and you want to raise the volume?
You must move your slider down, and then up. It becomes reasonably intuitive with a small amount of practice :)
Earlier quoted context omitted.
There are elegant ways for handling actuator/software mismatch for actuators with finite travel, like pots and faders. 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, inc…
What happens when software is at 0%, your slider is at 100% and you want to raise the volume?
Earlier quoted context omitted.
Audio software will typically allow you to configure a soft takeover, where you must move the fader or knob until it matches the software value, and only then does it take over, to eliminate these surprises. Rotary encoders are just not as good for controlling volume as faders.
Curious why rotary encoders aren't as good. I'm guessing because you cannot visually see the volume or the potential range based on the state of the interface? (E.g., How much is 1 tick of the rotary encoder? Who knows?) 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…
Earlier quoted context omitted.
Sounds like your hardware isn’t set right. The volume of your hardware device should be set so that it’s barely above comfortable listening volume when your device is at 100%, and then the device attenuation works from there. You probably have the hardware volume maxed out, which is also bad because it tends to run the amplifier all-out which will use much more power and generate more heat, as well as having lower dy…
I never have my hardware "maxed out". Usually barely 50%. But anyway, all of my Windows using friends have the same problem and find it equally ridiculous. Seems like whatever Windows does by default on our machines is just a not working so well default.
Unless the faders are motorized, which I believe are expensive, I don't see how you can make that thing work reliably without some nasty surprises. What happens if you change the levels through software and your faders do not move? I would just have used rotary encoders.
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.
What I really need is a software bass/treble control that can be mapped to keyboard shortcut.
newKeys conf@(XConfig {XMonad.modMask = modm}) = [
((modm .|. shiftMask, xK_m), spawn "easyeffects -l music"),
((modm .|. shiftMask, xK_v), spawn "easyeffects -l video")
]
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.
Earlier quoted context omitted.
I never have my hardware "maxed out". Usually barely 50%. But anyway, all of my Windows using friends have the same problem and find it equally ridiculous. Seems like whatever Windows does by default on our machines is just a not working so well default.
I've worked with hundreds and hundreds of users over a decade and this is not a thing, no idea what you're talking abut. Learn to set your gain properly on your external amplifier, it's a you problem, not Windows.
The fact, that this is a well known issue, that basically all my friends know about, having it right now, and in the past using various audio output devices themselves, tells me, that it is not a "me problem", but actually something that in general does not work so well in Windows. They have all accepted, that Windows volume mixer simply does this and that there is nothing that they can do. They are not regular GNU/Linux users like I am, so they are stuck with that.
Consider, that you might be in some kind of bubble, with your fortunate experiences. Consider, that maybe you did not understand the problem I am describing well. Since you are talking about "external amplifiers", makes me doubt, that you understand correctly what I am talking about. Note, that I have already stated, that I do not put volume externally to any maximum, like someone claimed earlier. So either you claim, that I am lying, or you do not understand what I wrote.
Perhaps you should rather ask questions about the issue and try to be helpful, instead of going on assuming and pretending the problem does not exist, when it very much does and you simply seem blissfully unaware of it.
I also find your tone quite in conflict with this site's rules. It is quite rude.
Unless the faders are motorized, which I believe are expensive, I don't see how you can make that thing work reliably without some nasty surprises. What happens if you change the levels through software and your faders do not move? I would just have used rotary encoders.
This is an ancient problem which has been around since synthesizers first got patch memory in the 1970s like the Prophet-5. 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 th…
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.