So are they going to address the problem or not? They better. As I said, rolling back the graphics driver is not an option here.

Well I did get another reply RE Graphic Drivers...

Hi Mark,

Thank you. We will keep that in mind as well.

So I guess they are aware of it now.

I just discovered that my post to the ticket with the process monitor trace never made it onto the ticket. Just RARed it and resubmitted.

THANK YOU 1000 times!!!

You are welcome

markrobotham wroteWell I did get another reply RE Graphic Drivers...

Hi Mark,

Thank you. We will keep that in mind as well.

So I guess they are aware of it now.

This is a Community forum.
Presonus does not visit here very often an only unofficially.
If someone can definitively describe the issue and fix f that issue I can pass it on to development.
Thanks

Update from Support:
http://answers.presonus.com/28563/why-a ... 564#a28564

My support ticket has gotten no responses from PreSonus in two days, and I'm still stuck with a non-functional v4.

Roll back and see what happens. Then roll forward. You got got nothing to lose.

Okay, I've run with the information from the person here:

viewtopic.php?p=173092#p173092

I have just tested a slew of NVidia drivers, all against my EVGA GTX 980 Ti Classified Edition. Here is a summary of the findings:

388.31 - Works
388.43 - Works
388.59 - Works
388.71 - Works
390.65 - Broken
390.77 - Broken
391.01 - Broken
391.24 - Broken
397.93 - Broken (released 5/24/18)

I can confirm that it's actually related to the 39x.xx series of GeForce drivers. This list was more comprehensive, and I felt it was worth the time to test to see exactly when things changed in a fashion PreSonus needs to accommodate. In all cases, the behaviour when it works is a successful run of the program and an ability to use it, and the behaviour when it's broken is a silent hang at "Scanning Plug-Ins...", with Process Monitor reporting absolutely no events after speaking with amazonaws servers successfully. Past that, it does nothing when running against a 39x.xx series driver.

It is -not- feasible to keep the video driver outdated simply for the sake of one application which is not coded to work properly. I have dozens of appliications which all want/need the latest driver at any given time, and which are optimised for the latest. I can't hold my system back for Studio One. I have re-upgraded to the latest GeForce driver at this time, and need to wait for Studio One to be fixed.

PreSonus, please fix this ASAP. It's simply unacceptable.

markluljak wroteOkay, I've run with the information from the person here:

viewtopic.php?p=173092#p173092

I have just tested a slew of NVidia drivers, all against my EVGA GTX 980 Ti Classified Edition. Here is a summary of the findings:

388.31 - Works
388.43 - Works
388.59 - Works
388.71 - Works
390.65 - Broken
390.77 - Broken
391.01 - Broken
391.24 - Broken
397.93 - Broken (released 5/24/18)

I can confirm that it's actually related to the 39x.xx series of GeForce drivers. This list was more comprehensive, and I felt it was worth the time to test to see exactly when things changed in a fashion PreSonus needs to accommodate. In all cases, the behaviour when it works is a successful run of the program and an ability to use it, and the behaviour when it's broken is a silent hang at "Scanning Plug-Ins...", with Process Monitor reporting absolutely no events after speaking with amazonaws servers successfully. Past that, it does nothing when running against a 39x.xx series driver.

It is -not- feasible to keep the video driver outdated simply for the sake of one application which is not coded to work properly. I have dozens of appliications which all want/need the latest driver at any given time, and which are optimised for the latest. I can't hold my system back for Studio One. I have re-upgraded to the latest GeForce driver at this time, and need to wait for Studio One to be fixed.

PreSonus, please fix this ASAP. It's simply unacceptable.

I think you need to cut them some slack here, this looks like quite an unusual problem, and there is a very good workaround for the moment. It could even be an nvidia issue for all we know (we just don't know yet).

I'm running a GeForce 1070, with version 397.93 (the very latest driver) on Windows 10 running Studio One V4. Absolutely no issues at all. We've got another Windows 10 user running a NVidia Geforce 1050 without issue as well.

The guys with problems who have signatures present all have Windows 7 in common. They are also running an NVidia GeForce 650 and an EVGA GTX 980.

Kev4, Talvin, deepho - Again can you please update your signatures with your OS version and display adaptor make and model at the very least (and anybody else posting here who may have it working or not). This will help us nail down the issue further, we need to see what you have in common - right now it seems to be Win7 and the latest nVidia drivers.

Windows 7 users - please absolutely make sure your Windows update is fully up to date - latest service pack and everything... even the option updates - run it several times.

markluljak wroteOkay, I've run with the information from the person here:

viewtopic.php?p=173092#p173092

I have just tested a slew of NVidia drivers, all against my EVGA GTX 980 Ti Classified Edition. Here is a summary of the findings:

388.31 - Works
388.43 - Works
388.59 - Works
388.71 - Works
390.65 - Broken
390.77 - Broken
391.01 - Broken
391.24 - Broken
397.93 - Broken (released 5/24/18)

I can confirm that it's actually related to the 39x.xx series of GeForce drivers. This list was more comprehensive, and I felt it was worth the time to test to see exactly when things changed in a fashion PreSonus needs to accommodate. In all cases, the behaviour when it works is a successful run of the program and an ability to use it, and the behaviour when it's broken is a silent hang at "Scanning Plug-Ins...", with Process Monitor reporting absolutely no events after speaking with amazonaws servers successfully. Past that, it does nothing when running against a 39x.xx series driver.

It is -not- feasible to keep the video driver outdated simply for the sake of one application which is not coded to work properly. I have dozens of appliications which all want/need the latest driver at any given time, and which are optimised for the latest. I can't hold my system back for Studio One. I have re-upgraded to the latest GeForce driver at this time, and need to wait for Studio One to be fixed.

PreSonus, please fix this ASAP. It's simply unacceptable.

Thanks
What screen resolution?
The seems to be narrowing in on resolutions.

I'm running windows 7 pro (fully updated) and geforce GTX 1050

My Windows 7 -is- fully updated.

Resolution: 2160p (4k)

I also have output dynamic range to full for HDR, but it's just as broken in Limited mode. vsync enabled, 60Hz.

This is fascinating....does this mean that Presonus released 4 without testing it with the latest Nvidia graphics card and driver? is that really possible?
If I'd paid money for this I'd be pulling my hair out in a mad rage

I'm also on Windows 7 (Ultimate 64 bit) and I have a Nvidia 1070 graphics card.

talvin wroteI'm also on Windows 7 (Ultimate 64 bit) and I have a Nvidia 1070 graphics card.

I'm not prepared to reconfigure my computer to make faulty software work my friend..mainly because I aint clever enough
when they fix it I'll buy it..looking forward to not using Cubase anymore...

cheers,

talvin wroteI'm also on Windows 7 (Ultimate 64 bit) and I have a Nvidia 1070 graphics card.

I have the same but I'm on Windows 10 and it's working.

kev4 wroteThis is fascinating....does this mean that Presonus released 4 without testing it with the latest Nvidia graphics card and driver? is that really possible?
If I'd paid money for this I'd be pulling my hair out in a mad rage

It looks like Nvidia/latest drivers and windows 7 combination right now, that situation could change but everybody is reporting this under Windows 7 so far.

I don't expect Presonus will be testing every graphics card on every OS. Most software developers/QA testers would not have any time for that. Also most devs use the latest OS, so it stands to reason most testing will be done on that OS.

PreAl wroteI think you need to cut them some slack here, this looks like quite an unusual problem, and there is a very good workaround for the moment. It could even be an nvidia issue for all we know (we just don't know yet).

I'm running a GeForce 1070, with version 397.93 (the very latest driver) on Windows 10 running Studio One V4. Absolutely no issues at all. We've got another Windows 10 user running a NVidia Geforce 1050 without issue as well.

The guys with problems who have signatures present all have Windows 7 in common. They are also running an NVidia GeForce 650 and an EVGA GTX 980.

Kev4, Talvin, deepho - Again can you please update your signatures with your OS version and display adaptor make and model at the very least (and anybody else posting here who may have it working or not). This will help us nail down the issue further, we need to see what you have in common - right now it seems to be Win7 and the latest nVidia drivers.

Windows 7 users - please absolutely make sure your Windows update is fully up to date - latest service pack and everything... even the option updates - run it several times.

And for the list now a NVidia GeForce 640 GT
Windows 7 with the latest update etc. I was also with the latest GFroce Driver but because of these driver problem with S4, i've rolling back.

PreAl wrote

talvin wroteI'm also on Windows 7 (Ultimate 64 bit) and I have a Nvidia 1070 graphics card.

I have the same but I'm on Windows 10 and it's working.

kev4 wroteThis is fascinating....does this mean that Presonus released 4 without testing it with the latest Nvidia graphics card and driver? is that really possible?
If I'd paid money for this I'd be pulling my hair out in a mad rage

It looks like Nvidia/latest drivers and windows 7 combination right now, that situation could change but everybody is reporting this under Windows 7 so far.

I don't expect Presonus will be testing every graphics card on every OS. Most software developers/QA testers would not have any time for that. Also most devs use the latest OS, so it stands to reason most testing will be done on that OS.

If it's a supported OS, it should have been tested, full stop.

EDIT: I would add that they should have tested it in the state they expect -us- to run things, which is fully updated, including the video drivers. This was completely avoidable.