I think that’s more than reasonable considering that this type of digital audio emulation requires a reasonable amount of processing power as you ‘push the envelope’ with your patches.
Gotcha. I can’t even remember when I’ve gotten half of my gear (let alone when it was released) because much of what I have was either a gift or 2nd-hand.
From what I read this supports AVX. If it does not I vote no to include AVX. It is literally the only laptop model that I know right now that reliably runs Rack for Live use due to its dedicated Nvidia GPU.
One other question I have is whether AVX optimizations have higher general impact than the current OpenGL performance requirements that turn modern laptops into space heaters. Is the performance improvement really noticeable that older hardware has to be locked out with 1.0?
EDIT: Looks like my Linux box does not support it: Intel® Core™2 Quad CPU Q9650 @ 3.00GHz (per /proc/cpuinfo)
Thank you for voting in the AVX CPU poll. The results in the last 12 hours on the forum and Facebook are that 47/321 = 14.6% of users cannot run AVX instructions. The official build of Rack will continue to require only up to SSE2 instructions as it always has been.
This data is valuable for VCV and third-party plugin developers to prioritize adding runtime CPU feature detection and AVX implementations in our plugins. Developers should keep in mind that AVX can improve DSP hotspots like IIR convolution, analog model solving, and polyphonic oscillators by up to about 1.5-1.8x compared to SSE2 (and up to 2.0x for AVX2). If anyone’s interested, open a thread in the development category of the forum and I’ll write up a list of cross-platform methods to elegantly handle CPU feature detection and compiling multiple versions of code.