I didn't claim there was necessarily an audible difference (especially without manipulating a signal hundreds or maybe thousands of times), but there are people who do just that, manipulate and manipulate a signal and it helps if the signal path remains pure as it can be. But under normal circumstances, you're definitely fine at 32-Bit FP. But again, if you're someone who manipulates his/her signal many many times, you'd probably appreciate a cleaner signal path. Your mileage may vary obviously.Can you provide some real world comparision between a 32bit song and 64 bit song, showcasing the need for 64bit floating point in all their plugs?Kilohearts Plug-ins Aren't Bit Transparent (Request 64-Bit FP update)
TL;DR request: Dear Kilohearts, please update all your plug-ins (including all 33 snapins) to operate at 64-Bit Floating Point internally and also send/receive their data at 64-Bit Floating Point so there would be no need for a 64-Bit to 32-Bit and 32-Bit to 64-Bit conversion either. So a Full End-to-End 64-Bit Floating Point signal path update please? So that there's no need for dither either.
Is it okay to link to a GS post, with audio examples of my post above? Or is linking to an external website (especially a competing one forbidden)?
Statistics: Posted by limitlesssss — Tue Jul 16, 2024 7:36 am