Repro 1 AU issues after upgrading to Catalina and latest Repro 2020 version (VST/VST3 working fine)

[spnc]

Hi guys,

I used to run Repro 1 fine with Mojave and since yesterday I updated to Catalina and also updated Repro to the latest 2020 January version - my AU became so slow when changing presets taking like 3-6 seconds and feezing my Ableton in the process each time - very very annoying. So I changed all my Repro 1 tracks to VST3 on my project and it's running flawlessly (and btw even faster than previous version with Mojave so great).

Am I the only one here I find it very strange that Repro 1 AU component only is having this issue?

Cheers.

[tasmaniandevil]

If you search this forum for slow GUI or sluggish GUI, you can find plenty of information on the topic.
Problems started with Mojave, and depend on the macOS version, the used host, probably also on the graphics card and the used display, and possible other factors as well.

We are, yet again, working on some fixes for this.
You can try to switch the display profile of your display to sRGB IEC61966-2.1, but there is no guarantee that it'll improve the situation (though it does for some affected users).

[spnc]

If you search this forum for slow GUI or sluggish GUI, you can find plenty of information on the topic.
Problems started with Mojave, and depend on the macOS version, the used host, probably also on the graphics card and the used display, and possible other factors as well.

We are, yet again, working on some fixes for this.
You can try to switch the display profile of your display to sRGB IEC61966-2.1, but there is no guarantee that it'll improve the situation (though it does for some affected users).

Like I said if you read carefully, it's working fine (with VST/VST3 only though). I was just bringing this to your attention in case the AU only issue had not been reported yet. Searching and finding "plenty of information" is not really helpful here.

Also why are you not fixing an issue that has been known "since Mojave"?

Anyway like I said luckily I had the presence of mind to swap to VST3 and it's working great. But please consider working on sluggish AU if it's a recurring issue, I never had any GIU issue with Serum or any other synth - I think it's not fair for non-advanced users that will buy your product, since they probably assume that your products are flawless (which they are minus minor GIU issues) and fully compatible with OS.

[tasmaniandevil]

Since this problem first appeared, we have already included bug fixes in our updates.

As I said, those issues depend on a large variety of factors (sometimes even on the cable you are using to connect your display with the computer), it's not as if they appear for all users, these issues appear if many unfortunate circumstances meet, and we might not even know all the conditions under which this can happen.

Sadly, Apple keeps changing graphics related functions with every major update, without documenting what exactly they changed and how this affects applications. This leaves developers guessing and testing and guessing some more until they can find solutions for the problems arising from those changes.

This also means a fix that works perfectly on one macOS version might not work at all with another macOS version.

Addtionally, host developers might also change graphics related code in their updates, resulting in problems that have not been present in earlier versions.
And yes, this can vary between plugin formats. While a VST version might run smoothly, an AU plugin might experience issues in the same host.

We are already working on another round of fixes for this problem since almost two months now, and at times this is quite frustrating. What works well on one test system has no effect at all on another, or even makes it worse.

Rest assured, we will continue to research and work on fixing this until we are confident to have a solution that works on all affected systems.

[spnc]

Since this problem first appeared, we have already included bug fixes in our updates.

As I said, those issues depend on a large variety of factors (sometimes even on the cable you are using to connect your display with the computer), it's not as if they appear for all users, these issues appear if many unfortunate circumstances meet, and we might not even know all the conditions under which this can happen.

Sadly, Apple keeps changing graphics related functions with every major update, without documenting what exactly they changed and how this affects applications. This leaves developers guessing and testing and guessing some more until they can find solutions for the problems arising from those changes.

This also means a fix that works perfectly on one macOS version might not work at all with another macOS version.

Addtionally, host developers might also change graphics related code in their updates, resulting in problems that have not been present in earlier versions.
And yes, this can vary between plugin formats. While a VST version might run smoothly, an AU plugin might experience issues in the same host.

We are already working on another round of fixes for this problem since almost two months now, and at times this is quite frustrating. What works well on one test system has no effect at all on another, or even makes it worse.

Rest assured, we will continue to research and work on fixing this until we are confident to have a solution that works on all affected systems.

Thanks for the comprehensive answer - understood

Sidenote: the new M1 and graphics from Apple might bring a lot more job for you ) good luck and keep the great work cheers.

[Max Antsiferov]

I have the same problem, although I'm still on Mojave