arokhsar

I am new to using Jitter, and can't find any information about this in the documentation. I have made several patches that extract audio features and use them as parameters for opengl material. Now I am trying to save the video work to disk, and have run into problems.

So far I have sent the opengl information to a matrix so I could use jit.qt.record or jit.qt.vcr, but the results are very poor -- slow, many missing frames, etc. I understand the benefits of using opengl, and it doesn't make sense to me to then force all that intensive graphics processing back onto my machine just to save it to disk. I must be missing something -- surely people are saving their opengl work!

Does anyone know a better way? Thanks very much.

I am new to using Jitter, and can't find any information about this in the documentation.  I have made several patches that extract audio features and use them as parameters for opengl material.  Now I am trying to save the video work to disk, and have run into problems.

So far I have sent the opengl information to a matrix so I could use jit.qt.record or jit.qt.vcr, but the results are very poor -- slow, many missing frames, etc. I understand the benefits of using opengl, and it doesn't make sense to me to then force all that intensive graphics processing back onto my machine just to save it to disk.  I must be missing something -- surely people are saving their opengl work!

Does anyone know a better way?  Thanks very much.


saving-opengl-material-to-disk

hey adam. there's an object in max5/jit1.7 called [jit.gl.asyncread]

that is a big helper in getting stuff out of opengl land

efficiently... no matter what, though, the usual things apply that

will result in a reduction of frame rate: your gpu is designed to get

a ton of information from the cpu, not pass tons of information back

to it, and [jit.qt.record]/[jit.vcr] is streaming lots of information

recording a smaller size context (i.e. setting your [jit.window] and

[jit.qt.record] to 640x480 or 320x240 rather than fullscreen) will

help quite a bit, as will using a video compression setting that

doesn't put a huge load on the cpu or the disk (something like

photojpeg). you can always re-compress the movie later.

On Tue, Dec 23, 2008 at 6:23 PM, Adam Rokhsar wrote:

> I am new to using Jitter, and can't find any information about this in the documentation. I have made several patches that extract audio features and use them as parameters for opengl material. Now I am trying to save the video work to disk, and have run into problems.

> So far I have sent the opengl information to a matrix so I could use jit.qt.record or jit.qt.vcr, but the results are very poor -- slow, many missing frames, etc. I understand the benefits of using opengl, and it doesn't make sense to me to then force all that intensive graphics processing back onto my machine just to save it to disk. I must be missing something -- surely people are saving their opengl work!

> Does anyone know a better way? Thanks very much.

hey adam.  there's an object in max5/jit1.7 called [jit.gl.asyncread]
that is a big helper in getting stuff out of opengl land
efficiently... no matter what, though, the usual things apply that
will result in a reduction of frame rate: your gpu is designed to get
a ton of information from the cpu, not pass tons of information back
to it, and [jit.qt.record]/[jit.vcr] is streaming lots of information
to disk.  so your mileage may vary.

recording a smaller size context (i.e. setting your [jit.window] and
[jit.qt.record] to 640x480 or 320x240 rather than fullscreen) will
help quite a bit, as will using a video compression setting that
doesn't put a huge load on the cpu or the disk (something like
photojpeg).  you can always re-compress the movie later.

On Tue, Dec 23, 2008 at 6:23 PM, Adam Rokhsar  wrote:
>
>
> I am new to using Jitter, and can't find any information about this in the documentation.  I have made several patches that extract audio features and use them as parameters for opengl material.  Now I am trying to save the video work to disk, and have run into problems.
>
> So far I have sent the opengl information to a matrix so I could use jit.qt.record or jit.qt.vcr, but the results are very poor -- slow, many missing frames, etc. I understand the benefits of using opengl, and it doesn't make sense to me to then force all that intensive graphics processing back onto my machine just to save it to disk.  I must be missing something -- surely people are saving their opengl work!
>
> Does anyone know a better way?  Thanks very much.
>
>


Also, you might want to check out iShowU or Snapz for Mac, or Fraps for Windows. I use iShowU - excellent software for a cheap price - uses Soundflower for audio. There have been several threads on this topic in the past. Here's one:

Thank you both so much... this really helps!

Saving opengl material to disk