[g-l Select a subtitle line to seek to] in windows git bash error.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 37k
- Forks
- 3.5k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 22
Description
mpv Information
mpv v0.40.0 Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
built on Mar 26 2025 06:10:23
libplacebo version: v7.349.0
FFmpeg version: 7.1.1
FFmpeg library versions:
libavcodec 61.19.101
libavdevice 61.3.100
libavfilter 10.4.100
libavformat 61.7.100
libavutil 59.39.100
libswresample 5.3.100
libswscale 8.3.100
Other Information
- Windows version: Microsoft Windows [版本 10.0.26100.3476]
- GPU model, driver and version: AMD7800
- Source of mpv: NA
- Latest known working version: NA
- Issue started after the following happened: NA
Reproduction Steps
- Download the latest git on Windows and check the option to integrate git bash into the terminal during the installation process.
- Prepare video and ass subtitles, the subtitle file name contains spaces.
- Open the video and press g-l to open the subtitles.
Expected Behavior
Successfully displayed subtitle list.
Actual Behavior
OSD shows "Failed to extract subtitles".
The log is as follows:
[select] [in#0 @ 000001d79f098ac0] Error opening input: Illegal byte sequence
[select] Error opening input file \c\Users\gpf233\Downloads\rs\anime[VCB-Studio] Fullmetal Alchemist꞉ Brotherhood [Ma10p_1080p][VCB-Studio] Fullmetal Alchemist꞉ Brotherhood [01][Ma10p_1080p][x265_flac].ass.
[select] Error opening input files: Illegal byte sequence
[select] Failed to extract subtitles.
Log File
Sample Files
I carefully read all instruction and confirm that I did the following:
- I tested with the latest mpv version to validate that the issue is not already fixed.
- I provided all required information including system and mpv version.
- I produced the log file with the exact same set of files, parameters, and conditions used in "Reproduction Steps", with the addition of
--log-file=output.txt. - I produced the log file while the behaviors described in "Actual Behavior" were actively observed.
- I attached the full, untruncated log file.
- I attached the backtrace in the case of a crash.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the g-l subtitle-selection flow on Windows Git Bash with the attached sample.zip and the subtitle path shown in output.txt. Trace the failure reported as “Illegal byte sequence” while extracting subtitles, then verify that g-l displays the subtitle list for paths containing spaces and the shown non-ASCII characters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, c
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100