How can I update Wavelab or Steinberg products between different releases ? I usually uninstall the current program with Revo (to avoid conflicts) then install the new release.

I always do a backup of the Setting folder located in C:\Users\Username\AppData\Roaming\Steinberg\WaveLab Pro 12
Can i just install the new version over the old one or do I have to paste the backup files in the new folder everytime?

 

anyone?

 

I talk for Cubase with R2R emu: you dont have to uninstall anything, you can download the installer from Steinberg site or Steinberg App (use the app like a legit user) then apply the copy-paste trick of "license-engine-access"

no need to wait to R2R modded release

 

Can we use other steinberg products like spectralayer and dorico along with cubase pro 13 v.r crack in macOS ?
I have a legit license for cubase pro 13
Legit license vs k'd ?
K'd version is stable like legit version ?
Can handle all music production into it ?

 

R2R's on WIN10 had better performance than legit in certain updates of C13. Actually feeling 100% the same. IMHO.

I talk for C13, WIN10, R2R. Don't know mac and V.R's

 

I know about r2r
In windows i used r2r c12 13 and worked great !
License of cubase for my friend and also i use

 

Can you explain what is the trick of "license-engine-access"?

 

After you have all R2R's tools (silk emu + root certificate) installed
you can download Cubase or any Steinberg app/library from official site (or downloader app) and install, then do this trick:

-copy file "licence-engine-access.dll" from "c:\Program Files\Common Files\Steinberg\TEAM R2R \"
-past it to "c:\Program Files\Common Files\Steinberg\Activation Manager\" and replace

you have to do the copy-paste every time install something new or updates,
it works with updates also, no need to wait for R2R's modded versions

 

Thanks for the reply, I tested it and I can confirm it works as expected. I have a doubt about this tho, can I download anything inside the download assistant and it will activate?

 

Quick follow up to this... I did download almost everthing inside the VST section of the download assistant and I think everything works... if you want something to be specifically tested just ask

 

Im an idiot sorry lol

 

so what about V.R. releases? I experienced error prompts at start in Dorico by V.R. (even though the program still works)

 

Spoiler: Cubase 13.0.50

What’s new?
October 24, 2024 – The Cubase 13.0.50 maintenance update is now available. This update introduces numerous fixes and improvements across various areas of the application. In addition to our usual platforms, you can now access a preview version of Cubase 13.0.50 for Windows on Arm CPUs.

The update is immediately available for download via the Steinberg Download Assistant.

Preview Version of Cubase for Windows on Arm CPUs
We are excited to announce the release of a preview version of Cubase for Windows on Arm CPUs. This preview has been specifically tested on devices powered by Qualcomm’s Snapdragon® X Elite processors and allows users to run Cubase natively on these systems for the first time.

Please note that this is a preview version that has not yet been fully optimized. As such, it may not offer the same level of stability and performance as our currently supported platforms. While it has undergone extensive testing, there are still known issues that must be resolved. Be aware that you may experience occasional bugs and limitations with this version.

We greatly value your feedback during this preview period and are committed to improving the user experience with future updates. Our goal is to release a fully supported version for Windows on Arm in early 2025, ensuring the same level of quality and performance that Cubase users expect on all platforms.

The Windows on Arm application installers are available from the Steinberg Download Assistant (SDA) in the category “Complementary Products”, as well as in the Steinberg Support download section.

A preview of the Yamaha Steinberg USB Driver for Windows on Arm is also available at the same locations.

Additionally, we have created a dedicated tag for Windows on Arm in the Steinberg Forums, and we encourage you to share your experiences and feedback regarding this new platform.

Thank you for your continued support as we expand our software to new platforms and push the boundaries of creativity across diverse computing environments.

We have improved the following features and functionality:
Miscellaneous

• Editing the Root Note on the Info Line for Scale Events now works as expected.
• We have added [MB1] new user interface elements for managing Snapshots on MIDI Device Panels.
• Trim & Downmix controls now correctly affect beds in the Renderer for Dolby Atmos.
• We have optimized the compatibility for importing decoded DolbyE .wav files.
• After using Undo for “Track Operation: Folder: Toggle” in the Event Transform Actions list of the Project Logical Editor, folders now expand/collapse as expected.
• We have improved the filtering by signature attribute in the MediaBay.
• When enabling Mute on tracks containing MIDI Parts, “Chase Events” data is now sent as expected.
• We have optimized the performance for projects using large amounts of Post Fader Sends.
• We have enhanced the font in the Time module of SuperVision in Beats mode, to improve display stability and to reduce unsteadiness.

MixConsole

• Removing a track with active side-chain routing and then undoing the removal now properly restores the side-chain routing.
• Working with Link Groups in the Lower Zone MixConsole is now accurately reflected on the user interface when only Inserts or Sends are displayed, instead of Faders.
• Copy/Paste of MixConsole EQ settings now works reliably.
• We have resolved a graphical glitch in Send slots that occurred when double-clicking a slot to enter values.

Video

• We have improved the compatibility for importing Video files with variable frame rates.
• We have resolved an issue where exporting video sometimes led to shifted colors.
• We have resolved an issue where exporting video with uncommon aspect ratios was not working as expected.

Stability
We have improved stability in the following areas:

• when working with the Editor Visibility List within the Key/Drum Editor.
• when editing SMF Events with active Note Expression MIDI Input in the List Editor.
• when attempting to use "Set Track Visibility Agents > Advanced Agents > Collapse All Visible Folders".

 

Spoiler: Cubase 14

November 6th, 2024 – We are excited to announce the immediate release of Cubase 14.

Cubase 14 is a major update that includes numerous improvements across various areas of the sequencer. You can find comprehensive information on the new features and enhancements on our product pages, along with a series of in-depth videos by Steinberg product specialist Dom Sigalas.

For those who want to explore further, additional detailed information on all new features is available in the official user manual.

We would also like to inform you about some important changes that are not included on the product page.

Improvement and changes in Cubase 14
Performance
We have updated key data structures in our code base to optimize memory allocation. This is positively impacting overall performance, especially in areas where large amounts of data are handled—such as start-up time, loading and saving large projects, and moving a significant number of events at once.

Single Installer for Pro, Artist, Elements, AI, and LE
All Cubase versions are now available through a single installer. Whether you’re installing Cubase Elements or Cubase Pro, the same installer applies, with the version that opens determined solely by your license. Upgrading from Elements to Cubase Pro no longer requires a reinstall.

The new Score Editor built upon Dorico technology
Cubase 14 introduces a completely revamped Score Editor powered by Dorico, our renowned music notation and composition software. This new Dorico-based Score Editor replaces the previous version, bringing numerous enhancements and a refined focus.

The new Score Editor is designed to provide a powerful and intuitive notation-based MIDI editor. It allows you to quickly and easily view and edit your music in notation form, producing clear and legible parts ideal for simple live recording projects.

You can now export your Cubase projects directly to Dorico, enabling you to leverage Dorico’s advanced music formatting and layout features when needed.

Utilizing Dorico’s sophisticated quantization and transcription algorithms, the new Score Editor automatically splits music into independent polyphonic voices and applies publisher-quality music spacing and layout algorithms, resulting in more beautiful and readable notation both on screen and on paper.

While the new Score Editor incorporates some of Dorico’s features, it is designed to look and feel consistent with other MIDI editors in Cubase. This ensures a seamless experience whether or not you are familiar with Dorico.

If you found the previous Score Editor challenging to produce legible results, we encourage you to try the new version. It significantly reduces the time and effort required to achieve professional-looking notation.

Still, there are some limitations you should be aware of:

• MusicXML import is not supported yet, but it will be implemented in the future.
• Some score symbols, such as Arpeggio, Glissandi, or Octave lines, are not available yet.
• Since the technology behind the new Score Editor is completely new, importing scores from projects created with the previous Score Editor is only partially possible. We have created a Steinberg Help Article that documents the limitations in detail.

Cubase 14 marks the beginning of a new era in integrating our leading DAW with our music notation software. We are committed to extending the functionality of the new Score Editor and developing additional features to further integrate Cubase and Dorico in future updates.

To learn more about the story behind the development of the new Score Editor, check out this blog article by Daniel Spreadbury (https://blog.dorico.com/2024/11/cubase-14-score-editor/).

DAWproject Support
We are excited to introduce support for DAWproject files in Cubase 14. DAWproject is an open file format enabling seamless project transfers between DAWs, offering users greater flexibility and efficiency. This format allows you to transfer entire projects with the full structure—tracks, channels, and groups—preserved, eliminating the need to export individual stems and reducing time and effort.

When importing a DAWproject file into another DAW, all elements remain intact, including tracks, groups, colors, markers, events, fades, MIDI, and plug-in settings. This facilitates smooth collaboration, easier transitions between music software, and a greater focus on creativity over technical tasks.

We collaborated closely with the Bitwig team to integrate DAWproject support in Cubase, and we’re thrilled about the benefits this will bring to customers working across multiple DAWs. While automation and crossfades are not fully supported in this initial Cubase 14 release, we plan to expand these features in upcoming maintenance updates.

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.

End of VST 2 Compatibility Support
As previously announced, Cubase 14 marks the end of official compatibility support for VST 2 plug-ins. By default, the VST 2 plug-in scan is disabled in the VST Plug-in Manager, with only the VST 3 plug-in folder being scanned.

VST 2 plug-ins can still be loaded (except on native Apple Silicon) if the VST 2 plug-in scanner is manually enabled in the VST Plug-in Manager. However, Steinberg will no longer provide support for any issues related to VST 2.

Grace Period Update
The Grace Period for Cubase 14 began on October 9, 2024. This means that anyone who has activated a Cubase version since this date is eligible for a free update to Cubase 14. Detailed instructions for updating within the Grace Period can be found in our Steinberg Helpcenter.

 

Cubase 14
- legit version runs with the already installed Silk driver without any problems
- R2R version also runs (of course) with the old Silk driver

In Version 13 there was a regress compared to v12. All libraries were tested every time I started the app (content collect library on the splash screeen). This regression is corrected with v14 and the annoying test is bypassed.

 

Last edited: Nov 6, 2024

tip of the century,thanks

 

r2r or v.r which one is better? which one should we install. I think r2r said that v.r changed the computer structure. that's why I'm afraid to install v.r but all vsts of v.r work fine, I'm undecided.