Skip to content
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

\t argument parsing: missing comma #91

Closed
rcombs opened this issue May 13, 2014 · 9 comments
Closed

\t argument parsing: missing comma #91

rcombs opened this issue May 13, 2014 · 9 comments

Comments

@rcombs
Copy link
Member

rcombs commented May 13, 2014

Style: OP2,Barmeno,50,&H00FFFFFF,&H000019FF,&H00000000,&H00000000,0,0,0,0,100,100,0,0,1,2,0,2,25,25,30,1
Dialogue: 0,0:01:53.21,0:01:56.09,OP2,,0,0,0,,{\fad(0,200)\blur2\c&H271417&\3c&HEDDBEC&\an8\t(1189,1189\3c&HAC607D&\3a&H5A&\c&HFFFFFF&)}It's scary to {\alpha&HFF&}let go{\alpha&H00&} of the life I cherish
Dialogue: 0,0:01:55.76,0:01:56.09,OP2,,0,0,0,,{\fad(0,220)\c&HFFFFFF&\3c&H734255&\an8\alpha&HFF&\blur2}It's scary to {\alpha&H00&\3c&HAC607D&\3a&H5A&\c&HFFFFFF&}let go{\alpha&HFF&} of the life I cherish

Apparently in VSFilter, these 2 lines appear overlapped at the same position. In libass, the second one is shifted downwards (as I'd expect it to be). Hell if I know why VSFilter doesn't follow the usual behavior here.

@astiob
Copy link
Member

astiob commented May 13, 2014

Why would you expect it to be shifted downwards? That’s \fad, not \pos.

@rcombs
Copy link
Member Author

rcombs commented May 13, 2014

2 lines on the same layer; the second gets shifted to prevent overlap? I forget the name for it.

@astiob
Copy link
Member

astiob commented May 13, 2014

O-oh, because there is no \pos. Yeah. (In libass this is called collision… er… well, just collisions.) Hm… I’ll have to actually test this in VSFilter before I believe it. inb4 I missed something obvious

@rcombs
Copy link
Member Author

rcombs commented May 13, 2014

I went back and forth with skiddiks on this for a while, not believing that it worked in VSFilter, but he's quite insistent that it's fine.

@astiob
Copy link
Member

astiob commented May 13, 2014

        if(!fPosOverride && !fOrgOverride && !s->m_fAnimated)
            r = m_sla.AllocRect(s, segment, entry, stse.layer, m_collisions);

and m_fAnimated is set if \t or if \org && (\move || \pos || banner || scroll).
Confirmed in both xy-VSFilter and MPC-HC source code.
Still haven’t tested the file in practice.

@astiob
Copy link
Member

astiob commented May 13, 2014

Confirmed in guliverkli (VSFilter 2.37) code as well.

@astiob
Copy link
Member

astiob commented May 13, 2014

But we already disable collision detection on \t.

Oh! There we go. This is a parsing bug and a bug in the script.
\t(1189,1189\3c&HAC607D&\3a&H5A&\c&HFFFFFF&)
\t(1189,1189\
pls comma (until I finish my dissertation and go back to finish implementing the fully compatible parser)

@astiob
Copy link
Member

astiob commented May 13, 2014

See #94.

@astiob astiob changed the title Layering issue? I'unno :| \t argument parsing May 13, 2014
@astiob astiob changed the title \t argument parsing \t argument parsing (missing comma) May 13, 2014
@astiob astiob changed the title \t argument parsing (missing comma) \t argument parsing: missing comma May 13, 2014
@astiob astiob self-assigned this May 13, 2014
@astiob
Copy link
Member

astiob commented Jun 6, 2014

Fixed by cc9aaeb.

@astiob astiob closed this as completed Jun 6, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants