Windows 10.2004 = Softube DOA

[WasteLand]

Alchemedia, I got a response from Softube support, and the fix actually worked.

Please go to the following location on your PC:
C:\Users\"username"\AppData\Roaming\Softube
Remove all txt files in that folder

'AppData' is a hidden folder so it might not show up be default. You can make it appear bu clicking 'Hidden Items' on the 'View' tab.

Let me know how you get on. Everything seems back to normal for me now.

wow, the effect of file with some values.. i assume they will written again..
but if this is solution, great! but strange, o well not strange, i must manually edit a txt file for a certain vsti, to let it work... only for standalone...

[Alchemedia]

Lucky you! Congrats!

Here's the response I received this morning from Softube tech support:
"The DAW-crashing problem you describe is currently, unfortunately, very common on Windows machines. When testing for the most recent update, a pretty critical graphics related bug slipped through the cracks. We're painfully aware of it, and our developers are working on a fix, to be released within a few weeks. A temporary work-around can be disabling Open GL for our plug-ins. It's sadly a bit of a coin toss if this works. For some it does, for others it does not. Normally this can be done in the options menu of our plug-ins, but by the sound of it you can't even get to those. You can manually disable Open GL by following the steps below:
1. Make sure your DAW is not running.
2. Go to the folder C:\Users\<$USERNAME>\AppData\Roaming\Softube
3.a. If the file “Softube Global Settings.txt” is there, open it and edit the line “USE_OPENGL BOOLEAN”, change “1” to “0”. Save."

This naturally didn't work for me. I'll try the alt suggestion you received and report back.

[Alchemedia]

Deleting AppData/Roaming/Softube dir did the trick, at least for now in Reaper, haven't tried my other DAW's yet. Thx so much WasteLand!

[LightGrenade]

Deleting AppData/Roaming/Softube dir did the trick, at least for now in Reaper, haven't tried my other DAW's yet. Thx so much WasteLand!

Not a problem! Glad you got it working. I couldn't believe it worked for me haha.

It's also pretty worrying that they have different support agents giving out different info haha. Oh well, I guess thats why we use forums!

[Alchemedia]

We are the champions my friend!

[WasteLand]

Deleting AppData/Roaming/Softube dir did the trick, at least for now in Reaper, haven't tried my other DAW's yet. Thx so much WasteLand!

it was lightgrenade that had this solution.

now i understand perhaps why modular erraticly crashes. with your message from softube.
i hope they fix it soon, softube and fixes, not always that fast... great stuff... but for the first time instability issues.. and the damned vermona module!

well the are "woke"..........

[Alchemedia]

Ah, yes, kudos to LG too!
As for Softube being "woke", we can only hope. This is really a long-standing intermittent game of whack-a-mole and I'm tired of losing.

[WasteLand]

i got today an e-mail, long overdue, but still. with the same advice, delete the .txt files. i already wanted do that, because of the instability of modular.

it works! and i can now even load the vermona module, when i am working in ableton live 10 suite, it crashed always immediately in that case...

strange, the .txt files, do not contain that special info, aren't complex, only the preset .txt files, perhaps there was an error.

or deleting them resets something, isn't the content of .txt important, but that a plugin reinitializes, perhaps.

o well. did beat modular, didn't crash, yet...

[Alchemedia]

I tried that too and it seemed to work, that is, until I rebooted my computer.

[mike841]

lfm, Dead On!
Anyone who gives you a "thumbs-down" is not affected. Probably because they have a pretty basic setup. But when your running the likes of multiple interfaces, multiple accelorators and multiple graphics cards on an i9-16 core cpu and you finally get your system locked and humming where you can offer full service to your clients (and yourself), the last thing you need is lack r&d from a vendor. And like you said, their blanket solution is always "change to this or update that" with no real regard for the serious end users and the interruption to their creative processes.

[SiliconDeath]

It's weird they can't fix this issue, maybe it takes too much resources for them to do it? I was looking to buy some new plugins from them, but after recently stumbling on these issues (after them working for long time without issue), I'm not so sure anymore.

[t.o.t.s.]

necrobump just to say its 2025, I've been having a lot of these same issues on WIndows 11 and I've been with Softube support on this easily since the beginning of Dec with no solutions as of yet and the ones presented here still aren't working. VST3 anyway. AAX don't seem to have these issues. a drag.