Different offset adjustment needed for each beatmap.

[Hirxsawa]

Type

Game behaviour

Bug description

Experimental low latency audio mode is something that I needed on Windows, this was something that I loved on Linux but I never played that much on that OS because I had some issues with my NVIDIA GPU. So when it got added on Windows, I got used to it and something that I realized is adjusting universal offset is pointless because for some reason a lot of beatmaps need a different offset. Isn't a big issue for me because doing a couple attempts on some map is enough to set the correct offset, but it would be annoying trying to play a new map on a multiplayer lobby for example. I want to make clear that low latency works perfectly fine and this issue isn't related to my hardware or OS and maybe the issue is on the mapping side (Now I'm playing on Linux and is the same problem).

Screenshots or videos

Using these env vars for less audio latency (I have some weird noises when opening the game for a couple seconds, after that all fine)
PIPEWIRE_LATENCY=64/44100 PIPEWIRE_ALSA='{ alsa.format=S32_LE alsa.channels=2 alsa.buffer-bytes=512 alsa.period-bytes=256 }'

My universal offset is based on these two maps: 3226413 3281757
The universal offset on windows was a negative number. (I think because of Linux reaching a lower latency audio) I don't remember the exact number but all the offset settings where correct on both OS.

These are some beatmaps with different offset adjustment

4575997

5440133

5573789

2671055

3819588

OS: Arch Linux x86_64
Kernel: Linux 6.19.9-zen1-1-zen
Packages: 774 (pacman), 8 (flatpak)
Shell: bash 5.3.9
Display (LF22T35): 1920x1080 in 22", 75 Hz [External]
DE: Cinnamon 6.6.7
WM: Muffin (X11)
WM Theme: cinnamon (Adwaita)
Theme: Adwaita-dark [GTK2/3/4]
Icons: Papirus-Dark [GTK2/3/4]
Font: Adwaita Sans (11pt) [GTK2/3/4]
Cursor: Bibata-Modern-Ice (24px)
Terminal: GNOME Terminal 3.58.1
Terminal Font: Adwaita Mono (11pt)
CPU: AMD Ryzen 3 3100 (8) @ 4.56 GHz
GPU: AMD Radeon RX 9060 XT [Discrete]
Memory: 5.25 GiB / 15.52 GiB (34%)
Swap: 947.83 MiB / 7.76 GiB (12%)
Disk (/): 24.86 GiB / 117.56 GiB (21%) - ext4
Disk (/mnt/568CD24D8CD226F1): 376.46 GiB / 447.13 GiB (84%) - fuseblk
Disk (/mnt/BC669D95669D514E): 292.76 GiB / 465.75 GiB (63%) - fuseblk
Disk (/mnt/usb-TOSHIBA_EXTERNAL_USB_20220804006591F-0:0-part2): 3.45 TiB / 3.64 TiB (95%) - fuseblk

This is my first time using github for this, sorry if I made something wrong. And sorry if my english isn't that good.

Version

2026.305.0-lazer

Logs

compressed-logs.zip

[Hirxsawa]

Am I the only player noticing this? I think this is something important, if something else is needed let me know please.

[Gooeys1]

#35269 wrong thing whoops

[Hirxsawa]

What do u mean with this? That offset setting is per beatmap, the universal offset is different.

[Gooeys1]

Whoops, I forgot that that issue was for the other settings, you can ignore this

[sineplusx]

I also have the same issue with my low-latency setup on linux. Universal offset is -18ms but I need further adjustment for some maps.

I think this is normal, because the maps were timed on stable with the default Windows audio latency "baked in". This obviously leads to a wrong offset when played back on a device with less audio latency. This sucks especially in multiplayer and ranked play, where you can't play maps in advance to get a correct offset.

[Hirxsawa]

Thanks for replying, I started to think that I was crazy and I was the only one with this issue.