tester wrote:what "node" (module) can be used to reinitialize plugin for rendering the file. It seems, that plugins just go continuously, just at CPU speed instead of realtime.
For rendering in Reaper, i always use one of these two methods...
1) Rendering - in the rendering options window choose "1 x Offline", or "Online" render modes - this will fix the render speed at "real-time". ('Online' keeps audio inputs active - e.g. if feeding in hardware effects).
2) "Save live output to disk" - from the file menu. Does the same thing, but always uses the same file format as the project recording options - so you can't make a new file with different bit-depth or re-sampling, but it's a bit quicker to set up.
I find these most reliable for SM plugins. It helps by keeping the "green" and stream parts of the plugin synchronised with each other. Because "green" events are on a 'low priority' CPU thread, the audio can sometimes race ahead of green if rendering faster than real time.
I have noticed the same problem with some other non-SM plugins too - I guess they must also use some timing systems that are not sample-rate locked.
Worth checking out the Reaper forums too - they are a bit disorganised compared to here, but Google brought up a few threads there about the subject of rendering troublesome plugins.
tester wrote:Was not my intention to insist anyone
No problem - does no harm to give a dormant project a little kick once in a while!