Anton Lazarev

Sadly I haven't been able to find any useful developer documentation on working with macOS hi-DPI scaling. I think last time I tried, the window was upscaled to 2x resolution...

Thanks for the report! I don't have access to Ableton myself so this is good to know. This is probably another issue with [`vst_window`](https://crates.io/crates/vst_window); I suppose Ableton does something different...

@alalalexexex or others, if you have a Mac it'd be interesting to see if `ampli-Fe` is also broken with Ableton there.

@detrimentalist after loading an instance of ampli-Fe, could you check your Bitwig's engine logs for any errors? Should be in `~/.BitwigStudio/log/engine.log` by default. I'm using Bitwig 4.1.0 in Arch without...

@detrimentalist yep, that's roughly what I expected to see. If one of the adapters works, but isn't automatically chosen by `instance.request_adapter(...)`, then it's an issue with `wgpu` or your installed...

@detrimentalist could you try building the [`update-wgpu` branch](https://github.com/antonok-edm/ampli-Fe/tree/update-wgpu)? That's using the latest published `wgpu` version. (I suppose others who were facing rendering issues are encouraged to try as well :smile:)...

The first one looks like an issue somewhere between `wgpu` and `vst_window`: ```rust pub fn new(handle: W) -> Self { let instance = wgpu::Instance::new(wgpu::BackendBit::PRIMARY); // Acquire the window as a...

I haven't actually done any checking of the generated assembly, so it's entirely possible I'm doing something wrong/inefficient here. I adapted the chunking logic from a synthesizer I've been working...

@fschutt It might be a good idea to open some issues with `good first issue` tags for newcomers. I think a lot of the Rust community is really interested in...

For what it's worth - [this](https://github.com/actix/examples/blob/master/http-proxy/src/main.rs) example seems to work great as a WebSocket proxy, as long as the timeout is increased (otherwise the server will bail with status `500`...