Studio One 7.0.1 / 7.0.2 - Discussion Thread

[Logical]

A centered playhead would be nice. There's needs for the existing sweeping playhead as well. It would be nice to make good use of both for different needs. One can hope we see that with Studio One in the not too distant future.

As a workaround for all tracks ripple edit, simply set the loop marker where you want to drop out sections along the timeline. Then simply right click to delete time along the timeline. This instantly deletes and closes the gap on all tracks, so this effectively works just as fast.

Yes definitely need both types of playhead behaviour.

The workaround you mention is one I’ve used and is very well implemented in Studio One.

 

[marrybanilow]

Still seeing random crashes which cause the laptop to shut down with 7.0.1 on MacOS Sonoma (M1 Pro). Was hoping '[macOS] Potential crash with certain plug-ins' would have fixed this

 

[Lukas]

Still seeing random crashes which cause the laptop to shut down with 7.0.1 on MacOS Sonoma (M1 Pro). Was hoping '[macOS] Potential crash with certain plug-ins' would have fixed this

It's important to remember that all your plug-ins are pieces of software, and any of them could potentially cause your computer to crash. Studio One can't prevent plug-ins from doing this, except in rare cases where the problem can be solved on the host side.

 

[marrybanilow]

It's important to remember that all your plug-ins are pieces of software, and any of them could potentially cause your computer to crash. Studio One can't prevent plug-ins from doing this, except in rare cases where the problem can be solved on the host side.

I get this however i have 0 issues/crashes when using the same plugins on Studio One 6 which 99% of the time is a stable experience

 

[js1]

I get this however i have 0 issues/crashes when using the same plugins on Studio One 6 which 99% of the time is a stable experience

We all have been there at some point, and understand your frustration. But it still could be a plugin issue.

ALL code of any scale has undiscovered bugs that can reveal themselves when the environment changes.

Not all of the code in Studio One is written by Presonus. It includes code that is provided by Apple/Microsoft to integrate to the operating system. That changes over time, and Presonus has to stay current at every release to take advantage of new OS capabilities and be compatible with new machines and OSes. And it WILL change the environment that the plugin is running in. Could be timing, could be tightening of security, tightening of APIs, could be error handling, and so on.

And there's a vast spectrum of developer skill and company rigor when it comes to code creation. Ensuring stability is difficult, tedious and expensive. So it should not come as a shock that a smaller developer might spend more time on the sound and DSP code than the other aspects.

Couple of questions:

1. On the start after the crash, you have to say if you want to start normally or disable services. Sometimes, on that panel, it will indicate if a plugin caused the crash. Is it naming a plugin?
2. Are you running plugins that aren't Apple native?

 

[marrybanilow]

We all have been there at some point, and understand your frustration. But it still could be a plugin issue.

ALL code of any scale has undiscovered bugs that can reveal themselves when the environment changes.

Not all of the code in Studio One is written by Presonus. It includes code that is provided by Apple/Microsoft to integrate to the operating system. That changes over time, and Presonus has to stay current at every release to take advantage of new OS capabilities and be compatible with new machines and OSes. And it WILL change the environment that the plugin is running in. Could be timing, could be tightening of security, tightening of APIs, could be error handling, and so on.

And there's a vast spectrum of developer skill and company rigor when it comes to code creation. Ensuring stability is difficult, tedious and expensive. So it should not come as a shock that a smaller developer might spend more time on the sound and DSP code than the other aspects.

Couple of questions:

1. On the start after the crash, you have to say if you want to start normally or disable services. Sometimes, on that panel, it will indicate if a plugin caused the crash. Is it naming a plugin?
2. Are you running plugins that aren't Apple native?

Hey JS, thanks for the reply. I don't disagree with you that it could be a plugin issue, it is just hard to narrow down which ones could be contributing.

1. Nope there is no mention of a specific plugin, when it comes back to that screen it always says 'Studio One quit unexpectedly' along with the options on how to start up.
2. It is very likely some of my plugins aren't optimized for Apple Silicon but i've opened the same sessions with same plugins in S6 and S7 and the hard crash/rebooting doesn't occur in S6.

What i've also noticed when comparing the same session with S6 and S7 is when in S7, it is using way more CPU according to the meter at the bottom

 

[js1]

What i've also noticed when comparing the same session with S6 and S7 is when in S7, it is using way more CPU according to the meter at the bottom

Then we have something to go on. I'm not seeing any difference in performance between S6 and S7, so there's a possibility that you have a plugin misbehaving under 7.

To narrow down the plugin, I'd do stuff like this:

• Make a copy of the project and replace ALL the plugins with the closest Presonus equivalent. Don't overthink it - we're not going for sound here. We just want to see how your system performs under similar load when using ONLY Presonus software. Check performance between S6 and S7 - I bet they're the same. If it isn't, then there's something fundamentally different between S6 and S7 on your system, and you should open a ticket with Presonus. But, if they perform the same, then we have to narrow down which plugin is the problem.
• Make sure that your plugins are at the latest release. If they aren't, or the vendor hasn't updated them in the last 3 years, they may have compatibility issues. Start by disabling those, and compare the performance in both S6 and S7.
• For $3, pick up PlugInfo (thinkersnacks.com/pluginfo/). It will list all your plugins and tell you which one require Rosetta (Intel64). Disable any of those in your project and compare the performance in both S6 and S7.

If you get to the point where the projects are now using about the same CPU, you can then start re-enabling plugins to see if one of those really cranks up the CPU.

 

[marrybanilow]

Thank

Then we have something to go on. I'm not seeing any difference in performance between S6 and S7, so there's a possibility that you have a plugin misbehaving under 7.

To narrow down the plugin, I'd do stuff like this:

• Make a copy of the project and replace ALL the plugins with the closest Presonus equivalent. Don't overthink it - we're not going for sound here. We just want to see how your system performs under similar load when using ONLY Presonus software. Check performance between S6 and S7 - I bet they're the same. If it isn't, then there's something fundamentally different between S6 and S7 on your system, and you should open a ticket with Presonus. But, if they perform the same, then we have to narrow down which plugin is the problem.
• Make sure that your plugins are at the latest release. If they aren't, or the vendor hasn't updated them in the last 3 years, they may have compatibility issues. Start by disabling those, and compare the performance in both S6 and S7.
• For $3, pick up PlugInfo (thinkersnacks.com/pluginfo/). It will list all your plugins and tell you which one require Rosetta (Intel64). Disable any of those in your project and compare the performance in both S6 and S7.

If you get to the point where the projects are now using about the same CPU, you can then start re-enabling plugins to see if one of those really cranks up the CPU.

Thank you very much for recommending these steps, and also PlugInfo. As it stands, i counted 2 plugins (that are intel only) that are present in both example sessions so i will see if there is an apple silicon update/remove entirely to see if behaviour improves

 

[marrybanilow]

Then we have something to go on. I'm not seeing any difference in performance between S6 and S7, so there's a possibility that you have a plugin misbehaving under 7.

To narrow down the plugin, I'd do stuff like this:

• Make a copy of the project and replace ALL the plugins with the closest Presonus equivalent. Don't overthink it - we're not going for sound here. We just want to see how your system performs under similar load when using ONLY Presonus software. Check performance between S6 and S7 - I bet they're the same. If it isn't, then there's something fundamentally different between S6 and S7 on your system, and you should open a ticket with Presonus. But, if they perform the same, then we have to narrow down which plugin is the problem.
• Make sure that your plugins are at the latest release. If they aren't, or the vendor hasn't updated them in the last 3 years, they may have compatibility issues. Start by disabling those, and compare the performance in both S6 and S7.
• For $3, pick up PlugInfo (thinkersnacks.com/pluginfo/). It will list all your plugins and tell you which one require Rosetta (Intel64). Disable any of those in your project and compare the performance in both S6 and S7.

If you get to the point where the projects are now using about the same CPU, you can then start re-enabling plugins to see if one of those really cranks up the CPU.

I don't want to jinx it, but i have removed all non-apple verified plugins and replaced the ones i use with updates that have been apple certified and i am seeing better CPU performance and no crashes yet. Fingers crossed!

Thank you so much for recommending PlugInfo.

 

[Navar]

I don't get it, why it is so difficult to include some settings for the grid lines. I have to do editing stuff a lot and V7 is still a pain without seeing the grid lines properly. I was really happy to read the note "improved", but sorry, that's a really small improvement from nearly nothing to a little bit.
I love the V7 a lot and it's working fantastic on my side, but this point drives me crazy because I think that there is no way that someone could say: "oh yeah nice, I would do audio editing on 24 drum tracks for 5-6 hours a day with this". And for screen ergonomics you can't sit too close the whole day so you need to see those things if needed.

 

[Vocalpoint]

I don't get it, why it is so difficult to include some settings for the grid lines. I have to do editing stuff a lot and V7 is still a pain without seeing the grid lines properly. I was really happy to read the note "improved", but sorry, that's a really small improvement from nearly nothing to a little bit.
I love the V7 a lot and it's working fantastic on my side, but this point drives me crazy because I think that there is no way that someone could say: "oh yeah nice, I would do audio editing on 24 drum tracks for 5-6 hours a day with this". And for screen ergonomics you can't sit too close the whole day so you need to see those things if needed.

It has been well documented that the colors and other visual aspects of S1 v7 AND v7.01. need work.

Not sure what was going on over there at Presonus between say v6.5 an v7 - but to me - the colors and visuals were as good as it gets in v6.6.4.

Also cannot recall ANY major outcry from users demanding changes in this area either. Matter of fact - I don't recall ANY major color or grid line comments, complaints or questions for several years as we moved thru v5 and v6.

But now - for whatever reason - Presonus decided it was time to wade into an area that I can't imagine anyone perceived as a problem and created one by not knowing when to leave something that was already good - alone.

VP

 

[Vocalpoint]

@Ari

Thanks for the 7.02 update! Installed now

Another question - that I just noticed from the 7.01 notes:

"Fixed: Kontakt 8 does not load sounds from song saved with Kontakt 7 or earlier"

Does this mean that Studio One v7 now actually supports "Kontakt Migration" - where if I had a old track using K6 (for example) - and I now have Kontakt 8 - the song will load K8 (instead of K6) and spare us from both the manual Kontakt intervention (rebuilding the old instance with the same sounds in a new instance) and effectively stopping all those "Plugin Not loaded" error messages of the past?

VP

 

[Lukas]

Another question - that I just noticed from the 7.01 notes:

"Fixed: Kontakt 8 does not load sounds from song saved with Kontakt 7 or earlier"

Does this mean that Studio One v7 now actually supports "Kontakt Migration" - where if I had a old track using K6 (for example) - and I now have Kontakt 8 - the song will load K8 (instead of K6) and spare us from both the manual Kontakt intervention (rebuilding the old instance with the same sounds in a new instance) and effectively stopping all those "Plugin Not loaded" error messages of the past?

Yes, Studio One 7.0.1 supports VST3 IPluginCompatibility (which Kontakt 7 and 8 use for plug-in migration). At least in my recent tests Kontakt 7 loads songs saved with K5 and K6 and correct preset data.

But please test yourself and report back.

 

[Vocalpoint]

Yes, Studio One 7.0.1 supports VST3 IPluginCompatibility (which Kontakt 7 and 8 use for plug-in migration). At least in my recent tests Kontakt 7 loads songs saved with K5 and K6 and correct preset data.

But please test yourself and report back.

Wow. Will do.

Thanks Lukas

VP

 

[Navar]

Not sure what was going on over there at Presonus between say v6.5 an v7 - but to me - the colors and visuals were as good as it gets in v6.6.4

Yeah, it's the same for me. I have to say, I don't really care if edges of events are sharp, round or whatever, or if plugins have textures of used tolex, all that matters to me is the usability. But of course, there are people which are more into aesthetics than me.
One big problem is, that it's difficult to match so many screen setups, and computer screens can be very different and it's difficult to do a "one setting for all" thing, if you are not Fabfilter or Valhalla DSP. If you allow users to change brightness, contrast, positive or negative visualization, than it's important, that some very important visual things like the grid lines or the alpha value of events can be adjusted too. Of course this make things more complicated but my very personal opinion is, that it is a lot more important to ensure the visibility and readability than to colorize everything a bit more green or blue.

 

[Vocalpoint]

I don't really care if edges of events are sharp, round or whatever, or if plugins have textures of used tolex, all that matters to me is the usability. But of course, there are people which are more into aesthetics than me.

Have said it before and will say it again - I am 100% all for "improvements" - but some of us did not ask for anything to be improved. We like things the way we like them (especially when it comes to colors and display elements) - and I think that stepping on that in favor of forward motion is both ignorant and ballsy all at the same time.

Any "improvements" should be allowed to switched on for those that want them and left off for those of us who did not ask for any change. Options - is what I am saying.

This is very much like the ATMOS implementation in v6. I was terrified that this thing would be rearing it's ugly head within my workflow at every turn - but in typical awesome Presonus design - they were logical and precise and allow it to be turned on or off as needed.

But this whole "racetrack" around an event in v7? Do not care about it - or for it - one bit. I never had a single complaint about event display and I have been using S1 since 2011. If I had an issue - I think it would have shown itself by now.

But can I turn this off? No. Can I make the god awful thickness of that event border smaller? No. Basically there is nothing that can be done.

Anyhoo - I edit a LOT of audio in S1 and these event/color changes have been jarring for me. That said - I am adapting and will soldier on - but the way this was handled - is not how you make a program better.

VP

 

[madFloyd]

Personally, I'd be disappointed if the visuals rolled back to v6. I think they are so much easier to read in v7. It's my favorite thing about v7; maybe the only thing I appreciate (although I could be forgetting something).

I'm not saying this to frustrate you, just making sure this thread isn't reflecting a consensus that the visuals went backwards.

 

[Vocalpoint]

Personally, I'd be disappointed if the visuals rolled back to v6. I think they are so much easier to read in v7. It's my favorite thing about v7; maybe the only thing I appreciate (although I could be forgetting something).

I'm not saying this to frustrate you, just making sure this thread isn't reflecting a consensus that the visuals went backwards.

Understood - not saying "roll back". And definitely not saying visuals went "backwards."

Saying "options"

VP

 

[marrybanilow]

But this whole "racetrack" around an event in v7? Do not care about it - or for it - one bit. I never had a single complaint about event display and I have been using S1 since 2011. If I had an issue - I think it would have shown itself by now.

But can I turn this off? No. Can I make the god awful thickness of that event border smaller? No. Basically there is nothing that can be done.

Anyhoo - I edit a LOT of audio in S1 and these event/color changes have been jarring for me. That said - I am adapting and will soldier on - but the way this was handled - is not how you make a program better.

VP

Agree with all of this 100%. The racetrack (as i will now call it from now on!) makes editing between events just that little bit more difficult than it should be. Definitely the worst adjustment in the new update - there should definitely be options to customise/go back to how it was

 

[marrybanilow]

Then we have something to go on. I'm not seeing any difference in performance between S6 and S7, so there's a possibility that you have a plugin misbehaving under 7.

To narrow down the plugin, I'd do stuff like this:

• Make a copy of the project and replace ALL the plugins with the closest Presonus equivalent. Don't overthink it - we're not going for sound here. We just want to see how your system performs under similar load when using ONLY Presonus software. Check performance between S6 and S7 - I bet they're the same. If it isn't, then there's something fundamentally different between S6 and S7 on your system, and you should open a ticket with Presonus. But, if they perform the same, then we have to narrow down which plugin is the problem.
• Make sure that your plugins are at the latest release. If they aren't, or the vendor hasn't updated them in the last 3 years, they may have compatibility issues. Start by disabling those, and compare the performance in both S6 and S7.
• For $3, pick up PlugInfo (thinkersnacks.com/pluginfo/). It will list all your plugins and tell you which one require Rosetta (Intel64). Disable any of those in your project and compare the performance in both S6 and S7.

If you get to the point where the projects are now using about the same CPU, you can then start re-enabling plugins to see if one of those really cranks up the CPU.

Just for reference - i was still getting crashed after updating all my apps to apple native. The crash logs within mac Console were indicating (in my interpretation) an issue with Studio One and the GPU on the OS. I noticed i was on an older version of Sonoma (14.5) and i have updated to (14.7) where change log shows some imrpovements with the gpu module - touch wood but i have not had any crashes since.