Simply because I don’t want to have any more problems in the future. I imagine that the two software programs, as well as Iconica and others, share the same type of beta testing, and what happened with Cubasis is very likely to happen with Dorico.
1 Like
Do you honestly believe Logic Pro is bug free? Do you honestly believe you get any similar support from Apple, like direct contact to team members, like here?
These products use completely different code bases, the teams are completely different and run on totally different platforms. Sorry to say, but your assumption is far away from reality.
Read the Dorico forum for a while and then decide again.
2 Likes
Hi Lars- Regretably this is Not solved. I still have to close down and re-open a project to restore plug ins. Hoping for a permanent fix and thanking the team for their efforts. Happy New Year.
1 Like
I would probably follow your path if Logic workflow wouldn’t be so unintuitive for me…
Let’s not be too generous, you get regular direct contact with one team member, that is more of a spokesperson/IT/store support than anything. There’s no internal insight to be gained by talking with Lars, only copy/pasted support thread talk. To be honest, his job is actual AI fodder, sad as that is to realize.
What kind of internal insight do you expect?
Btw. I was talking about Dorico in the post you replied to, Lars is not part of Dorico.
So..Dorico has a front facing dev, that does not mean Cubasis does..you used “these products” and “completely different teams”. I’m on the Cubasis forum category..
Internal insight such as
“what foundational framework changes have been made to Cubasis in 3.8 that have caused so many problems? No foundational changes were mentioned in the initial update and now Lars is saying that’s why this release is so buggy. So what good foundational changes have been made?”
Are they referring to adapting to iOS 26 (input selection, external monitor support (that already existed) and making the app work at all with the operating system, as foundation reworking? That is simply keeping up with the operating system! The bare minimum is breaking our work!
2 Likes
Hi @hamishflute
Thank you for your report and HNY2026 to you too!
Hi Lars- Regretably this is Not solved. I still have to close down and re-open a project to restore plug ins. Hoping for a permanent fix and thanking the team for their efforts. Happy New Year.
Please create a separate thread so we can discuss this problem in more detail. It would be very helpful if you could provide a project that allows our engineering team to reproduce the issue.
To share the project via a download link or similar, please find my email address in the private message and get in touch. In this case, no separate topic would be required, but please make sure to add the full correspondence.
Thanks,
Lars
Hi @hamishflute
We’re in preparation of Cubasis 3.8.2.
I still find I have to completely close down Cubasis and restart my iPad to get Auv3s back. also as observed Cubasis is indeed behaving strangely
Since we’re unable to reproduce the AUv3 issue, do you still encounter the problem?
If so, it would be great to discuss it further. Once we (or our engineering) can see the issue, there’s a good chance to see it fixed.
Best regards,
Lars