Clarification on real-time processing

Alexander Bean's icon

I was working on a project using groove~, and I tried to set the time stretch output quality to best (since this isn't a processor intensive project) using the @quality attribute. When I entered this into the object, Max Console gave me the message, "Quality "best" is unavailable in real-time processing". This seems to imply that one can use Max to pre-render audio for later playback. Assuming this is the case, can this also be done with Jitter for video? I haven't found directions for this in the forums or in documentation, so I'm not entirely clear whether this is actually a functionality of the program.

Thanks.

Postscriptum, I am using Max 7, which is the only version that has quality control in groove~.

Roman Thilenius's icon

it is hard to tell wether a nonrealtime mode for video exists or not, because it is basically the same than running video in realtime.

to put it simple, the difference for video is that in "realtime mode" you would trigger the next frame by a qmetro or metro, while in "nonrealtime mode" you would trigger the next frame by a bang, which is produced when all the processing and writing of the last frame has finished.

so you would have both in one patch (and you would rather call it "preview" and "rendering" modes)

as opposed to audio, where max needs the nonrealtime audio driver for nonrealtime, because all other drivers have a fixed rate set from outside the program.