Nuendo 15....I'm back to Nuendo 12

Nuendo
1

So…I’ve been on Nuendo 12 for quite a while…bought the update to 13 but never installed…bought the update to 14 and never even entered the code so when 15 came out I figured let’s give it a shot! I didn’t use prior preferences to see what happened. Here’s what happened-

  1. GUI…after 12 15 is horrible! Looks like a piece of cardboard with little holes cutout for the tiny fonts and the barely contrasted elements. I’ve tried using colors to make it at least tolerable but it still looks like a Fisher Price toy. If you want to see what I think is a nice looking GUI go look at Harrison MixBus!
  2. As far as operations I created an empty project and added an instrument track for starters to try recording. The track had no arm(record) button…in fact not much of anything, just Solo and Mute??? Shouldn’t an R button be default in a DAW? I did find the “track presets” or whatever they’re called to get an actual R button. There’s a lot of junk off to the left that should be on the track itself but I’m not a “modern music producer” :wink:
  3. I didn’t get to play for long because every…and I mean every…time I play any project about halfway through the whole thing crashes to the point Windows reboots!
  4. Open Nuendo 12 and all the projects play perfectly! I can spend hours in Nuendo 12 without an issue :slight_smile: So Nuendo 12 only for now!

Windows 11 Pro 25H2

ASUS ProArt Z690- Creator

Intel i9-12900k

128gb RAM

Right now 2 internal Nvme SSD and 4 SATA with an additional external SATA(18tb total)

Presonus Quantum 2626 connected TB3 to TB4

2

You just go to “Track Control Settings” and pick what you want to see.
Do it once.
Done.

3

Hmm. I wiped out all my preferences at the filesystem level for fun and started N15, and all the desirable buttons were there:

image
image402×277 6.78 KB

4

For some reason my tracks only had the M and S buttons, nothing else. No Arm, Monitor, Write, Read, etc.

5

Oh, another thing :slight_smile: Nuendo turned on Autosave…I have never used nor needed autosave…I use Save and Save As as needed using descriptive names for the Save As files…plus explorer shows me the timestamps so there’s no need for Nuendo to autosave…imagine leaving a project open for 4 hours while you tend to ther things and come back and you now have 16 more saved files of the same file you saved before you left! In case you’re wondering I’m not a fan of autosave :slight_smile:

6

How about uploading the last two crash reports here? I assume you used version 15.0.21?

7

Autosave only saves if there are unsaved changes in your project. If there are no new modifications to the project file since the last save (manual or automatic), the Auto Save timer effectively “pauses” to avoid creating identical redundant backup files.

8

I haven’t been back to the DAW for a while, hopefully in the next few days! I’m going to make sure the settings in 12 and 15 match and give that a shot! Maybe some VST2 give 15 trouble? I use VST3 where I can but I’m on Windows, VST2 is still a thing in our world :slight_smile:

If this doesn’t work out I’ll post the crash reports! I’m all in with Steinberg- Nuendo, Wavelab, Halion, Dorico…I’d like to stay that way:)

9

Oh yeah…the GUI is still ugly :wink:

10

Yes, you are asking for trouble. To ensure stability use VST3 only. Support for VST2 was officially discontinued some time ago; https://helpcenter.steinberg.de/hc/en-us/articles/4409561018258-VST-2-Discontinued

11

Lack of support doesn’t mean doesn’t work :wink: I understand VST3 has been out for quite a while and they want 3rd party companies to get onboard but not everything is there yet. I use VST3 as much as I can but get stuck sometimes with VST2 when there is not an alternative.

12

The sound design possibilities, are so much more available with VST3.

VST2.4 and below, is blocked for a reason.

13

Until preferences, are removed.

14

Obviously…

15

Why would anyone go back to version 12?

Version 15 works that much better on Windows 10 ESU, and I imagine Windows 11.

16

Why would anyone use 12? It’s rock solid here…15 not so much, and that’s Win 11 25H2. The GUI in 12 has better definition between elements…I’m trying to get 15 to work for me but the choices are limited…everything blends into everything else other than creating a kindergarden color scheme. I really prefer a dark theme but there’s no contrast, sections should have different coloring to go with that dark background…you should be able to read the meters better…at the end of the day I enjoy Nuendo, just not 15, but I’m trying :slight_smile:

17

The superior UX/UI.

18

For all of the reasons Cookie_Jarvis mentioned and much more! SB keeps taking away tools that are ESSENTIAL for some of us. I’ve never even looked at 13 or higher (though I own all of them, right up to 15.0.21) when they removed the Project Browser!:face_with_steam_from_nose: :angry: That was my “Line in the sand!”

I hate the black with white lettering appearance that is now the SB default setting. Every one of my versions still has the gun metal gray look of a real desk. They took away the single environment and that’s been a nightmare ever since it’s introduction in Ver. 7. They they took away the transparent wave files, that I loved, from version 10. Okay, get over it. But when they took the Project Browser Window, That was a “Oh Hell no!” moment for me.

I don’t do post, well not much anyway. I’m a Composer and I’ve only used Nuendo as my DAW. Been with it since version 1 and I love it. I’m completely tied into the SB Ecosystem (Nuendo, Halion, Spectral Layers, etc.) and I didn’t feel it necessary to switch to Cubase when SB started marketing Nuendo as a Post Product, rather than a Production Product. MAYBE if I did Post full time, I might see the need for the newer features. But for MUSIC, N12 has absolutely everything that I NEED! So, like Cookie-Jarvis, I’m fine with using N12.

There’s a lot to be said for staying with a particular version. The longer you work with it, the better you work with it, until it almost becomes invisible. You don’t have to think about it. You just focus on the work and the DAW does what you want to do that work. Every time there’s a new iteration, you have to figure out WHY they moved functions from locations that you spent years getting used to, fiddling with new features that are buggy as hell and don’t get me started on the THOUSANDS OF DOLLARS LOST IN INVESTMENT on Plugins that THEY decided for you that can no longer use!:scream: THAT ALONE is the number one argument for using hardware. So, now you’re bouncing around between iterations just to hang on to some plugs, because the replacements don’t do as well as the original, for whatever reason. It’s madness!

I hit the heart symbol on this post before I even read it because I KNEW what he was going to say and I totally agree with his assessment. If N16 comes out with a single environment, transparent wave files and a restored project browser, I’d consider switching. Until then, I’m very happy with N12 and being able to just work, as opposed to spending hours trying to figure out how to do what I used to be able to do without even considering it!:face_with_steam_from_nose:

19

Unfortunately, it sometimes does mean just that in v15. VST2 plug-ins may work but they may not.

Steinberg are extremely unlikely to re-instate full support for VST2. TBH more than 4 years notice does seem pretty reasonable.

Yes, it’s inconvenient if you are currently obliged to use a lot of VST2 plug-ins whose developers have not bothered to update to VST3. On the other hand, the pragmatic solution is to gradually phase out the use of all VST2 plug-ins anyway - this will avoid issues and frustration in the future.

If you’re happy with 12 then stay with 12.

20

That annoyed me at the time but there are other ways of seeing the data and I wouldn’t be surprised, if there are good things coming in respect to listed data.

I just get used to the interface as it changes, and there are still many parts of the application that require modernisation so I don’t see the situation regressing in any way, morover there are small changes being made all the time, that point towards a more modern interface in the future, maybe one that encompasses contextual preset mechanisms such as track specific presets, i.e., group track presets as opposed to track presets, and also Audio Connections, File Exports and so on but many of these aren’t exportable and are removed with preference deletion,