ok thank you !!<br><br><div><span class="gmail_quote">2007/9/17, IOhannes m zmoelnig <<a href="mailto:zmoelnig@iem.at">zmoelnig@iem.at</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
henrik wurster wrote:<br>> ok...what I meant was creating a video-movie. like a command to save a<br>> file, like "writesf* does for sound.<br>> I was not sure if it is possible with such fast open-gl stugg...
<br><br>there are several ways to do this:<br>[pix_write] will capture the current screen and write it to an<br>image-file on disk (so you get a series of images which you then have to<br>assemble into a movie-file using your favourite non-realtime video app)
<br>[pix_record] should be able to record the pixes into a movie on the fly.<br>you will have to do the conversion from the rendering-window into a pix<br>"by hand" (this is: via [pix_snap]); you can only use quicktime movies
<br>at the moment; for some people it seems to be stable.<br><br><br>> In german we call this "rendering" and lots of programmes also call it<br><br>in austria, we refer to "the rasterization from high-level
<br>representation into low-level data" as "rendering".<br>for instance, in the context of our spatialization engine, i use<br>"render" for the creation of loudspeaker-signals out of a semi-abstract
<br>representation of sound-objects (input-signal + room information)<br><br><br>> rendering or for the "render settings" when you create a file out of<br>> your composition...<br><br>but the applications you are talking about are usually non-realtime.
<br>that is why the "render" to a file per default. for realtime<br>applications (like Pd) it seems to be more natural to render into a<br>volatile medium (like a screen, a loudspeaker-feed,...)<br><br><br><br>mfga.sdr
<br>IOhannes<br></blockquote></div><br>