Different oversample settings during bounce
-
- KVRist
- 217 posts since 25 Feb, 2010
A little feature request here. Vojtech, I know you always say that oversampling should not be used unless necessary (as opposed to other developers who believe it is always a good idea). But it would be nice to have the option of using different oversample settings during bounces than we use in real time. That way if we do decide oversampling is needed, we can have it applied during bounces without it eating into our CPU the rest of the time (or having to remember to change settings around before each time we bounce).
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14325 posts since 15 Mar, 2008 from Czech republic
Well, this is not a good idea. Oversampling induces latency! So for example you would add it to a track, everything would seem fine, and then you would render it and whoops, one track would be slightly out of time.
Oversampling seems to be some kind of 'cure for everything' these days, but the truth is, it doesn't help so much in most cases and causes some artifacts. People recommend it, because they are afraid you would hear some aliasing from their plugins, so it's kind of "backdoor". But I still claim you should use it only IF YOU ARE SURE YOU NEED IT! (and you hear the differences). Btw. most engineers I'm contact with say the same thing, and usually I have to admit their ears are much better than mine
).
Oversampling seems to be some kind of 'cure for everything' these days, but the truth is, it doesn't help so much in most cases and causes some artifacts. People recommend it, because they are afraid you would hear some aliasing from their plugins, so it's kind of "backdoor". But I still claim you should use it only IF YOU ARE SURE YOU NEED IT! (and you hear the differences). Btw. most engineers I'm contact with say the same thing, and usually I have to admit their ears are much better than mine
).
-
- KVRist
- Topic Starter
- 217 posts since 25 Feb, 2010
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14325 posts since 15 Mar, 2008 from Czech republic
Not really, plugins cannot CHANGE latency. So either all of them would have to report the latency even if they don't need it and then simulate latency, so that the host can compensate for it (which is crazy IMHO) or don't report it.
Out plugins do report it, when you reload the project, but the question is if all hosts let the plugin load first and then ask for latency. Some hosts can change the latency on the fly, but it's risky - e.g. if you have an automatable parameter, which affects latency, then you could make the host quite crazy with this.
Out plugins do report it, when you reload the project, but the question is if all hosts let the plugin load first and then ask for latency. Some hosts can change the latency on the fly, but it's risky - e.g. if you have an automatable parameter, which affects latency, then you could make the host quite crazy with this.