Re: internal sampling rate
Posted: Tue Jul 07, 2020 12:48 pm
i use, almost from the beginning, 24 bit/48Khz, no real big decision, or reason. nice compromise.
the internal sample rate of 48Khz of VM seems to be necessary to constrain (...) anti-aliasing a bit, and i think it is also for audio rate. it must be fixed.
in reaktor you can change the internal sample rate, and more plugins use internally other sample rates, or do oversampling.
there is not much difference in quality between 48Khz and 44.1Khz, but i prefer it. i am used to it.
the resampling is the task of a plugin.
in reaktor you can indeed here the difference between 48Khz and 96Khz, internal setting. not always that big. i let it stay at 48Khz. it is one core plugin, even a 5Ghz AMD or Intel, will.. o well, i also never change the buffer size, i stand by my buffer size! that can help. o well when you set your project for instance to 96Khz, double the buffer size... (latency will be the same..) somewhat confusing answer. haha.
no option for offline rendering, but perhaps that is choice, for reaktor, because it really changes the sound.
but internally VM is always busy, when things are connected, at a fixed sample rate. i know the basics, and sometimes my head works better..
for your own projects, your daw, 44.1 or 48Khz does not change much.
although 48Khz has a small advantage for nyquist.
that is why, i think cherry audio has choosen for this sample rate, 96Khz would put a lot of strain on the cpu (and not only the cpu, it is complex, real time audio within the realm of a computer).
why the bit depth of 24 bit in my case, bit depth of my interface (but in reality only 20 bits are used...). more headroom.
EDIT: it seems that VM uses a low-pass filter for Nyquist also, only sample rate doesn't do it. there are more ways to prevent anti-aliasing.
i don't much about filters for nyquist. chopping of frequencies is one way, but it must be done before...
oversampling is another way, but it puts strain on the pc.
see the other reactions in this thread.
the internal sample rate of 48Khz of VM seems to be necessary to constrain (...) anti-aliasing a bit, and i think it is also for audio rate. it must be fixed.
in reaktor you can change the internal sample rate, and more plugins use internally other sample rates, or do oversampling.
there is not much difference in quality between 48Khz and 44.1Khz, but i prefer it. i am used to it.
the resampling is the task of a plugin.
in reaktor you can indeed here the difference between 48Khz and 96Khz, internal setting. not always that big. i let it stay at 48Khz. it is one core plugin, even a 5Ghz AMD or Intel, will.. o well, i also never change the buffer size, i stand by my buffer size! that can help. o well when you set your project for instance to 96Khz, double the buffer size... (latency will be the same..) somewhat confusing answer. haha.
no option for offline rendering, but perhaps that is choice, for reaktor, because it really changes the sound.
but internally VM is always busy, when things are connected, at a fixed sample rate. i know the basics, and sometimes my head works better..
for your own projects, your daw, 44.1 or 48Khz does not change much.
although 48Khz has a small advantage for nyquist.
that is why, i think cherry audio has choosen for this sample rate, 96Khz would put a lot of strain on the cpu (and not only the cpu, it is complex, real time audio within the realm of a computer).
why the bit depth of 24 bit in my case, bit depth of my interface (but in reality only 20 bits are used...). more headroom.
EDIT: it seems that VM uses a low-pass filter for Nyquist also, only sample rate doesn't do it. there are more ways to prevent anti-aliasing.
i don't much about filters for nyquist. chopping of frequencies is one way, but it must be done before...
oversampling is another way, but it puts strain on the pc.
see the other reactions in this thread.