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

Use a separate thread to update the display (#57) #58

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

drfiemost
Copy link
Member

No description provided.

@drfiemost drfiemost changed the title Draft: Use a separate thread to update the display (#57) Use a separate thread to update the display (#57) Oct 16, 2024
@drfiemost drfiemost marked this pull request as draft October 16, 2024 19:00
@drfiemost drfiemost linked an issue Oct 16, 2024 that may be closed by this pull request
@drfiemost drfiemost marked this pull request as ready for review October 20, 2024 18:39
@drfiemost drfiemost self-assigned this Oct 20, 2024
@ruby-R53
Copy link
Contributor

not sure if you're aware but it seems like the display doesn't get updated enough here, it gets quite noticeable with tunes that switch waveforms very fast like Jeroen Tel's Kinetix.sid at subtune 1

which's weird considering the display updates every 16 or 20 ms, to correspond to 60 and 50 Hz··· and lowering that refresh rate just makes the screen flicker more while still not updating the information properly

@drfiemost
Copy link
Member Author

Yeah, it seems like updates happen in bursts, have no clue why...

@drfiemost
Copy link
Member Author

Oh wait, the problem is that the audio writes are blocking so there is no update to the emulation while buffers are played back. So we are still limited by the buffer size. If you try with -w you can see the display is very quick.

@ruby-R53
Copy link
Contributor

yeah that's what i was guessing x)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use a separate thread to update the display
2 participants