For those licenses that are computer-based, the issues would remain for the plugins on any system, whether or not Cubase itself is portable. Regarding plugin licensing, many plugins utilize a hardware-based solution (such as iLok and eLicenser) which can be easily moved system to system.
Cubase portable install#
Also, the user may just have to manually install some plugins until a future time at which more plugins might be portable/modular.
Cubase portable zip file#
zip file and require no “installation” into the OS.
Examples of self-authored releases of commercial portable software are numerous here are just a few quick examples: GoodSync ($300 version) Sublime Text, Beyond Compare (which offers a traditional and a portable install in one installer), etc. Portable apps are popularly known by platform-based examples such as those found here and here and here and here, although it seems highly likely that a portable Cubase Pro would be built and released directly by Steinberg rather than released via one of these platforms. At this time, portable apps are a fairly widespread solution provided by many software companies. The application is adapted to work this way. The point of a portable application is that the application is self-contained in a single directory with no use of system registry, system files, etc. For a standard installed application, you are correct. That occurs during the installation thanks for your note. Like most programs Cubase depends on a whole bunch of Registry entries both existing and being properly set. Pretty sure that the Window’s Registry would balk at doing this.