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

Sound delay (first keystroke) #13

Open
TRaMeLL opened this issue Jun 21, 2020 · 10 comments
Open

Sound delay (first keystroke) #13

TRaMeLL opened this issue Jun 21, 2020 · 10 comments
Labels
bug Something isn't working !stale Prevent bot from marking as stale

Comments

@TRaMeLL
Copy link

TRaMeLL commented Jun 21, 2020

There is a delay in sound when you first press a key in a new application window.

Windows 10x64 \ Mechvibes 2.1.1

SysSpec1

@hainguyents13
Copy link
Owner

Does it delay when you first start Mechvibes or open any new app window?

@TRaMeLL
Copy link
Author

TRaMeLL commented Jun 24, 2020

Any new app window and after idle.
It's look like delay happens only when Mechvibes minimized to system tray.

@hainguyents13
Copy link
Owner

delay after idle is a known issue and it happens to all of the "keyboard events manager" apps
please understand

@TRaMeLL
Copy link
Author

TRaMeLL commented Jun 24, 2020

Yes, I understand, but maybe there is a way to prevent the delay. As I said, there is no delay if Mechvibes is not minimized to system tray.

@hainguyents13
Copy link
Owner

Thanks for the information, that's helpful. I'm working on that.

@botsblitz32
Copy link

Encountered this too, delay is more noticeable in Linux than in Windows

@hainguyents13
Copy link
Owner

I'm still working hard on that, and due to my lack of knowledge about javascript GB, it's harder than I thought.
If anyone has a solution, please let me know!

@ghost
Copy link

ghost commented Apr 10, 2021

It appears that the application is sleeping as it sees that it doesn't receive any keystrokes.
Once you start typing the loop starts running again.
This is my idea of what might be happening...

Or perhaps it could be related to the audio data being flushed in memory and needing
to reload?

Copy link

This issue has been automatically marked as stale because it has not had any activity in the last 60 days. It will be closed in 7 days if no further activity occurs. Please feel free to leave a comment if you believe the issue is still relevant.

@github-actions github-actions bot added the stale This issue is stale and will be closed soon label Apr 20, 2024
Copy link

This issue has been automatically closed due to inactivity.

@NotLazy NotLazy reopened this Apr 29, 2024
@NotLazy NotLazy removed the stale This issue is stale and will be closed soon label Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working !stale Prevent bot from marking as stale
Projects
None yet
Development

No branches or pull requests

4 participants