View Issue Details

IDProjectCategoryView StatusLast Update
0018995MMW 5Otherpublic2022-11-01 00:09
ReporterLudek Assigned To 
PriorityurgentSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version5.0 
Target Version5.0.4Fixed in Version5.0.4 
Summary0018995: Consider adding HW acceleration switch to Options > Performance
DescriptionCurrently Chromium with enabled HW acceleration has better performance, but can lead to various issues in specific user environments.

1) Undocking laptop from a USB dock station can cause freeze in certain environments
(e.g. user from ticket # 4076, similar to https://superuser.com/questions/830162/chrome-browser-freezes-on-undocking )

2) MM5 can fail to run in certain environments (issue 0018609 and related KB article https://www.mediamonkey.com/support/knowledge-base/mediamonkey-install-config/mediamonkey-wont-open/ )

3) Maximizing MM5 window while YouTube video is playing in background can cause freeze in certain environments (issue 0018957)

Workaround is to use the MediaMonkey_noGPU.bat that runs MM5 without HW acceleration (more intensive CPU usage, less intensive GPU usage)

With above in mind I wonder whether we shouldn't add new checkbox to
Options > Performance
[..] Use hardware acceleration when available (better performance)

and probably maybe disabled by default to prevent from possible issues described above ?
Additional InformationAnother issue appearing only with HW acceleration is [Ticket # 4431]
TagsNo tags attached.
Fixed in build2663

Relationships

related to 0018957 resolvedpetr MM5 window freeze when playing YouTube while MM is minimized 
related to 0018609 closedLudek Some users can't run MM5 (until HW accelaration is disabled) 

Activities

Ludek

2022-04-22 19:32

developer   ~0067680

Assigned to Rusty for review + possible wording suggestions.

Ludek

2022-04-22 19:57

developer   ~0067681

Last edited: 2022-04-22 19:58

BTW: As discussed with Petr offline, Chromium has ability to run GPU process separatelly, so ideal solution would be to auto-switch to SW rendering whenever the GPU process crashes.
In that case the switch might be no longer needed, Petr is solving this in course of 0018957

jiri

2022-05-05 13:56

administrator   ~0067998

Based on what I've seen so far, the idea seems to make sense. As we aren't able to fix all GPU-related issues, we could possibly try to include this as a feature.

Ludek

2022-06-27 21:03

developer   ~0068709

Last edited: 2022-06-27 21:07

Added the config to Options > Performance
[x] Use hardware acceleration when available (requires restart)

Added in build 5.0.4.2656

Ludek

2022-09-14 10:47

developer   ~0069252

The tooltip text updated in 5.0.4.2663

lowlander

2022-09-16 19:22

developer   ~0069329

Verified on 2663, option is implemented.

Would there be a way to detect failed start and then next start automatically start with this option disabled? Alternatively could MM detect graphics cards and automatically disable this for GPU's known not to support this?

Ludek

2022-09-19 13:38

developer   ~0069359

Last edited: 2022-09-19 13:42

I don't think there is a general way how to detect issues with HW acceleration, this is the reason why I suggested to have HW acceleration disabled by default.
And for purposes of "3D album view" it could be enabled during the addon install?

But I guess this all depends on the percentage of users having troubles with HW acccelaration -- which I suppose is unknown atm?
i.e. if there is only a few users having troubles with HW acceleration then we can leave it enabled by default.

rusty

2022-09-19 20:28

administrator   ~0069377

Last edited: 2022-09-19 20:30

In some cases remote desktop only works with MM5 if h/w acceleration is disabled (this feature can help with that case). But generally, the issue of MM being unable to run is relatively uncommon as of late (it tends to occur more often on older PCs and with Windows 7), so it probably makes sense to leave the current default of h/w acceleration enabled.

The ideal approach would be to disable it for hardware/software environments known to exhibit the problem, but as mentioned, that doesn't seem to be feasible atm.

Resolving, since the original issue is fixed. A new bug to either change the default (manually or automatically) can be opened should the need arise.

peke

2022-11-01 00:09

developer   ~0070065

Verified 2679