Package Details: yesplaymusicosd-origin-electron-git 0.4.5.r47.g90a57c3-2

Git Clone URL: https://aur.archlinux.org/yesplaymusicosd-origin-git.git (read-only, click to copy)
Package Base: yesplaymusicosd-origin-git
Description: 高颜值的第三方网易云播放器,支持 Windows / macOS / Linux :electron: 支持桌面歌词!(no fork). (with system electrton)
Upstream URL: https://github.com/shih-liang/YesPlayMusicOSD
Keywords: cloud lastfm lyric music netease
Licenses: MIT
Conflicts: yesplaymusic, yesplaymusicosd, yesplaymusicosd-electron
Provides: yesplaymusic, yesplaymusicosd, yesplaymusicosd-electron
Submitter: ZhangHua
Maintainer: None
Last Packager: ZhangHua
Votes: 0
Popularity: 0.000000
First Submitted: 2022-08-09 08:17 (UTC)
Last Updated: 2023-12-24 07:38 (UTC)

Dependencies (8)

Required by (0)

Sources (4)

Latest Comments

mikaelblomkvists commented on 2024-05-14 06:48 (UTC)

@ZhangHua please write the description in english. Otherwise the package will be removed.

ZhangHua commented on 2024-01-04 06:30 (UTC)

截至 2024-01-04,https://github.com/shih-liang/YesPlayMusicOSD 已经是和 https://github.com/qier222/YesPlayMusic 一样的仓库了,也就是说这个软件包没有单独存在的意义了,请诸位切换至标准的 yesplaymusic 或者其它变种,考虑到 yesplaymusic-git 目前是弃置状态,yesplaymusic-bin 是有一个未处理的请求,建议使用常规的 yesplaymusic 以获得最佳体验。

ZhangHua commented on 2022-12-13 09:34 (UTC)

@Sparky_14145 确实有这个问题。不过我并不熟悉 js 这边,也找不到解决方案。建议向上游项目反映这个问题。

Sparky_14145 commented on 2022-12-12 03:10 (UTC) (edited on 2022-12-12 03:12 (UTC) by Sparky_14145)

貌似现在桌面歌词存在问题,就是在歌曲更换以后,如果新更换的歌曲没有歌词,那么歌词不会自动改变,而是会一直停在更换歌曲时的那一句歌词(直到重启桌面歌词前无论再如何更换歌曲歌词都不会变化,哪怕后来再更换到有歌词的歌曲)?

ZhangHua commented on 2022-08-15 08:12 (UTC)

@kuohuanhuan That's weird because this package works well on my computer. Also, your package will build AppImage and Arch Linux package, that's useless for AUR building. Maybe it is because that you are using npm as package manager? The original repo uses yarn for package management, if you use npm, the yarn.lock will be ignored and you may not have proper dependencies installed. Using npm will results a package-lock.json which does the same as yarn.lock, but I don't find it in your repo, so npm will always use the latest version when run npm install command and this may results compatibility problems.

kuohuanhuan commented on 2022-08-15 07:38 (UTC)

Note that we use a fork repository is 'coz the origin's build settings WRONG.