|
|
Possibly same issue is with user EagleScout -- [Ticket # 3217] and forum post https://www.mediamonkey.com/forum/viewtopic.php?f=30&t=100740 Wating for confirmation via the ticket... EDIT: For the user from [Ticket # 3217] it was another issue, for him installing the MM5 outside of 'C:\Program Files (86)' folder helped, so probably a permission issue, gathering further info via the ticket... |
|
|
5) I suppose that once it is HW/driver issue we can't actually fix the problem, we might just try to somehow detect this situation and auto-switch to SW acceleration (solution 2) So far only the user in ticket 3232 (with NVidia) confirmed that it is the HW acceleration issue (I'll ask him to try 5.0.1 and the alternate NVidia driver), the other user [Ticket # 3217] resolved it by installing outside of PF folder -- gathering more info via the ticket. EDIT: I noticed that Chromium actually creates /GPUCache/ subfolder in the MM5 install folder. My theory is that if MM5 is installed in C:\Program Files (x 86)\Mediamonkey 5\ then MM5 probably don't have enough rights to write to the /GPUCache/ subfolder and this may be cause of the issue ? To be confirmed. EDIT2: It seems that clearing the GPUCache folder might also do the trick for some users per https://freepctech.com/browser/google-chrome-black-screen/ (item 3 there) |
|
|
Assigned to Petr to move the GPUCache subfolder from the install folder to the system temp (or MM temp). |
|
|
Petr has moved the GPUCache to the temp dir, resolving to test in 2524 by the affected users whether it does the trick. |
|
|
FYI: HW acceleration is enabled in both Chrome and MM5 by default (to decrease CPU load and increase GPU load) but this can result in MM5 not able to be run in some specific environments (like in case of ticket [# 3232] ) I think that we sould just create KB article about how to disable HW acceleration i.e. all is needed is to create MediaMonkey.bat in the MM5 install folder with the following content: MediaMonkey.exe --use-gl=swiftshader which disables the HW accelaration on the problematic PCs. BTW: we could include this BAT in the installer, I am just a little bit out of ideas how to call the *.bat Something like 'MediaMonkey without HW acceleration.bat' seems cumbersome ;-) |
|
|
Added MediaMonkey_NoGPU.bat in build 2527 |
|
|
1) Tested the batch file on 2527 and it works. BUT is there a way of automatically closing the terminal window? |
|
|
1) Updated "MediaMonkey_NoGPU.bat" so that no CMD window is shown |
|
|
3) Confirmed that BAT workaround work on My old HP Proliant server with Windows Server 2012. |
|
|
Verified that the batch file in 2528 works as intended. |
|
|
Closing Verified again in 2528 and with one of users by using .bat from 2528 file on 2526. TEST NOTE: If .bat file do not resolve MM stating it is most likely different issue. |
|
|
FYI: There are three other cases of this after recent Chromium update in 2606: Tickets: # 3732, # 3722, # 3751 , forum https://www.mediamonkey.com/forum/viewtopic.php?p=494368#p494368 Do we have a KB article covering this issue already? |
|
|
No, We do not have dedicated KB article. Adding ToDOC Tag. Is there any way that apron MM start results from chrome://gpu gets logged somewhere and in case of freeze we can pull this up for debugging? EDIT: It could be usefull for users that observe issue to get results from EDGE by entering "edge://gpu/" in address bar. |
|
|
It was shown that the Chrome/Edge version for the user from ticket # 3732 is also 98.0 , but the Chrome/Edge output is this: image.png (44,127 bytes) |
|
|
i.e. Chrome/Edge can detect the missing capability and can run without HW accelaration automatically. To be found how they are doing it. image-2.png (11,186 bytes) |
|
|
BTW: Here is tutorial how to enable HW acceleration: https://www.youtube.com/watch?v=5IqETseKAK4 |
|
|
User from ticket # 3732 confirmed that command line switcher --ignore-gpu-blocklist does the trick. So the way should be to use this switcher by default. |
|
|
Maybe adding another BAT file based on https://wiki.archlinux.org/title/chromium#Force_GPU_acceleration in order to force GPU HW acceleration eg.: MediaMonkey_ForceGPU.bat -------- START MediaMonkey.exe --ignore-gpu-blocklist -------- |
|
|
The users that reported the issue after Chromium update in 2606 confirmed that --ignore-gpu-blocklist param resolves the issue. So I added the --ignore-gpu-blocklist for the render process as default in build 2608. The MediaMonkey_NoGPU.bat is left there and still can be used for tests whenever a blacklisted GPU has some issues, but mostly it is just about driver's release date. And asked affected users for the tests. |
|
|
Users confirmed that adding switch to Shortcut fixes problems and I verified 2608 that it does not introduce any regressions with GPUs that already supported HW acceleration. |
|
|
Added as: https://www.mediamonkey.com/support/knowledge-base/mediamonkey-install-config/mediamonkey-wont-open/ |
|
|
Re-opened to fix a regresion in 2608: Running without HW acceleration (using the MediaMonkey_NoGPU.bat) now renders buttons/icons without anti-aliasing: image-3.png (1,162 bytes) |
|
|
Fixed the anti-aliasing regression in build 2616 |
|
|
Verified 2616 Icons/buttons are Anti-aliased. |
- Anonymous
