sumitagarwal
Inspired
Love the fact that ICONS looks like they've moved the goalpost on input calibration with repeatable reference tones, etc. But from what I'm looking at, seems like there's another approach we could use with ICONS too.
One thing I hate about plugins is there's no firm target on what the "correct" input level is, because they're designed to be interface agnostic. That's not the case with ICONS, since there is a particular input level methodology for specific hardware (FAS hardware modelers). Given that there's a real target there, I think we might be able to get it accurate across any interface with a published or measured maximum input level.
NAM embeds this concept with calibrated NAM profiles. The plugin let's you enter the interface's maximum input level in dBu.
Anyone more technical than me know how we'd do this in the ICONS world?
One thing I hate about plugins is there's no firm target on what the "correct" input level is, because they're designed to be interface agnostic. That's not the case with ICONS, since there is a particular input level methodology for specific hardware (FAS hardware modelers). Given that there's a real target there, I think we might be able to get it accurate across any interface with a published or measured maximum input level.
NAM embeds this concept with calibrated NAM profiles. The plugin let's you enter the interface's maximum input level in dBu.
Anyone more technical than me know how we'd do this in the ICONS world?
