Studio One Pro Update Releases?

[Vocalpoint]

Unfortunately, the push to implement improvements and more features can often result in triggering more bugs.
Currently, here's the list of all the features/improvements and bug fixes since the release of Studio One Pro 7.

New Features and Improvements (22 total):
● 30-day demo version now available
● New virtual instrument “Cinematic Lights”
● “Transform to rendered audio” option for busses
● [Impact] Envelope controls for in-place editor
● [Impact] User-definable crossfade for looped samples
● Grid and event visibility improvements
● Note Event selection and editing improvements
● Multi-out instrument bus improvements
● New commands for Launcher
● Option to keep speaker format on bounce in place
● [Note Editor] Added Lydian and Locrian musical scales, also for Atom [SQ]
● Status indicator for transformed tracks, busses, and channels
● Moving/Copying Note Events with arrow keys now follow scale setting
● Improvements for Italian localization 1
● Splice extension updated to v1.1.1, requires Studio One 7.0.1
● Ability to set "follow key" from Studio One
● Populate BPM filter when turned on with the project's current BPM
● Added "Your Library", "Collections", Pack pages
● Support for fractional time signatures
● Improved visibility of grid lines behind translucent Events
● Improved DAWproject compatibility
● Improved visibility of selected vs. unselected Tracks and Channels

Trucky

As a long-time S1 devotee - I am not going to pick on specifics with your list of "new" features. Except to say that at a few on here - are either a tad laughable (easy to see those I think) or they are really just "fit and finish" that the crew probably should have delivered back on Oct 9.

There are about 10-12 here that do actually fit the definition of New Feature and of course we appreciate that

But the math does not lie - given the gusto/vibe of that keynote video, how much time has elapsed since the v7 launch - AND the never-ending list of things that are still broken/requested for Studio One - if delivering say - a baker's dozen of actual features and improvements since Oct 9 is considered "success" - I am sure you can understand why some of us remain disappointed (and worried)

Here's to hoping for a better list soon.

VP

 

[AAV]

I for myself wouldn't count "30-day demo version now available" as a feature

I wouldn't either because I bought the upgrade and paid for a year of +. But to be fair, this was widely and broadly requested on many/most forums. I would say it was definitely one of the most requested/demanded/criticized (for lack of it's availability) features. That's the thing about features - they're not everybody's favourite requests or needs.

 

[Vocalpoint]

I would say it was definitely one of the most requested/demanded/criticized (for lack of it's availability) features.

The issue with listing this at all (if it is not obvious enough already) is that it should have been available on Oct 9.

VP

 

[ianaeillo]

I think anyone trying to make tempo changes will find the "tempo map" incredibly un-intuitive and clunky (almost unusable at times) - constant need to use Undo as each attempt to add another change in tempo goes wrong. If ever there was a need for a list editing function for tempo, then this is it.

And don't get me started on Scrolling and particularly Auto Scroll which switches itself off.

That is how I feel about tempo map and strip silence. Both things that feel like a “we will refine that later” from V1.

 

[OneBass]

Does anyone have inside insight into what impact (if any) the sale of PreSonus to Fender has/will have on the continued development of Studio One?

I wonder to what extent it's the same programmers maintaining and enhancing the software; likewise for its long range vision.

 

[RobWJ]

Presonus should take a leaf out of Blackmagic Design DaVinci Resolve's book.
A one-time license of $300 and free updates for decades.
And the speed with which they release new features is remarkable.
They support the programming with their Hardware.
Similar to Presonus, they also have Hardware.

But maybe in a different world and life

 

[Vocalpoint]

Does anyone have inside insight into what impact (if any) the sale of PreSonus to Fender has/will have on the continued development of Studio One?

I wonder to what extent it's the same programmers maintaining and enhancing the software; likewise for its long range vision.

I am sure there are some key users on here with lots of insight. All of it wrapped in a nice warm fuzzy NDA.

As far as "vision" and long range - Presonus (like many other vendors) has been tight lipped. They never announce anything until it''s ready. Never talk publicly about dev plans and certainly no chat from the C Suite on where it's all going.

FWIW - I never bought into the "Fender" stuff from the beginning. Simply because most people believe "Fender" is the parent here when in reality - they too are just one of a long list of companies (like Presonus) actually owned by the "real" owner - which is Servco Pacific Inc.

So who really knows who is calling the "real" shots from the "real" top.

VP

 

[apessino]

Unfortunately, the push to implement improvements and more features can often result in triggering more bugs.
Currently, here's the list of all the features/improvements and bug fixes since the release of Studio One Pro 7.

[...]

Sure, except that none of the bugs I mentioned were introduced by these new features - we are talking about functionality that has *never* worked correctly (or completely). And once egain, these are easily reproducible, acknowledged problems. The lack of prioritization for core issues is what I find concerning.

 

[lokeyfly]

I for myself wouldn't count "30-day demo version now available" as a feature

I have to say, I would count it as a feature. It may not be your feature, but the 30 day demo version absolutely needed to be caught up. One of might offer the v.7 demo to a friend, or client, who is just wishing to explore Studio One. Obviously, we're all looking at what we feel best serves our own needs. The demo release isn't going to send us doing backflips, but it's absolutely a feature. Like it or not.

I'm not going to get caught up in the expectations on this subject on a whole.
There were statements made by the Presonus staff in their v7 sizzle video, of how many releases they will make in the coming year. I believe it was three to four. Customers have a right to hold them to that, because that was a premise on which customers bought in (and purchased). I respect that, no matter my situation which is largely comfortable getting on with what has been entirely working for me. Heck, I may cruise for two or three years with the current version 7. That is unless there is some major milestone advancement. So if you guys want to hold them to their claims, good going. You obviously are expecting something that will provide improvement to your workflow. Currently, I might hope that is greater launcher features (and a few of my own recomendations). So fight the fight. But let's not cherry pick that a demo isn't a feature. It is.
Oh, and pack a good set of C rations and dry socks, and keep it cordial because you're probably going to be dug-in, on this hill for a while.
Peace, out.

 

[Vocalpoint]

I have to say, I would count it as a feature. It may not be your feature, but the 30 day demo version absolutely needed to be caught up. One of might offer the v.7 demo to a friend, or client, who is just wishing to explore Studio One.

If the demo was available on Oct 9 - you are bang on. But dropping it months later and then branding that a "new feature" is a bit rich. I mean that ranks right up there with changing a color in the Presonus corporate logo and calling that new. Does not wash with me unfortunately.

Given the obvious outcry of "Where is the demo" starting on Oct 10 (at least on some of the forums I frequent) - this was a huge miss TBH.

I do not usually get riled up over potential updates etc - but going back to that keynote video - many things were said - that has still not transpired.

Like the bit (@ the 1:22 mark) about "Version naming being "time-based". I took this to mean instead that Studio One would no longer have a old school version number associated with it and we would see a transition to something like "Studio One Pro 2025.2" or similar. So far none of that has materialized.

On the positive - there is lot of potential here - as always. But not a lot of delivery.

If I can quote that keynote one more time - Gregor nails it at the 1:10 mark "We want to get MAJOR new features in your hands much faster"

So just do it.

VP

 

[AAV]

The issue with listing this at all (if it is not obvious enough already) is that it should have been available on Oct 9.

VP

We all have different wants/needs. I bought, so I am happy with the features I got (including the launcher that needs refinement) and also happy that resources weren't expended on rolling out a demo, especially since users unsure about a buy or subscribe decision could have easily paid for a month or two of plus and tried it out. But that's me, and I understand that some (like you, clearly) see it differently. It's still a feature, the argument is really whether it was soon enough. C'est la vie. In a year I might be grumbly about something I need, but right now, I'm glad to have upgraded from 6.x to 7 and whatever comes along.

 

[lokeyfly]

@ Vocalpoint. It's probably best described as part of the update (and it was bulleted as such).
I do remember someone saying (no names) from here on out, new releases will provide users new features, quicker. I'm just thinking that was indeed the case, here. That said, I'm not entirely sure getting customers features quicker has any advantage. Particularly when there could likely still be bugs to be worked out.
Of course the demo is a little rich in claim. There was always a demo on the onset of every past release. Only, the version 7 release was likely a move to get going or else (by the powers that be), and that's what we're all kind of faced with as consumers/staff. Hey, I'm glad you guys are chasing them down. I won't, but as I've said in the past, I can ride right out of town, with what I need, and not pay another red cent. I'd be happy. I'm not entirely sure through the years, new releases made new or immediate product by customers. Sure, a couple of years might do that. I tend to think of snow ski equipment. Those latest binders, boots, and ski designs don't really produce improved skiers. Time on the mountain skiing, does.
Just my silly point is all.

 

[Vocalpoint]

We all have different wants/needs. I bought, so I am happy with the features I got (including the launcher that needs refinement) and also happy that resources weren't expended on rolling out a demo, especially since users unsure about a buy or subscribe decision could have easily paid for a month or two of plus and tried it out. But that's me, and I understand that some (like you, clearly) see it differently. It's still a feature, the argument is really whether it was soon enough. C'est la vie. In a year I might be grumbly about something I need, but right now, I'm glad to have upgraded from 6.x to 7 and whatever comes along.

I am not that broke up about it. And yes - of course I see the utility - but disagree on the timing. And especially calling it a "feature".

If a demo is anything in this ultra competitive space - it is a bloody "requirement" really.

VP

 

[Vocalpoint]

I tend to think of snow ski equipment. Those latest binders, boots, and ski designs don't really produce improved skiers. Time on the mountain skiing, does.

Just as I want to really get the Launcher into my workflow. But "time in the Launcher - launching" - in this case - is not a recipe for improvement when the tool I am trying to use - has nothing but a handle.

This thing screams "Awesome" but is so basic - it has become a negative instead of a positive.

I gave it all I could and am now back to Arranging the old-fashioned way - and work is getting done.

Major downer for a "Major New Feature" - Faster - I guess.

VP

 

[lokeyfly]

Just as I want to really get the Launcher into my workflow. But "time in the Launcher - launching" - in this case - is not a recipe for improvement when the tool I am trying to use - has nothing but a handle.

This thing screams "Awesome" but is so basic - it has become a negative instead of a positive.

I gave it all I could and am now back to Arranging the old-fashioned way - and work is getting done.

Major downer for a "Major New Feature" - Faster - I guess.

VP

True, true.
It's the things we use a lot, or we're use to using a lot that impacts workflow the most. I'd find new launcher features fun, and even newly creative if done correctly. Sort of a skip by matrix and hear new ideas from. But I'd give that up in a heartbeat for some simple velocity metering instead of that silly on/off indicator. Variable velocity indicators would produce a more visual and dynamic dashboard along the instrumen tracks. Will they do that? Years mentioning it, and no results tells me they refuse to change anything near the core of the program. As I see it, it wouldn't have to be a major modification at all. What we're left with are instrument on/off indicators (trigger is all) no different than the Kristal audio engine. How's that for decades development?
I do understand your points, my friend.

 

[Craig Anderton]

I don't know if the two are connected, but the music industry is not healthy right now. The pandemic sugar high is gone, there's a glut of used gear, and many companies are struggling. I don't know whether PreSonus is affected by this, but the industry as a whole is. That means fewer new users and fewer people spending money on gear. Tariffs are the coup de grace. I just heard from two companies. One has $100K of product coming from China on a cargo ship in LA but since the time it was shipped, it will now cost the company $240K to get it off the boat, and they can't afford it. Another company shipped $50K of product to China before tariffs when into effect, but it was returned because the Chinese distributor couldn't afford the tariff when it arrived. MI companies have to juggle a lot right now.

Of course, PreSonus will continue to add features and fix bugs. Whether they're significant is in the eye of the beholder. For me, being able to render buses, improved gridline visibility, and better handling of multi-output instruments are big deals. Also, .dawproject compatibility has come a long, long way since it was introduced. It's a standard with long-range importance, so I'm glad it's being improved instead of abandoned. It has the potential to be the ultimate tool for those who wish program A had the features of program B, but want to stay mostly in program A. Then again, I might have a different perspective if I was using Apple Silicon...

I've been dependent on software in my business since the 70s. If there's one thing I've learned, it's that software is always a moving target for developers and users. My philosophy is to use what I've got, because that's all I can do. Software has a long history of not meeting the expectations of the companies that make it, or the consumers who use it. On the other hand, I'm sooooo happy not to be buying reels of 2" tape, lapping heads, and doing window splices

 

[Lukas]

Does anyone have inside insight into what impact (if any) the sale of PreSonus to Fender has/will have on the continued development of Studio One?

I do have some insights, but as Vocalpoint rightly mentioned, I obviously can't share any internal information that isn't public.

That said, the acquisition happened back in 2021/2022, so it's been a while. Everything that's happened since then - and how Studio One has evolved - is out there for everyone to see. So it's not really a mystery, everyone can judge for themselves based on what's been delivered.

In addition:

I wonder to what extent it's the same programmers maintaining and enhancing the software; likewise for its long range vision.

It is still the same brilliant team and some very good friends of mine working on Studio One. That's not a secret either: You could see the whole Hamburg-based development team (where Studio One is made) listed on https://presonussoftware.com until recently. Over the past few years, the team has actually grown steadily. (Looks like that page was taken down recently, though.)

If you’re interested in the core team behind Studio One, I did an interview with Matthias Juwan (the creator of Studio One and now Vice President of Technology at PreSonus) that you might find interesting.

Kreatives.org

Kreatives.org is the personal website and blog of Matthias Juwan, intellectual father of Studio One DAW and original developer of KRISTAL Audio Engine and the CCL application framework.

kreatives.org

Here's the English translation (kindly translated by @Trucky):

https://lukas-ruschitzka.com/content/interview-matthias-juwan-2019-english.pdf

Sure, a few years have passed since the interview, but everything in there still gives a good idea of who’s behind Studio One. And while big decisions are always made behind the scenes, PreSonus is still pretty transparent compared to a lot of other DAW companies.

 

[Lukas]

Didn’t Presonus say they were going to roll out 4 major updates per year?

Not really. V5, V6, V7 are major updates. What was announced were 3-4 feature releases per year.

Major version: Big new version (6 → 7)
Minor version: Feature updates (7.0 → 7.1)
Hotfix: Bug fixes / maintenance updates (7.1.0 → 7.1.1)

 

[Vocalpoint]

Gonna have to correct (disagree) you there Lukas.

The whole point of that keynote was to completely do away with whiz bang “every two years” big updates and dissolve these major releases down into 4 month chunks on an ongoing basis. While charging us perpetual users annually - instead of every two years.

But if you are actually telling me that a “major” Studio One V8 is scheduled to come out in October 2026 - that whole keynote chitchat, annual update plan and all the rest of that video makes zero sense in any way.

VP

 

[Lukas]

...and dissolve these major releases down into 4 month chunks on an ongoing basis.

Yes, that's what I was saying.