• 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

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 ....
I'm not sure how one from support or development, chase items or complaints passed that were noted on Reddit without any relevent one-on-one feedback. Copy/paste problems, delete, latency, and so forth reflect individual occurences. Not global.

I dont suggest some dont have issues. I do suggest it doesn't bolster any one's own individual issue(s) with their installing v7.2. that they need to stress some kind of massive problems list, elsewhere. Probably best to keep one's issues within their own confines. Also starting a thread would be a good idea as this is getting quite long. I keep seeing a new post under "new" and this topic keeps re occuring.
Just a case in point, this repetative subject matter debacles the point of this thread.
Then again, I could be wrong. (Shrug)
Keeping it friendly of course.
absu, I would really start my own thread on this, if you please. TY.
 
absu, I would really start my own thread on this, if you please. TY.

This ^
I would also support all relevant posts here being moved to that thread (contain the loop).
 
lokefly: "absu, I would really start my own thread on this, if you please. TY."
Number6: "I would also support all relevant posts here being moved to that thread."


You both are right - but please only 1 bug/issue per thread!!!

Thanks
Ari
 
This ^
I would also support all relevant posts here being moved to that thread (contain the loop).
Agreed! Best idea of the day.
 
@absu

Ari already asked to keep things friendly and to let the discussion rest when it comes to issues that have already been reported and are being looked into. There's no need to bring them up again here. Please avoid posting further complaints about this update in this thread. If something still needs to be addressed, the best way is to report it directly to PreSonus Support - that's where it can officially be tracked and fixed.

If you have questions or other issues that haven't been covered yet, feel free to open a separate thread (as mentioned: one topic per thread). Just a reminder - this forum isn't official PreSonus support (neither official nor PreSonus support ;-)), and no one here is obligated to provide troubleshooting help. It's a community forum.

We're aiming to keep the tone respectful and the discussions focused - this isn't Reddit. Thanks for your understanding!
 
Why are you guys arguing this? but these issues are definitely happening to people.

I think it's because some users in here are making this sound like it's a COVID level event - with thousands upon thousands of users falling victim to a poorly tested release.

When in reality - it's more like 200 - 8 of which are in here.

I have been using S1 since 2011 - and have put this release through my usual rigorous client level workouts this past week - and exact none of those Google Ai generated baddies above have surfaced here.

I have had nothing but the usual stability and maturity that S1 always brings.

If people would dial down the drama - I think the temperature would lower as well.

VP
 
Last edited:
I have had nothing but the usual stability and maturity that S1 always brings.
Same here. I think I read a ton of similar responses in Reddit. 😆
Ok..... A little levity goes a long way in getting the subject back on track.

My impressions so far with 7.2: I am really enjoying the continuous left and center scrolling modes. Both that, and the full on/off select [F] that now works with Autoscroll. To the point that I keep forgetting to load Sub Zero Bass. I blame the devs for doing too good a job!
 
I can't disagree. I love the 7.2 update. I've used the Sub Zero Bass several times already and it's pretty great! While I did roll back to test a few things, I am currently using 7.2 and can wait until the patch for the fixes for what I am dealing with. None of them are critical to my normal workflow.
 
I must say, I do find it downright odd that bug-reporting wouldn't be permitted on a 'release version discussion' thread...

On virtually every one of the many forums that features a 'product/version announcement' for vendors, this is standard practice.

If the issues aren't shared across users you simply respond with some form of 'nope, not having the issue'; this is quite a simple thing to do and no molotovs get thrown.

Someone claiming a bug is almost seen as a threat by some in this thread which provokes a hostile/reactionary response... the defensive tone is very uncalled for and frankly quite toxic.

Bug reporting and feature discussion are the two main ways we make software better, and most importantly to enlighten other users as to whether the issue in question is shared or only exists on their end.

Everybody just chill, be helpful (if not kind) and take in that beautiful Summer weather Ari mentioned earlier!
 
I must say, I do find it downright odd that bug-reporting wouldn't be permitted on a 'release version discussion' thread...

On virtually every one of the many forums that features a 'product/version announcement' for vendors, this is standard practice.

If the issues aren't shared across users you simply respond with some form of 'nope, not having the issue'; this is quite a simple thing to do and no molotovs get thrown.

Someone claiming a bug is almost seen as a threat by some in this thread which provokes a hostile/reactionary response... the defensive tone is very uncalled for and frankly quite toxic.

Bug reporting and feature discussion are the two main ways we make software better, and most importantly to enlighten other users as to whether the issue in question is shared or only exists on their end.

Everybody just chill, be helpful (if not kind) and take in that beautiful Summer weather Ari mentioned earlier!
TD,
yes, can I just add to that...
New user's coming to Studio One might be reading this forum for help, it's up to us to make them feel welcome, if we want a vibrant community.

Kindest regards
 
I must say, I do find it downright odd that bug-reporting wouldn't be permitted on a 'release version discussion' thread...

On virtually every one of the many forums that features a 'product/version announcement' for vendors, this is standard practice.

If the issues aren't shared across users you simply respond with some form of 'nope, not having the issue'; this is quite a simple thing to do and no molotovs get thrown.

Someone claiming a bug is almost seen as a threat by some in this thread which provokes a hostile/reactionary response... the defensive tone is very uncalled for and frankly quite toxic.

Bug reporting and feature discussion are the two main ways we make software better, and most importantly to enlighten other users as to whether the issue in question is shared or only exists on their end.

Everybody just chill, be helpful (if not kind) and take in that beautiful Summer weather Ari mentioned earlier!

No one has a problem with bug reporting, quite the opposite - I have listed a bunch of issues I had before this update and no one argued with me. It's the litany of repeated complaints or the insane hyperbole ("this update is a disaster!", "they did not test this at all!", etc.) that people get annoyed of.

It's not being defensive, it's just the normal reaction to the entitlement and over the top melodrama that some people bring to the discussion. That behavior is the toxic part, and it's actually quite encouraging that, at least in this forum, that attitude is nipped in the bud.
 
Is this debate still continuing?

Nobody has issues with reporting bugs, if you think you've got an issue start a new thread, write down steps to reproduce, try and get it reproduced, and then here in this thread, for fun, link here and ask people to reproduce the issue, and state your specs.

Rather than declare people that they are far more experienced, and the poster responding is too young to be taken seriously (and then when somebody responds it's that it is irrelevant, complain that they are banging on about their experience, and then write an essay about how experienced they are).

Rather than write a gazillion posts that they must be fanboys and think that other people's problems are not existent. Believe me if there are problems I WANT to know about them.

Rather than declare that they are very important because this is used in their day job, as though they are the only people who do this here.

Rather than post an AI summary presenting a distorted view of the Reddit forum without any references. There aren't loads of people complaining. Looking through Reddit (although the original poster didn't supply a single URL reference).there *may* be an issue with freezing and AMD CPU's which *could* be down to the system config, or not, it needs to be troubleshooted and reproduced. The OP has a Ryzan, it would be good then to see if he has Windows fully up-to-date with windows update and that his motherboard BIOS is updated, maybe turn off some C States, but I suspect if that was suggested it would be overridden by *it only started happening after the last studio one update, therefore it must be studio one* yada yada.

Rather than see if anything gets better by disabling antivirus, because "it worked before" ignoring the fact that a brand new executable has been installed and their antivirus could be handling this "different" application (as far as it is concerned) differently. Symptoms being described *could* easily be a consequence of locked files, but hey no, what a silly suggestion I made.

Rather than do a load of posts about how much they are being victimised because their self diagnosis cannot be questioned (i.e. studio one worked until I upgraded it!!! Therefore it's obvious Studio one is at fault).

Rather than paraphrasing the first paragraph of what somebody has written, whilst completely ignoring the rest of what was written.

Rather than attacking people who are stating literal facts, that they cannot reproduce any specific issue (which of course is difficult to do because full steps aren't being provided) and that things are working well for them, which basically means more info and troubleshooting is required, in order to investigate if it's actually a config issue or an actual bug (yes it has to be a bug because AI says so!). It may be disappointing that others don't have the same problem as you, but please stop jumping to the conclusion that they are doing it just because you think they are praying to the God of Presonus on a daily basis, it gets boring.

Studio one may very well be at fault, but again, post a thread with clear steps to reproduce, rather than pointlessly bombard this thread full of emotional posts, and then tell people to "be nice".

People want to help, but if you aren't helping them by showing what the specific actual issue is, and merely declaring that it's all a buggy mess, this is what you get. It's not helpful to them and it's not helpful for people who want to help, but the poster needs to demonstrate specifically their problems, rather than throw the toys out of the pram.

I look forward to further responses quoting/cherry picking just the first line of what I said and editing out/ ignoring the rest of what has been said.
 
Last edited:
It's the litany of repeated complaints or the insane hyperbole ("this update is a disaster!", "they did not test this at all!", etc.) that people get annoyed of.

This.

VP
 
Lets think about probabilities on this issue. I've taught a couple of course on statistical analysis at the college level, mainly focusing on Multi-Variant Regression analysis.

Lots of folks are still on 201x systems running Windows 10, a no longer supported system. Lots of folks are running W11 on more modern machines. We have different types of users, from hobby to professional, we also create different types of music , we have an highly complex set of tools in PC and Apple VT's that can have programming that interacts with not only the DAW but other vst's. No matter what DAW you buy you can expect that a "bug" has a possibility who chance of happening is defined by a statistical probability that all of the variables outside the DAW programing can cause issues. When you try and define your issue you should know the difference between you hypothis and the Null (the analysis will only all you to know if the Null fails). Presonus has provided a way to provide information for a bug report. A couple of hundred users using varied systems and plugins does not have a probability that in my opinion (I have not run the analysis which could right or wrong) leaded to the DAW being the primary cause of such issues. Most PC setups are unique and allow for combinations of operating system, programs, and addons like virtual instruments. The actual cost of system which can handle all of these issues would be beyond what most people could pay. Rational management says try and add tools which the majority of users what first and add others as time/budget allows. Most people react emotionally and focus on their specific needs. My guess is that for the current version there that current users of SO1 7.2 is say 75% of all current users of the program. 200 people reporting the same error is statistically insignificant and would have lower value to the producer of the product than a true bug effecting say 5% of users. The dark tone of many of these replies shows our focus or the "me mentality" as well as the current pressure on professional users. Even as an amateur, I know the frustration as I got caught by the ilock/AMD 9000 series issues and was without the program I use from the newer Opus EW stuff. The fix took around 6 weeks to be released. EW west proved Play to all the Opus users as a work-a-round and it was not their fault, not the same but it allowed for similar work. Does a bug kill your workload, go back to the SO version that allows you to work. File a proper report and keep in contact will support. Adapt and survive. Just my 2 cents.
 
Last edited:
Thanks to the admins for turning off loop mode.
Let the decent friendly conversation continue!
 
Back
Top