Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New GLSL waveforms are less detailed than legacy waveforms #12641

Open
fwcd opened this issue Jan 24, 2024 · 12 comments
Open

New GLSL waveforms are less detailed than legacy waveforms #12641

fwcd opened this issue Jan 24, 2024 · 12 comments

Comments

@fwcd
Copy link
Member

fwcd commented Jan 24, 2024

Bug Description

Moving #12448 (comment) to a new issue here. Comparing the current GLSL waveforms:

Screenshot 2024-01-24 at 18 04 29

to the legacy GLSL waveforms:

Screenshot 2024-01-24 at 18 04 38

...there is a fair bit of detail missing in the new GLSL waveforms, especially the bass-heavy parts display more structure.

Version

2.5-alpha-207-g7ab184441d (HEAD)

OS

macOS 14.3

@mxmilkiib
Copy link
Contributor

mxmilkiib commented Jan 25, 2024

Looks mono, not stereo

Edit: ah I see #11837

@fwcd
Copy link
Member Author

fwcd commented Feb 1, 2024

Here's another example of GLSL

Screenshot 2024-02-01 at 16 29 36

vs. GLSL (legacy)

Screenshot 2024-02-01 at 16 29 44

I've found myself switching back to the legacy waveforms for live use, the bass peaks are just much more recognizable.

@ronso0
Copy link
Member

ronso0 commented Feb 1, 2024

Related #11833 (comment)

How shall we proceed here?
Regardless the huge performance improvement, is this a regression? Is it severe enough to be fixed before the release?

@daschuer
Copy link
Member

daschuer commented Feb 1, 2024

Since the legacy waformsvate still there, this should not block the release.

@mxmilkiib
Copy link
Contributor

mxmilkiib commented Feb 1, 2024

Are these top examples still with the curve that makes it look clipped when it's not? That's the only reason I can imagine it looks that inflated. It's like it lost a battle in the normalisation wars. Or is that new example current 2.5-alpha?

Re colour, in the other issue, the fact that green never appears to be used is buggy to me.

A skin with only waveforms n library would be good for comparisons.

@fwcd
Copy link
Member Author

fwcd commented Feb 1, 2024

Both screenshots were taken with the (then) most recent 2.5/main builds

@mxmilkiib
Copy link
Contributor

mxmilkiib commented Feb 1, 2024

I don't get it then, it literally looks clipped. That boost curve was removed, iirc, yes? If so, why then does it look normalised in the first example and clipped in the second? Edit: there's also a lot of headroom also, so that's confusing me too, but that could just be the track(?).

@acolombier
Copy link
Contributor

acolombier commented May 8, 2024

It looks like this is impacting all waveforms with various degree of difference. Here is a video which might help to illustrate better these difference.

Kooha-2024-05-08-18-15-40-10MB.mp4

(Only the beginning is relevant, the rest is demo for PR #13220)

@ywwg
Copy link
Member

ywwg commented May 9, 2024

degree of difference

have you tested with the texture PR?

@acolombier
Copy link
Contributor

I haven't no, will try and merge the branch in mine and share a video when I can

@acolombier
Copy link
Contributor

Here is a comparison with RGB and Filtered and it looks even more different (except the color, which is fixed for filtered)

Kooha-2024-05-09-23-44-50.mp4

@ywwg
Copy link
Member

ywwg commented May 10, 2024

we really need to fix the gain issues with our waveforms, it makes direct comparison impossible. Either 2x everywhere or nowhere, not in some of them

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

No branches or pull requests

6 participants