RAVE models must be exported with --streaming to avoid click artifacts in realtime hosts

By default, RAVE uses non-causal convolutions which look at future context — acceptable for offline batch processing but incompatible with sample-by-sample streaming. The --streaming flag switches all convolutions to a cached (causal) mode that stores a rolling buffer of past activations, eliminating the need for future samples. The resulting .ts (TorchScript) file is then loadable in nn~ (Max/MSP / Pure Data) or the RAVE VST. Forgetting --streaming causes clicking artifacts because the model attempts to access future samples that do not exist in the buffer. Command: rave export --run /path/to/run --streaming.

Examples

Export with streaming: rave export --run /model/out/my_model --streaming. Load the exported model in Max with nn~ my_model forward 2048.

Assessment

A user loads a RAVE model in Max and hears rhythmic clicking. What is the most likely cause and how is it fixed? What flag must be added to the export command?