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

無法記憶資源偏好 #174

Closed
NeKoOuO opened this issue Apr 17, 2024 · 8 comments
Closed

無法記憶資源偏好 #174

NeKoOuO opened this issue Apr 17, 2024 · 8 comments
Labels
M 重要优先级 s: media 子系统: 数据源基础 t: bug 类型: bug
Milestone

Comments

@NeKoOuO
Copy link
Contributor

NeKoOuO commented Apr 17, 2024

上圖是設置

下圖是找一個沒碰過的條目做復現 結果顯示的跟設置完全不一樣

Screenshot_2024-04-17-14-57-32-111_me.him188.ani.jpg

Screenshot_2024-04-17-14-57-43-560_me.him188.ani.jpg

@Him188 Him188 added t: bug 类型: bug M 重要优先级 s: media 子系统: 数据源基础 labels Apr 17, 2024
@Him188 Him188 added this to the 3.0.0 milestone Apr 17, 2024
@Him188
Copy link
Member

Him188 commented Apr 17, 2024

fixed by c996ea7

@Him188 Him188 closed this as completed Apr 17, 2024
@Him188
Copy link
Member

Him188 commented Apr 17, 2024

目前假如设置里把 mikan 排序为第一位, 搜索时就只会考虑 mikan, 即使 mikan 里并没有偏好的字幕组的资源...

感觉应该做成优先, 而不是只选择

@Him188
Copy link
Member

Him188 commented Apr 17, 2024

那自动选择的优先级就这样吧, 越靠前越高:

  1. 分辨率
  2. 字幕语言 (未匹配时换下一个分辨率)
  3. 字幕组 (未匹配时随机选择一个)
  4. 数据源 (未匹配时换下一个, 设置中不勾选的永不使用)

规则:

  • 分辨率最高优先: 1080P >> 720P, 但不能为了要 4K 而选择不想要的字幕语言
  • 不要为了选择偏好字幕组而放弃其他字幕组的更好的语言

@NeKoOuO
Copy link
Contributor Author

NeKoOuO commented Apr 17, 2024

我覺得目前這樣底層的邏輯沒問題

但顯示的時候我覺得把資源放在最前面比較好

@Him188
Copy link
Member

Him188 commented Apr 17, 2024

把资源放前面是什么意思

@NeKoOuO
Copy link
Contributor Author

NeKoOuO commented Apr 17, 2024

那個數據源顯示在第一個

@Him188
Copy link
Member

Him188 commented Apr 17, 2024

beta12 应该是显示在最前面了吧

@NeKoOuO
Copy link
Contributor Author

NeKoOuO commented Apr 17, 2024

看到了👌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
M 重要优先级 s: media 子系统: 数据源基础 t: bug 类型: bug
Projects
None yet
Development

No branches or pull requests

2 participants