jansenmtan

Results 8 comments of jansenmtan

1920x1080@60 for 180 seconds HEAD: 2d920dc04c3cb83689dc9b3e75f931b3e0835753 Linux 5.15.11-zen1-1-zen #1 ZEN SMP PREEMPT Wed, 22 Dec 2021 09:23:53 +0000 x86_64 GNU/Linux 8 Intel(R) Core(TM) i3-10100F CPU @ 3.60GHz python 3.10.1 (main,...

Issue is still open as of 2022.902.1-lazer. Varying audio offset between 0 ms, -40 ms, and -80 ms still yields average judgement offsets of ~30 ms late for each. ![osu_2022-09-02_09-35-44](https://user-images.githubusercontent.com/36340429/188174942-f780f3af-c067-4ed6-8ffe-e1d3e808b8d2.jpg)...

Get the execstack package and put these into the terminal: `execstack -c /usr/lib/arm-linux-gnueabihf/libx264.so.142` `execstack -c /usr/lib/arm-linux-gnueabihf/x264-10bit/libx264.so.142` Audacity will run, but still has issues.

The problem is not global offset or local offset. For example, every play below the green line is on time. Not a single one of them are more than 4...

I just found out that the bug can also revert in the same session, going back to the same timing as when the game launched. eg, today, when the bug...

I've managed to reproduce this bug. https://youtu.be/bOQZbVMUpSI As I suspected, it has to do with the editor, the editor waveform, and zooming into the editor waveform. The bug, when activated,...

> I'm not sure how you are discerning that it's related to the waveform, but I don't think it can be. It's 100% more likely to be seek operations or...

#19974 did not address the issue affecting the editor offsets. When changing the audio offset, both the beatmap timing offset (ie, local offset) and the audio offset are affected, effectively...