Ryan C. Gordon
Ryan C. Gordon
(Putting this in 3.2.0, but we should do this to SDL2, also.)
This sounds more like a bug in SDL than a behavior we should document.
CC @slouken
Sending this over to the SDL issue tracker so someone can verify if this is still an issue. The original comment is in reference to SDL2.
This is probably the PipeWire emulation thing. I assume that fix hasn't made it back to SDL2 yet...?
This change needs a better log message than "initial commit," if you could change that. Run `git commit --amend` to edit the log, followed by a `git push -f` to...
Do you _actually_ get 44100Hz if you don't explicitly set that? It's a weird choice of defaults, and it's even weirder that explicitly asking for it gets you something different...
(Also of note, there's a generous amount of waffling between calling the other direction "output" and "playback" devices...)
I happened to have SDL laying around for some reason. :) But this is probably something that needs to be simplified or documented better.
Fwiw, SDL2 defaults to nearest for textures, too, but can be overridden with a hint: https://github.com/libsdl-org/SDL/blob/82cd3bfe1ccf83ade85847460d76b370b94ada53/src/render/SDL_render.c#L1229-L1232 So maybe we should default to nearest for the logical framebuffer, too? Both defaults...