How common is it for VSTs to misbehave when run at 192k?

[THE INTRANCER]

Who cares about 192Khz and aliasing... it's the music that matters more than anything... here's a track I did as an experiment last year to illustrate my point.

https://soundcloud.com/scott-moncrieff- ... -labyrinth

[Triplefox]

A slightly different take on how to do a workaround: treat the misbehaving plugins as material for sampling. Instead of trying to put all of them in the track directly, render out the content you need at the higher rate, and then load that into a sampler. This is the lowest common denominator for getting all the sounds you want in one place - whether it's acoustic recordings, old synth hardware, sound effects, old stems, or disagreeable plugins. If you expend the effort and disk space on building up a sample library, you have a straightforward way to access "the sound" later - not all of the sound, but the parts of it that you cared about at the time. Trying to keep old software running, on the other hand - that's hard, and it impacts your ability to let your workflow continue evolving.

[fluffy_little_something]

What rate is considered the minimum for professional recordings?
When rendering, the file size depends a lot on the sampling rate, so why waste a lot of virtual storage space if it is not necessary