tinne26

Quick heads up: https://github.com/hajimehoshi/oto/pull/160 has finally derived into hajimehoshi re-adding configurable buffer sizes in Oto, in case you want to start experimenting with it. The performance and latency is extremely...

So, I've been digging even deeper. I don't know why I said that it's clear that this is not Ebitengine's fault; it may actually be, because GLFW actually behaves correctly,...

@gen2brain I made a couple tests, and the audio issues may not be *directly* related to Ebitengine. I used some code to capture the audio being served by mpg, then...

So, if I understand correctly, the issue is that when the callbacks are set, data should be consumed there. The fact that we are using *both* the audio reader directly...

I made a small package to make it easier to manage this on Ebitengine: https://github.com/tinne26/mpegg. Still a work in progress, but it works. The key idea is to let Ebitengine...

I'll open an issue on your mpeg repository instead if that's fine with you and we can debate it there. This issue is already resolved and both mpeg and Ebitengine...

Just got bitten by this. An improved error message mentioning that the configuration doesn't work with Windows OpenSSH instead of the vague "Agent protocol error", or a small label next...

Brief summary of the discussion we had on discord: - Tick-based state freezing should remain the main method to handle input even in ebitengine/v3. New async APIs should be opt-in,...

Gentle reminder: this is most likely what we discussed on October 28th (early update + FIFO blocking leading to async events taking a longer time to be applied than one...

Yes. I just set up a live usb and tested again, and it's still broken. The situation is basically that GLFW handles it properly and Ebitengine doesn't, because as you...