non-real-time rendering

Programming Questions

terekita

in Programming Questions • 2 years ago

Hello,

I'd like to render frames of video at a fairly high resolution, regardless of how long they take to render, and without skipping any frames.

I can't figure out from reading the docs whether save-frame does this. I.e, does it 1) save "all" frames, regardless of how long they take to compute, or 2) saves frames on the fly as it is able (therefore resulting in smoother sketch performance, but some dropped frames)? It is seeming like the answer is the latter, but because I don't know, I can't tell exactly where my problems are.

If someone could let me know whether save-frame can work in non-real-time, and if not, if there is some way to do what I describe above, that would be greatly appreciated! (Googling high-definition rendering and non-realtime-rendering +processing.org didn't answer this question.)

Many thanks, Michael

Replies(6)

PhiLho

Re: non-real-time rendering

2 years ago

No, if a frame takes longer to render (even without saveFrame), the frame rate drops, ie. Processing won't skip frames to respect a given frame rate.

terekita

Re: non-real-time rendering

2 years ago

Very useful to know--thanks very much for the reply!

luis2048

Re: non-real-time rendering

2 years ago

some reasons why you may be losing frames could be:

your sketch (or library being used) is dependent on time to clock the animation

examples include: animation tweening, timers, millis(), seconds()

your sketch or library is using threads.

This is difficult to troubleshoot without seeing code. I use "movie maker" instead of save frame to save processing sketches into a move file.

This is what I use to render video from a processing sketch:

/*
render processing to video
*/
import processing.video.*;
MovieMaker mm; // Declare MovieMaker object
void setup(){
// set canvas size
size(1280,720);
// 720p resolution
mm = new MovieMaker(this, 1280, 720, "deformation.mov",25, MovieMaker.MOTION_JPEG_B, MovieMaker.BEST);
}
void draw() {
// put your visuals here
// 25fps * seconds wanted = frames you have to render
mm.addFrame(); // Add window's pixels to movie
if (frameCount >= 250) // 250 is 5 seconds at 25fps
{
mm.finish(); // close the movie file
exit(); // exit processing app
}
}

result: http://vimeo.com/4440148

The real-time version took several seconds to render each frame. Movement at 60FPS was really slow when moving 1pixel at a time. You may want too increase or decrease any movement variables to take the target FPS into consideration.

My guess is that you are using time or a 3rd party library which uses time or threads.