Installed this morning. Install and activation went perfectly. No issues so far, everything running great. Had to use Rosetta because I still have some VST2 instruments and FX. Drum machine is super cool. Will explore new features later, just happy I can do my normal work. Great release Steinberg, one of the best ever!
Thanks to all the developers for your hard and much appreciated work.
No
I can activate Write, just not with the shortcut key
The track behind the notification is not the track I was writing to.
If you bought your 12 to 13 upgrade in the September sale you payed less.
Explanation. 12 to 13 sale 50 euros, 13 to 14 now 100 eurosā¦ Total 150 euros.
If you hadnāt bought in September 12;to 14 now will cost you 200 euros.
You are 50 euros up on the deal.
I can confirm that, after registering it shows 12, I was quite surprised
It was gifted to me but never registered it.
Thank you - fixed it!
Sameš
I tend to agree with you. The release schedule of Steinberg Cubase has been quite consistent over the years. Whoever bought Cubase 13 on sale (like I did) was paying for that specific product and what it offers. The fact that Steinberg offers a grace period is by no means a āgivenā in the software industry and we should be thankful that they offer it. Naturally it is fully within Steinbergās purview to determine the length of the grace period as they deem strategically appropriate. And since they have invested the many man-hours of development into this new version 14, why should they not expect there to be a price to purchase it and to exclude the grace period from the sales period. This is good business practice. The goal is to earn money not lose it! Duh.
Do certain customers here truly believe that they are somehow entitled to get something for nothing? As the expression goes, āthere aināt no such thing as a free lunchā (TANSTAAFL)!
I think one very good reason to delay upgrading to Cubase 14 from 13 on Windows 11, if you donāt need any of 14ās new features, is the forthcoming Windows MIDI Services API which is about to drop imminently on Windows Insider builds. This will give full MIDI 2.0 support to at least Windows 11 users, and WMS is intended to replace both the original WinMM and WinRT MIDI APIs (but be backwards compatible with both of them). So Iād be tempted to wait until Cubase 15 (or maybe 16) which hopefully will include working WMS support, and I expect by the time Cubase 15/16 is released Microsoft will have dropped support for Windows 10 anyway, which is due to happen on 14 October 2025.
You could have just stopped there really. 
Live looping is missing and practically all the tools I use in Ableton would already be integrated. Maybe one day there will be some deep integration with Max, but I know that is more difficult.
I read that modulators do not work with external instruments (bug?).
Its intended that way, its not a bug.
Youāre joking? When it says it failed to connect or whatever the message is, thatās by design?!
Why do they put outgoing MIDI CCās in the selectable destination list if itās intended not to work? That makes no sense whatsoever.
Everything Iāve read states they only work on plugins or audio tracks. No MIDI.
Jeez people, its a brand new feature they put in specifically to please all of you whining about Ableton this, Bitwig that. Give them some time to hash it all out, its probably coming in the next point update.
But they modulate automation parameters, so at least it should work in that state. Yet, If you assign them to a MIDI Insert control, which has automatable parameters, it still fails too.
If itās a bug that theyāre to iron out, then fair enough but you said itās intended that way which is completely different and suggests itās going to stay like this.
I read that someone had it running by using the External Instrument plugin via a rack so was going to try that later, anyway.
Seems to be true.
Controls made in MIDI Device Panels donāt work with this new modulator system either.
External kit knows nothing about VST parameters unless it comes with a special VSTi plugin that ātranslatesā such things to something like CC or SYSEX events.
For the time being, the old MIDI Insert Auto LFO accomplishes the same thing for CC style modulation.
For Sysex modulation, unless the synth comes with a special VSTi that translates VST parameters to SYSEX, weāre out of luck until such as time as Modulator can work with āMIDI Deviceā automation tracks, or we bolt on third party plugins that allow ālinkingā a registered VST parameter to controls we build ourselves (Maybe Ctrlr would work?)
Good update. I am in.
However, I was just thinking about the meanwhile good UI of 13 and now with 14 I see inconsistent UI mix, which comes from the -functionally excellent- new drum track and the ānewā control room.
Steinberg, please finally hire someone who masters UI and UX 
@Monotremata . Your reply is so spot on 
Cub15 then with Cliplauncher 
Wow, you guys knocked the ball out the park with this one, AMAZING! the possibilities, really great, thank you all for your hard work. all the best.
Note: