Rendring Large Images to Files & Non Real Time Rendering

    Oct 06 2012 | 5:05 pm
    Hey, Guys:
    First of all, I would like to ask a question and talk about my experience with rendering large chunks of the real time data in Jitter. It seems that Jitter rendering engine is really good and fast. There are a couple of ways that you can render image to file.
    1. {name space}---->jit.matrix (window has to be present in the name space) Size of matrix in this process is defined by the window. Quality is realy good, but anti aliasing should be set to 0. Furthermore if you need large rendered image, 6000 x 4000 for exemple, you need to create window of this size. This can slow down rendering to the process, in my case it means that I can't render in the real time.
    2. {name space} ---------> jit.matrix {defined namespace} is slower process but it functions marginally better on the large files. The Quality of the line is not as pristine.
    Am I missing some secret formula for rendering? Was there ever an external for rendering that would allow to slowdown the rendering process. It is possible to do it your self, but for my programs it would require creating separate capture mechanism (I am creating music compositions from EEG data) and play back mechanism that would slow down proces of playback of audio files.
    Then sync them to the single qmetro object. Am I correct? Or making huge mistakes, re-inventing a wheel?