whyterabbyt wrote:Probably - because one of the plugins is doing calculations which rely on hardcoded values related to an expected sample rate instead of actually checking what the sample rate actually is?beingmf wrote:Just tried the demo with 4 instances of Nebula / 4 bands of a 1073 EQ.
Oversampled the chain sounds *completely* different from the original sampling rate. Any insights why this happens?
No this is not the case of bad/wrong plugin. There is a problem in Metaplugin. Any plugin i throw inside of Metaplugin and when i press oversampling and then PDC is making DDMF Metaplugin doing same weird behavior. Tested in two different DAW.
Like (example) i throw in Soundtoys Effect rack, i add few plugins and then press oversample. then Press PDC and i get (recalling from memory just as an example there was different value again this is just example) 512 samples of delay. If i press PDC again i get 1024 (yes just by pressing PDC again). If i press it third time i am getting 2048 samples of delay. Yes just by pressing PDC button three times.
Today i was getting even weirder situation. I think i throw Slate VMR and one 1176 plugin in VMR. I pressed oversampling (i work at 44khz) but Metaplugin reported 0 latency to my host. Wow. oversampling enabled with zero latency great. It's just that i know oversampling with zero (0) latency is impossible in today universe so it must be Metaplugin acting weird. I know for a fact that oversampling was enabled since aliasing disappeared under Voxengo Span but still it was reported by Metaplugin as a 0 latency. And since it did not reported latency to my host and there was obvious delay in a track caused by oversampling - that track would always lag behind other tracks.
As i see it it is great plugin it really is but oversampling and PDC feature need some bugfixing.