Skip to content

ASS render in a wrong order. #2124

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

Closed
1 task done
peerless2012 opened this issue Feb 11, 2025 · 3 comments · Fixed by #2137
Closed
1 task done

ASS render in a wrong order. #2124

peerless2012 opened this issue Feb 11, 2025 · 3 comments · Fixed by #2137
Assignees
Labels

Comments

@peerless2012
Copy link

peerless2012 commented Feb 11, 2025

Version

Media3 1.5.1

More version details

1.5.1 release version.

Devices that reproduce the issue

Pixel 5

Devices that do not reproduce the issue

None (I think)

Reproducible in the demo app?

Yes

Reproduction steps

Chose a video with a customer ass.

Play

Expected result

The red latter should render behind the white, and before the gray.

Image

Actual result

The gray is before the white, and red before all.

Image

Media

The sample will post to media email later.

Bug Report

@peerless2012
Copy link
Author

peerless2012 commented Feb 11, 2025

The ass file looks like:

[Script Info]
; Script generated by Aegisub 3.2.2
; http://www.aegisub.org/
Title: Default Aegisub file
ScriptType: v4.00+
WrapStyle: 0
YCbCr Matrix: TV.601
PlayResX: 720
PlayResY: 480

[V4+ Styles]
Format: Name, Fontname, Fontsize, PrimaryColour, Bold, Italic, Underline, StrikeOut, ScaleX, ScaleY, Spacing, Angle, BorderStyle, Outline, Shadow, Alignment, MarginL, MarginR, MarginV, Encoding
Style: Default,Arial,48,&H00F6F6F6,0,0,0,0,100,100,0,0,1,0,0,5,0,0,0,1
Style: Shadow,Arial,72,&H000000FF,0,0,0,0,100,100,0,0,1,0,0,5,0,0,0,1
Style: Back,Arial,96,&H00AAAAAA,0,0,0,0,100,100,0,0,1,0,0,5,0,0,0,1

[Events]
Format: Layer, Start, End, Style, Name, MarginL, MarginR, MarginV, Effect, Text

; add 4 square in corner
Dialogue: 2,0:00:00.00,0:00:30.00,Default,,0,0,0,,{\pos(100,100)}X
Dialogue: 2,0:00:00.00,0:00:30.00,Default,,0,0,0,,{\pos(620,100)}Y
Dialogue: 2,0:00:00.00,0:00:30.00,Default,,0,0,0,,{\pos(100,380)}Z
Dialogue: 2,0:00:00.00,0:00:30.00,Default,,0,0,0,,{\pos(620,380)}W

; add 1 square in center
Dialogue: 2,0:00:00.00,0:01:00.00,Default,,0,0,0,,{\pos(360,240)}A

; add center square background
Dialogue: 0,0:00:00.00,0:00:60.00,Back,,0,0,0,,{\pos(360,240)}A

; add damic background square
Dialogue: 1,0:00:00.00,0:00:03.00,Shadow,,0,0,0,,{\pos(100,100)}X
Dialogue: 1,0:00:03.00,0:00:06.00,Shadow,,0,0,0,,{\pos(620,100)}Y
Dialogue: 1,0:00:06.00,0:00:09.00,Shadow,,0,0,0,,{\pos(100,380)}Z
Dialogue: 1,0:00:09.00,0:00:12.00,Shadow,,0,0,0,,{\pos(620,380)}W
Dialogue: 1,0:00:12.00,0:00:15.00,Shadow,,0,0,0,,{\pos(360,240)}A
Dialogue: 1,0:00:15.00,0:00:18.00,Shadow,,0,0,0,,{\pos(100,100)}X
Dialogue: 1,0:00:18.00,0:00:21.00,Shadow,,0,0,0,,{\pos(620,100)}Y
Dialogue: 1,0:00:21.00,0:00:24.00,Shadow,,0,0,0,,{\pos(100,380)}Z
Dialogue: 1,0:00:24.00,0:00:27.00,Shadow,,0,0,0,,{\pos(620,380)}W
Dialogue: 1,0:00:27.00,0:00:30.00,Shadow,,0,0,0,,{\pos(360,240)}A
Dialogue: 1,0:00:30.00,0:00:33.00,Shadow,,0,0,0,,{\pos(100,100)}X
Dialogue: 1,0:00:33.00,0:00:36.00,Shadow,,0,0,0,,{\pos(620,100)}Y
Dialogue: 1,0:00:36.00,0:00:39.00,Shadow,,0,0,0,,{\pos(100,380)}Z
Dialogue: 1,0:00:39.00,0:00:42.00,Shadow,,0,0,0,,{\pos(620,380)}W
Dialogue: 1,0:00:42.00,0:00:45.00,Shadow,,0,0,0,,{\pos(360,240)}A
Dialogue: 1,0:00:45.00,0:00:48.00,Shadow,,0,0,0,,{\pos(100,100)}X
Dialogue: 1,0:00:48.00,0:00:51.00,Shadow,,0,0,0,,{\pos(620,100)}Y
Dialogue: 1,0:00:51.00,0:00:54.00,Shadow,,0,0,0,,{\pos(100,380)}Z
Dialogue: 1,0:00:54.00,0:00:57.00,Shadow,,0,0,0,,{\pos(620,380)}W
Dialogue: 1,0:00:57.00,0:01:00.00,Shadow,,0,0,0,,{\pos(360,240)}A

The first line is a full text, and the below is a bigger text with a different color.

The right way is render the word first (sort by the Layer).

@peerless2012
Copy link
Author

@icbaker Any idea about this bug?

@icbaker
Copy link
Collaborator

icbaker commented May 9, 2025

#2137 has been merged to fix this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants