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

Request: external deinterlacing shaders #1458

Closed
wareya opened this issue Jul 12, 2016 · 2 comments
Closed

Request: external deinterlacing shaders #1458

wareya opened this issue Jul 12, 2016 · 2 comments

Comments

@wareya
Copy link

wareya commented Jul 12, 2016

I want to experiment with realtime deinterlacing, because the game I'm playing through right now doesn't have a progressive hack (low res framebuffer or something) and I'm running at native resolution so the interlacing is a huge eyesore.

Theoretically, still areas are ideal to weave, but moving objects are ideal to blend or bob.

I don't want to rebuild PCSX2 whenever I make changes, and "detecting motion" to choose between weaving and bobbing a particular output pixel requires sampling multiple extra frames from the past: if the field being deinterlaced is even, then you need the first previous odd field in the first place; but to detect motion, you need at least the first previous even field, and ideally also the second previous odd field.

Bonus: games that are 30fps but output as interlaced 60fps can't be deinterlaced in the ideal way (gather both fields, merge, finally output a frame) with the built in deinterlacers because the built in deinterlacers don't really store past frames. Blend almost does but it just stores a weave frame and blends it before output. If there's a real frame history available to a single shader, someone could implement right deinterlacing for this kind of game (30fps, but output as 60fps interlaced) without hacking more frame history into PCSX2 or implementing it as multiple shaders.

@lightningterror
Copy link
Contributor

Might be worth checking
https://forums.pcsx2.net/Thread-No-interlacing-codes

@lightningterror
Copy link
Contributor

lightningterror commented Jun 24, 2022

Closing, trivial.

@lightningterror lightningterror closed this as not planned Won't fix, can't repro, duplicate, stale Jun 24, 2022
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

3 participants