Studio One 7.2.3 - Discussion Thread

[sintil8]

And like the option to review and hold off - if I so choose. The time has come for Presonus to impress me.

VP

I think we can take that as a given. I just like to keep a positive vibe...
My take, you catch more bees with honey than you do with vinegar, but yes get the cane out when needed.

Best and kindest regards

 

[Lukas]

I want to know from @Ari if the PreSonus team will be working on a major update for Studio One in the near future. If so, when exactly this update will be released and what significant new features this update will include. Personally, I consider this general secrecy regarding software developments to be absolutely unprofessional and developed without the actual users/customers. Unfortunately, this affects almost all software companies. I am certainly not alone in this opinion.

Since you're surely familiar with how Studio One updates are released and communicated, you know that we can’t share any details about ongoing development. New versions are announced once they’re ready (or as part of a marketing campaign ahead of release). All I can say is that, of course, new versions of Studio One are in development.

 

[Vocalpoint]

Personally, I consider this general secrecy regarding software developments to be absolutely unprofessional and developed without the actual users/customers.

There is gigantic host of reasons why companies keep their development close to the vest. Presonus is no different.

This is a business and a VERY competitive one at that.

If you are a car maker - you don't go around broadcasting your new designs to everyone - before it comes to market.

VP

 

[carlosjuvandes]

Could someone confirm if the fades are working good using Melodyne on the new update v7.2.3

 

[carlosjuvandes]

I had tested it again with v7.2.2 and worked good with fades... But the v7.2.3 not, it gives some clicks

 

[Crossinger]

I had tested it again with v7.2.2 and worked good with fades... But the v7.2.3 not, it gives some clicks

Oh no - we already had this in 6.6.1

EDIT: @carlosjuvandes Can you provide a minimal example here for the bug? I no longer have the file for the issue back in 6.6.1. And right now, on my Mac with 7.2.3 and Melodyne Assistant 5.4.2 I cannot reproduce the issue. But maybe I'm missing a specific step to cause the clicks.

 

[Midiboy]

Since you're surely familiar with how Studio One updates are released and communicated, you know that we can’t share any details about ongoing development. New versions are announced once they’re ready (or as part of a marketing campaign ahead of release). All I can say is that, of course, new versions of Studio One are in development.

100% agree. Not sure why some people think this is "unprofessional" when in reality it is the exact opposite. Imagine what would happen if a company were to announce what features were coming in the next version and one of two things (or both) happened...

1) Another company steals the idea and beats the original to the punch...
2) Something happens and said "promised" feature isn't ready for the next release.

Anyway, Lukas and Ari, I for one really appreciate all you do for the community and whatever your involvement is with Presonus, keep it up! You do great work.

 

[carlosjuvandes]

Oh no - we already had this in 6.6.1

EDIT: @carlosjuvandes Can you provide a minimal example here for the bug? I no longer have the file for the issue back in 6.6.1. And right now, on my Mac with 7.2.3 and Melodyne Assistant 5.4.2 I cannot reproduce the issue. But maybe I'm missing a specific step to cause the clicks.

I already did a video. I'm gonna post it later

 

[Kisnou]

Actually, this question is quite easy to answer. I want to know from @Ari if the PreSonus team will be working on a major update for Studio One in the near future. If so, when exactly this update will be released and what significant new features this update will include. Personally, I consider this general secrecy regarding software developments to be absolutely unprofessional and developed without the actual users/customers. Unfortunately, this affects almost all software companies. I am certainly not alone in this opinion.

Here's my 2 cents on your comment. Most companies do not share the development of updates, so I really don't understand how can you define that unprofessional. It is quite the opposite - a professional behavior, expected by a company like Presonus or Ableton or any other.
What I partly agree with (and I hope that's what you meant) is that we don't have the good old 'presonus feedback forum' anymore (I might be mistaken, was it called Presonus Answers..?) where people could actually vote for feature requests and they would normally get implemented in a future update. So that may cause the feeling that we're not really an active part in the development anymore, and on that I would agree with you.

I wish there could still be a place or a platform where people can post feature requests and get votes by the community. But calling their behavior unprofessional is just wrong.

 

[Sombreuil]

The problem isn't the frequency of updates, but the lack of communication by Presonus.
They have changed their business model so often in the past few years that it makes everything confusing. They didn't need to say 3 or 4 major updates each year, it was obvious to everyone that it was a lie they couldn't handle.

The only thing that happened to users like me is that, at the end of the day, it costs me twice as much as before to stay up to date when it comes to bug fixes, and I'm prisoner of a subscription model.
We can discuss for days whether or not they did provide enough updates, the only thing that I notice is that I need to spend way more money for the same thing, and if things keep going like this, for actually less content.

 

[Jens]

Let's take a look at what other DAW makers are doing.

Cubase: They used to run a poll after every release. Expression maps improvements always made it high on that list (usually 4-5th place) for 6+ years. When that feature request (BTW like many others) didn't make it in the next release people were expressing disappointment in the forum and the Steinberg PR guy always responded the same way: Expression maps improvements remain a top priority but it just didn't make it this time.

FL Studio: If I'm not mistaken the PR/developers of this DAW talk in their forum about the general direction they want to take their DAW in the future responding to user requests to streamline its unusual workflow. Progress in this direction is slow and I don't think it will ever happen because it would require a rewrite of their DAW with backward compatibility and a re-education of their user base.

Point is: Statements of PR people are meant to tame/manipulate their users and prevent them from switching to other DAWs for as long as possible. They are meaningless.

 

[Jens]

The problem isn't the frequency of updates, but the lack of communication by Presonus.
They have changed their business model so often in the past few years that it makes everything confusing. They didn't need to say 3 or 4 major updates each year, it was obvious to everyone that it was a lie they couldn't handle.

The only thing that happened to users like me is that, at the end of the day, it costs me twice as much as before to stay up to date when it comes to bug fixes, and I'm prisoner of a subscription model.
We can discuss for days whether or not they did provide enough updates, the only thing that I notice is that I need to spend way more money for the same thing, and if things keep going like this, for actually less content.

Is this actually true?

PreSonus don't communicate future features. Nothing has changed.

The feature set of the perpetual pro licence was not reduced. Nothing has changed.

The new subscription includes software/sounds that previously needed to be purchased in their shop. Nothing was essential to the core tasks of a DAW and pretty much anything could be replaced by purchasing it from independent developers. Some of it was/is third party anyway, so the PreSonus shop was partially a reseller like amazon.

There were around 3 major updates each year. Nothing has changed. (And they didn't promise anything, they just stated their intention. I never understand what the fuss about the video is about.)

Bugfixes are provided for the current version and not retrospectively. Nothing has changed.

Free updates are provided only for a year. This looks significantly shorter than the previous 2 year period. But there was always a 6+ month long period where no major updates were provided. Plus, the price for new customers was halved. The update price for perpetual users was kept the same but perpetual users can easily wait a few month to match the previous cycle for updates like before or wait longer if features are unconvincing.

 

[Sombreuil]

If you wait, you don't get the bug fixes updates. I still stand to what I said, it's now 12 months of support compared to 24 months for the same price.
And I'm only talking about the full price, which was easily avoided by waiting a few month, so I basically never paid more than 99€ for an update.

Now though...

 

[Jens]

If you wait, you don't get the bug fixes updates. I still stand to what I said, it's now 12 months of support compared to 24 months for the same price.
And I'm only talking about the full price, which was easily avoided by waiting a few month, so I basically never paid more than 99€ for an update.

Now though...

You never got 24 months of feature releases. You're just repeating the same argument I challenged in my previous reply. And you didn't even bother to argue any of my responses to your other claims either.

Bugfix releases are not bound to any active licence time frame. There are 3 bugfix releases since Jun 3, 2025, the release of 7.2. Which means there is almost 5 additional months of bugfix support.

You also know that a feature version introduces new bugs, for the new features and existing ones, so updating instantly makes no sense. And again, if things are too expensive for you or features are unconvincing, you just wait and optimize cost per feature.

 

[Sombreuil]

You never got 24 months of feature releases. You're just repeating the same argument I challenged in my previous reply. And you didn't even bother to argue any of my responses to your other claims either.

Because your answer to any counter argument is that "I don't care what Presonus said, people who took their word for it shouldn't have."
"Other companies that actually communicate are just doing meaningless PR stuff". FL Studio has a beta you can try before the update actually comes out, but I guess it's just another meaningless PR useless stuff.

Also, you're right, there is always 6 months of nothing each each, which also applies to v7 and still costs twice as much. They have two months two release two major updates and they are the ones who promised those, not me. You can call it "intension" "whishes" or whatever you like, they did say it was their plan and if they fail to accomplish that during the first year, I do understand the people who are afraid of the futur of Presonus, especially since they have changed their pricing about 4 times in the past 4 years.

You also forgot to answer the part where I said that, by waiting a bit, which I always do, you could buy an update for much cheaper through Thomann or whatever. Now, how would you do that? You can do all the mental gymnastics you want, it will cost you twice as much over a period of 24 months.

Subscription modesl are the poison of the decade, I can't even comprehend that someone could disagree with that, I'll admit that.