With Cubasis 3.8.1, we resolved the major user-reported issues that were within our control. Following the release, we received several reports related to mouse functionality, while some iOS-related issues could be partially resolved. Your specific issue depends on Qt and is outside our hands. We’ve escalated it and will include the fix once Qt provides a solution.
No, you still don’t get it. All you can do is continously ranting.
Steinberg is dependent on the framework from a company QT, because that is what is used to build the application. If this company delivers a bug with its framework Steinberg is just running into it.
All they can do is wait for a bug fix from QT and then rebuild Cubasis with the fixed framework from QT
@JuergenP Oh so steinberg dont have the final say in what is fit for deployment and what is not here?! That’s just BS mate simple as that. I work in cyber security as my day job which includes quite a lot of application security DAST/SAST along with functional testing, I can tell you for a FACT this is basic bread and butter stuff, blaming others for their own mistakes does not sit well with me at all
@JuergenP QT = single code repository provider for multi platform applications which doesn’t work properly right now and nobody from stienberg bothered with basic due diligence (TWICE!) before they pulled the trigger.
@JuergenP its not like they couldn’t have checked for bugs before the release though! Also not as if its like some niche rarely used function either, to blame a different organisation for that would seem more like your own misunderstanding of how SDLCs are supposed to operate in reality
All this ‘energy’ could have been better spent by buying a proper computer for music production instead of using and Android tablet as money doesn’t have seemed to be a deciding factor…
Show me whenever they accountabillity for their screw ups instead of blaming 3rd party entities? (Instead of blaming (ex.) Google, hardware manufacturers or anybody except them)
Now, this past week i saw the claim that the ios,android and chromebooks version are completely different apps while using QT proves that 2 out of the 3 “versions” are ports and not just completely seperate apps.
If there is a bug in 3.8 and you are told they will fix it in the next update and then in 3.8.1 it is not fixed.. ofcourse people will put pressure on them..
Getting evasive responses where they dont adress the totallity of someome’s post but only the part where they can fabricate an excuse (basically saying it’s out of their hands) doesnt help either.. more transparancy and direct answers/explinations go much further than trying to be an enigma.
I was already around in the Music Studio days and later migrated to FL Studio mobile then they changed their UI so after a while i migrated to Cubasis (more familiar UI and Steinberg’s reputation of professional quality) so i dont know why Cubasis is struggling so much, where FL doesnt
We hear you regarding your Android mouse issue, and we are in contact with Qt to resolve it.
In addition, Cubasis 3.8.2 is currently being prepared to address further user-reported problems.
@ all
If you encounter additional issues, please share the exact details so we can reproduce the problem - otherwise, we are unfortunately unable to resolve it.
To recap what has been done, said, and planned…
Posted on December 24, 2025
With Cubasis 3.8, the underlying Qt framework was upgraded to improve long-term stability and performance, while enabling new iOS features such as windowed mode and external display support, as well as fulfilling the latest Android OS requirements. Despite extensive testing over many months, some compatibility and transition issues occurred with the release of Cubasis 3.8, which have been partially resolved in yesterday’s Cubasis 3.8.1 update.
As posted on Jan 7, 2025
With Cubasis 3.8.1, we resolved the major user-reported issues that were within our control. Following the release, we received several reports related to mouse functionality, while some iOS-related issues could be partially resolved. Your specific issue depends on Qt and is outside our hands. We’ve escalated it and will include the fix once Qt provides a solution.
Current State
We are preparing Cubasis 3.8.2, which aims to address additional user-reported issues. The Android mouse fix cannot be implemented on our own and requires a solution from Qt first.