Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] AHK is typing to fast causing half the letters not to show. #26

Open
VNRARA opened this issue Oct 18, 2022 · 4 comments
Open

[Bug] AHK is typing to fast causing half the letters not to show. #26

VNRARA opened this issue Oct 18, 2022 · 4 comments
Labels
bug Something isn't working help wanted Extra attention is needed low priority low priority

Comments

@VNRARA
Copy link

VNRARA commented Oct 18, 2022

Describe the bug
A clear and concise description of what the bug is.

AHK typing speed is to high causing it to type to fast and missing letters and doing the " wrong.
PMC (also based on AHK does the same thing). An option type speed should be set in the program.

To Reproduce
Steps to reproduce the behavior:

Follow normal steps.

Expected behavior
AHK to type normal.

@VNRARA VNRARA added the bug Something isn't working label Oct 18, 2022
@enoversum
Copy link

Can verify this. When projects get more complex, LES often not picks the item I selected, but re-inserts the last plugin or preset I had used. You can watch it type and select the wrong plugin in the browser.

@Inversil
Copy link
Member

someone else messaged me about this on twitter the other day and unfortunately there isn't really a good way to fix this, as ableton's terrible UI lag is at fault here. I've been bugging them about their poor UI performance for years..

The only way to fix it is to increase the amount of time the program waits before attempting to add the device, which is currently hardcoded... but even then; it would be a tradeoff and it would make the menu more unresponsive also when it doesnt need to be.

It would be possible to add extra waiting times on search queries; but these waits would always happen. I considered maybe adding a toggle in the submenu so you can switch between a "fast" and a "slow" mode- but this is a terrible solution for a more systematic problem with ableton itself.

@Inversil Inversil added help wanted Extra attention is needed low priority low priority labels Apr 23, 2023
@enoversum
Copy link

someone else messaged me about this on twitter the other day and unfortunately there isn't really a good way to fix this, as ableton's terrible UI lag is at fault here. I've been bugging them about their poor UI performance for years..

The only way to fix it is to increase the amount of time the program waits before attempting to add the device, which is currently hardcoded... but even then; it would be a tradeoff and it would make the menu more unresponsive also when it doesnt need to be.

It would be possible to add extra waiting times on search queries; but these waits would always happen. I considered maybe adding a toggle in the submenu so you can switch between a "fast" and a "slow" mode- but this is a terrible solution for a more systematic problem with ableton itself.

In the latest 11.3 beta of Live they state they have solved this long-term UI lag problem. I haven't really had the chance to check it out, as they have introduced a severe bug with pitch modulation on audio clips that prevent me from actively using the Beta. Once they got this nasty little insect ironed out, I'll try to replicate the sluggishness that comes with heavier projects in order to evoke this lag-and-won't-find-search-terms behaviour and report back here.

On another note, Elisabeth Homeland's VisualBrowser, which is an alternative, obviously pure visual attempt at having a self-built library menu, allows for changing the delay/speed of a search query. Since I'm very much used to LES, I haven't checked it out actively, but a configurable delay or waiting time would be a very valuable addition to LES.

@VNRARA
Copy link
Author

VNRARA commented Apr 23, 2023

someone else messaged me about this on twitter the other day and unfortunately there isn't really a good way to fix this, as ableton's terrible UI lag is at fault here. I've been bugging them about their poor UI performance for years..

The only way to fix it is to increase the amount of time the program waits before attempting to add the device, which is currently hardcoded... but even then; it would be a tradeoff and it would make the menu more unresponsive also when it doesnt need to be.

It would be possible to add extra waiting times on search queries; but these waits would always happen. I considered maybe adding a toggle in the submenu so you can switch between a "fast" and a "slow" mode- but this is a terrible solution for a more systematic problem with ableton itself.

Windows by itself has a similar problem with other programs written with AHK itself. This had been mentioned on AHK forums. One solution is to use the paste command after ctrl-f instead of key input.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed low priority low priority
Projects
None yet
Development

No branches or pull requests

3 participants