summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorOneric <oneric@oneric.stub>2022-08-14 18:40:14 +0200
committerOneric <oneric@oneric.stub>2022-08-14 18:46:29 +0200
commitb890df23eb8931728acdf240fd5d29e53401b4f2 (patch)
tree6255a18aa2488f80a363271794b71344e3bb84b2
parent2c744a3dcb9057805009f4843014cb2700ada66e (diff)
downloadlibass-b890df23eb8931728acdf240fd5d29e53401b4f2.tar.bz2
libass-b890df23eb8931728acdf240fd5d29e53401b4f2.tar.xz
issue_template: explain "xy-VSFilter with libass"
Previously, some bug reporters used it to create (plain) "xy-VSFilter" reference screenshots.
-rw-r--r--.github/ISSUE_TEMPLATE/wrong-rendering-report.yml2
1 files changed, 2 insertions, 0 deletions
diff --git a/.github/ISSUE_TEMPLATE/wrong-rendering-report.yml b/.github/ISSUE_TEMPLATE/wrong-rendering-report.yml
index 73cc196..23519bd 100644
--- a/.github/ISSUE_TEMPLATE/wrong-rendering-report.yml
+++ b/.github/ISSUE_TEMPLATE/wrong-rendering-report.yml
@@ -22,6 +22,8 @@ body:
in a video player that uses VSFilter to render subtitles (for example, MPC-HC).
If it looks the same, even if it still feels wrong, this is probably intentional
and not an issue with libass.
+ Note, that “xy-VSFilter with libass” is not a VSFilter-based ASS renderer
+ and should thus **not** be used as a comparison.
- type: textarea
id: issue-screenshots