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

Processing on dGPU even disabled it on settings #521

Open
rafa9101 opened this issue Dec 27, 2024 · 3 comments
Open

Processing on dGPU even disabled it on settings #521

rafa9101 opened this issue Dec 27, 2024 · 3 comments
Assignees
Labels
Investigation required Needs to be investigated by the assignee

Comments

@rafa9101
Copy link

rafa9101 commented Dec 27, 2024

Environment:

Operating System: CachyOS
Desktop Environment: KDE Plasma 6.2.4
Kernel Version: Linux 6.12.6-2-cachyos
Graphics Platform: Wayland
Processors: 12th Gen Intel(R) Core(TM) i5-12500H (16) @ 4.50 GHz
Memory: 32GiB RAM
Graphics:
Intel Iris Xe Graphics @ 1.30 GHz [Integrated]
NVIDIA GeForce RTX 4060 Max-Q / Mobile [Discrete]

tidal-hifi Version: 5.17.0 (AUR)

Issue Description:
Opening Tidal-HiFi having disabled GPU processing toggle on the app settings, I can see a process of Tidal running as gpu-process, using the dGPU even on battery, this keeps the dGPU powered on until I close Tidal and draining battery unnecesary.

Captura de pantalla_20241227_090031

Captura de pantalla_20241227_090721

@Mastermindzh
Copy link
Owner

Hey,

I'd have to dive into this.
Our app doesn't control the type= flag but it shouldn't be passing the --enable-gpu-rasterization flag.

Did you modify the AUR instance in any way?
What is logged when you start tidal from the CLI? (you should not see logs like these: enabling command line option ${flag} for the values you haven't enabled in settings.

@Mastermindzh Mastermindzh self-assigned this Jan 20, 2025
@Mastermindzh Mastermindzh added the Investigation required Needs to be investigated by the assignee label Jan 20, 2025
@rafa9101
Copy link
Author

rafa9101 commented Feb 4, 2025

Hi!, sorry for delayed response, and not, didn't shows this logs

Image

Edit: and without modified script on install

@Mastermindzh
Copy link
Owner

Yeah, that confirms that it isn't the app itself that is setting those flags. Very weird.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Investigation required Needs to be investigated by the assignee
Projects
None yet
Development

No branches or pull requests

2 participants