May I have your settings file, and where should I place it?
1 Like
I’ve tried to post this several times already but to no avail, the forum keeps giving me a HTTP403 Forbidden response whenever I post it. I’ve posted it as a gist on Github here.
I’m a little tired, but so far no dice getting it to work properly through WINE. I think once you’ve authenticated and gotten libraries installed it probably works, but there’s a few roadblocks.
To enable OpenGL rendering you’ll need to go into drive_c/users/youruser/AppData/Roaming/Dreamtonics/Synthesizer V Studio 2/settings and open settings.xml. I think this file won’t generate until you’ve ran and closed SVS2 at least once.
Under General add the property “useOpenGL” and set it to 1.
<?xml version="1.0" encoding="UTF-8"?>
<ApplicationSettings>
<General useOpenGL="1"/>
At this point you’ll have a (seemingly) functional UI, but the next hurdle to tackle is to log in.
When you click the log-in button, WINE will by default open the link in your default browser, when you log in it will redirect to a custom uri scheme dreamtonics-svstudio2://and this is where I’ve gotten stuck.
I found this thread on Reddit where people offer various solutions. I’ve done the registry editing and had it open a WINE version of Chromium, but no matter what when I log in in the browser and click the uri-scheme, even though Chromium prompts to open SVS2, nothing happens past that and SVS2 just sits there waiting for you to finish logging in.
I’ve also tried setting a WINE application as a uri handler like described here, but I’m faced with the same problem.
The voice library downloader is a webview, and I’ve no idea if that will work or not as I’ve not gotten past the login process.
Lastly, menu items don’t really seem to work at all? I can’t really explore the application since I’m not authenticated but when you click the menu items they just appear as black for me.
This is as far as I get, the callback from the browser, be it the Chromium that’s running in WINE, or the native Gecko browser, just doesn’t seem to arrive to the app.
2 Likes
Thank you for the settings file!! I had no idea how to enable OpenGL without the UI.
As for the login screen, I’ll see if I can fiddle with that myself later today. I’m sure there’s some way to brute-force the callback into SVS2 lol
You can’t enable OpenGL even in the GUI, as far as I can tell atleast. I installed SVS2 on a Windows 10 VM to compare with it running natively, and I can’t find the OpenGL setting anywhere in the settings.
OpenGL rendering clearly still works somewhat for now, but since it’s not there as a setting I wouldn’t be surprised if they silently patch that out at some point. Granted, since the menu items don’t render properly maybe it’s better if we can get it to work through DXVK anyway.
The rendering section in the settings has to do with the rendering of the audio and not the application.
As for brute-forcing it, I did read a comment where someone had simply run the URI in a command prompt, but I wasn’t able to get this to launch anything, the command prompt just gave me errors. I think this has more to do with me not doing it properly than anything else though, so that might be doable.
Lastly, it seems like the license file that’s in the %appdata% directory after logging in gets regenerated on occasion. I’m guessing that the application phones home to Dreamtonics servers on occasion, so getting the login to work properly seems like a must.
Interesting that they won’t do a linux version for security reasons. I’m now trying desperately to get away from windows for security reasons. My surface pro updated the other day and uploaded gigs of my personal files to one drive and left shortcuts in their place. This functionality is default according to Microsoft. Why would i want my files online? I have a laptop so i can take my files with me, what if i don’t have internet access out and about? Morons.
Where’s the petition for a linux version?
4 Likes
I have no idea at all about Linux, but looking at the host of problems with the Windows version that need to be rectified, I can’t see Linux happening any time soon …
I’d rather turn around the question; if they have dropped Linux support in favour of improving the Windows and MacOS versions, then what difference did it make, given the amount of issues still present?
4 Likes
Yep, I can agree with that for sure.
1 Like
Guess the new features in SVS2 were a difficult task. 
Anyway, upgraded Wine to 10.4 and tried running SVS2 again, but no luck this time, either.
1 Like
I think it might be worth inquiring in a WINE related forum. Maybe there’s some log or callstacks one could glean some insights from. I’ve not had the energy to do so yet however.
1 Like
As “sign the petition” was typed in quotation marks, I think there is no actual petition, but Bobox referred to this or any similar post on the forum. Or writing individual requests to the support team. Anything that shows the devs there are more than three people total running SynthV on linux.
4 Likes
SVS2 doesn’t seem to output any logs itself (at least not in the %APPDATA%\Dreamtonics\Syntheiszer V Studio 2 folder).
Here’s Wine’s console output in case you want to include mine when posting elsewhere.
1 Like
That is correct … at the time of writing … there is no official petition. My comment was in single quotes, denoting a colourful metaphor for people letting Dreamtonics know how much they would like Linux support for SV2.
Sorry if you found this confusing.
2 Likes
I suppose it is this thread - the more who add to it, perhaps Dreamtonics will start to seriously consider the request ! Writing to them directly too will obviously help 
1 Like
Something interesting:
I’ve been following SynthV since 2018, and I’m pretty sure the very, very first demonstrations of it were on Linux.
I don’t actively use Linux anymore, but it was my main OS when I was younger.
I thought it was a miracle and very considerate of them to have Linux support as the leading vocalsynth software on the market. So it confuses me why they would drop support for Linux support now.
I’ll definitely email them.
5 Likes
I had version 1 running well on Linux Mint, with an Intel Tiger Lake chipset. However the same version 1 and the same Linux Mint resulted in ridiculously long load times on a Meteor Lake i9 processor. No idea why. I tried it on Fedora Jam Lam (with a Linux 6.13 kernel, on the same Meteor Lake machine) and it was no better. By contrast it loads fairly quickly on Windows 11 / Meteor Lake. So there’s a lot more going on than meets the eye with the Linux Builds. I have SVS2 running in parallel with that (on Windows 11); and I have to say that so far I’m distinctly unimpressed. I can get much more subtlety out of SVS1. There is a supplementary issue with Linux, arising from whether you are using X11 or Wayland as your display server. X11 no problem, but with Wayland some of the screen / mouse interaction functionality is lost. Personally I would like Linux builds to be issued as AppImages, though that may create dependency problems with voice libraries. A more pressing concern for me is that version 1 voice banks sound awful in SVS2 … at at my time of life I sure as heck am not going to pay for upgrades to the eight voices that I use regularly. Most probably I’d settle for a feature-freeze and offline working all the time.
2 Likes
Love the idea of using AppImages. Short of that, maybe working a bit to make the GUI usable in WINE would be nice. I’m still really disappointed about a lack of Linux version, for now I’m using a virtual machine to run SVS2 in and the workflow works, but I’d really rather not touch Windows at all.
Given that SynthV was originally developed on Ubuntu way back in the mid 201Xs it’s a little disappointing that they’ve chosen to forego the platform.
2 Likes
I updated Wine to 10.5 and the same issues with SVS2 persist on this version.
TBH the state SV2 is in now isn’t worth it anyway. It’s extremely buggy and has far worse performance than SV1, it feels like they released it a year too early or something. fingers crossed that Linux support is on the way.
But I think it’s a bad sign if even THAT’s something they’ve cut. It feels as if they threw away a lot of the stuff that was great about SV1, in favor of starting over from nothing. All we got that’s new are some mediocre features that definitely aren’t worth it, and some things don’t even seem to work yet.
2 Likes
As bad as Version 2 might be at the moment, they will not improve V 1 any more. So eventually, V 2 will have better performance and offer more possibilities than the first. In particular if you compare how much the recent (V 1) voice bank versions have improved, I doubt this will take the developers excessively long.
I hope their management might reconsider a linux version one day, though I am not particularly optimistic.
3 Likes