Yousician 5.34 working in Bottles with Google login and low-latency audio

[SFaguiar]

I want to share a reproducible Bottles configuration that made the current Windows version of Yousician work on Linux.

Disclaimer: this is a community workaround and not an official Bottles or Yousician support path. Apply it on a backed-up bottle and treat every test as at your own risk.

Validated environment:

• Bottles Flatpak 64.1
• Debian 13.6, KDE Wayland/XWayland
• Yousician 5.34.0
• custom runner: Kron4ek Wine-Proton 11.0-1
• DXVK 3.0.1
• PipeWire 1.4.2
• Intel UHD 620 and a FIFINE USB microphone

Working features include Google authentication through the host browser, post-login loading, fully rendered menus, microphone input, audio output and normal navigation.

The final bottle uses:

Arch: win64
Environment: Application
Windows: win10
Runner: wine-proton-11.0-1-amd64
DXVK: dxvk-3.0.1
Limit_System_Environment: true
Environment_Variables:
    WINEDLLOVERRIDES: d3d11=n,b;dxgi=n,b
Inherited_Environment_Variables:
- DXVK_CONFIG_FILE
Parameters:
    dxvk: true
    vkd3d: false

The DXVK configuration is:

dxgi.maxFrameRate = 60

The most important Bottles-specific finding was process tracking. Yousician Launcher.exe exits after starting the real app. In this Flatpak flow, bottles-cli then considered the tracked program finished and closed the execution environment containing Yousician.

The reliable solution was to keep the launcher for installation/updates but register the real executable as a second Bottles program:

flatpak run --command=bottles-cli com.usebottles.bottles add \
  -b Yousician \
  -n YousicianApp \
  -p '/path/to/Yousician Launcher/Yousician/Yousician.exe' \
  -l '--api https://api.yousician.com --sock https://sock-prod.yousician.com --web https://account.yousician.com'

The final desktop launch passes the DXVK config explicitly:

flatpak run \
  --env=DXVK_CONFIG_FILE=/path/to/bottle/dxvk.conf \
  --command=bottles-cli com.usebottles.bottles \
  run -b Yousician -p YousicianApp

For audio, Windows 10 Audio with a 480-frame buffer at 48 kHz worked reliably. The 240-frame automatic setting produced repeated ALSA/PipeWire underruns on the tested laptop.

System Wine and Soda each solved only part of the problem. Wine-Proton 11.0-1 was the first tested runner to provide both the working Unity rendering path and working WASAPI audio.

Full guide with runner checksum, installation steps, logs and failed approaches:

https://gist.github.com/SFaguiar/4628ce08cc891399e8f99fd471cf18bb

The troubleshooting and working configuration were performed for me by GPT-5.6-sol xhigh. I tested the resulting setup and confirmed that Yousician is working properly on my machine.

This is a compatibility report, not a Bottles bug report. If other users can reproduce it on clean bottles, it may be a useful candidate for a maintained community installer or recipe.