176 postsPage 9 of 9
1 ... 5, 6, 7, 8, 9
No, I don't think that.
They have tested under several Win 7 conditions (NVidia, AVG, ...).and contacted several third parties to fix. AVG has supplied a patch. Nvidia has not.

You have a choice of:
1) Reporting to the third party and waiting for the third party to make a version that works.
2) Migrating to a newer OS.
3) Downgrading the NVidia driver

1) For HELP Read the Manual.
2) Create a SUPPORT TICKET. "Select Submit a Request".
3) For Comunity Help add your specs to your SIGNATURE AND.
Include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce
Detailed how to HERE.

My Website, Free Studio One Advance Training
SPECS:Win 10 64-bit, 12 Core i7: 32Gb DDR4 ram, 40" 4K monitor, StudioLive 24, Quantum, Faderport16, Central Station Plus, Sceptre 6,Temblor T10, Eris 4.5, HP60, Studio One Pro 4.0, Reaper 5.9, Sonar Platinum
User avatar
by PreAl on Wed Jul 11, 2018 6:52 pm
We've got one person working on Nvidia 1070 and one person who isn't. So do the math.

We've also got somebody here saying Presonus can't be bothered to fix it and yet they simply can't be bothered to update their signature with the specs (and be helpful). Nothing like a guessing game (please don't expect us to trawl through the thread finding your specs).

Studio One Pro 4, Faderport 1, Focusrite Saffire Pro 40, Maschine Studio, Octapad SPD-30, Roland A300, Windows 10 Pro 64 bit.
EVGA Geforce 1070 (Nvidia drivers). A bigly amount of other gear.
User avatar
by martin14 on Thu Jul 12, 2018 1:07 am
jpettit, You seem to patrolling around these threads just being an apologist for Presonus.
After all these reports, from all these Presonus customers, you're telling me they should totally pass the buck and refuse to do the slightest bit of proper diagnostics! I don't mean this trial and error, but at least they should go back to their boot process and do some simple code/sub-routine elimination.

And then either they could do a simple workaround -- eg. maybe it's happening with the animated blue border on the VST scan window or something innocuous like that. Would take their coder a few mins of his/her time to bypass that and see the effect. Then they could go back to Nvidia and give them some useful info to work on.
User avatar
by PreAl on Thu Jul 12, 2018 7:56 am
Go and apply for a team leader job at Presonus perhaps.

martin14 wrote"refuse to do the slightest bit of proper diagnostics! I don't mean this trial and error, but at least they should go back to their boot process and do some simple code/sub-routine elimination.



What on earth are you talking about? You are certainly no developer. Are you applying to be the next Dr Who?

Because Presonus are REFUSING right? Quote please then.

Studio One Pro 4, Faderport 1, Focusrite Saffire Pro 40, Maschine Studio, Octapad SPD-30, Roland A300, Windows 10 Pro 64 bit.
EVGA Geforce 1070 (Nvidia drivers). A bigly amount of other gear.
User avatar
by jpettit on Thu Jul 12, 2018 10:15 am
Here are some more details on this situation.
It is still being looked into as a corner case but the best options at this time are:

This is the current state of affairs with what works and what does not work.
viewtopic.php?p=173532#p173532

A second workaround is to decrease the resolution.

Because some versions work and others do not it appear to be an NVIDIA issue.

1) For HELP Read the Manual.
2) Create a SUPPORT TICKET. "Select Submit a Request".
3) For Comunity Help add your specs to your SIGNATURE AND.
Include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce
Detailed how to HERE.

My Website, Free Studio One Advance Training
SPECS:Win 10 64-bit, 12 Core i7: 32Gb DDR4 ram, 40" 4K monitor, StudioLive 24, Quantum, Faderport16, Central Station Plus, Sceptre 6,Temblor T10, Eris 4.5, HP60, Studio One Pro 4.0, Reaper 5.9, Sonar Platinum
User avatar
by ionian on Mon Jul 23, 2018 10:43 pm
Definitely a presonus issue. The most recent Nvidia driver worked with 3.5 but doesn't work in 4 so whatever Presonus changed between 3.5 to 4 in the startup routine broke the functionality with the Nvidia driver.

NVidia has nothing to fix. Their driver does what its supposed to and works with the video card. If it borked the video card, then they'd have something to fix. But the issue is clearly with SO4 as SO3.5 works fine with the driver. Therefore the onus is on Presonus to fix whatever it is they changed on the startup routine as it worked before but doesn't now.

I have a GeForce 750 Ti. I had to roll back from the most recent driver to 388.13. This is current as of today, July 23rd as I updated from 3.5 today to 4 and experienced this for the first time.

Also I don't like all that extra garbage so I do a manual install. There's no nvidia experience or driver update checkers running in the background. So those can't be causing any issues.

"For every man who has ever lived, in this Universe there shines a star."
- Arthur C. Clarke
User avatar
by donaldbaarns on Tue Jul 24, 2018 12:06 am
ionian wroteDefinitely a presonus issue. The most recent Nvidia driver worked with 3.5 but doesn't work in 4 so whatever Presonus changed between 3.5 to 4 in the startup routine broke the functionality with the Nvidia driver.

NVidia has nothing to fix. Their driver does what its supposed to and works with the video card. If it borked the video card, then they'd have something to fix. But the issue is clearly with SO4 as SO3.5 works fine with the driver. Therefore the onus is on Presonus to fix whatever it is they changed on the startup routine as it worked before but doesn't now.

I have a GeForce 750 Ti. I had to roll back from the most recent driver to 388.13. This is current as of today, July 23rd as I updated from 3.5 today to 4 and experienced this for the first time.

Also I don't like all that extra garbage so I do a manual install. There's no nvidia experience or driver update checkers running in the background. So those can't be causing any issues.


Whatever... I'm not sure how you account for the fact that it's working for some people on Win7 with the latest Nvidia driver, and not others.

Or the fact that it's working in Win 10 with the latest Nvidia drivers.

So while I can't say for sure (nobody on the outside can), just because it ran on a previous version of S1, doesn't mean it's a PreSonus issue.

We've all seen specific games not work with certain releases of nearly all video drivers. I read the "Know issues" sections of their release notes. Often it's specific resolutions, or refresh rates, or some other detail, but it seems every release has some game or app that doesn't work IF all the factors come together.

Again: I can't say for sure, but if I were using Win7, I'd be sure I'm also reporting it to Nvidia. Let them point the finger at PreSonus if that's the case. Or just revert.

Your call, over my pay grade to figure out who actually has the issue.

Best either way, and I hope a resolve is found soon.

Don

Studio One v4.x Professional - latest version
PreSonus Studio 26
Eris E5s
iZotope RX6 Advanced
Windows 10 Pro x64-16 GB RAM
MacOS High Sierra (10.13.3) iMac i5 w 8 GB RAM


Free: Narrators Toolbar Lite (Simple but powerful editing tools.)
https://youtu.be/nNKa2rKn3ug

FB group for Studio One Users - Audiobooks, VO and Podcaster focused:
https://www.facebook.com/groups/StudioOneNarrationVO/

Studio One and iZotope RX Tutorials for Narrators/Podcasters/VO/Dialog:
https://www.youtube.com/user/RedBaarnsAudio
User avatar
by PreAl on Tue Jul 24, 2018 1:54 am
^
Yup. It's not an open and shut case.

Studio One Pro 4, Faderport 1, Focusrite Saffire Pro 40, Maschine Studio, Octapad SPD-30, Roland A300, Windows 10 Pro 64 bit.
EVGA Geforce 1070 (Nvidia drivers). A bigly amount of other gear.
User avatar
by tuzemec on Fri Jul 27, 2018 2:11 am
That's what I've got from the support team yesterday:

It is still being worked on by the Studio One Developers for a later Studio One update. Please keep an eye out for bug fixes in Studio One update release notes.

Win7, Studio One 4, RME 802, Faderport 1, MSI 1070 Gaming X
User avatar
by Just After Midnight on Sun Aug 12, 2018 12:51 pm
I am having this issue as well. Rolling back my video driver did not fix it. Disabling my antivirus did not fix it.
User avatar
by PreAl on Sun Aug 12, 2018 1:03 pm
Just After Midnight wroteI am having this issue as well. Rolling back my video driver did not fix it. Disabling my antivirus did not fix it.


Can you confirm what your specific issue is please.?
Exact version of Studio One?
Operating system?
Have you tried removing, restart and adding back the plugin scan paths.

Studio One Pro 4, Faderport 1, Focusrite Saffire Pro 40, Maschine Studio, Octapad SPD-30, Roland A300, Windows 10 Pro 64 bit.
EVGA Geforce 1070 (Nvidia drivers). A bigly amount of other gear.
User avatar
by Just After Midnight on Sun Aug 12, 2018 1:15 pm
PreAl wrote
Just After Midnight wroteI am having this issue as well. Rolling back my video driver did not fix it. Disabling my antivirus did not fix it.


Can you confirm what your specific issue is please.?
Exact version of Studio One?
Operating system?
Have you tried removing, restart and adding back the plugin scan paths.


The same issue as everyone else - Studio One v4 gets stuck during boot process at "scanning plug-ins"

I'm using windows 7. Have I tried removing, restart and adding back paths? Do you mean the path being specified within the options of s1? If so, then no. S1 won't launch.
User avatar
by Just After Midnight on Sun Aug 12, 2018 1:49 pm
Just to update - I rolled back my nvidia gfx driver to an even earlier version (387.92) and now s1 v4 will launch. Problem solved. Hopefully Presonus sorts this out soon so we can keep our drivers up to date.
User avatar
by PreAl on Mon Aug 13, 2018 1:48 am
Just After Midnight wroteJust to update - I rolled back my nvidia gfx driver to an even earlier version (387.92) and now s1 v4 will launch. Problem solved. Hopefully Presonus sorts this out soon so we can keep our drivers up to date.


We can't make the assumption if it's Presonus problem. It's more likely an Nvidia problem with Windows 7 (although we don't know own 100% Further info already on this thread). You may be able to run slightly later drivers if Windows update is fully up to date (run it multiple times). If you want to use the latest drivers update to Win10.

Studio One Pro 4, Faderport 1, Focusrite Saffire Pro 40, Maschine Studio, Octapad SPD-30, Roland A300, Windows 10 Pro 64 bit.
EVGA Geforce 1070 (Nvidia drivers). A bigly amount of other gear.
User avatar
by peludismo on Mon Aug 13, 2018 5:13 pm
Hi. I bought Studio one 4 artist yesterday and I'm having this problem as well. I'm on Windows 7 and my nvidia driver is up to date. I found out that runing Studio one as administrator solves this problem, the only downside is that you can't drag and drop files (I guess it's a security measure runing as administrator).

Check if it works. Hope it gets patched up soon.

Update: Well, it turns out that sometimes it works and sometimes it doesn't. I guess I'll try to rollback my nvidia drivers.
User avatar
by PreAl on Tue Aug 14, 2018 9:11 am
peludismo wroteHi. I bought Studio one 4 artist yesterday and I'm having this problem as well. I'm on Windows 7 and my nvidia driver is up to date. I found out that runing Studio one as administrator solves this problem, the only downside is that you can't drag and drop files (I guess it's a security measure runing as administrator).

Check if it works. Hope it gets patched up soon.

Update: Well, it turns out that sometimes it works and sometimes it doesn't. I guess I'll try to rollback my nvidia drivers.


If it works for you but would not advise running as as admin all the time. Another thing would be to try and create a new user account and run it under that. More likely to be drivers though as you say

Studio One Pro 4, Faderport 1, Focusrite Saffire Pro 40, Maschine Studio, Octapad SPD-30, Roland A300, Windows 10 Pro 64 bit.
EVGA Geforce 1070 (Nvidia drivers). A bigly amount of other gear.

176 postsPage 9 of 9
1 ... 5, 6, 7, 8, 9

Who is online

Users browsing this forum: Damageplan and 10 guests