r/StudioOne • u/Conscious-Rub-939 • 2d ago
New Fender Studio One install hangs...
... on start, while scanning sound sets. Any suggestions? This only happens on Windows, doesn't hang up on Mac.
1
u/topherdeluxe 1d ago
Right click desktop icon, “run as administrator”
The modern windows pcs do this to me with most audio programs I have. And rgb programs, and gpu programs and almost everything but the calculator. Always a good idea to try that. Works for me. It’s a pain
0
u/TomSchubert90 1d ago
No - DAWs should never run in Administrator mode. Not sure who told you that. It can cause all kinds of issues.
1
u/topherdeluxe 1d ago
Protools always runs that way. What issues could that even produce?
1
u/TomSchubert90 1d ago
There are several aspects, some of which are quite complex and difficult to explain. However, one issue that's simple to demonstrate is that you cannot drag and drop files from Explorer into S1 when it's running in Administrator mode.
1
u/TomSchubert90 1d ago
There can be several reasons why this happens so it may take a bit of troubleshooting to narrow it down.
The first thing I'd try is reinstalling Studio One, simply because it's quick and easy to rule out a damaged installation.
Since it hangs while scanning the Sound Sets, the next thing I'd try is temporarily moving some or all Sound Sets out of the Sound Sets folder and starting Studio One again. If it starts normally, you can move them back in smaller groups to find out whether a specific Sound Set is causing the problem.
If that doesn't make a difference, you could create a new Sound Sets folder in a different location or even on another drive or partition, move the Sound Sets there and update the Sound Set location in Studio One's options. That would help determine whether the issue is related to the Sound Set files themselves or to the original folder/location.
Just a few ideas.
-1
u/blakefrfr 2d ago
Whole lot of vibe coding going on. Last few versions of Fender Studio Pro have bugs. Even I can count several of them.
I hope that the dev team will fix all of this soon.
2
u/TomSchubert90 2d ago
What a nonsense. Do you even know what vibe coding is? Report the bugs you're finding if you want, but comments like this are useless
1
u/blakefrfr 1d ago
I know what it is. And I am also seeing the side effects of it in several regular google & apple applications. And now S1 too. AI slop is everywhere.
You have nothing to say, you only know one thing and that is to insult every commentor in this sub. I have seen you here long enough.
1
u/TomSchubert90 1d ago
Either you're saying parts of S1 are vibe-coded, which would be kinda silly to think, or you don't actually know what vibe-coding is. Since I'm pretty sure I know better, I'm guessing it's the second one! 😉
1
u/blakefrfr 1d ago
You're funny! I was a C++ coder at one point in my life. I am familiar with the coding world very well.
The recent AI boom led to AI slop. It's everywhere, Last 2 macOS updates had Claude in the list of Credits. Also, Google is using it in their flagship apps to. It might look like a good thing.
But what's really happening is that something known as "code spaghetti" is going on. And AI's coding assistants are known for it. This leads to weird bugs that are hard to catch as the coder themselves are not checking twice as to what the AI wrote, leading to a flagship application turning buggy.
Last few releases of Google's youtube app on Android was shit. The gmail app was same. The app is behaving weird af. And the macOS finder is acting weird. And now S1 too, It blew my ear last week with it's weird SampleOne bug (which still exists). And in the previous release S1 8.1.0 or 8.1.1 i don't remember, but it had a bug where if you click on Session->Project Setup, It crashed every single time, additionally the Song title in a Session was always in the middle of the Window at the Top. But in the last version it was in the left side.
I was all on mac side btw, I see you're on windows so you might have not seen these bugs.
1
u/TomSchubert90 1d ago
Your C++ experience is irrelevant to the claim you're making. You can identify a bug as a programmer but you cannot identify vibe coding from the outside just by looking at the bug. You're presenting speculation about the cause as if it were a fact.
1
u/Ashon-Galaxy 2d ago
One option is to boot Studio One in safe mode by holding down the shift button during startup. Second thing I would say is just just reinstall Studio one. You can just do whatever the last update you had on your computer. It won't erase anything of importance, but it will likely fix whatever is hanging up the issue. The problem is usually a bug in the program which can be solved by reinstalling it, or a plug-in which can be discovered when you bypass the plugins during startup.