Skip to content

Best match means best; preference preselects the combo row - #49

Merged
Linuxuser67 merged 1 commit into
mainfrom
best-match-best
Sep 18, 2026
Merged

Linuxuser67 merged 1 commit into
mainfrom
best-match-best

Conversation

@Linuxuser67

Copy link
Copy Markdown
Owner

Best match (combo index 0) carried the global Preferred quality instead of best available, so x.com Best-match rows downloaded at the preference height while manual picks landed correctly.

  • Index 0 now stores quality best (tallest split / muxed / HLS variant in every path — all arms already handle it).
  • The global preference keeps its job as the preselected combo row at resolve time (new pure default_quality_index: Best stays on Best match, else closest listed height, ties taller).
  • Exact picks unchanged (pin + picked height).

218 passing, clippy clean. No string changes (label already says Best match, truthfully now).

@Linuxuser67
Linuxuser67 merged commit 812f102 into main Sep 18, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant