The engineering file of nuendo14 cannot be used in software before nuendo12, displaying “Invalid Engineering File” Is it normal that Cubase cannot be opened? How should I use old software to open 14 project files?
TBH, how should a software older than the current version know something about the new features?
It’s not possible.
I tried the engineering file of nuendo13 and it can be opened with old software
From Cubase and Nuendo 14 there is a new 64 bit file format… Which only can be opened in the last update (or maybe two) of C 13 and N 13.
Projects started in C 14 and N 14 will not open in older versions.
Projects started in version 12 (and early v 13) WILL open in older versions (they keep the former file format also when opened in C 14 or N 14 (until certain project file size is reached)).
From the Release Notes of C 14 (same goes for N 14):
Project compatibility
Cubase 14 introduces two major changes affecting forward compatibility with older Cubase versions, meaning that not all previous versions will be able to open projects created in Cubase 14. However, the backward compatibility of Cubase 14 is not impacted—you can still open projects from previous versions in Cubase 14.
With a complete redesign of event volume curve technology, Cubase 14 projects have limited forward compatibility in versions before Cubase 13.0.50. Event volume curves created in Cubase 14 can only be correctly reproduced in Cubase 13.0.50 or later. In earlier versions, these curves will reflect incorrect volume levels.
This applies to:
- Cubase 14 projects
- Tracks from Cubase 14 projects
- Cubase 14 track archives with event volume curves
Older version event volume curves remain compatible in Cubase 14. For versions 13.0.50 and later, a converter is included to ensure correct reproduction of Cubase 14 event volumes. Additionally, in the Export Track Archive function (exporting selected tracks), there is a new compatibility option to support earlier versions.
Cubase 14 also introduces a 64-bit project file format, enabling project files larger than 2 GB. This improvement addresses limitations encountered with audio extensions and certain third-party instruments that store data directly within project files. Projects saved in Cubase 14 will default to this 64-bit “RIF2” format, compatible only with Cubase and Nuendo versions 13.0.30 or newer. Projects saved in the older 32-bit format will remain in that format unless specific conditions are met, as detailed in the Help Center article.
1 Like
One of the least professional things to deal with in software. If introducing a new file format then there should be the option to backwards save like Pro Tools does. Say what you will about Pro Tools but they understand compatibly issues and have functions to mitigate potential issues.
2 Likes
I see
But is there a solution? I can’t demand that every one of my partners must upgrade to 13 and 14, it’s not realistic
The only “solution” is to start the project in an old version of the software and hope at some point it doesn’t save into the new file format. Any sessions created in the v14 will be saved in the new project file format and render them incompatible. The solution our team has gone with for the majority of systems is to simply not upgrade Nuendo.
It’s really something that should be fixed but it seems a lot of people use the software on single-systems in isolation, so compatibility doesn’t seem to be a priority.
Okay, thank you. This has caused some loss of interactivity in my work, and I cannot share my project with my friends in a convenient way
If I work with collaborators who have not upgraded to C/N 14, I start all my new projects in Cubase/Nuendo 12… before opening them in 14 and keep working from there.
This way it will be stored in the old file format (RIF)… Until it reaches a certain file size. That’s a limit I have yet to encounter… and at that point I do think we will get a “warning” in form of some information that the project is to be stored in the new file format (RIF2).
PS. I only work in audio… so maybe some of the movie working folks have experienced the file format conversion.
2 Likes
Disappointing at the silence from Steinberg. We’ve advised everyone in the team to not upgrade.
Had the same problem recently, however, as a workaround, you can export the tracks and choose file compatibility during export which then it lets you choose between cubase /nuendo 10 up to cubase/nuendo 13.
After that I created a new project in Nuendo 12 imported the tracks and then it worked.
1 Like
yes
This can solve some problems, but it becomes quite inconvenient for sharing larger engineering files, and many people are not familiar with this process
As a “professional” software, this should not happen. I think many users would probably consider not upgrading the software, not knowing which upgrade might suddenly make previous projects unopenable. Interaction is a very important part, and team collaboration often occurs
I think you are misunderstanding. Nuendo14 is backwards compatible, just not forward compatible (for okder versions).
This means you can open old sessions in 14, but cannot open 14 files in older versions (by default). So upgrading is only a problem if someone is left ‘behind’ working in 13 or older (although there are work arounds, as mentioned).
yes
There’s something wrong with my expression
Sorry
The old version of the software cannot open projects created by the new version, which is equally frustrating. It’s impossible to require everyone to upgrade to the latest version, and in team collaboration, it’s inevitable to use both the new and old versions of the software. I think that when using the old version to open the new version, it should prompt that certain effect parameters are incorrect and unusable, but it should not be completely unopenable. Many of my friends are still using old versions like 5, 8, 10, and 12
Probably they have very good reasons to be such old versions (ie v5 & 8) but still you can collaborate with them.. as mentioned.
Also your own license is downward compatible so you can also work in their version.. I understand that it is a workaround but it is not extremely hard to get working I would say.
and yes I would also love to not have to think about these things.. but it comes with progressive aspect of the digital musical landscape.