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 custom FBO rendering function #815

Conversation

kblaschke
Copy link
Member

Added a new API function projectm_opengl_render_frame_fbo() to pass an optional custom OpenGL FBO ID for the final rendering output copy operation. This will allow users to render to an offscreen texture or a framebuffer provided by the embedding application's drawing subsystem, e.g. Qt.

kblaschke added 2 commits June 8, 2024 17:22
This will allow external apps to pass in any custom FBO to render to. Defaults to 0, keeping previous behavior if not given.
@kblaschke kblaschke added this to the 4.2 milestone Jun 8, 2024
@kblaschke kblaschke self-assigned this Jun 8, 2024
@kblaschke kblaschke merged commit bd2b1ba into projectM-visualizer:master Jun 9, 2024
9 checks passed
@kblaschke kblaschke deleted the add-custom-fbo-rendering-function branch June 9, 2024 10:19
@Jonathhhan
Copy link

Jonathhhan commented Feb 14, 2025

This is a great feature, thanks! This way it is possible to use it with an fbo in Open Frameworks. I did not had any issues so far. It would be very nice, to have it in the release versions too.

@kblaschke
Copy link
Member Author

It'll be in the 4.2 release. I hope to get all the backlogged features done ASAP, e.g. the debugging/logging API, user sprites etc. so we can release it.

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

Successfully merging this pull request may close these issues.

3 participants