Ohhh , so all the other bugs that were caused by the .5.1 are still there ? So this yet again was about getting your remote scriptors working but nothing about functionality for the people that actually use your software for the Audio industry ?
specifically which new bugs in 12.0.51 are you referring to ?
I’m only aware of that one.
obviously LOTS of other bugs remain 
2 Likes
Which ones weren’t there in 12.0.50 or 12.0.40 already?
Obviously, you have your blinkers on
Sorry i don’t mean to sound rude but there have been lots of reports of breakages from lots of people updating from 50 to 51 and having to revert, they are all out there, it’s your forum.
If this is the true course of Steinberg now, caring more about the Remote app than functionality then i think it’s time to leave, yes i know thats my choice and not an easy decision but as i’m mainly Acustica Audio plugins now it makes sense to move to a more efficient DAW. Shame but it is what it is .
The final straw was having to wait 3 months for you to rectify the most basic of things that Steinberg made their name with ’ Key editor alinement ’ but as soon as your scriptors want a patch to fix the new toy. Sorry, i can see where this is going. Updating is going back like the old days, more volatile and more chance of breakages and it’s getting harder to find a version that will work stable on the system .( wait for the “must be your system” )
You can all scream to your blue in the face that most things are system based, yes your right most things are, BUT not the basic silly breakages your coders make on things that made your name.
As i said , it’a shame but ,it’s time to jump off the update bandwagon
3 Likes
because of a NEW crash issue introduced in 51 which has been fixed in 52
quite possibly - but I’ve been reading most of the reports and they all the NEW issues in 12.0.51 seem to relate to MIDI remote - hence why I asked the question ?
I’m certainly no apologist for Steinberg ! - and I think the 12.0.51 update was a mess because of they way it was handled
I’m still not quite sure about what other bugs you are referring to that were introduced in 12.0.51 ?
Think I’ll stick with 12.0.50. Has no issues for me. 
1 Like
Good job!
Now - with 12.0.52 - my PreSonus Faderport works fine.
1 Like
thanks steinberg team
I think it’s a good idea to have quick updates as a optional update that fixes one or two problems or issues
or adds one or two features, as Microsoft does,
and a major update every 6 months
Until we reach a completely stable version, and this helps people to test the application,
sometimes my problem is different from the problem of other members
Good work, I hope we will get a full stable version soon and get some features
Long requested here on the forum
-Such as stopping scroll the mouse from controlling the mixer by placing a lock button on top of the mixer
-more cue mix to control room
-ability to change the sizes of some windows and toolbars and re-design them
In every Microsoft update, they redesign a single window interface, from legacy to modern
and new task manager design and a lot of small changes .
1 Like
Any others having issues with audio connection assignment causing crash and freeze in Cubase 12 and nuendo I’m aware of two others
@Matthias_Quellmann AHA! With the recent Cubase update 12.0.52 my Nektar Panorama P1 is suddenly back with full function! Apparently there was a problem with MIDI controller handling? I am amazed that this has been fixed! Thanks (finally) Steinberg!
2 Likes
Loading of the Plugins Alliances are now immediate Thanks Steinberg for this release 12.0.52 !!!
In this update, have you addressed the problem of Auto-Save not saving in the assigned time?
Auto-Save not working properly / Cubase !2 - Cubase - Steinberg Forums
1 Like
First post pretty clearly states what was and wasn’t included…
1 Like
Installed this release. No change for me as compared to 12.0.51. I am running MacOS Ventura on M1 Ultra. Runs very stable!
Really hope they could fix Retrologe 2 patch saving with the next release 
I’ve been unable to assign attributes to my patches since C12 came out. Must be some quirk in Retrologe and Padshop.
I, myself, am nervous about upgrading from 12.0.50 since this version is ultra-stable. It’s one of those “if it ain’t broke, don’t fix it” things, and 12.0.50 works fine. My controller, a Nektar Impact LX88+, has full functionality, that’s why I I’m staying with 12.0.50.
Haven’t heard of the wdmaud freeze bug (Windows audio driver)?
This new update fixed my issues with the Novation Impulse buttons crashing Cubase in 12.0.51.
The info highlighted below are my observations using the Impulse with Midi Remote,not with the update.
On the Impulse ,I had to change some cc buttons to different types.
The changing maps ,I have the button set as type MTY instead of t9L.
With cc button type t9L ,I had to press the button twice to change maps in Midi Remote,with it changed to MTY,now the button only needs a single press.
Other Midi Remote mappings work better with cc number type t9L.
Just test them and change to MTY or vice versa.
Make sure to use these CC numbers
MIDI CC 3
MIDI CC 9
MIDI CC 14-15
MIDI CC 20-31
MIDI CC 85-90
MIDI CC 102-119 TRANSPORT (112-117)
on the buttons of the Impulse as they are unassigned.
My Impulse after powering, set a button to cc number 64 which is assigned to the sustain pedal of the KB so if I hit that button,Cubase would crash.
The transport buttons can be left alone as they are unassignable buttons and have no conflicts.
After the update ,nothing has stopped working,all good.
TY Steinberg.
Faderport v1 or v2?
I had problem with my V1 and disconected it 2 months ago. Is it really back now?
I used old native driver.
no - I’m not aware of any other NEW bugs in 12.0.51 that were not in 12.0.50
if you were having Windows Audio Driver issues (why not use ASIO?) in 12.0.51 then it’s likely that it was there in previous versions as no changes were made to that area.