Voice AI 2.0.5 plugin crash when trying to process

i'm have the same problem here. but, only in local processing. when i click to processo in cloud works ok, but take credits. But when i click to process local the ableton crashes. my CPU its a 14900k, i'm using windows 11. ableton are update. i want to use the software but just cant because of this problem.

Same here in Cubase 13 - also in Bitwig and Samplitude. AMD Ryzen 5 Pro 4650G, 32GB RAM, WIN11

I opened a support request on this and for some reason, a short while after opening the incident, the version 2.0.5. just started to work after several un- and reinstalls.

However, it may be useful to report this issue to the same support engineer so it can be collected by support as an incident which occurs more than once. My support engineer was Arty. It may help to refer to this engineer when opening the request.

Arty also mentioned that a new version will be released soon. Maybe it resolves this issue as well.

Hi guys, 

Thanks for reporting the issue! We have reported it to our development and it is under investigation. We have reached out to you in individual support request threads for some additional information. 

If anyone else sees the issue, please submit a support request too. Many thanks!

Quick followup on this one:

We have a reason to believe that the issue might be related to having SoundID VoiceAI installed on a different/external hard drive. 

Alexander Lesswing Pablo Escobar Christian Froehner can you please try to reinstall it on the main C drive instead:

1. Uninstlal everything first, and remove all leftover files ad foldes as shown here: [WIN] How to uninstall SoundID VoiceAI
2. Reboot
3. reinstall the latest version on your main drive, download here

Let us know if that solves the problem, thank you! 

Hi Kärlis,

as explained in the support ticket, an uninstall and fresh re-install of 2.0.5. did work for me, (regardless of the drive) 

Update: I installed it, using the default parameters causing the software to be installed on the system drive as well which was obviously the reason why it worked again. 

This does not change the intention of the following paragraph:

Also, I want to add that the software should work on any drive the user selects to install it to. It's a truely irresponsible trait in the last years from software developers to just install their software on the system drive (C in most cases). The system drive is as the name says, a drive for the OS and not meant for all application binaries. Many users install a decent/fast SSD to have a swift OS running but as those SSDs are significantly more expensive, there is not that much space to be expected unlike most other storage in the system which provides more capacity with less performance. Just imagine if all software developers ask the user to install everything on the system drive, how big shall this drive be? 8TB? 10TB? 20TB? This is impossible as you know and a such, a software developer with reason and responsibility should always let the user decide where to install the software and the software should always work on the user provided storage. 

The installation on C in this case may apply for test purposes/workaround only but certainly not as solution.

Alexander Lesswing of course, you are correct. I'm not suggesting that the main drive should be a permanent solution - it should work on other drives too. 

Currently, we are only looking to confirm our suspicion that there is an issue when it is installed on a different drive. Bug fixes will follow once the issue is confirmed.

That's great! I am happy to assist you (did provide my results already to the ticket) to get this issue confirmed and solved in a future version.

I may sound a bit grumpy about this “use the system drive” thing but I had to extent the system partition several times already and even had to exchange the SSD with a bigger one just because so many software companies throw everything on the OS drive without any responsibility. appdata is bloated like hell and for music production, the VST3 also defaults to the system drive (although a symlink may work to reduce the data load on the OS drive). And I am sure not to be alone with those concerns about this trend.

We have reproduced the issue in-house too. Please stand by and use the main drive workaround for now, we will give you a heads up once a bug fix is released for this (shouldn't take too long, it will probably be inlcded in an update within a month or so).

Just installed version 2.0.6.6292. Crashing when trying to process under FL Studio win10.

Dawid Janek did you install it on the main boot drive as explained above, or on a different drive?

Kārlis Stenders I've Installed on different drive then c. It looks like some of the program especially the voices are installed in the default SoundID folder. Do you think I should reinstall to C?

Dawid Janek please have a quick read through the thread, and the workaround instructions above. We have explained that the issue is caused by having VoiceAI installed on a different drive. 

Hi just buyed VoiceAI perpetual , installed version 2.0.7.6346 for Windows on C_ drive and have the same problem during process in local mode the plugin freezes for a short time and then crashes and also the DAW , tried with Ableton 12.1 and Studio One 17. Only process in cloud works . 

Love the plugin, good work but this is a showstopper, there's maybe a solution about ?

Thanks !

I was just having the same problem. I can confirm that the work around fixed the crashing issue.

Hi everyone, thanks for standing by!

The problem has been resolved, and we have already pushed it out in a new update. Update to the latest 2.0.9, download here.

You can now also install the software in any drive you like, but do let me know if you see anything suspicious. Thanks again! 

Hi Kärlis,

As mentioned in the ticket mail already (including several screenshots as evidence), this issue has not been resolved. The option for a custom path simply got removed so that the software will be forcefully installed on the system drive. Basically switching a workaround to a permanent “solution”. A true resolution of this issue is to let the customer select a custom path and the plugin still works.

Thanks for the quic reaction Alexander Lesswing 

I have already sent you a reply in your support request thread, but I'll expand here too. I was in a bit of a rush earlier, so let me  elaborate:

• The DAW crash issue (or sometimes “One or more files couldn't be processed” error message) when VoiceAI is installed on a different drive is fixed.
• You are correct, the main installation now cannot be customized anymore. We have to admit that it was a bad idea to allow that in the first place, especially for the licensing service components, which can be subject to all sorts of errors if on a different drive. These take up very little space, though, so it shouldn't be a problem
• Common Assets install path can now be customized! This is what takes up most of the space, as the presets for offline processing are stored here.

That concludes the resolution of this specific bug, but we are not done with the development in this area yet: the cache folder will also be addressed in the near future. The cache folder contains the raw audio processing files, so it can get very sizeable. We will implement a custom install path for it too. This will probably be release with an update in a month or two, although I cannot provide any specific ETA for it right now.

I hope it makes sense now. Thanks to everyone involved in troubleshooting this - it is highly appreciated!

Fair enough. I can confirm that Common Assets can be installed on a different path and the installer automatically moves the already downloaded models to the new path as well. This reduces the binary load on the system drive by roughly 5GB which is very good. I am aware that Microsoft causes quite some trouble as they pushed this "all in one space" nonsense including the unintuitive rights management. I appreciate your efforts to minimize the footprint of your software on the system drive!

Alexander Lesswing update on the custom location for the audio cache folder:

The development of this feature is delayed, so we have implemented a temporary workaround. The custom path for the cache folder can now be set up via the settings.xml file, see instructions here: Setting up a custom location for the SoundID VoiceAI audio cache folder

Let us know if you're able to set it up successfully following the instructions in the article, thank you! 

Hi Kārlis,

I was able to change the cache location using the instructions on VoiceAI 2.1.5.

Looking forward to see it implemented as feature.

Thanks for the update. Great support. I really appreciate it!