Dimitris Zervas

What is needed to move this forward? Just the tests?

The drivers have a "standby" pin that has to be pulled low early in order to function. Check it out on your firmware (klipper/marlin) for the required configuration.

Check this: https://github.com/Klipper3d/klipper/issues/3549#issuecomment-739323618 The ticket more or less explains what's happening and how you can solve it

Oh, I see that `libmage.so` uses external libraries: `readelf -d libmage.so` ``` Dynamic section at offset 0x74538 contains 30 entries: Tag Type Name/Value 0x0000000000000001 (NEEDED) Shared library: [libdl.so.2] 0x0000000000000001 (NEEDED)...

The binary is C. The libmage.so is Rust. `parse(...).write(...)` works as expected. The first problem that I had was that I was exporting functions that were called by Rust underneath...

I've created a POC on the above linked repo, take a look. Shouldn't be too hard to use my example for another MCU

@HKalbasi You can contribute by creating Rust bindings for all of the C++ code. Maybe https://cxx.rs can help. There's a blog post of what I've done (more or less): https://whynot.fail/coding/rusty-arduino-bindings/...

I tried moving to DXVK but the main window does not render. I can see the tools and select buttons but the main viewer shows nothing

@hasmar04 DX9 has the same problem for me... I tried installing amdvlk and prepending `AMD_VULKAN_ICD=AMDVLK` but same results. Maybe it needs DXVK needs some specific configuration?

Damn my video is HEVC (H.265 encoded) MP4! And that brings me to the next question: Is there support for MP4/MKV/AVI H264/H265/etc.?