Ever since SV2 came out and I had my hands on it, I was blown away by its overwhelmingly streamlined UI and user experience, and how much better it feels to use compared to SV1. The splitting of VMs, mouth opening, shortcuts, hotkeys, middle-mouse navigation, etc, etc, etc. However, in some aspects SV2 has regressed in terms of its engine sound, which many users report. Most notably, Miyamai Moca VB from AHS, although in my experience AVER also sounds somewhat worse than her SV1 version.
Since I don’t know the software architecture of SVS2 and SVS1, I can’t estimate how difficult the following feature suggestion would be, but I was wondering if there was any way to build in an engine selector in SV2 between SVS1 and SVS2 versions of the voicebanks (the “AI“ versions, of course, not “standard”), making a unified frontend for both of them. Of course, with checks that the user owns SVS1, and the corresponding voicebanks, and of course, with SV2-exclusive features locked out for SV1 voicebanks. If this is easy enough to implement, I believe it can make SVS2 attractive so SVS1 owners even if they don’t like the engine.
while you can’t purchase synthesizer v 1 dreamtonics vocals, synthesizer v 1 3rd party vocals seem to be available still. at least from most 3rd party vendors and are usable in the second engine.
the issue is that while the voicebanks might have the same name and the same voice provider, they sound different between svs1 and svs2. like I’ve mentioned, svs2 moca is notorious for sounding off in svs2
ah yeah, i can see that. i have never used moca but i’ve never really heard anything bad about her sv2 voice or that it sounded different so i was unaware.
Well, I have searched the entire forum and cannot find anyone saying she sounds “off” - does that just mean not identical to the SV1 version? Could you quote your source(s) for this statement please?
