chichogp
Member
I had a similar experience after installing v7.1 and the problem solved itself with a clean install. Just uninstall Studio One altogether and install it from the most recent installer.
-
Hi and welcome to the Studio One User Forum!
Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!
Studio One 7.2 - Discussion Thread
- Thread starter Ari
- Start date
I did it yesterday, full reinstallation, and deleting studio one settings) in documents...
didn't help, I repeat, in 7.1.1 everything works fine))
Number6
Active member
Well I hate to say it, it works fine for me, so I would say no.
Software behaviour can change upon updating, it's how things interact, just because the last piece of software you installed made it go bad, that doesn't mean that's the real problem.
Number6
Active member
Full uninstall, then install. Not just reinstall.
chichogp
Member
In my case I formatted my PC. I'm not saying you should do that, I did it because I needed to format it anyway, but what I mean is uninstall and nuke every trace of the program in the usual folders (%appdata%, %programdata%, %programfiles%, etc.) and then do a fresh install.
Midiboy
Active member
It's definitely not just him....it's quite a few. None of these suggestions will really fix these issues. Already reported a couple of them to Presonus. They are aware and are working on fixes.
Vocalpoint
Well-known member
I must admit I am curious as to your version of Win 11 and the version of Universal control - both of which are old and out of date.
I am guessing there must be a reason for that?
VP
this is obviously strange logic, if it works fine for me, then it works fine for everyone else) and if not, then it's their problem)
and the answer is obvious)_ presonus didn't test the update at all)
it is possible that for you - studio one is one of the options for entertainment, but for me it is daily work) every day) and any similar bug - makes me lose money and time, and time is money)
Vocalpoint
Well-known member
Not even close to being "obvious". You have no verifiable evidence of what was (or what was not) tested whatsoever.
The only thing that is 100% certain is that Presonus did not test this - on YOUR system. At YOUR place - with YOUR unique setup.
Please do not speak for the rest of us (or make wild non-factual speculations on testing) simply because your system is suddenly exhibiting issues.
VP
Midiboy
Active member
Guys, this isn't really something to argue or get all upset about. Yes, there are bugs. Yes, Presonus is aware of them. Yes, they said they are working on them. It is nigh impossible for them to test every variable that every unique system brings to the table. I'm glad that some of you have had no issues! That's AWESOME. I usually don't have issues at all. I've done all the steps recommended to troubleshoot the issue, I sent the DMP files to Presonus. They were able to isolate the problem. It will be fixed. I have full confidence in that. It could be as simple as a MS patch that broke something that some have and other don't, it could be a DLL issue from another software program? Who knows! All I do know is that I'm not the only one having the issue, and Presonus told me that the devs are now aware of the issue and will be working on it.
So, you have two choices....continue with 7.2 and don't bother Detecting Tempo and ignore the wonky cursor issues, or go back to 7.1.1 until they fix it. There is likely not anything in 7.2 that is required for your daily work to be completed that is preventing you from going back to 7.1.1 until this gets fixed.
So, you have two choices....continue with 7.2 and don't bother Detecting Tempo and ignore the wonky cursor issues, or go back to 7.1.1 until they fix it. There is likely not anything in 7.2 that is required for your daily work to be completed that is preventing you from going back to 7.1.1 until this gets fixed.
are you blind )?), I have already repeated a hundred times that VERY many users EVERYWHERE complain about bugs
at the same time, I have never had such bugs in 5 years)) and I have made hundreds and thousands of projects in s1 since version 5.0
and now some youngling, to me, a person with more than 25 years of experience in the music industry, tells something about my computer, are you on Presonus's payroll?
Last edited:
Number6
Active member
You said:
Previous version works fine therefore it must be the latest version.
I repeat, that isn't a conclusion you can jump to, it could easily be an additional piece of software that worked with the previous version that isn't working with the new version. That piece of software may need updating to ensure compatibility and stability.
It works for me, therefore it works for you.
This is exactly the same strange logic as saying that the previous version works so the new version must be bugged (and yet it's working for others?. I think you missed my actual point here. Same flawed logic.
Let me give you my full quote
"Well I hate to say it, it works fine for me, so I would say no.
Software behaviour can change upon updating, it's how things interact, just because the last piece of software you installed made it go bad, that doesn't mean that's the real problem.
It may well be that the latest version of Studio one didn't handle the upgrade correctly, hence a full uninstall and then a new install is required."
What I would say if that if there were similar issues, this forum would be littered with others having the same issue. Maybe they will post here later.
One thing I can guarantee is that lots of people will be having problems with their configs after upgrade..it always happens, and mostly they are entirely different issues to do with their machine, or maybe they all have something in common, like they are all running Windows 10 and they need to run windows update. I'm just pissing on the wind guessing here.
You mentioned you had a dmp file, Google for "blue screen view" utility and please post a screenshot.
One thing I notice is you are running Windows 10, which leads me to believe it could be a programming library issue. If you want an easier ride, upgrade to latest Windows 11. That's what the Devs test on. They aren't going to be testing on every version of Windows.
Regardless after taking the advise here I suggest you start a new troubleshooting thread giving clear full steps.to repro so that others may reproduce.
BTW I'm 55 if that counts. 35 years of experience, not that it should count whatsoever.
Last edited:
OP
OP
Please stay friendly! It's summer (nearly) and the weather is great. 
It has already been mentioned that the problem has been reported and they know about the error. Databases have been updated in the background to ensure future compatibility. It has been written that the error has not yet occurred in 5 years. This is because the code was only installed a few months ago.
The problem with this bug is that it does not affect all users on all systems. Therefore, some are affected and others do not even know where the displeasure comes from. Therefore, the error was also overlooked because it simply did not appear on the systems tested. With absolutely every update, I can only advise everyone to create separate installation folders for 2-3 versions. All versions can be installed in parallel and do not interfere with each other in any way.
The bug will be fixed and thanks a lot for reporting it!
This thread should be reopened for other topics of this version.
All the best
Ari
It has already been mentioned that the problem has been reported and they know about the error. Databases have been updated in the background to ensure future compatibility. It has been written that the error has not yet occurred in 5 years. This is because the code was only installed a few months ago.
The problem with this bug is that it does not affect all users on all systems. Therefore, some are affected and others do not even know where the displeasure comes from. Therefore, the error was also overlooked because it simply did not appear on the systems tested. With absolutely every update, I can only advise everyone to create separate installation folders for 2-3 versions. All versions can be installed in parallel and do not interfere with each other in any way.
The bug will be fixed and thanks a lot for reporting it!
This thread should be reopened for other topics of this version.
All the best
Ari
Last edited:
Ari
My friends reporting about more bugs ,,,, crash with delete audio track .... crash then opening project (which is normal working in 7.1.1 )crash with opening spire ( which is work normal in 7.1.1 )
all of them is roll back and problems gone ...
this update is disaster ....
Several users on Reddit have reported various bugs in Studio One Pro 7.2, primarily concerning its stability and functionality. These include issues with copy/paste, freezing, deleting events, and latency problems. Additionally, some users have experienced crashes, glitching, and difficulty recording mono tracks.
Here's a more detailed breakdown of the reported issues:
General Stability and Performance Issues:
- Freezing and Unresponsiveness:
Users have reported Studio One becoming completely unresponsive, particularly when attempting to copy, paste, delete, or duplicate events.
- Crashing:
Some users have described Studio One crashing frequently, especially after updating to version 7. 2
- Latency Problems:
Some users have experienced red latency meters and issues with third-party plugins.
- Glitches and Pink Boxes:
Some users have reported screen glitches, pink boxes appearing, and Studio One shutting down, especially on newer Macs.
- Copy/Paste Problems:
Users have reported that copy and paste functions stop working randomly, requiring them to restart Studio One.
- Deleting Events/Tracks:
Some users have encountered issues deleting events or tracks, especially when working with audio files imported from Splice.
- Mono Recording Issues:
Some users have noted that mono tracks are being recorded as stereo in Studio One Pro 7, even when previously recording as mono in Studio One 6.6.
- CPU Spiking and Glitchy Clock:
Some users on Windows 11 have experienced CPU spiking and a glitchy clock, even with no plugins, which is exacerbated by the use of VST3 plugins.
- Several users suggest avoiding the update to version 7.2 or downgrading to a previous version (e.g., 7.1 or 6.6) due to the reported instability.
- Some users have found temporary fixes by closing and reopening Studio One or re-scanning plugins.
- Users are encouraged to report bugs to PreSonus.
They are obliged to test until the working version is listed as compatible on the manufacturer's website (and it is listed)
Number6
Active member
"Obliged" lol
You've got to be kidding if you think they have the time and resources to test all OS's, all hardware and specific configurations etc etc.
That's what we do.
I love the fact you've pasted a Google AI summary but show no specific sources (URLs), and most of these issues will happen for "several users" on every single release.
You've got to be kidding if you think they have the time and resources to test all OS's, all hardware and specific configurations etc etc.
That's what we do.
I love the fact you've pasted a Google AI summary but show no specific sources (URLs), and most of these issues will happen for "several users" on every single release.
Last edited:
Midiboy
Active member
Why are you guys arguing this? Seriously, folks. I get that you want to defend your favorite DAW. I love Studio One also, but these issues are definitely happening to people. Several are happening to me as well. And like I've said numerous times, I've already sent the info, including DMP files to Presonus, and they CONFIRMED the issues as bugs and are working on getting them fixed. I was actually impressed at how quickly they responded. These issues ARE being reported in several places online in various Facebook Groups, Reddits, etc.
Get over yourselves and stop making those of us that have bugs seem like we don't know what we are doing by saying things like, "Well, I've got 35 years experience, blah blah blah." Guess what? I have 25 years of Digital Recording experience myself, and almost 40 years of studio recording experience. (I'm 57). I also have been in IT as well as Medical IT for most of my life. I know what I'm doing as well, but I'm not flaunting my knowledge as superior to other people that are having issues.
Ari is the admin here, he asked people to stay friendly. He also confirmed that there are issues.
This is the main reason I stopped going to the official Presonus forums before they shut down, because people argue over stupid crap.
Please don't ruin this forum also.
Get over yourselves and stop making those of us that have bugs seem like we don't know what we are doing by saying things like, "Well, I've got 35 years experience, blah blah blah." Guess what? I have 25 years of Digital Recording experience myself, and almost 40 years of studio recording experience. (I'm 57). I also have been in IT as well as Medical IT for most of my life. I know what I'm doing as well, but I'm not flaunting my knowledge as superior to other people that are having issues.
Ari is the admin here, he asked people to stay friendly. He also confirmed that there are issues.
This is the main reason I stopped going to the official Presonus forums before they shut down, because people argue over stupid crap.
Please don't ruin this forum also.