There was no event log entry referencing Cubase, nor any that reference “freeze”, from when I closed Cubase last night, or perhaps early this morning.) (Sorry, I deleted the event log info because I just realized that, while that was the most recent Cubase error in Event Log, the time stamp was actually earlier than could be possible for this latest occurrence of the issue. The associated event log entry has an Event ID of 1000, and the following details: In this case it is specifically saying it terminated with an error while executing a fille named Freeze, but I have no clue what that is, nor whether that was also what was referenced in the other cases. I just hope that Steinberg release a urgent fix for this instead of waiting for an update.
#Waves nx made my mixes worse pro#
And in the contect of my issue, if it is a waves plugin and that plugin performed flawlessly in Cubase Pro 9, 10 & 11, but now has an issue under Cubase Pro 12 then it is obvious that the issue is Cubase. In the context of a Cubase driven studio, Cubase is the critical software that should not be causing issues.
There should be Alpha and Beta versions long before the final version is released. My partner is a software tester for a well know company and its the job of the team that she is a part of to try and break the software and then fix the program so that it can not be broken in that way again. Waves plugins are unversally used in most recording and mastering studios world wide so the developers should have tested Cubase Pro 12 with them before release, thats part of the job of developing. The thing is I neither have the time to mess about as I have clients who want thier work completed on time, and I should not have to, that is what Steinbergs developers should have sorted out before releasing Cubase Pro 12.
0 kommentar(er)
