What plug-in is it stuck at? Watch it and try and find out. You may need to uninstall something temporarily. Also, make sure a plug-in isn't throwing up a dialog box like expired ilok demos do. If so, you need to click ok or continue or whatever for things to proceed.

Same thing here. I have a crazy 1772 plugins in my VST folder and on startup v4 hangs on every one, eventually saying "failed to scan ...."

Same problem here. So frustrating...

Otherwise S1 V4 rocks

Funkybot wroteWhat plug-in is it stuck at? Watch it and try and find out. You may need to uninstall something temporarily. Also, make sure a plug-in isn't throwing up a dialog box like expired ilok demos do. If so, you need to click ok or continue or whatever for things to proceed.

Thanks for the reply. It doesn't show anything, just the text that its scanning VST. I can`t even grab a screen shot to show, as it just freezes.

The first time you install, everything runs, vst scans etc, as normal. It`s after you close the program then come to open it again.

I uninstalled everything, had to search C drive for all reference to "Studio One 4" delete it only then could I reinstalled, again everything went as it should, I thought great I've fixed it, but closed the program, reopened and stuck again, frustrating. Like I said V3 works fine and looking at some of the replies, I`m not the only one.

markrobotham wrote

Funkybot wroteWhat plug-in is it stuck at? Watch it and try and find out. You may need to uninstall something temporarily. Also, make sure a plug-in isn't throwing up a dialog box like expired ilok demos do. If so, you need to click ok or continue or whatever for things to proceed.

Thanks for the reply. It doesn't show anything, just the text that its scanning VST. I can`t even grab a screen shot to show, as it just freezes.

The first time you install, everything runs, vst scans etc, as normal. It`s after you close the program then come to open it again.

I uninstalled everything, had to search C drive for all reference to "Studio One 4" delete it only then could I reinstalled, again everything went as it should, I thought great I've fixed it, but closed the program, reopened and stuck again, frustrating. Like I said V3 works fine and looking at some of the replies, I`m not the only one.

I have exactly the same issue! 1 to 1!
And i have made the same steps like you.

I even contacted support, but they obviously don`t read as they sent me the same reply to the license issue!

Manged to start OBS screen recorder going before opening Studio One. This is what happens...

https://youtu.be/BJt67MVNXls

Same problem here.

Not good... I bought the update but it's scary. Can I use V3 and V4 on the same computer just in case V4 have problem?

I also opened a ticket.

Still haven't heard back. Itching to get to get stuck in, been watching Studio One 4 Advanced from Groove 3 and I`m pretty impressed with the new version, just at the moment I cant do anything till this issue is sorted as its it always stuck on the VST scan. Gonna be away from Friday too until early next week.

You could rename your VST dirs to get the out of the way and see if it loads. Does V4 ask about importing V3 settings? I doubt if V4 on its own put all the correct paths in, unless it took from V3 prefs files. No clue. Just guessing

WaterlooSunset wroteYou could rename your VST dirs to get the out of the way and see if it loads. Does V4 ask about importing V3 settings? I doubt if V4 on its own put all the correct paths in, unless it took from V3 prefs files. No clue. Just guessing

Thank you, but i guess it has nothing to do with the plugins. It freezes before it "read scripts". When it watches for plugins..not when it scan for plugins.
Because after the first start scan all plugins and all has works perfect.

Yes i'm still wait of a answer. Nothing till now. It seems that it need some time to solve this issue.

I tried renaming folders and giving SO4 no plugin folders so that no external stuff is used. It doesn't solve the problem. The second time Studio One start it hangs again. It only helps to delete the settings file...SO3 is running fine though.

Mine went through the initial scan of 769 plugins, and finished with that bit. It then installed the additional software to which I was entitled.

Upon restarting, it's now stuck at "Scanning Plugins..." and is -not- bringing up the external scanner which did the initial scan of my plugins. I've killed it with Iarsn TaskInfo and restarted it, but it hangs at the same place. It's not actually using any appreciable (if any) amount of CPU at all, according to TaskInfo. Not even 0.01%. No activity at all. No reads, no writes, nothing. It's a ghost.

The rest of my computer is remaining responsive, however. Studio One v3 still works, looks like. It's just v4 which is fouled somehow. (You have to kill v4 to be able to start v3.)

EDIT: Just submitted a version of this as a ticket, altering only the first sentence to make it clear that it's S1 v4.

At least it appear easy to replicate. Put your info in your signatures for the future. Run it as admin?

markrobotham wroteAfter the issues with the invalid license file, finally got Studio One 4 Pro to register, but after installing updates every time I open SO4 it just hangs on VST scan, then computer become unresponsive. Have to use reset button to restart computer. Have uninstalled, reinstalled etc, but just keeps hanging. V3 running as normal, but had to re-register that in my account to get it to show up to activate it.

https://support.presonus.com/hc/en-us/a ... g-ins-now-
Have you tried disabling the hanging plugin?

1) Running as admin yields no different behaviour.

2) It's no specific plugin which is hanging. All plugins were scanned on the initial launch. It's not even bringing up the plugin scanner on subsequent launches.

3) The plugin launcher log still has the contents of the initial successful scan, even though I've run S1 v4 at least seven times since. Likewise, the actual Studio One log itself is zero bytes, and remains as such no matter what I do. The plugin scanner shows the original scan completed successfully, so nothing broke inside that, as far as I can tell.