Studio One 7.2

[aMUSEd]

DAW devs at some point should remove outdated features, to free up developer ressources. In S1 case, audiounit-support would be such a thing. Audiounit-support makes no sense, if you don't even offer an iOS version of your software. Other than for iOS, it is a very proprietary plugin format, only existing for Apple's Logic. CLAP, VST2, VST3 snd ARA support are more than enough. Please remove it.

Not at all - AU support in Studio One is very useful, there are some plugins that only exist as AU and also some plugins that I can load in S1 using AU that would otherwise require me to run the whole host in Rosetta mode - such as Isotope Iris and Absynth. I am very grateful for StudioOne having the best range of plugin formats and for actually also supporting their presets unlike some other hosts. I wish they would support au3 though.

[qtheerearranger]

I have never thought of using something similar to Bitwig's modulators or Cubase's FX modulators in Studio One, until today. I assume this is nothing that they have added to Studio One, yet?

no s1 doesn't have modulators - and interestingly cubase has modulators section in their 3rd party vst library manager window - I wonder if cubase has vst3 modulator protocol for devs? or if they are going to release it with cubase 15? in which case all s1 would have to do is enable it as a midi plugin? interesting times the future is always fun

[Hanz Meyzer]

[Not at all - AU support in Studio One is very useful, there are some plugins that only exist as AU and also some plugins that I can load in S1 using AU that would otherwise require me to run the whole host in Rosetta mode - such as Isotope Iris and Absynth. I am very grateful for StudioOne having the best range of plugin formats and for actually also supporting their presets unlike some other hosts. I wish they would support au3 though.

I don't find you reasoning very convincing... Just for some outdated plugins (which as you say would run in rosetta mode) keeping a whole plugin adapter stack intact?

Regarding my thought of freeing up developer ressources/time/complexity, what else would you then remove from S1?

[starflakeprj]

I have never thought of using something similar to Bitwig's modulators or Cubase's FX modulators in Studio One, until today. I assume this is nothing that they have added to Studio One, yet?

no s1 doesn't have modulators - and interestingly cubase has modulators section in their 3rd party vst library manager window - I wonder if cubase has vst3 modulator protocol for devs? or if they are going to release it with cubase 15? in which case all s1 would have to do is enable it as a midi plugin? interesting times the future is always fun

Thank you for the confirmation, then I can stop looking for now. I guess Cableguys MidiShaper can be used to achieve something desirable until PreSonus implements something similar in Studio One.

[aMUSEd]

[Not at all - AU support in Studio One is very useful, there are some plugins that only exist as AU and also some plugins that I can load in S1 using AU that would otherwise require me to run the whole host in Rosetta mode - such as Isotope Iris and Absynth. I am very grateful for StudioOne having the best range of plugin formats and for actually also supporting their presets unlike some other hosts. I wish they would support au3 though.

I don't find you reasoning very convincing... Just for some outdated plugins (which as you say would run in rosetta mode) keeping a whole plugin adapter stack intact?

Regarding my thought of freeing up developer ressources/time/complexity, what else would you then remove from S1?

No if I ran the whole host in Rosetta I would lose the benefits of Apple silicon native plugins as well as the advanced multithreading. AU makes it possible for those older plugins to be run only individually in rosetta mode, only when I need them, and alongside other plugins that are native. Anyway as I said there are also plugins I can only run in AU so the rosetta point is secondary anyway. If anything I want S1 to support more modern au3., ditching AU completely is a bad idea.

[bk]

Regarding my thought of freeing up developer ressources/time/complexity, what else would you then remove from S1?

How about Splice integration and Dolby Atmos? Two features I'll never use.

Honestly, if you ask a dozen people what should be removed, you'll get a dozen different answers.
I'm not sure why you think things need to be removed.

[Hanz Meyzer]

Because with each new layer of functionality, the complexity raises in such a huge project, until to a point when development is stuck. This is a very common and normal thing in Informatics. A DAW is one of the most complex softwares existing. So if you want the S1 dev team to improve functionality or even add new features, it is wise to also remove not so neccessary stuff, too.

I think AudioUnit support would be such a thing. Since almost all plugins are available as VST3 or CLAP, there are only a few reasons left to keep this. You also still could run an older version of S1, still having Audiounit support, for those old song projects in which you use abandoned synths... Apple also plans to remove Rosetta2 quite soon.

Of course removing stuff will be always a compromise. Knowing this now, what would you then remove?

[Bowsy]

Here we are again.

Post on Page 2 "There are four areas where PDC is broken"
https://studiooneforum.com/threads/are- ... ated.1131/

Broken PDC brought up again for the how ever many times it has been in the last 10 years. I think V3.4 was the last time it actually worked. All you get is crickets from Presonus, the main Studio One influencers avoide commenting on it like the plague surprise surprise. They know it's broken, it's not like it hasn't been reported over and over. At this stage it feels like they either can't fix it or simply refuse to fix it for what ever reason. They seem to have plenty of time for things like Atmos, Stem Seperation, Splice, Virtual Instruments, so on and so forth. Every other DAW I have used gets this right but S1. What use is a DAW with broken PDC in this day and age.

[Digivolt]

So what can we do to get Presonus to take notice and at least try to fix this issue ? I've encountered it myself, I thought maybe it was a "me" problem due to settings (drop out protection/low latency mode etc) and I have found some workarounds, one is using Ableton to do the midi sequencing and rewire the audio into Studio One but it's not ideal because I need 2 projects on 2 different DAW's and have to remember them, I also managed to get Harmony Bloom to work on grid but that only worked if I disabled all my plugins bar VSX, Harmony Bloom and the single VST and then recorded the midi then not use HB but again that's not ideal, ideal would be the midi not being delayed by whatever latency you have

[Bowsy]

So what can we do to get Presonus to take notice and at least try to fix this issue ? I've encountered it myself, I thought maybe it was a "me" problem due to settings (drop out protection/low latency mode etc) and I have found some workarounds, one is using Ableton to do the midi sequencing and rewire the audio into Studio One but it's not ideal because I need 2 projects on 2 different DAW's and have to remember them, I also managed to get Harmony Bloom to work on grid but that only worked if I disabled all my plugins bar VSX, Harmony Bloom and the single VST and then recorded the midi then not use HB but again that's not ideal, ideal would be the midi not being delayed by whatever latency you have

I honestly don't know other than spend your money else where till they fix it or stand outside the company doors with pitch forks . I use Cubase as a work around but after a while you think what's the point of using S1 anymore. Don't get me wrong I spend the time shifting or phase aligning data, it's a fairly normal thing to do. I just think it's a joke people have to correct data for a bug that causes it in the first place for a DAW with PRO in it's title name. Printing to track in stages then aligning tracks is the way I work around it. You kind of expected this 20+ years ago with a DAW but it shouldn't happen in this day and age.

The only reason I can think this isn't one of the biggest complaints ever is probably the fact less experienced people using the stock or low latency third party plugins never noticed it was there. Once you know it's there you have to work around it or at least double check things for your own sanity.

As you rightly pointed out, why should you or anyone else have to question yourself or a plugin then waste time figuring out why because of a bug that should of been fixed years ago.

[Digivolt]

I guess it also shows how few people are using midi sequencing plugins who use Studio One if the complaints about the issue aren't widespread or there's a lot of user who don't realise it's not supposed to work that way and think aligning the midi manually is just the "done" thing but you're right at some point if you're having to use another DAW to solve a problem, you may as well just use that DAW entirely, although the one thing I love most about Studio One is the ability to categorise all your plugins into folders and sub folders and have pictures of them to help remember exactly what you want to pull out, I'm not sure I could live without that now that I have it

[Fornicras]

Regarding my thought of freeing up developer ressources/time/complexity, what else would you then remove from S1?

How about Splice integration and Dolby Atmos? Two features I'll never use.

Honestly, if you ask a dozen people what should be removed, you'll get a dozen different answers.
I'm not sure why you think things need to be removed.

I use Splice very heavily for drum samples, it was really hard for me to use its own app back and forth with studio one, now it's easier.
Still it has some problems but still better than any DAW can provide at the moment (maybe FL studio is better with FL Cloud, idk)
AI feature is also great to find some perc loops after I finished most of the sections.

I don't have a setup for Dolby Atmos, but I think pro mixers use it.

[Crossinger]

I honestly don't know other than spend your money else where till they fix it or stand outside the company doors with pitch forks

The issue with bugs is that as long as only a small portion of users are affected, there won’t be much of an outcry. My usage pattern is quite simple: I only utilize a fraction of the features and often employ the same methods I used two decades ago because I lack the motivation to learn new workflows. Consequently, if there are shifts or delays in my recordings, I simply cut off the beginning and move the clip to the starting point. That’s it. Essentially, it’s more of a habit than anything else that drives me to regularly purchase upgrades. The only exception is compatibility with my Macs. Logic Pro 8 or Cubase 4.5 from 2008 would likely suffice for me.

[jrwaltb]

So what can we do to get Presonus to take notice and at least try to fix this issue ? I've encountered it myself, I thought maybe it was a "me" problem due to settings (drop out protection/low latency mode etc) and I have found some workarounds, one is using Ableton to do the midi sequencing and rewire the audio into Studio One but it's not ideal because I need 2 projects on 2 different DAW's and have to remember them, I also managed to get Harmony Bloom to work on grid but that only worked if I disabled all my plugins bar VSX, Harmony Bloom and the single VST and then recorded the midi then not use HB but again that's not ideal, ideal would be the midi not being delayed by whatever latency you have

I honestly don't know other than spend your money else where till they fix it or stand outside the company doors with pitch forks . I use Cubase as a work around but after a while you think what's the point of using S1 anymore. Don't get me wrong I spend the time shifting or phase aligning data, it's a fairly normal thing to do. I just think it's a joke people have to correct data for a bug that causes it in the first place for a DAW with PRO in it's title name. Printing to track in stages then aligning tracks is the way I work around it. You kind of expected this 20+ years ago with a DAW but it shouldn't happen in this day and age.

The only reason I can think this isn't one of the biggest complaints ever is probably the fact less experienced people using the stock or low latency third party plugins never noticed it was there. Once you know it's there you have to work around it or at least double check things for your own sanity.

As you rightly pointed out, why should you or anyone else have to question yourself or a plugin then waste time figuring out why because of a bug that should of been fixed years ago.

I would be very surprised if Cubase does not also have PDC issues as I know Ableton does as well. Would you be able to show how you test this for yourself as I want to verify I am doing it right?

[Bowsy]

So what can we do to get Presonus to take notice and at least try to fix this issue ? I've encountered it myself, I thought maybe it was a "me" problem due to settings (drop out protection/low latency mode etc) and I have found some workarounds, one is using Ableton to do the midi sequencing and rewire the audio into Studio One but it's not ideal because I need 2 projects on 2 different DAW's and have to remember them, I also managed to get Harmony Bloom to work on grid but that only worked if I disabled all my plugins bar VSX, Harmony Bloom and the single VST and then recorded the midi then not use HB but again that's not ideal, ideal would be the midi not being delayed by whatever latency you have

I honestly don't know other than spend your money else where till they fix it or stand outside the company doors with pitch forks . I use Cubase as a work around but after a while you think what's the point of using S1 anymore. Don't get me wrong I spend the time shifting or phase aligning data, it's a fairly normal thing to do. I just think it's a joke people have to correct data for a bug that causes it in the first place for a DAW with PRO in it's title name. Printing to track in stages then aligning tracks is the way I work around it. You kind of expected this 20+ years ago with a DAW but it shouldn't happen in this day and age.

The only reason I can think this isn't one of the biggest complaints ever is probably the fact less experienced people using the stock or low latency third party plugins never noticed it was there. Once you know it's there you have to work around it or at least double check things for your own sanity.

As you rightly pointed out, why should you or anyone else have to question yourself or a plugin then waste time figuring out why because of a bug that should of been fixed years ago.

I would be very surprised if Cubase does not also have PDC issues as I know Ableton does as well. Would you be able to show how you test this for yourself as I want to verify I am doing it right?

That's not me below by the way. It's a nice guy from the old Studio One forums who also flagged it when the rest of us did over the years. He explains it nice and simple. Someone also reported PDC issue's with "Aux Channels linked to external Instruments" but I never tested it.

I know it might look like I'm being a bit harsh with Presonus but I still use it and for good reason. I agree with you as well, as if there's such a thing as a perfect DAW. It's just a bit sad they won't look into this more. The worst part for me is the fact playback sync is out of wack against the rest of your tracks. Your only option is to render the instrument track to audio. Your just listening to bad phase alignment or delayed notes otherwise depending on the situation.