diff options
Diffstat (limited to '.github')
20 files changed, 1370 insertions, 273 deletions
diff --git a/.github/ISSUE_TEMPLATE/1_dont_ignore.md b/.github/ISSUE_TEMPLATE/1_dont_ignore.md deleted file mode 100644 index 578d5604fd..0000000000 --- a/.github/ISSUE_TEMPLATE/1_dont_ignore.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -name: 'README: DO NOT IGNORE OR DELETE THE ISSUE TEMPLATE' -about: 'Chose and fill out one of the following templates!' -title: '' -labels: priority:ignored-issue-template -assignees: '' - ---- - -We ask you to not ignore the issue template. Fill it out as good and correct as -possible. Issues that don't adhere to our request will be closed for ignoring -the issue template. This is because analyzing a bug without a log file is harder -than necessary. Low quality bug reports are noise. - -Please go back and chose the proper issue template. Opening issues with this -template will be closed immediately. diff --git a/.github/ISSUE_TEMPLATE/2_bug_report_linux.md b/.github/ISSUE_TEMPLATE/2_bug_report_linux.md deleted file mode 100644 index 46a5bf99f4..0000000000 --- a/.github/ISSUE_TEMPLATE/2_bug_report_linux.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -name: 'Report a Linux Issue' -about: 'Create a report for a runtime related Linux Issue' -title: '' -labels: 'os:linux' -assignees: '' - ---- - -### Important Information - -Provide following Information: -- mpv version -- Linux Distribution and Version -- Source of the mpv binary -- If known which version of mpv introduced the problem -- Window Manager and version -- GPU driver and version -- Possible screenshot or video of visual glitches - -If you're not using git master or the latest release, update. -Releases are listed here: https://github.com/mpv-player/mpv/releases - -### Reproduction steps - -Try to reproduce your issue with --no-config first. If it isn't reproducible -with --no-config try to first find out which option or script causes your issue. - -Describe the reproduction steps as precise as possible. It's very likely that -the bug you experience wasn't reproduced by the developer because the workflow -differes from your own. - -### Expected behavior - -### Actual behavior - -### Log file - -Make a log file made with -v -v or --log-file=output.txt, paste it to -https://0x0.st/ or attach it to the github issue, and replace this text with a -link to it. - -The issue will be closed for ignoring the issue template. - -### Sample files - -Sample files needed to reproduce this issue can be uploaded to https://0x0.st/ -or similar sites. (Only needed if the issue cannot be reproduced without it.) -Do not use garbage like "cloud storage", especially not Google Drive. diff --git a/.github/ISSUE_TEMPLATE/2_bug_report_linux.yml b/.github/ISSUE_TEMPLATE/2_bug_report_linux.yml new file mode 100644 index 0000000000..b2e47d6291 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/2_bug_report_linux.yml @@ -0,0 +1,143 @@ +name: "Report a Linux Issue" +description: "Create a report for a runtime related Linux Issue" +labels: ["os:linux"] +body: +- type: textarea + attributes: + label: "mpv Information" + placeholder: | + mpv v0.38.0-96-gf776be6af5 Copyright © 2000-2024 mpv/MPlayer/mplayer2 projects + built on May 5 2024 18:37:43 + libplacebo version: v7.349.0 (v6.338.0-120-g7b294350) + FFmpeg version: 6.1.1 + FFmpeg library versions: + libavutil 58.29.100 + libavcodec 60.31.102 + libavformat 60.16.100 + libswscale 7.5.100 + libavfilter 9.12.100 + libswresample 4.12.100 + description: | + Provide the output of `mpv --version`. + render: bash + validations: + required: false +- type: textarea + attributes: + label: "Other Information" + description: > + Provide follwing information if applicable. + - Linux Version: `cat /etc/os-release | grep "NAME"` + - Kernel Version: `uname -a` + - GPU Model: `lspci -nn | grep VGA` or `lshw -C display -numeric` + - Mesa/GPU Driver Version: `glxinfo -B | grep "OpenGL version string"` or `vulkaninfo | grep driverInfo` + - Window Manager and Version + - Source of the mpv binary + - If known which version of mpv introduced the problem + - Possible screenshot or video of visual glitches + + If you're not using git master or the latest release, update. + Packages and builds can be found [here](https://mpv.io/installation/). + value: |- + - Linux version: + - Kernel Version: + - GPU Model: + - Mesa/GPU Driver Version: + - Window Manager and Version: + - Source mpv: + - Introduced in version: + validations: + required: true +- type: textarea + attributes: + label: "Reproduction Steps" + description: > + Try to reproduce your issue with `--no-config` first. If it isn't reproducible + with `--no-config` try to find out which option or script causes your issue. + + + If the issue is render performance-related, try to reproduce it with `--no-config + --profile=fast`, which is designed to work on lower-end mobile devices. + + + For decoding performance-related issues, additionally try to enable hardware + decoding with `--hwdec=yes` or the `Ctrl+h` shortcut. + + + Describe the reproduction steps as precise as possible. It's very likely that + the bug you experience wasn't reproduced by the developer because the workflow + differs from your own. + validations: + required: true +- type: textarea + attributes: + label: "Expected Behavior" + placeholder: "What were you expecting?" + validations: + required: true +- type: textarea + attributes: + label: "Actual Behavior" + placeholder: "What happened instead?" + validations: + required: true +- type: textarea + attributes: + label: "Log File" + placeholder: "Drag and drop log file here (Don't paste content directly)" + description: > + Make a log file with `--gpu-debug --log-file=output.txt`, which is our preferred way, and + attach it to the issue. + + + If you have trouble producing a log file, you can alternatively use `--gpu-debug -v -v`, + save the terminal output to a file, and attach it to the issue. + + + In the case of a crash, please provide a [backtrace](https://wiki.archlinux.org/title/Debugging/Getting_traces). + + + Without the log file, this issue will be closed for ignoring the issue template. + validations: + required: true +- type: textarea + attributes: + label: "Sample Files" + placeholder: "Drag and drop sample files here" + description: > + Please provide sample files for a minimal reproduction case, if the issue can't be + reproduced without it or it is helpful to demonstrate the issue. + + + Preferably files should be attached directly within the text field below. Due to GitHub's + upload restriction, you may need to archive the sample file first and upload it as `.zip` + file. If the sample file is too big to attach directly, use a solution that is easy to + access with possible long-term retention. Possible services include, but are not limited + to, the following: + + - [0x0.st](https://0x0.st/) (no long-term retention) + - [Dropbox](https://www.dropbox.com) + - [Google Drive](https://www.google.com/drive/) + - [iCLoud Drive](https://www.icloud.com/iclouddrive/) + - [MediaFire](https://www.mediafire.com/) + - [OneDrive](https://onedrive.live.com/) +- type: checkboxes + attributes: + label: "I carefully read all instruction and confirm that I did the following:" + options: + - label: "I tested with the latest mpv version to validate that the issue is not already fixed." + required: true + - label: "I provided all required information including system and mpv version." + required: true + - label: >- + 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`. + required: true + - label: >- + I produced the log file while the behaviors described in "Actual Behavior" were + actively observed. + required: true + - label: "I attached the full, untruncated log file." + required: true + - label: "I attached the backtrace in the case of a crash." + required: true diff --git a/.github/ISSUE_TEMPLATE/2_bug_report_macos.md b/.github/ISSUE_TEMPLATE/2_bug_report_macos.md deleted file mode 100644 index 43620a3918..0000000000 --- a/.github/ISSUE_TEMPLATE/2_bug_report_macos.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -name: 'Report a macOS Issue' -about: 'Create a report for a runtime related macOS Issue' -title: '' -labels: 'os:mac' -assignees: '' - ---- - -### Important Information - -Provide following Information: -- mpv version -- macOS Version -- Source of the mpv binary or bundle -- If known which version of mpv introduced the problem -- Possible screenshot or video of visual glitches - -If you're not using git master or the latest release, update. -Releases are listed here: https://github.com/mpv-player/mpv/releases - -### Reproduction steps - -Try to reproduce your issue with --no-config first. If it isn't reproducible -with --no-config try to first find out which option or script causes your issue. - -Describe the reproduction steps as precise as possible. It's very likely that -the bug you experience wasn't reproduced by the developer because the workflow -differes from your own. - -### Expected behavior - -### Actual behavior - -### Log file - -Make a log file made with -v -v or --log-file=output.txt. If you use the Bundle -from a version later than 0.32 a default log is created for your last run at -~/Library/Logs/mpv.log. You can jump to that file via the Help > Show log File… -menu. Paste the log to https://0x0.st/ or attach it to the github issue, and -replace this text with a link to it. - -In the case of a crash please provide the macOS Crash Report (Backtrace). - -The issue will be closed for ignoring the issue template. - -### Sample files - -Sample files needed to reproduce this issue can be uploaded to https://0x0.st/ -or similar sites. (Only needed if the issue cannot be reproduced without it.) -Do not use garbage like "cloud storage", especially not Google Drive. diff --git a/.github/ISSUE_TEMPLATE/2_bug_report_macos.yml b/.github/ISSUE_TEMPLATE/2_bug_report_macos.yml new file mode 100644 index 0000000000..9df7c26eef --- /dev/null +++ b/.github/ISSUE_TEMPLATE/2_bug_report_macos.yml @@ -0,0 +1,138 @@ +name: "Report a macOS Issue" +description: "Create a report for a runtime related macOS Issue" +labels: ["os:mac"] +body: +- type: textarea + attributes: + label: "mpv Information" + placeholder: | + mpv v0.38.0-96-gf776be6af5 Copyright © 2000-2024 mpv/MPlayer/mplayer2 projects + built on May 5 2024 18:37:43 + libplacebo version: v7.349.0 (v6.338.0-120-g7b294350) + FFmpeg version: 6.1.1 + FFmpeg library versions: + libavutil 58.29.100 + libavcodec 60.31.102 + libavformat 60.16.100 + libswscale 7.5.100 + libavfilter 9.12.100 + libswresample 4.12.100 + description: | + Provide the output of `mpv --version`. + render: bash + validations: + required: false +- type: textarea + attributes: + label: "Other Information" + description: > + - macOS Version: `system_profiler SPSoftwareDataType | sed -rn 's/^ *System Version: (.*$)/\1/p'` + - Source of the mpv binary or bundle + - If known which version of mpv introduced the problem + - Possible screenshot or video of visual glitches + + If you're not using git master or the latest release, update. + Nightly builds from master can be found [here](https://github.com/mpv-player/mpv/actions/workflows/build.yml?query=branch%3Amaster+event%3Apush), + click on the latest workflow run, scroll down to the Artifacts section and download the + appropriate build. Packages and builds can be found [here](https://mpv.io/installation/). + value: |- + - macOS version: + - Source of mpv: + - Introduced in version: + validations: + required: true +- type: textarea + attributes: + label: "Reproduction Steps" + description: > + Try to reproduce your issue with `--no-config` first. If it isn't reproducible + with `--no-config` try to find out which option or script causes your issue. + + + If the issue is render performance-related, try to reproduce it with `--no-config + --profile=fast`, which is designed to work on lower-end mobile devices. + + + For decoding performance-related issues, additionally try to enable hardware + decoding with `--hwdec=yes` or the `Ctrl+h` shortcut. + + + Describe the reproduction steps as precise as possible. It's very likely that + the bug you experience wasn't reproduced by the developer because the workflow + differs from your own. + validations: + required: true +- type: textarea + attributes: + label: "Expected Behavior" + placeholder: "What were you expecting?" + validations: + required: true +- type: textarea + attributes: + label: "Actual Behavior" + placeholder: "What happened instead?" + validations: + required: true +- type: textarea + attributes: + label: "Log File" + placeholder: "Drag and drop log file here (Don't paste content directly)" + description: > + Make a log file with `--gpu-debug --log-file=output.txt`, which is our preferred way, and + attach it to the issue. If you use the Bundle, a default log is created for your last run + at `~/Library/Logs/mpv.log`. You can jump to that file via the `Help > Show log File…` menu. + + + If you have trouble producing a log file, you can alternatively use `--gpu-debug -v -v`, + save the terminal output to a file, and attach it to the issue. + + + In the case of a crash, please provide the macOS Crash Report or create a [backtrace](https://developer.apple.com/library/archive/documentation/General/Conceptual/lldb-guide/chapters/C5-Examining-The-Call-Stack.html) + yourself. + + + Without the log file, this issue will be closed for ignoring the issue template. + validations: + required: true +- type: textarea + attributes: + label: "Sample Files" + placeholder: "Drag and drop sample files here" + description: > + Please provide sample files for a minimal reproduction case, if the issue can't be + reproduced without it or it is helpful to demonstrate the issue. + + + Preferably files should be attached directly within the text field below. Due to GitHub's + upload restriction, you may need to archive the sample file first and upload it as `.zip` + file. If the sample file is too big to attach directly, use a solution that is easy to + access with possible long-term retention. Possible services include, but are not limited + to, the following: + + - [0x0.st](https://0x0.st/) (no long-term retention) + - [Dropbox](https://www.dropbox.com) + - [Google Drive](https://www.google.com/drive/) + - [iCLoud Drive](https://www.icloud.com/iclouddrive/) + - [MediaFire](https://www.mediafire.com/) + - [OneDrive](https://onedrive.live.com/) +- type: checkboxes + attributes: + label: "I carefully read all instruction and confirm that I did the following:" + options: + - label: "I tested with the latest mpv version to validate that the issue is not already fixed." + required: true + - label: "I provided all required information including system and mpv version." + required: true + - label: >- + 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`. + required: true + - label: >- + I produced the log file while the behaviors described in "Actual Behavior" were + actively observed. + required: true + - label: "I attached the full, untruncated log file." + required: true + - label: "I attached the backtrace in the case of a crash." + required: true diff --git a/.github/ISSUE_TEMPLATE/2_bug_report_windows.md b/.github/ISSUE_TEMPLATE/2_bug_report_windows.md deleted file mode 100644 index cd19438aed..0000000000 --- a/.github/ISSUE_TEMPLATE/2_bug_report_windows.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -name: 'Report a Windows Issue' -about: 'Create a report for a runtime related Windows Issue' -title: '' -labels: 'os:win' -assignees: '' - ---- - -### Important Information - -Provide following Information: -- mpv version -- Windows Version -- Source of the mpv binary -- If known which version of mpv introduced the problem -- Possible screenshot or video of visual glitches - -If you're not using git master or the latest release, update. -Releases are listed here: https://github.com/mpv-player/mpv/releases - -### Reproduction steps - -Try to reproduce your issue with --no-config first. If it isn't reproducible -with --no-config try to first find out which option or script causes your issue. - -Describe the reproduction steps as precise as possible. It's very likely that -the bug you experience wasn't reproduced by the developer because the workflow -differes from your own. - -### Expected behavior - -### Actual behavior - -### Log file - -Make a log file made with -v -v or --log-file=output.txt, paste it to -https://0x0.st/ or attach it to the github issue, and replace this text with a -link to it. - -The issue will be closed for ignoring the issue template. - -### Sample files - -Sample files needed to reproduce this issue can be uploaded to https://0x0.st/ -or similar sites. (Only needed if the issue cannot be reproduced without it.) -Do not use garbage like "cloud storage", especially not Google Drive. diff --git a/.github/ISSUE_TEMPLATE/2_bug_report_windows.yml b/.github/ISSUE_TEMPLATE/2_bug_report_windows.yml new file mode 100644 index 0000000000..9fedc64d06 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/2_bug_report_windows.yml @@ -0,0 +1,140 @@ +name: "Report a Windows Issue" +description: "Create a report for a runtime related Windows Issue" +labels: ["os:win"] +body: +- type: textarea + attributes: + label: "mpv Information" + placeholder: | + mpv v0.38.0-96-gf776be6af5 Copyright © 2000-2024 mpv/MPlayer/mplayer2 projects + built on May 5 2024 18:37:43 + libplacebo version: v7.349.0 (v6.338.0-120-g7b294350) + FFmpeg version: 6.1.1 + FFmpeg library versions: + libavutil 58.29.100 + libavcodec 60.31.102 + libavformat 60.16.100 + libswscale 7.5.100 + libavfilter 9.12.100 + libswresample 4.12.100 + description: | + Provide the output of `mpv --version`. + render: bash + validations: + required: false +- type: textarea + attributes: + label: "Other Information" + description: > + - Windows Version: `ver` (cmd) or + `"$([Environment]::OSVersion)/$((gp 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' -Name CurrentBuild).CurrentBuild).$((gp 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' -Name UBR).UBR)"` (PowerShell) + - GPU model, driver and version + - Source of the mpv binary + - If known which version of mpv introduced the problem + - Possible screenshot or video of visual glitches + + If you're not using git master or the latest release, update. + Nightly builds from master can be found [here](https://github.com/mpv-player/mpv/actions/workflows/build.yml?query=branch%3Amaster+event%3Apush), + click on the latest workflow run, scroll down to the Artifacts section and download the + appropriate build. Packages and builds can be found [here](https://mpv.io/installation/). + value: |- + - Windows version: + - GPU model, driver and version: + - Source of mpv: + - Introduced in version: + validations: + required: true +- type: textarea + attributes: + label: "Reproduction Steps" + description: > + Try to reproduce your issue with `--no-config` first. If it isn't reproducible + with `--no-config` try to find out which option or script causes your issue. + + + If the issue is render performance-related, try to reproduce it with `--no-config + --profile=fast`, which is designed to work on lower-end mobile devices. + + + For decoding performance-related issues, additionally try to enable hardware + decoding with `--hwdec=yes` or the `Ctrl+h` shortcut. + + + Describe the reproduction steps as precise as possible. It's very likely that + the bug you experience wasn't reproduced by the developer because the workflow + differs from your own. + validations: + required: true +- type: textarea + attributes: + label: "Expected Behavior" + placeholder: "What were you expecting?" + validations: + required: true +- type: textarea + attributes: + label: "Actual Behavior" + placeholder: "What happened instead?" + validations: + required: true +- type: textarea + attributes: + label: "Log File" + placeholder: "Drag and drop log file here (Don't paste content directly)" + description: > + Make a log file with `--gpu-debug --log-file=output.txt`, which is our preferred way, and + attach it to the issue. + + + If you have trouble producing a log file, you can alternatively use `--gpu-debug -v -v`, + save the terminal output to a file, and attach it to the issue. + + + In the case of a crash, please provide a backtrace, attach the approriate `.dmp` file + from `%LOCALAPPDATA%\CrashDumps`. + + + Without the log file, this issue will be closed for ignoring the issue template. + validations: + required: true +- type: textarea + attributes: + label: "Sample Files" + placeholder: "Drag and drop sample files here" + description: > + Please provide sample files for a minimal reproduction case, if the issue can't be + reproduced without it or it is helpful to demonstrate the issue. + + + Preferably files should be attached directly within the text field below. Due to GitHub's + upload restriction, you may need to archive the sample file first and upload it as `.zip` + file. If the sample file is too big to attach directly, use a solution that is easy to + access with possible long-term retention. Possible services include, but are not limited + to, the following: + + - [0x0.st](https://0x0.st/) (no long-term retention) + - [Dropbox](https://www.dropbox.com) + - [Google Drive](https://www.google.com/drive/) + - [iCLoud Drive](https://www.icloud.com/iclouddrive/) + - [MediaFire](https://www.mediafire.com/) + - [OneDrive](https://onedrive.live.com/) +- type: checkboxes + attributes: + label: "I carefully read all instruction and confirm that I did the following:" + options: + - label: "I tested with the latest mpv version to validate that the issue is not already fixed." + required: true + - label: "I provided all required information including system and mpv version." + required: true + - label: >- + 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`. + required: true + - label: >- + I produced the log file while the behaviors described in "Actual Behavior" were + actively observed. + required: true + - label: "I attached the full, untruncated log file." + required: true + - label: "I attached the backtrace in the case of a crash." + required: true diff --git a/.github/ISSUE_TEMPLATE/3_bug_report.md b/.github/ISSUE_TEMPLATE/3_bug_report.md deleted file mode 100644 index b42c254584..0000000000 --- a/.github/ISSUE_TEMPLATE/3_bug_report.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -name: 'Report a different Issue' -about: 'Create a report for a runtime related Issue' -title: '' -labels: '' -assignees: '' - ---- - -### Important Information - -Provide following Information: -- mpv version -- Platform and Version -- Source of the mpv binary - -If you're not using git master or the latest release, update. -Releases are listed here: https://github.com/mpv-player/mpv/releases - -### Reproduction steps - -Try to reproduce your issue with --no-config first. If it isn't reproducible -with --no-config try to first find out which option or script causes your issue. - -Describe the reproduction steps as precise as possible. It's very likely that -the bug you experience wasn't reproduced by the developer because the workflow -differes from your own. - -### Expected behavior - -### Actual behavior - -### Log file - -Make a log file made with -v -v or --log-file=output.txt, paste it to -https://0x0.st/ or attach it to the github issue, and replace this text with a -link to it. - -### Sample files - -Sample files needed to reproduce this issue can be uploaded to https://0x0.st/ -or similar sites. (Only needed if the issue cannot be reproduced without it.) -Do not use garbage like "cloud storage", especially not Google Drive. diff --git a/.github/ISSUE_TEMPLATE/3_bug_report.yml b/.github/ISSUE_TEMPLATE/3_bug_report.yml new file mode 100644 index 0000000000..056d907906 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/3_bug_report.yml @@ -0,0 +1,136 @@ +name: "Report a different Issue" +description: "Create a report for a runtime related Issue" +labels: [] +body: +- type: textarea + attributes: + label: "mpv Information" + placeholder: | + mpv v0.38.0-96-gf776be6af5 Copyright © 2000-2024 mpv/MPlayer/mplayer2 projects + built on May 5 2024 18:37:43 + libplacebo version: v7.349.0 (v6.338.0-120-g7b294350) + FFmpeg version: 6.1.1 + FFmpeg library versions: + libavutil 58.29.100 + libavcodec 60.31.102 + libavformat 60.16.100 + libswscale 7.5.100 + libavfilter 9.12.100 + libswresample 4.12.100 + description: | + Provide the output of `mpv --version`. + render: bash + validations: + required: false +- type: textarea + attributes: + label: "Important Information" + description: > + - Platform and Version + - GPU model, driver and version + - Source of the mpv binary + - If known which version of mpv introduced the problem + - Possible screenshot or video of visual glitches + + If you're not using git master or the latest release, update. + Packages and builds can be found [here](https://mpv.io/installation/). + value: |- + - Platform version: + - GPU model, driver and version: + - Source: + - Introduced in version: + validations: + required: true +- type: textarea + attributes: + label: "Reproduction Steps" + description: > + Try to reproduce your issue with `--no-config` first. If it isn't reproducible + with `--no-config` try to find out which option or script causes your issue. + + + If the issue is render performance-related, try to reproduce it with `--no-config + --profile=fast`, which is designed to work on lower-end mobile devices. + + + For decoding performance-related issues, additionally try to enable hardware + decoding with `--hwdec=yes` or the `Ctrl+h` shortcut. + + + Describe the reproduction steps as precise as possible. It's very likely that + the bug you experience wasn't reproduced by the developer because the workflow + differs from your own. + validations: + required: true +- type: textarea + attributes: + label: "Expected Behavior" + placeholder: "What were you expecting?" + validations: + required: true +- type: textarea + attributes: + label: "Actual Behavior" + placeholder: "What happened instead?" + validations: + required: true +- type: textarea + attributes: + label: "Log File" + placeholder: "Drag and drop log file here (Don't paste content directly)" + description: > + Make a log file with `--gpu-debug --log-file=output.txt`, which is our preferred way, and + attach it to the issue. + + + If you have trouble producing a log file, you can alternatively use `--gpu-debug -v -v`, + save the terminal output to a file, and attach it to the issue. + + + In the case of a crash, please provide a backtrace. + + + Without the log file, this issue will be closed for ignoring the issue template. + validations: + required: true +- type: textarea + attributes: + label: "Sample Files" + placeholder: "Drag and drop sample files here" + description: > + Please provide sample files for a minimal reproduction case, if the issue can't be + reproduced without it or it is helpful to demonstrate the issue. + + + Preferably files should be attached directly within the text field below. Due to GitHub's + upload restriction, you may need to archive the sample file first and upload it as `.zip` + file. If the sample file is too big to attach directly, use a solution that is easy to + access with possible long-term retention. Possible services include, but are not limited + to, the following: + + - [0x0.st](https://0x0.st/) (no long-term retention) + - [Dropbox](https://www.dropbox.com) + - [Google Drive](https://www.google.com/drive/) + - [iCLoud Drive](https://www.icloud.com/iclouddrive/) + - [MediaFire](https://www.mediafire.com/) + - [OneDrive](https://onedrive.live.com/) +- type: checkboxes + attributes: + label: "I carefully read all instruction and confirm that I did the following:" + options: + - label: "I tested with the latest mpv version to validate that the issue is not already fixed." + required: true + - label: "I provided all required information including system and mpv version." + required: true + - label: >- + 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`. + required: true + - label: >- + I produced the log file while the behaviors described in "Actual Behavior" were + actively observed. + required: true + - label: "I attached the full, untruncated log file." + required: true + - label: "I attached the backtrace in the case of a crash." + required: true diff --git a/.github/ISSUE_TEMPLATE/4_bug_report_build.md b/.github/ISSUE_TEMPLATE/4_bug_report_b |