Mikewando
Mikewando
Feature Request: Expose GLFWwindow handle or otherwise allow means of registering certain callbacks
For example I want to handle drag & drop events in my app. This is easy to do with GLFW by calling `glfwSetDropCallback(handle, callback)`. But the window handle isn't currently...
Currently (as of R57) audio output for VFW always uses `WAVE_FORMAT_EXTENSIBLE`. As I understand it (which is not deeply) that supports arbitrary channels and perhaps other desirable things that `WAVE_FORMAT_EX`...
Moved `libplacebo` to a git submodule (on latest master) and updated the github actions workflow. I don't have strong opinions on the various bits of github action workflow, the changes...
`VideoNode.output()` is quite convenient for piping to e.g. an ffmpeg process spawned by python. But `AudioNode` has no equivalent function, and it would be cool if it did.
USMs can have multiple HCA tracks each with different sample rates (for example the lunar silver star remastered opening cutscene has japanese audio at 22.05KHz and english audio at 48KHz)....
Audio header padding is now correctly applied. Without the change taking an existing USM with VP9 + HCA and simply extracting and rebuilding would yield a USM that would throw...
The flowfps frame count calculation seems to have always been done with `- 1` before multiplying and `+ 1` after, but I don't understand what the rationale for this arithmetic...