Skip to content

[Windows] VST using imgui-rs and baseview changes Ableton scaling and doesn't get the right window when Windows scaling isn't set to 100% #107

Closed

Description

@Fredemus

Hello, I've talked about this issue on the discord before but I thought I'd raise a proper issue with my findings.
For some reason, when the Windows scaling isn't 100% (under setttings -> display -> make everything bigger), my baseview/imgui-rs VST changes the scaling in Ableton and is served a too small window.

In FL Studio, the window is also too small but at least the scaling doesn't change. Fl Studio doesn't seem to ever scale up VSTs.

A VST that causes the issue can be found here: https://github.com/Fredemus/svf_filter

Before adding the vst, windows scaling set to 125%
before adding baseview vst
After adding the vst, windows scaling set to 125%. Note that Serum and the channels in Ableton got smaller.
after adding baseview vst

Interestingly, after adding the VST, then changing scaling to 100%, then back to 125% seems to solve the issue.

Edit: Forgot to mention, this problem didn't exist before this commit: ae2f28c

Activity

  1. y-fujii commented on Oct 8, 2023

    @y-fujii

    This problem also occurs on Cubase 10.5 / Windows 11.
    It was confirmed with nih-plug/gain_gui_egui, which uses baseview.

  2. prokopyl commented on Mar 25, 2024

    @prokopyl
    Member

    While working on #174 I found this very suspicious piece of code:

    baseview/src/win/window.rs

    Lines 707 to 709 in 998ced8

    SetProcessDpiAwarenessContext(
    winapi::shared::windef::DPI_AWARENESS_CONTEXT_PER_MONITOR_AWARE,
    );

    This is called on baseview window creation, but it changes the DPI awareness for the entire process, which might explain why other windows like Ableton and Serum's are affected.

  3. micahrj commented on Mar 25, 2024

    @micahrj
    Member

    I doubt that's the issue, since in the parented case that call is most likely just failing (source):

    You must call this API before you call any APIs that depend on the DPI awareness (including before creating any UI in your process). Once API awareness is set for an app, any future calls to this API will fail. This is true regardless of whether you set the DPI awareness in the manifest or by using this API.

    Though we definitely shouldn't be calling it in the parented case anyway.

  4. added a commit that references this issue on May 19, 2026
    459dc3d
  5. prokopyl commented on Jun 13, 2026

    @prokopyl
    Member

    Hi again! Sorry it took so long @Fredemus @y-fujii. Can you check if this issue is still present with #266 ? I believe that should fix this issue, and I can't reproduce it or other DPI-related issues on my system with that PR.

  6. prokopyl commented on Jun 15, 2026

    @prokopyl
    Member

    After some additional testing with #266 I can't reproduce this on my end anymore, so I'll be closing this.

    If any of you still experience the issue, please let me know in here and I'll reopen. 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions