After having released Cubasis 2.8.2, we’ve received complaints about the in-app shop window, which immediately opens with every app launch. The issue has been resolved in the Cubasis 2.8.3 hotfix update, which is now available for download on the App Store…
So far, we are unable to reproduce your problems, and it seems unlikely that the 2.8.2/2.8.3 updates have introduced CPU issues.
Are you able to check the update on an iPad which has iOS 13.3 installed?
I have tested Cubasis 2.8.3 on iPad 5th gen ios13,
T C Electronic “Voice rack FX” still crashes
I have been in touch with the dev and they have said it is not the iOS
But the update in Cubasis that has caused the issue,
As it was working fine on Cubasis before the 2.8 update with the same iOS version as mentioned (12.3, iPad Pro)
So far, we did not experience any CPU related issues with Cubasis 2.8.3, but we’re running the app mostly on iOS 13.3.
Please give your iPad a restart, and let me know if this helps to resolve the problem.
I have restarted the iPad several times, with no affect…
It is still peaking cpu on random projects when selected and press play.
It is beginning to get to the point where I no longer have faith in
I am yet to write a review and have to be honest, since I updated to 2.8.2,
These issues have started.
It is not the iOS, as Cubasis was running without these issues before I updated.
As mentioned above, I‘ve exchanged with our engineers, who analyzed your video example with the following outcome:
From your video we can deduct that certain AU plugins in your projects get stuck upon (or after) loading.
This is why they produce no sound and why the CPU indicator goes to 100%, which means that something (an AU plugin) holds up the Cubasis audio rendering.
Could it be that one or more of the AU plugins that you are using received an update around the time Cubasis 2.8.2 was released, and that the plugin’s update somehow causes the Cubasis rendering thread holdup?
In order to find the cause, we’ll have to narrow it down to just one AU plugin.
(1) Can you reproduce the issue with 2 projects that only use one AU plugin?
(2) Or can you send us 2 projects where the issue often occurs (when switching between them)?