Wine 11.0 arrives with a year of development work, more than six thousand changes, and broad improvements across graphics, WoW64 compatibility, gaming, and system performance. From Vulkan and Direct3D tweaks to new Wayland desktop features and better device support, this release marks a confident leap forward for Windows application support on Linux.

Wine fans have a reason to smile today. Wine 11.0 is finally here, and it is a big deal for anyone running Windows software on Linux. After a full year of work, more than six thousand code changes, and hundreds of bug fixes, Wine is moving forward in a way that feels like a turning point. This release tightens up major subsystems, improves performance, expands hardware support, and carries a big win for compatibility. If you have been waiting for Wine to feel smoother and a little less fussy, 11.0 might be the moment you jump back in.

  • Freakazoid@lemmy.ml
    8·
    3 days ago

    Anyone knows if vsts work in this version?

    My wine is currently being helt at version 9.21 due to some bugs in newer versions.

    • Malix@sopuli.xyz
      4·
      2 days ago

      While I don’t specifically know about version 11 (EDIT: now I do!), but I’ve been running windows daw + vst’s on wine 9-10.?? for ages. Using Renoise + bunch of different vst’s (mix of vst2 and vst3), all of them seem to work just fine. I did have to install dxvk to the wineprefix to get the ui of some plugins to work, but they do work fine(ish) with it.

      Now, the thing I have NOT tested is ilok drm. So far I’ve managed to do with plugins which don’t use it.

      I see wine 11 is already in my distro’s testing repos. Aggressive waiting starts.

      edit: for clarification, preset dropdown menu’s from one specific plugin vendor (solemntones) vst’s needs to be click/dragged the right way, otherwise they seem to not work. Bit annoying, but otherwise my plugins work.

      edit: seems to work just as well on wine 11. But sample size = me & my vst/vsti’s.

        • Malix@sopuli.xyz
          1·
          2 days ago

          I’ve set it to 16ms in renoise, not 100% how accurate that is but audio doesn’t crackle and jamming on vsti’s doesn’t seem to have noticeable input delay. I don’t have any actual instruments to test.

          • underscores@lemmy.zipEnglish
            1·
            1 day ago

            16ms would be too laggy to play actual instruments sadly, is it possible for you to set it to 4ms?

            • Malix@sopuli.xyz
              1·
              15 hours ago

              apparently renoise doesn’t allow values less than 5ms… which also seems to work just fine, huh.

              ASIO doesn’t seem to want to work, and it doesn’t do anything for me anyway, I’ve been more than kontent with the DirectSound (I have no idea what wine 9/10/11 does with it under the hood, plays fine through pipewire & my virtual devices) - and renoise isn’t really a traditional daw anyway, it can record instruments for sure, but it’s more of a old-skool tracker with vst/vsti and daw-like automation.

              edit: “kontent”… my kde-isms peaking through. heh.

              edit2: ffwiw: when I last used renoise on this same machine on win10, I absolutely could not have set the latency below 20ms, even a single instrument of any kind would immediately crackle.

              • underscores@lemmy.zipEnglish
                1·
                15 hours ago

                I imagine some vsts do not play nice with low latency but I use low latency piano vsts (kontakt, Ravenscroft 275)

                In pipewire I had to use Jack to lower the latency as pulse and alsa were too laggy for playing instruments