Hey all, I’ve been getting some PMs about whether or not Dorico 4 is up and running on Linux yet. Until today the answer was no, but I’m happy to say that I’ve just gotten it working (with some… caveats…)
I’ll do a quick writeup here about the steps in case anyone is itching to get going with things, with hopefully some improvements to the process and an instruction video (or heck, maybe even an install script, who knows) to come in… hopefully… the near-ish-future. Be forewarned that some of the steps right now are a bit kludgey, but they work. Mostly. The one thing that I don’t have working yet is audio, though it does look like Dorico/wine sees pulseaudio, so I’m not sure what’s up with that.
The reason this all has taken so long is that, one, life got busy with a recent minor career upheaval (those are always fun) and, two, I still haven’t managed to get the activation manager to open links from a web browser in Linux; it can open a browser, but getting it to listen to one is a different story (the download assistant has the same issue, but that’s not a prerequisite to running Dorico). The release of the offline activation feature seemed to elude my notice several months back I guess, but, luckily, as I suspected, activation was the only real substantial roadblock to the entire install process and everything else works, at least mostly.
Also, right now, this relies on having a Windows machine handy to do some file transfers. Can totally be virtual, in fact, this is probably preferable because a shared folder makes file transfers super easy. If you’ve already got a Windows machine with Dorico 4 already installed, that also works great.
So without further ado, strap in, because here’s how I’ve gotten things running, for now:
- On the Windows machine, download and install Dorico and the Activation Manager as normal. Sign into the Activation Manager, but don’t necessarily activate this install (I mean, you can if you want, like if you plan to use it, but it shouldn’t be necessary for this process). Set this aside.
- On Linux: Download Steinberg Activation Manager and Dorico 4 installation files here (Dorico 4 Updates and Downloads | Steinberg). Unzip the things that need unzipping and set aside somewhere handy.
- Install Bottles, Lutris, and winetricks.
- You might also need to install wine, but one of the other app installs might do that for you. You will need it though. I’m on Fedora, and I’ve got Lutris as a flatpak; Bottles and winetricks are native RPMs. (Can probably definitely be done with flatpak Bottles; I just didn’t like how long the path names to wine prefixes were and how annoying they are to find). These should all be available on your distro in some way, shape, or form, but you might need to make slight adjustments to these instructions based on versions and package formats. If you’re on Ubuntu or some system that’s going to use the stable branch of wine, consider using the development branch (it looks like Fedora might be on v7.19 or at least that’s the version I’m using in this guide, which is much closer to the dev branch, v7.21, than to the stable branch, v7.0.1)
- Create a new “gaming” bottle. Name it as you please. I did “Dorico 4” which names the wine prefix folder “Dorico-4”.
- Go to Preferences. Scroll to System. Open the Components entry. Change the runner from soda to sys-wine-7.19. If you don’t see sys-wine-7.19, you probably need to install wine. Do that, hopefully such that your version is similar.
- Change the Synchronization (right below Components) to System.
- Go to the Dependencies tab. Install vcredist2019. Install d3dx11 (not sure if this one’s necessary yet or not; doesn’t seem to hurt though).
- In a terminal run: WINEPREFIX=/home/YourUsername/.local/share/bottles/bottles/WinePrefixFolderName/ winetricks -f dotnet48 –this is for the non-flatpak version of Bottles. If you use the flatpak, you’ll want to look up the path to flatpak apps, then find the Bottles app and then the wine prefix folder from there. I think flatpaks are in /var?
- Back in Bottles, on the Details and Utilities tab, run executable SteinbergActivationManager.msi. Install as normal.
- At this point you can either activate your license using the offline license activation process, or you can do the next several steps first. The order here doesn’t matter too much. If you’re worried about using one of your activations on this install, feel free to go with a trial license (or SE license), though remember that if things happen to go completely belly up with a real license, Steinberg does let you deactivate offline activations through their website; haven’t needed to try it, but looks instant and stress free. If you want to activate now, hop to steps 16-23 for instructions, then come back.
- Run executable Dorico4.msi. Install as normal.
- Run executable Generic_Lower_Latency_ASIO_Driver_64bit.msi. Install as normal.
- Run executable HALion_Sonic_SE_3.5.10_Installer_win.exe. Install as normal, though this doesn’t seem to work right. That’s one of the reasons why we have the Windows machine. In the next step, we’ll undertake the very tedious process of copying some of the installation over.
- On the Windows machine find any file that has anything to do with Halion or VST or Audio Engine things. If you see Library Manager things, doesn’t hurt to grab those too, and it may help. These will be in places like:
C:\ProgramData\Steinberg\Content…
C:\Program Files\Common Files\Steinberg\Shared Components…
C:\Program Files\Common Files\VST3…
C:\Program Files\Steinberg\HALion Sonic SE…
C:\users\YourUsername\AppData\Roaming…
Basically, just look everywhere you can, and anywhere you see those things, grab them and transfer them to the same place in the wine prefix. Have fun…
- For some reason, the settings and libraries as we have them in the bottle aren’t quite configured right to make things work, but miraculously, opening the Activation Manager with Lutris fixes that. So, open Lutris. On the main Games page, click the plus to add a game.
- “Add locally installed game”
- Name whatever. Set runner as Wine.
- On Game options tab, browse to the Activation Manager exe to set that. Do the same thing for the wine prefix (should be the same as from installing dotnet48 above (/home/YourUsername/.local/share/bottles/bottles/WinePrefixFolderName which is the same as ~/.local/share/bottles/bottles/WinePrefixFolderName). Save.
- On the Games page, click the program. Click Play. You should see a popup that says updating wine prefix. Good.
- If everything has been done correctly, you should see the Activation Manager running normally. You can close it and remove the program from your Lutris library (removing is a two step process; basically just remove it twice; you’ll see what I mean). Close Lutris. That’s all we needed it for.
- Go back to Bottles. Run the Activation Manager again. Once again, you should see a popup that says it is updating the prefix. Once again, if everything has worked right, the Activation manager should run totally normally. You’ve now got a working Steinberg Activation Manager.
- If you haven’t already, activate the install using the offline activation process (in conjunction with the Activation Manager on your Windows machine). N.B. Sometimes it looks like the activation has disappeared, but merely “rebooting” the bottle seems to fix this. Not sure what that’s about, but it’s always come back after a “reboot” or a “shutdown”, so I’m not too worried about it.
- Once activated, you should now be able to run Dorico, albeit without any sound (again, if it gives you a license issue, just reboot the bottle). It might tell you that the VSTAudioEngine.exe terminated abnormally or something during the splash screen, just ignore it (don’t even touch the window) and see if Dorico continues to load. If it does, you’re good. If not, see below.
Note, this is not the exact order I’ve done everything in, and, for instance, I had to reinstall the dotnet48 thing once or twice again after I’d screwed other things up, but I’m fairly certain it should work as written. Though while not the exact order, this is every step that I took, at least every step that changed something or had any effect on the install. Feel free to try installing noteperformer if you’ve got it, though obviously, it’s not working without sound right now. Once again, I’ll do my best to see if some of these steps can’t be cleaned up and made simpler, especially that HALion stuff and the Lutris step, etc etc. Hopefully I can make that happen soon, but I guess we’ll see.
Totally open to suggestions, corrections, improvements, etc.
If you want to try to tackle getting the activation manager to work online, here’s a starting point on that (for some reason this has played funny with firefox for me, so I usually use librewolf while fiddling with this): https://www.reddit.com/r/winehq/comments/v40jas/how_to_get_a_wine_app_to_open_a_url_redirect/
Stay tuned. It likely only gets better from here, and the semi-working activation manager means that new versions of other Steinberg software can likely be made to run on Linux as well. I seem to remember getting Cubase working one time a while back.
Cheers! 
-Matt