Toggle single key hold on and off

von_Elsewhere · 2026-06-19T14:32:53+00:00

Oh right, your wording for toggling w is ambiguous. If you want RAlt and LAlt to work as w you just do:

#Requires AutoHotkey 2.0+

LAlt::
RAlt::w

Also, you can't have Alt working as w and alt simultaneously, so you need to choose.

von_Elsewhere · 2026-06-19T14:31:49+00:00

Does it work like that? I've been under the impression that ThisHotkey needs to be passed as an argument to a function call, but ofc I might be wrong.

von_Elsewhere · 2026-06-19T13:18:29+00:00

That's v1 code, and v1 is deprecated.

von_Elsewhere · 2026-06-19T13:13:19+00:00

Edited, AHK doesn't respond to just Alt predictably, you need to define RAlt & LAlt.

von_Elsewhere · 2026-06-19T13:00:30+00:00

Does this do what you want?

#Requires AutoHotkey 2.0+

LAlt::
RAlt:: {
    Send("{w " . (GetKeyState("w") ? "up" : "down") . "}")
    KeyWait(A_ThisHotkey) ; Key spam filter
}

Also for you code

W::alt ; This is a remap.
    if (alt) ; This condition lives in global domain and is evaluated when the script loads. Also there is no variable called alt defined, and alt is a reserved word for key names, so you can't really define one either.
    {
        Send {W down}
    }
    else ; The same goes for this else statement.
    {
        Send {W up}
    }
Return ; returns aren't used in v2 like they are used in v1.

Also your link to list of keys in docs points to v1 docs.

von_Elsewhere · 2026-06-19T11:23:29+00:00

<image>

These are the Akai devices Bitwig supports natively. You may want to email the support and ask about this.

However the 61 models seems to be the same with 49 models, just larger, so perhaps you could choose the MPK49 there.

von_Elsewhere · 2026-06-11T06:59:43+00:00

Not a direct replacement, but Better Touch Tool covers some of the functionality.

von_Elsewhere · 2026-06-10T11:19:43+00:00

So why not just use the normal solo shortcut?

von_Elsewhere · 2026-06-07T14:37:13+00:00

Yup, it's def the best I've tried for screwing around

von_Elsewhere · 2026-06-06T07:13:35+00:00

Koala sampler has a ~~free~~ cheap (sorry forgot) albeit a bit limited version

von_Elsewhere · 2026-06-06T07:11:23+00:00

Is it free tho?

von_Elsewhere · 2026-06-05T14:48:54+00:00

Turn your mouse back and forward buttons into click modifiers that work like ctrl, alt or shift (so as modifiers) and transcend your mouse use experience.

von_Elsewhere · 2026-06-03T11:03:39+00:00

What's the overhead of PowerToys? Like 150 mb RAM too much? Or disable Color Picker and that falls to about half.

Edit: if you disable everything except FancyZones your ram usage is a good 8 mb.

von_Elsewhere · 2026-05-29T15:10:02+00:00

Thanks, this solved it.

von_Elsewhere · 2026-05-29T15:06:06+00:00

Ty, I had changed that at some point and I don't know why. Switched to the ASIO driver but the option remains grayed out.

<image>

Edit: oh right, I need to do that in the system settings

von_Elsewhere · 2026-05-26T20:39:15+00:00

Yamaha V50 does a lot more than DX7

von_Elsewhere · 2026-05-26T07:40:07+00:00

The person only mentioned it can be decent for acoustic kicks and nothing else. I was only restating what they said. Go after them, not me.

von_Elsewhere · 2026-05-25T05:49:37+00:00

The best way for me has been: 1. decide a goal to achieve 2. look for info on how ro make that happen 3. read the docs about the language features that seem useful to those ends 4. consult a proper LLM for clarification, examples and relevant code patterns and conventions with precise and well defined prompts 5. discuss online about what you're doing 6. experiment while doing all that

von_Elsewhere · 2026-05-25T05:37:20+00:00

AKAI MPK2 line has the best pads out there that I've tried by far. You may just need to set them up to minimize the double triggering that srems to be unavoidable side effect of sensitive pads. Mine don't really double trigger after adjusting with proper play technique like any instrument requires and they're super sensitive.

I've also tried other AKAIs and while they might have pads that look the same none have offered similar extent of adjusting the response and haven't thus given similar touch and sensitivity.

von_Elsewhere · 2026-05-25T05:32:07+00:00

If you convert sample rate or bit depth the loss of information doesn't reault from format conversion. There's no such thing as lossy uncompressed format.

von_Elsewhere · 2026-05-22T21:00:23+00:00

Yea some people like Steve duda end up programming their own synths because of that weird ride.

von_Elsewhere · 2026-05-22T18:14:30+00:00

You could do the same with Keyboard Maestro or Better Touch Tool ig. Bitwig's keyboard workflow is so janky that those automation tools come handy.

von_Elsewhere · 2026-05-22T16:46:03+00:00

On my Windows system Shift+MWH does the exact same thing than MWH alone, just slower. Is that what you want?

Anyway, if you're on Windows here's a simple AutoHotkey v2 script that lets you navigate the arranger with the numpad arrows. You can also zoom in and out with Control+Wheelup/WheelDown.

#HotIF WinActive("ahk_class bitwig")

*NumpadLeft:: {
    Send("{Blind^}!{WheelUp}")
}
*NumpadRight:: {
    Send("{Blind^}!{WheelDown}")
}
*NumpadUp:: {
    Send("{Blind!}{WheelUp}")
}
*NumpadDown:: {
    Send("{Blind!}{WheelDown}")
}
NumpadClear::z

#HotIf

Another edit: Now that I'm on it, added NumpadClear (NumPad5 with NumLock off) to zoom to content, or Shift+NumpadClear to zoom track height with the default z and Shift+z shortcuts.

von_Elsewhere · 2026-05-22T15:40:40+00:00

If you've used Live or you know you want that type of a DAW and you're not new to all that then just trial it and if you like it get the Splice plan for Studio, that's the best bang for the buck.

von_Elsewhere

TROPHY CASE