Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COThanks so much. Basically what you are saying is what Apple's RosyWriter example does. https://developer.apple.com/library/ios/#samplecode/RosyWriter/Introduction/Intro.html There is a big problem. OpenGL-ES EAGLContext switch from main thread to worker thread will need mutex to lock them to avoid hardware driver to render wrong result? B/c there is only 1 hardware resource. Everytime main thread/worker thread needs to draw, it must call [EAGLContext setCurrentContext:currentContext] That will become a bottleneck. Do you have a way to get around that problem?
      singulars
    2. CO@Howy - Well, technically, you can access the bytes from your pixel buffer in any thread, not just the one that is current for your OpenGL ES context. However, you'll notice if you do so that you'll get screen tearing when recording off of this buffer due to rendering taking place while your movie writer is reading the bytes from the pixel buffer. No matter what, you'll need to use a blocking `glFinish()` right before reading, on your rendering OpenGL ES context. For this, I use a serial dispatch queue and wrap my accessed to one OpenGL ES context in blocks dispatched to that queue.
      singulars
    3. COThis is extremely lightweight, and avoids expensive locks around a shared context. I use this in my image processing framework, as well as my molecular modeler, for operations that run at a smooth 60 FPS.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload