Syphon-Framework icon indicating copy to clipboard operation
Syphon-Framework copied to clipboard

Published 20 hours ago • verified publisher icon Syphon

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

Open vade opened this issue 3 years ago • 2 comments

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 avatar Feb 21 '22 18:02 vade

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 avatar Feb 21 '22 18:02 vade

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 avatar Dec 21 '23 00:12 vade