Font issue
notDavid opened this issue · comments
Hi there, any idea how to fix this issue? I've installed the Font but... it doesn't seem to work.
Thank you :-)
macOS 12.6 (M1)
as soon as i have my hands on a mac, i will check if theres something wrong with it.
#16
we had that issue once, and one other user confirmed if that idea worked or not.
im not sure when i have access to a mac, but ill make sure to have it asap.
Great, thank you for looking into it.
Status Report: i still wasnt able to replicate the bug even after speaking with 8 friends who run macs daily. as soon as i have a mac for testing myself, i try to replicate it asap :) sorry for the long wait!
Thank you @Tsubajashi , if you want me to test anything let me know.
after speaking with 8 friends who run macs daily
I assume some of them also use M1 Mac's ?
all of them run m1 macs, and some also used developer versions of ventura by that time i saw them
Status Report: i still wasnt able to replicate the bug even after speaking with 8 friends who run macs daily. as soon as i have a mac for testing myself, i try to replicate it asap :) sorry for the long wait!
got the same error with the new mpv release on linux. It's not font related. osc script is just broken.
again, i cant reproduce it at all.
just freshly installed mpv from the arch repos just to make sure it wasnt flatpak related that it just worked - and no matter which version i pick, even running it on windows, i cant reproduce it.
@notDavid can you check if the recent merges fixed it for you?
Thank you @Tsubajashi , I'm afraid it was not fixed yet...:
As a workaround until we figure it out you can delete the mordenx.lua in scripts and set osc=yes in mpv.conf
@notDavid as of right now, mordenx has been removed. It will come back at a later date if those issues can be fixed :)
@notDavid can you verify that this bug does not happen for you anymore?
@Tsubajashi Yes, thank you for the workaround!
screenshot:
@Tsubajashi Yes, thank you for the workaround!
screenshot:
no need to thank me, @Xathros1 seems to have found the workaround by speaking with upstream. credits fully to them :D
All credits to the authors and the guy who made the pull request. I've just updated the file here.
But I think we can close this then
for sure!