Studio One 7.0.1 / 7.0.2 - Discussion Thread

[lokeyfly]

I also don't understand the rational behind changing the wave form view to 'mono' when track height is reduced. The whole point of the track view is to give you visual information regarding the tracks in your session, why the heck are they removing useful visual feedback from the track view??

This is quite jarring because I regularly have large sessions (many times over 100 tracks) where I used to be able to determine what tracks are what, just by looking at the wave forms, and this strange "collapses into mono" feature (or bug?) is a step backward. There seems to be no workflow enhancement or other purpose to this change, and if they are trying to mimic Logics wave form view, they shouldn't, because logics wave form view is trash.

Well, I'm certainly not diminishing your need to see stereo tracks. I certainly don't think it was a bug. I often use around forty-ish tracks of mostly stereo tracks and I really need to know where the audio resides, often over it displaying stereo. So merging the stereo into a larger rendition really helps with seeing positioning in a lot of cases. So I simply appreciate the larger scale. Yes, waveforms can be re scaled, but with stereo, they can often be too squished in appearance.

I guess the ideal scenario would be to select the preference. There's always the tracks section at left displaying stereo/mono.

You can perform certain tasks to view only the tracks that are playing. That might help you. Dunno. Just mentioning, it's an improvement for some. Logic certainly isn't some new kid on the block, and they also do this. Anyway, good luck. Maybe Studio One will give some options to this, eventually.

 

[starkid84]

Well, I'm certainly not diminishing your need to see stereo tracks. I certainly don't think it was a bug. I often use around forty-ish tracks of mostly stereo tracks and I really need to know where the audio resides, often over it displaying stereo. So merging the stereo into a larger rendition really helps with seeing positioning in a lot of cases. So I simply appreciate the larger scale. Yes, waveforms can be re scaled, but with stereo, they can often be too squished in appearance.

I guess the ideal scenario would be to select the preference. There's always the tracks section at left displaying stereo/mono.

You can perform certain tasks to view only the tracks that are playing. That might help you. Dunno. Just mentioning, it's an improvement for some. Logic certainly isn't some new kid on the block, and they also do this. Anyway, good luck. Maybe Studio One will give some options to this, eventually.

I agree that the stereo collapsing into mono view should be an option. My comment regarding Logic is in more in reference to devs attempting to mimic apple's UX approach to simplifying things, at the expense of giving their user base a choice to utilize a feature or not. A simple toggle switch goes sooo much further than an arbitrary 'always on approach' that may, or may not break established work flows.

I'm also aware Logic is not new. I remember using the last version of Logic 5 on PC as a kid when it was still owned by Emagic, (along with Reason 2.5 and gems like N-track Studio 3.x). I personally have never been a fan of how current iterations of Logic's default view collapses stereo waveforms to mono, unless you expand the track significantly. If Presonus wants to copy that functionality, then they should at least be mindful enough include the mono / stereo icon (little circles on the wave event in logic) that denotes whether a track is mono or stereo.

All in all I think we need to start challenging devs (and convince greedy shareholders) that it's in their best interest to give us more options and not less; even if that means burying toggles in an options menu to avoid cluttering the UI.

 

[lokeyfly]

I'm all for options, and that is ultimately the answer so that users can make that choice.

I don't believe it has anything to do with shareholders In the lleast. These type of additions rest on the laurels of the developers, and the feedback they receive. Potentially, more like lack of descent feedback. That seems to be the shortcoming.

Yes, I remember when Emagic were just climbing on board with sequencing with both Mac and then Atari ST. I'm pretty ok with everything that has happened with them since. Had they still supported the PC, I'd probably be using it.

Lets hope for a few more options. Not a ton of; but a few.

 

[whichi123]

Why not use a plug-in sandbox like bitwig to prevent project crashes? In version 7, I'm getting more crashes than ever.
Giving users a choice is better than nothing

 

[Lukas]

Why not

"Why not?"

Just some ideas: Sandboxing comes with a cost. It usually introduces higher latency, increases CPU and RAM usage and can make debugging more complex. "More crashes" usually means plug-ins are failing, not Studio One itself. Instead of relying on sandboxing, it’s more effective to identify problematic plug-ins and report them to the developers.

 

[whichi123]

"Why not?"

Just some ideas: Sandboxing comes with a cost. It usually introduces higher latency, increases CPU and RAM usage and can make debugging more complex. "More crashes" usually means plug-ins are failing, not Studio One itself. Instead of relying on sandboxing, it’s more effective to identify problematic plug-ins and report them to the developers.

I agree with you, but sometimes we also wish for some more timely and faster solutions. Therefore, we hope to provide more choices to those in need.
By the way, your tools is very good, I like it very much

 

[lokeyfly]

Why not use a plug-in sandbox like bitwig to prevent project crashes? In version 7, I'm getting more crashes than ever.
Giving users a choice is better than nothing

Sorry if I missed earlier responses, Did someone else complain of crashes? It sounds like your crash situation is yours only. In any case, a system crash is usually unique to One's own system, and there will be few upon a major release. It's why they are beta tested and then some.

There's a slew of questions that usually come up when someone is experiencing crashes after updating a product. I agree with the response to report the issue, as the nature of crashes is typical with one's own computer, what they may have additionally loaded, remaining used HD space, etc. Sandboxing besides being a weighty addition, adds a lot of complexity to something traditionally is on a case by case basis. That's my take, anyway.

You're system might be very lean, and you keep any problematic other software off your computer. Most users of Studio One, from what I've encountered don't. Hence, calling support about crashes works and is far better than building taller over sand.

 

[Vocalpoint]

I agree with you, but sometimes we also wish for some more timely and faster solutions. Therefore, we hope to provide more choices to those in need.
By the way, your tools is very good, I like it very much

The faster (and more timely solution) is always report your crashes and especially which plugins are causing them.

Been a Studio One user since 2011 - and I think I have had 2 crashes in total since then - BOTH plugin related.

S1 is extremely stable - if you give it a good operating environment and use known good standard third party plugins within it.

VP

 

[marrybanilow]

The faster (and more timely solution) is always report your crashes and especially which plugins are causing them.

Been a Studio One user since 2011 - and I think I have had 2 crashes in total since then - BOTH plugin related.

S1 is extremely stable - if you give it a good operating environment and use known good standard third party plugins within it.

VP

About 2 months ago, i had crashes almost immediately after opening sessions (on S1 7 only, S1 6 was fine - much like you, never really experienced any crashes). I went through all my plugins, updated all of them that had updates and removed any that weren't Apple Silicon ready, also disabled AU plugins so VST 3 only. It wasn't until i uninstalled a completely non-audio related bit of software called Magnets that the crashing stopped. I've mixed around 30 sessions since with S1 7 and no crashing whatsoever - until this week. Crashing and hard rebooting my macbook around every 5 minutes i would say. No new plugins since, and crash report gives no mention of any potential plugins that could be causing it.

I get that the opinion is plugins is likely the factor here, but the realtime behaviour is S1 6 does not exhibit the same behaviour and i've also been using Cubase 14 a fair bit out of frustration to get these sessions finished and seeing no performance issues there either. I have seen quite a few posts on FB with people exhibiting the same symptoms

 

[Vocalpoint]

About 2 months ago, i had crashes almost immediately after opening sessions (on S1 7 only, S1 6 was fine - much like you, never really experienced any crashes). I went through all my plugins, updated all of them that had updates and removed any that weren't Apple Silicon ready, also disabled AU plugins so VST 3 only. It wasn't until i uninstalled a completely non-audio related bit of software called Magnets that the crashing stopped. I've mixed around 30 sessions since with S1 7 and no crashing whatsoever - until this week. Crashing and hard rebooting my macbook around every 5 minutes i would say. No new plugins since, and crash report gives no mention of any potential plugins that could be causing it.

I get that the opinion is plugins is likely the factor here, but the realtime behaviour is S1 6 does not exhibit the same behaviour and i've also been using Cubase 14 a fair bit out of frustration to get these sessions finished and seeing no performance issues there either.

Well - I can't speak to Mac in general. There are simply too many variables in play with that OS series and each time Apple changes the game - users and (probably Presonus too) are left scrambling.

For Windows 10 22H2 - I stand by my statement. This is a bulletproof, tank-like environment that hasn't even thrown a single error since I built this DAW on Feb 3, 2024. I use VERY modern hardware, very limited plugins (ALL VST3) and have gone thru the last 4 versions of v6 and now two versions of v7

As far as v7 is concerned - I do agree. The development has slowed dramatically VS what we were led to believe back during that "keynote" video in late Sept 2024. We were supposed to see "faster" development, more bug fixes, more "good stuff" earlier and so on - and since then we have received two very basic maintenance releases (v7.02 being specifically VERY thin) and nothing more.

I will admit I probably took the high road on that announcement and filled my own head with excitement and what I know now - are clearly unrealistic expectations. The updates are not coming any faster and the "good stuff" is still not available. I mean we have 10 days left to go in January and still nothing. I think that last ultra light bug fix (v7.02) was last week of November...

While I have not had any troubles with v7 - it stands to reason that will just two maintenance releases - there is simply no way v7 will near as stable at v6.6.4 was at this point - so you may very well be experiencing code that has not been battle hardened yet. It took v6 - 2.5 years to achieve that level of stability.

VP

 

[marrybanilow]

Well - I can't speak to Mac in general. There are simply too many variables in play with that OS series and each time Apple changes the game - users and (probably Presonus too) are left scrambling.

For Windows 10 22H2 - I stand by my statement. This is a bulletproof, tank-like environment that hasn't even thrown a single error since I built this DAW on Feb 3, 2024. I use VERY modern hardware, very limited plugins (ALL VST3) and have gone thru the last 4 versions of v6 and now two versions of v7

As far as v7 is concerned - I do agree. The development has slowed dramatically VS what we were led to believe back during that "keynote" video in late Sept 2024. We were supposed to see "faster" development, more bug fixes, more "good stuff" earlier and so on - and since then we have received two very basic maintenance releases (v7.02 being specifically VERY thin) and nothing more.

I will admit I probably took the high road on that announcement and filled my own head with excitement and what I know now - are clearly unrealistic expectations. The updates are not coming any faster and the "good stuff" is still not available. I mean we have 10 days left to go in January and still nothing. I think that last ultra light bug fix (v7.02) was last week of November...

While I have not had any troubles with v7 - it stands to reason that will just two maintenance releases - there is simply no way v7 will near as stable at v6.6.4 was at this point - so you may very well be experiencing code that has not been battle hardened yet. It took v6 - 2.5 years to achieve that level of stability.

VP

Yeah i definitely understand all of this and not naive enough to suggest S7 in it's current form is at a super stable point. In hindsight i should have carried on with 6 but my experience in the past month led me to believe maybe i found the root cause for this crashing and since i rely on hit detection/audio bends a fair bit, i resort to Cubase 14 for that anyway (audio bend issues discussed previously in this thread).

In regards to Apple OS, i don't update OS until i know all my main plugins are definitely compatible (which isnt the case currently so still on 14). Hopefully we'll see more updates in the near future - there are not really any features i'm begging for, just overall performance fixes would even be nice

 

[Crossinger]

I will admit I probably took the high road on that announcement and filled my own head with excitement and what I know now - are clearly unrealistic expectations. The updates are not coming any faster and the "good stuff" is still not available. I mean we have 10 days left to go in January and still nothing. I think that last ultra light bug fix (v7.02) was last week of November...

From a developer point of view:

a) assumption: Presonus uses 3-week iteration ("sprint") as development cycle
b) if the last release was late November: no product manager will approve a release closely before holiday vacation (mid December) for the staff.
c) If the "usual" cycle for the developers started in the 2nd week of 2025, then we can expect the next release by the end of January (maybe with some days on top for QA) at soonest.

But of course: I have no insight. These are merely educated guesses.

 

[Vocalpoint]

From a developer point of view:

a) assumption: Presonus uses 3-week iteration ("sprint") as development cycle
b) if the last release was late November: no product manager will approve a release closely before holiday vacation (mid December) for the staff.
c) If the "usual" cycle for the developers started in the 2nd week of 2025, then we can expect the next release by the end of January (maybe with some days on top for QA) at soonest.

But of course: I have no insight. These are merely educated guesses.

Oh - trust me - I know the "typical" sprint cycle. And - I totally understand the holiday season and family time - but simply say that nothing is happening between Dec 15 and Jan 10 and I think everyone would be just fine with it - instead of getting their hopes up.

VP

 

[JX-84]

I'm still hanging back on V6.

The 3-4 bigger updates a year sounds too good to be true, so I'm cautiously waiting to see how this first year (of the new schedule) plays out.

 

[Vocalpoint]

I'm still hanging back on V6.

The 3-4 bigger updates a year sounds too good to be true, so I'm cautiously waiting to see how this first year (of the new schedule) plays out.

As am I. But what other choice does one have?

I am just kicking myself for creating all these grandiose visions in my mind about how we "might" see faster bug fixes releases (like say one every 4 weeks or so) falling in between the so-called Feature Drops - but that was just wishful (and assumption based) thinking.

All this schedule will end up looking like is most likely 3-4 "pseudo" quarterly releases - just like they always did.

That said - I will give them a bit of a pass on this first one of 2025 - as - if the context of that keynote video was correct - this could be the first S1 Pro release which actually dumps the "v7' branding and moves to a "time based" naming convention - say something like Studio One Pro (v2025.1)

If this comes to pass with this first release of 2025 - they might need extra time to arrange the marketing, messaging and so on - because I suspect LOTS of users will be very confused if there is suddenly no more "v7" releases.

Gregor dashed over that part so fast in the video - not sure a lot of folks actually picked up on what this potentially means.

VP

 

[lokeyfly]

.....I am just kicking myself for creating all these grandiose visions in my mind about how we "might" see faster bug fixes releases (like say one every 4 weeks or so) falling in between the so-called Feature Drops - but that was just wishful (and assumption based) thinking.

Well, you certainly came from a right place, with positive points and optimism for v7. Let's see, they might make good yet on their claims (and investment?), or be even close. As long as the end product stays on track.

Sorry to hear you had to stay with v6. I understand if that's the case. I'm not sure why, but you seem to be taking it well and in stride. It just sucks, shelling out cash you're not using. They made claims, and if they don't hold to them, shame on them. If twice, shame on us.

I'm admittedly in a good place because there's really no snags or annoying issues with version 7 that I've encountered. If I can create, I'm good. I'll remain in a holding pattern with version 7 though until I see how things progress. I consider the 7.0.x release gave me all I need with additional tools to go forward with. For me with active and projected projects, it's best not to get mid flight in altitude, only to find there's a "Ladies and gentlemen, there seems to be a slight issue with the landing gear." announcement. Forcing us to upgrade to v8.

Hope it gets better for all though! As you do VP, I remain optimistic.

 

[Vocalpoint]

Sorry to hear you had to stay with v6.

Oh I am not still on 6. I made the transition to v7 within a week of release. And yes like you there are no snags that I have encountered - v7.02 is stable enough for production work and I have no immediate issues that are holding me back in any way.

The color space and other "changes" remain annoying - but manageable.

I just look at the calendar and see that it has been 3+ months now since the launch only to arrive at 7.02 . Justifying that number does not jive with what I watched back in late September 2024.

That said - I too am optimistic. Perhaps too optimistic.

VP

 

[madFloyd]

I admit to being annoyed at the lack of bug fix releases.

I have been using Studio One since version 1 and love this DAW so I'm hoping this negative feeling goes away whenever the next update occurs.

 

[lokeyfly]

I understand there may not be a running list of current bug fix requirements, but if there is one, can someone post it. Of course, only if it's easy to provide. Would be helpful. Thanks!

 

[lokeyfly]

I went back a few pages. Like I said, I can see no list is really made or should be. I just thought if it was there. No biggie. Thanks guys. I'll remain out of this thread, unless I can contribute to a found issue.
Thanks just the same and enjoy.