Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Isn't it more than that though? It isn't just about sample rate and resolution which for a single sound should be extremely accurate, it's about replicating the effect on the sound as the knobs are twisted and sliders moved around. That's a whole different set of problems and I imagine very very difficult to accurately replicate/synthesize.


Let's put it this way: modern plugins that try to replicate this as close as possible (zero-latency filters etc) have a huge CPU hit.


Can you point me in the direction of the plugins you mean? Because I haven't had problems with CPU levels for a long time now. Just curious.


Here's an example: https://www.u-he.com/cms/diva -- it's widely regarded as one of the best sounding analogue emulations (mostly due to its filters) and as a CPU hog (in its "divine" sound engine mode).

Mind you, in a modern CPU you can still run a few instances, but very fewer compared to regular plugins.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: