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.

Sign up for GitHub

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

Jump to bottom

Rethink direct CPU memory access limitation due to unified memory model on new systems? #67

Open
vade opened this issue Feb 21, 2022 · 2 comments
Open

Rethink direct CPU memory access limitation due to unified memory model on new systems? #67

vade opened this issue Feb 21, 2022 · 2 comments

Comments

@vade
Copy link
Member

vade commented Feb 21, 2022

Given that M1 machines provide universal memory and GPU shares memory with CPU, it might make sense to revisit our 'hiding' of the raw IOSurface in Syphon?

Just branching the subject to discuss w @bangnoise
@vade
Copy link
Member Author

vade commented Feb 21, 2022

We could in theory provide an IOSurface backed CVPixelBufferRef as a method in the framework? Thinking aloud? I imagine this would open up some use cases and provide a unified way to access surfaces with a clean interface.

@vade
Copy link
Member Author

vade commented Dec 21, 2023

I've got a good use case of 'getting' a new IOSurface from some other library. It would be cool to be able to publish using either the SyphonServerBase class, or a new SyphonSurfaceServer which consumed an input IOSurface and polished it directly?

@vade vade mentioned this issue Dec 21, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vade