Andre Weissflog

PS: the log function in sokol_log.h looks so weird because I want to avoid pulling in a large `printf()` function. In Zig this probably isn't an issue and we could...

Ok, very quick proof-of-concept in the clear.zig example: ```zig export fn log(tag: [*c]const u8, log_level: u32, log_item: u32, msg: [*c]const u8, line_nr: u32, filename: [*c]const u8, ud: ?*anyopaque) void {...

...a real logger function should format the message closer to the original, at least include the tag, log level and error id: ``` [sg][error][id:335] VALIDATE_BEGINPASS_SWAPCHAIN_EXPECT_WIDTH: sg_begin_pass: expected pass.swapchain.width > 0...

Reminder to self: also test WASM (does the Zig callstack dumper actually work there? could always conditionally just call the sokol_log.h C function from within the Zig override when target...

Btw very related, this stale PR from a time before the runtime logging hook existed :) https://github.com/floooh/sokol-zig/pull/33

Hmm, interesting. I guess SoLoud will have the same problem then. That's were the sokol_audio.h backend code is taken from. It works on my Asus Zenbook laptop with Ubuntu (currently...

Ok I committed a fix, it's quite different from your code though: https://github.com/floooh/sokol/commit/8611fae87cb48cdce9efbf866fbee1ff7b624c39 ...but it's hard to test without being able to reproduce the original problem. I think the order...

Man that's weird.. Is this one of the sokol-samples or your own code? What's the initial value for buffer_frames? The sokol-samples use the default buffer size of 2048 frames, it...

1881 isn't even a multiple of 32, 64 or 96... (96 frames seems to be the minimal supported buffer size on my config).

Hmm... currently I have no clue what to do about this. If ALSA allocates such weird buffer sizes the entire code of pushing audio packets needs to be rewritten... why...