Plugin bypass function not working since 5.9.2 update
It's just come to my attention that since updating to version 5.9.2 , the Bypass mode doesn't work, meaning that my mixes (including one sent out for a major advertising job) has the EQ curve still printed on it. I repeat, the latest version of Sound ID reference will print the room correction curve in bypass mode!! The only way round this is to remove the plug in from your session, and then revert back to previous version of software.
I can just about forgive the critical error made in the update, but i can't forgive the fact that you haven't emailed every user that the software is not working (when you have no problem sending me marketing emails )and will ruin your mixes until you spot the fault. They've known of this issue for over 2 weeks.
The entire point of this software is help me send better and more reliable sound to clients. The very least you could do is warn me the current version is totally unfit for purpose.
4 comments
Hi brockduffy,
Thanks for reaching out. I'm sorry to hear you're also experiencing the plugin bypass issue following the 5.9.2 update. We understand the inconvenience and are looking into it. This issue appears to impact a small portion of users though, so we're currently addressing it publicly via our Help Center content and other solutions. There is always a list of bugs and issues present in various stages of fix development, and direct messaging to mostly unaffected users would likely cause more distress than do good.
However, your input is valid, and we've forwarded it for consideration regarding an email update. For anyone else facing this issue, please submit a support request to help us address it faster. For immediate workarounds, refer to this guide: [Plugin bypass function not working since 5.9.2 update - issue resolved, article removed].
Stephen Navarrete - I see you have created another post regarding some measurement issues, I will address that in your post.
There's also some stuff going on with the test signals. Everything goes smoothly with signal A, but when I tried signal B, it stalls during the listening position portion right before the final measurements.
That is because the company spends more money on advertising than software quality.
Eckart Debusmann in case you missed it, the issue was resolved with the 5.11 update back in June (hence the ‘Completed’ status marked on top of this post). See this Community post for details, and full release notes here.