markluljak wroteI literally (in the old sense of the word) tested all the drivers from 388.31 forward. The problem definitively starts with the 39x.xx.

They didn't have to test -every- driver on Win7. Testing against just the most recent would have illustrated the problem.

As far as it being NVidia's problem? No. Not when the entire line of 39x.xx drivers is not accepted by v4, but v3 runs just fine on them, as does every other application and game I run. When even v3 runs fine on the latest, I don't know how you can even hedge on this. You're being an apologist. That multiple people here have tracked it down (and I have a complete list of drivers and their results back to 388.31) is indisputable. Good luck saying our evidence isn't evidence. You're incorrect. It's -damned- conclusive. I'm not -jumping- to anything. I spent 1.5hrs doing PreSonus' own work last night -proving- it empirically. I have all the proof I need, as I ran the bloody empirical experiment myself. I -do- have proof. I did more work on it than you (or PreSonus, for that matter) have done, by far, so don't even try to invalidate that effort.

And your "solutions" aren't. They're gross hack workarounds. Rolling back your drivers to suit one program is ludicrous, especially when games expect and are optimised for the latest drivers. You have a vary myopic view of video drivers if you recommend that with a straight face. I can only assume you use your computer for a single purpose, because that's frankly insane for a multi-use system. Rolling back to v3 negates 100% of the value of having purchased v4. How you think either is a valid option is beyond comprehension.

I'll agree to disagree...vehemently.

Credit to the original discoverer of the conflict for giving me something to run with so I -could- test empirically.

jpettit wroteIMHO People on a 9 year old operation system should consider themselves lucky that it is still supported as long as they were not running the 32 bit version of S1.

PreAl wrote

jpettit wroteIMHO People on a 9 year old operation system should consider themselves lucky that it is still supported as long as they were not running the 32 bit version of S1.

Yup, application and hardware/driver support on Win7 is fading fast (good luck with the latest games lol).

markluljak wrote*facepalm* Turning...off...the...shader...cache...
No application is worth resorting to such [edit] manoevers. If it can't be run normally, it won't be run here.

markluljak wroteWin10 is an MS-spyware-infested [edit] with a lousy GUI by comparison. I'm waiting until almost the last possible minute before grudgingly upgrading. I'm especially not looking forward to MS Office unregistering itself and having to spend three hours on the phone with MS convincing them to reactivate what I've legitimately purchased because their code [edit]. I have better things to do for now.

markrobotham wroteThanks 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, .... reinstalled, again everything went as it should, ... reopened and stuck again, frustrating. Like I said V3 works fine and looking at some of the replies, I`m not the only one.

martin14 wrote

markrobotham wroteThanks 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, .... reinstalled, again everything went as it should, ... reopened and stuck again, frustrating. Like I said V3 works fine and looking at some of the replies, I`m not the only one.

Yes, exactly the same problem for me too!!

(I'm running Windows 7 64bit)

ps. I managed to generate a screen capture by clicking on another open app on my other monitor -- see attached JPEG image -- showing where it hangs on the dreaded "Scanning Plug-Ins..."

Funkybot wrote1. Are you using Nvidia drivers?
2. Have you read the thread and tried downgrading your Nvidia drivers? if yes, same result? If not, is there a reason you can't? If not, try it.
3. You should be seeing another window pop-up that performs a quick plugin scan, is that window just not coming up at all?

PreAl wroteTurning off the shader cache takes one minute. It's under Nvidia control panel->3D settings, change it and apply. Then reboot. If it does not work merely change it back. Could not be more simple.
It would be useful to at least know if this makes it work or not with latest driver/Win7.

martin14 wrote

PreAl wroteTurning off the shader cache takes one minute. It's under Nvidia control panel->3D settings, change it and apply. Then reboot. If it does not work merely change it back. Could not be more simple.
It would be useful to at least know if this makes it work or not with latest driver/Win7.

I just did that. No difference.

martin14 wroteAnother diagnostic observation:

~ Only after completely rebooting Windows 7 can I successfully launch S1v4.
~ However, after exiting Studio One v4, I cannot subsequently launch it again -- just hangs (so I have to re-start the PC).
~ But Studio One v3 has no problem booting.

Therefore something is definitely wrong with S1v4 .

ps. If it helps, Presonus are welcome to send me over a 'developer' version of S1v4 which produces a full boot / process trace log file (I'm sure they have one) and I can send them back the resultant log file.

PreAl wroteAfter Studio one is "closed"...
Check task manager and kill off any Studio One processes then perhaps it will start up again. Or perhaps turn audio interface off and on .. that may release a "stuck" audio driver.

martin14 wroteAnother diagnostic observation:

~ Only after completely rebooting Windows 7 can I successfully launch S1v4.
~ However, after exiting Studio One v4, I cannot subsequently launch it again -- just hangs (so I have to re-start the PC).
~ But Studio One v3 has no problem booting.

Therefore something is definitely wrong with S1v4 .

ps. If it helps, Presonus are welcome to send me over a 'developer' version of S1v4 which produces a full boot/process trace log file (I'm sure they have one) and I can send them back the resultant log file.