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

Add API call to supply a "burn-in" texture for the next frame #794

Open
kblaschke opened this issue Mar 19, 2024 · 0 comments
Open

Add API call to supply a "burn-in" texture for the next frame #794

kblaschke opened this issue Mar 19, 2024 · 0 comments
Milestone

Comments

@kblaschke
Copy link
Member

Milkdrop has two places where it "burns" something into the preset main image:

  • After the title text display is finished, the text is burned into the preset.
  • If a user sprite is "done" and burn-in is enabled, it's also burned into the preset.

Displaying of user sprites will be handled by projectM (see #734), but title text display and other effects are not. So it will make sense to add an API call that gives applications the possibility to burn any texture into the current preset image.

As the texture might not be filling the whole screen, the API call should have parameters to provide rectangle coordinates (in texels relative to the drawing surface) where to apply the texture on the preset image.

The new API call should go into the render_opengl.h header, with a signature similar to this:

PROJECTM_EXPORT void projectm_opengl_burn_texture(GLuint texture, int left, int top, int width, int height);

The given texture would then be drawn once onto the active preset(s) main texture during the next call to projectm_opengl_render_frame(), right before the composite shader is applied.

@kblaschke kblaschke added this to the 4.2 milestone Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

1 participant