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

Frame Meta Data #82

Closed
maybites opened this issue Jan 3, 2023 · 1 comment
Closed

Frame Meta Data #82

maybites opened this issue Jan 3, 2023 · 1 comment

Comments

@maybites
Copy link

maybites commented Jan 3, 2023

Hi

This is not a feature request, rather an inquiry about its technical feasablilty:

Spout has the ability to pass on an arbitrary byte-buffer with each frame. (link to header file). FYI: The latest MaxMSP - Spout package is already exposing it.

This is very interesting when sending realtime rendered images from game-engines together with camera intrinsic and extrinsic information to applications for spatial augemented reality.

Does such a functionality exist for syphon, too? And if not, with the current solution, could it be implemented into the framework in a similar way?

@bangnoise
Copy link
Member

This is a dup of #29. This feature doesn't exist in Syphon at present.

As I understand it, in Spout this feature isn't tied to any particular frame so it's isn't particularly useful for per-frame data.

At present Syphon (and Spout) only present a single texture which is always the "latest" frame, but as Syphon currently works, synchronising changes in that texture with changes in other memory would introduce unwanted CPU/GPU dependencies. #29 remains open and we'll consider it if other changes in the framework make it possible.

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

No branches or pull requests

2 participants