Studio One 7.2.1 - Discussion Thread

[AAV]

I deleted all preference files and wrote the Presonus support. This support moron replied "You don't need the vst 2 version anymore, the vst 3 version is better" So I can't edit the drums on 2 records I did anymore. Thank you Presonus.

In my experience Presonus support have done a great job (and don't deserve the derision). VST2 is being phased out (by everyone, not just Presonus). I am still using some VST2 plugs myself but can't/wouldn't blame Presonus if their use and usefulness disappears one day. The simple solution in your case would be to roll back to 7.1.1 (in which you said, the VST2 worked for you) to edit your drums. No?

Edit to add - there has been a similar problem observed with Spire in it's VST3 version. In that case it relates to the screen size/scale factor and resolution. I wonder if any of this applies in your case? You should add your signature to your forum preferences to aid others in helping you. It helps to identify potential issues and correlations to problems.
https://studiooneforum.com/threads/...-after-update-to-studio-one-7-2.931/post-7467

 

[Monot]

No. Why? Other bugs are solved and CPU usage is improved on Apple Silicons.
Look, if you write the support your vst 2 plugin works in 7.1 and in 7.2 not anymore you shall expect from a support that they look into it, not blocking you and give you wise advise not to use the vst 2 version anymore. And this happens since Fender took over.
I don't know how many times I wrote them that the launcher doesn't work properly and they gave me stupid advices and blocked it and in 7.1 they approved it...It is complete waste of time to write the Presonus Support...

 

[Lukas]

Updated the other day, yesterday started a new session. Put an instance of Omnisphere into the song and got an authorization request screen.

That usually happens when something about your hardware or OS has changed.

Look, if you write the support your vst 2 plugin works in 7.1 and in 7.2 not anymore you shall expect from a support that they look into it, not blocking you and give you wise advise not to use the vst 2 version anymore.

I agree. Support (and ultimately QA/development) should check whether it's a plug-in issue (Addictive Drums 2) or a Studio One issue. I've submitted a report.

AD2 (VST2) works fine on Windows 10 here - so it's probably a macOS graphics-related issue.

And this happens since Fender took over.

I don't think this is the case.

 

[sintil8]

@Lukas
If something hasn't booted up as expected.
Nothing had been changed. I have had the odd occassion where Pace has not installed in the past causing ilok stuff to shout, what's going on.
It was just odd, nothing more, which is why I mentioned it and it did not repeat so not a problem.
Could I ask that my mentioning such is not conflated with other issues please.

Kindest regards

 

[Midiboy]

Here's an issue I've been seeing twice now...in the Project page....the Loudness Information doesn't ALWAYS work. It does the detection, but doesn't show the results. Here's an example screenshot. This is AFTER the detection. Note the arrow is pointing down, so it should be showing the results.

 

[Trucky]

Here's an issue I've been seeing twice now...in the Project page....the Loudness Information doesn't ALWAYS work. It does the detection, but doesn't show the results. Here's an example screenshot. This is AFTER the detection. Note the arrow is pointing down, so it should be showing the results.

View attachment 1252

Per your signature, are you still using Studio One Pro 7.1 and not the latest release?

 

[Midiboy]

Sorry, I'm on the latest, greatest. I forgot to update my sig.

 

[Trucky]

Here's an issue I've been seeing twice now...in the Project page....the Loudness Information doesn't ALWAYS work. It does the detection, but doesn't show the results. Here's an example screenshot. This is AFTER the detection. Note the arrow is pointing down, so it should be showing the results.

View attachment 1252

Is this issue happening on all your projects?

Is there anything unique regarding the songs that are failing?

I checked all the songs in my projects and none of them failed to show the loudness results after detection.

 

[Trucky]

Sorry, I'm on the latest, greatest. I forgot to update my sig.

Thanks for updating your signature!
Many of us are used to looking there for issues that may be related to system and software specs.

 

[Jemusic]

Not an issue just an odd one!
Updated the other day, yesterday started a new session. Put an instance of Omnisphere into the song and got an authorization request screen.
Curious that this should happen, the only thing that I have changed recently is the update.
It's not a problem as re-authorization is straightforward. Just curious if any one else has had a similiar experience after an update?

Regards folks

Ps. It's quiet in here...sssh

Just out of interest I was getting a lot of having to re-authorise Omnisphere. It was occasional at first but got worse and more frequent over time. I am on a Mac and they told me that MacKeeper actually causes this and told me to remove it which I did and it never happened again. I see you are on Windows. Maybe contact them and ask. They are very helpful. There might be a similar app on your Windows machine that is doing the same thing.

 

[sintil8]

Just out of interest I was getting a lot of having to re-authorise Omnisphere. It was occasional at first but got worse and more frequent over time. I am on a Mac and they told me that MacKeeper actually causes this and told me to remove it which I did and it never happened again. I see you are on Windows. Maybe contact them and ask. They are very helpful. There might be a similar app on your Windows machine that is doing the same thing.

@Jemusic
I have only ever seen this happen once, so it is not an issue at the mo', and am not too concerned at this stage.
When I put this computer together, I was in contact with Spectrasonics and as you say, they were "very helpful" sending me a link to a full D/Load
of my instruments and the Steam sound library all in one installer, which was ace to install.

I will bear in mind what you have said, just in case it should happen again.

Kind regards and thanks for the heads up.

 

[ianaeillo]

Here's an issue I've been seeing twice now...in the Project page....the Loudness Information doesn't ALWAYS work. It does the detection, but doesn't show the results. Here's an example screenshot. This is AFTER the detection. Note the arrow is pointing down, so it should be showing the results.

View attachment 1252

I’ve had this happen on my PC laptop as well. I figured it was something I did wrong and just closed and reopened the project and it was there after I redetected. Never had it happen on my Mac, though.

 

[Midiboy]

To those that asked....no, I have no recipe on how to recreate this issue. It happens SOMETIMES on SOME song....I can delete the song from the project, and put it back in and it works. If I save the project, and reopen it, it doesn't fix it. BUT, like I said, deleting, and putting it back DOES fix it...most of the time. If it doesn't display on one song in a project, it might display on the next song, or it may not. This update is the first update that this has started happening on me. It's not a HUGE deal, as it's easy enough to fix, but it's annoying.

 

[madFloyd]

Anyone noticing that when you open a song, there's an asterisk beside the name - i.e. Studio One behaves as if it's been modified?

 

[Midiboy]

Yes. I get that as well, even just for opening a song, project, etc.

 

[madFloyd]

Yes. I get that as well, even just for opening a song, project, etc.

I don't know if it's new behavior or not, but I've only noticed it recently.

 

[Lukas]

That's when plug-ins report parameter changes to the DAW upon loading.

 

[madFloyd]

That's when plug-ins report parameter changes to the DAW upon loading.

Interesting, thanks for pointing that out!

 

[Number6]

So it appears sync'ing via MIDI is mostly broken and has been for a long time?

MIDI clock won't follow the timeline (song positions pointer, SPP), especially when I press stop, move timeline position and then press play again, other conditions too.
https://www.kvraudio.com/forum/viewtopic.php?t=396666

Also it appears that MIDI sync'ing Studio One as slave is broken too...
https://studiooneforum.com/threads/studio-one-sync-ableton-live-via-midi-timecode.1093/#post-8169


Apparently this has been the status quo for some time, and with Rewire no longer supported, I would suggest that we need this functionality more than ever. In some use cases you can workaround and bypass all this, and in some others you can't.

I can't believe it's been over 10 years since this hasn't been fixed? Or am I making a silly assumptions here?
Anyway I'll keep calm carry on (I'm leaving my toys firmly in the pram for now!).

Edit...

In Summary.

"Studio One does not sync well via MTC when in slave mode. It’s a bug they have not addressed (afaik) since MTC was provided in slave mode"

No midi clock receive.

Issues with song position pointer (see link).

And a pretty easy fix, the MIDI features under the Synchronization tab, nowhere does it state the word "receive", very confusing. Just put that word somewhere.

Dear universe, please sort.

 

[Branis]

@Monot It’s not ideal, but there is a solution to your problem since you can have multiple S1 versions installed on your sistem. You could install the lastest S1 where vst2 worked, replace AD drums with the vst3 version, save the song file under a new name and then edit it in the latest S1.