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

Assessing VSFilter for ASS Rendering #445

Open
softworkz opened this issue Nov 28, 2024 · 6 comments
Open

Assessing VSFilter for ASS Rendering #445

softworkz opened this issue Nov 28, 2024 · 6 comments

Comments

@softworkz
Copy link
Collaborator

I just had a kind of Epiphany.... 😉

Seems I've done too much x-platform work in the past years. I notice that I've even assimilated the habit to rule out platform-specific or worse: Windows-specific solutions - would have never happened earlier.

So - the point is: there's another ASS rendering implementation which is generally considered equal to libass (even though there are some differences and some may disagree on both sides). The de-facto-standard authoring tool for ASS subs is Aegisub. And Aegisub allows to switch rendering betwen the two, while VSFilter is the default.

What is is? It's a DirectShow filter, development has ceased long ago, but there are several forks of it still alive.

Is it suitable for us? I absolutely can't say that. Haven't thought about it neither looked at it.

But it's definitely worth to take a quick look and think about it once.

@brabebhin
Copy link
Collaborator

Pretty sure everything directshow is not compatible. Maybe we can use it for reverse engineering.

@softworkz
Copy link
Collaborator Author

Yes, or just use parts of the code if the license is compatible.

Without having ever seen the code, what might stand on the positive side is that it's probably very Windows oriented code and API usage and things might be done in ways that can benefit from Windows APIs and acceleration techniques than libass.
Also compilation wouldn't be an issue here.

But I don't know how it renders and whether that would be compatible in a more elegant way than libass.

@brabebhin
Copy link
Collaborator

The Windows API part is very important, because we cannot use APIs that's are not available in UWP.

@softworkz
Copy link
Collaborator Author

The Windows API part is very important, because we cannot use APIs that's are not available in UWP.

Oh..right!

@softworkz
Copy link
Collaborator Author

Just checked for libass. Here they are explicitly mentioning UWP, so the lights is green in that direction:

https://github.com/libass/libass/releases/tag/0.15.2

@brabebhin
Copy link
Collaborator

Yes iirc they were supporting uwp for quite some time but the build system was meh so we waited until meson was supported.

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

No branches or pull requests

2 participants