Why did you leave Studio One?

[Resonant- Serpent]

When should v7 be announced? I'm hoping for updated sampler and drum machine!

Both of those have had bugs for years that have never been fixed. I highly doubt there will ever be an updated version.

[Fornicras]

When should v7 be announced? I'm hoping for updated sampler and drum machine!

Both of those have had bugs for years that have never been fixed. I highly doubt there will ever be an updated version.

Not using the drum machine but the sampler really has awful bugs/problems and bad design choices that they haven't addressed since v4. I really hate that I have to use Waves Sampler for simple stuff.
They must do something about them.

[andypryce]

When should v7 be announced? I'm hoping for updated sampler and drum machine!

Both of those have had bugs for years that have never been fixed. I highly doubt there will ever be an updated version.

Did they get any update at all since they were introduced? Seems like they are implemented and forgotten.

[jamcat]

What are these bugs?
Can you describe what actions cause them, and what happens?

[CapnLockheed]

I actually used to work for Presonus. I switched to Studio One after many years of using various flavors of Cubase/Nuendo. When I made the switch S1 was still at V2. It worked well for me for a long time. I still have a lot of Presonus hardware.

Due to health issues, I had to step away from the game for a while. Now that I'm past that, I decided to jump back in. I just installed the latest version of Studio One Pro: 6.6.2.100548. Installation and activation went fine. Plugin scanner saw all my 3rd party plugins no problem.

But here's the problem....and it's pretty damn big one for me. I spent a long time organizing a VST folder tree with various folder & subfolders oragnized by type and my workflow preferences. When the pugin browser is set to FOLDER view, Some of my personal folders are NOT showing up. And worse still, the folders that ARE visible are missing many of the individual plugins that ARE in those folders. Not good. Now, I'm not a noob. The proper VST locations have been selected in "options". If they had not been NONE of my personal folders would be visible.

And it has absolutely nothing to do with any plugins being blacklisted. I know this because the really strange thing about this nonsense is that, when I switch to VENDOR view, ALL of my 3rd party plugins are accessible in their respective companies' folders. This is NOT an acceptable workaround as it's EXTREMELY disruptive to my established work flow to be forced to search through VENDOR folders to find plugins I need for sessions.

And it's DEFINITELY an S1 issue. I also use Plogue Bidule as both a standalone host and VST plugin. Bidule sees my folders and plugins EXACTLY as I have them organized. It sees ALL my folders, subfolders and ALL of my plugins are right there where they should be. So opening Bidule in S1 is a possible workaround but it an extra layer of BS I shouldn't have to deal with.

I don't recall this behavior in previous versions of S1. Do I need to roll back to an earlier verion just to access my plugins or has someone else experienced this issues and resolved it? VERY frustrating!!

I purchased the upgrade to 6 as soon as it was released. I leap frogged from 4 to 6. This wasn't an issue in any version of 4 and I don't recall it being a problem in 6.0 or 6.1 but I'm not sure as I was getting sick at that point. Also I can't really be sure as this was not an upgrade from a previous version. This is a clean install....fresh SSD, OS, plugins etc.

I can see maybe some plugins not showing perhaps due to VST2/3 conflicts. But that doesn't explain why some enitire folders are missing or why the problem isn't replicated in Bidule which sees and displays all folders, subfolders, VST2 & VST3 plugins properly.

Soooo.....I did some digging and....It would seem that the problem was stemming from duplicate ID's. Apparently S1 can't handle having both a VST2 instance AND a VST3 instance of the same plugin without screwing up my VST2 folder system. This REALLY sucks. Bidule and other hosts don't lose their minds over this. But apparently, I'm going to have to go thru my plugin cache with a fine-toothed comb and eliminate ALL VST3 plugins that also have VST2 instances installed JUST so I can use Studio One in the way that best suits my workflow....as I have for years.

VST3 plugins are ridiculously hard to organize in any way that suits my flow. That, of course, is Steinberg's fault. That being said, Studio One's inability to handle co-existing instances VST2/VST3 plugins without making a big mess of my, once orderly, file structure of the lies squarely with Presonus. If even a simple standalone host like Bidule can handle it......there's no excuse for Studio One not to be able to handle plugins in a more sensible manner.

Ok....did some more digging.....Well that was only a partial fix. After deleting all VST3 duplicates of VST2 plugins, (which...BTW...I should NOT have had to do!), and after adding EACH and EVERY one of my folders & subfolders manually to VST plugin paths in "options", the folders are all now visible. But nearly half of my VST2 plugins are not showing up in their folders. This JUST a Studio One problem. Every other host I've tried sees ALL of my VST2 plugins exactly where they live. Cubase? No problem. Reaper? No problem. Bidule? No problem. Even crappy little VSTHost & SaviHost have no problem seeing and instantiating ALL of my plugins.

I've invested a LOT of my time AND money in Presonus. I'd really hate to have to switch to another DAW now but having to open another host inside my main DAW JUST so I can access my plugins is simply not a viable workaround.

[Trancit]

It´s hard to tell what´s happening there, I never had any issues with that...

Nonetheless and if it´s perhaps related to a too complicated folder structure you have done, in Studio One there is actually no need to sort them this way on your hard drive... you can create your own folder structure in S1´s browser no matter where/how your plugins are sorted on your hard drive...
This is especially handy because of the limitations of VST3 which on the other side gives you advantages over VST2 like parameter automation with real values instead of percentages...

Perhaps S1 cannot read too long files paths Idk, but making it simpler could help and if you sort them in S1 itself you don´t lose anything...

[jamcat]

Yeah, studio One prioritizes VST3 over VST2.

I culled all VST2 plugins from my system a long time ago. But that’s just me.

Organizing VST3 plugins is easy.

[Resonant- Serpent]

I actually used to work for Presonus. I switched to Studio One after many years of using various flavors of Cubase/Nuendo. When I made the switch S1 was still at V2. It worked well for me for a long time. I still have a lot of Presonus hardware.

Due to health issues, I had to step away from the game for a while. Now that I'm past that, I decided to jump back in. I just installed the latest version of Studio One Pro: 6.6.2.100548. Installation and activation went fine. Plugin scanner saw all my 3rd party plugins no problem.

But here's the problem....and it's pretty damn big one for me. I spent a long time organizing a VST folder tree with various folder & subfolders oragnized by type and my workflow preferences. When the pugin browser is set to FOLDER view, Some of my personal folders are NOT showing up. And worse still, the folders that ARE visible are missing many of the individual plugins that ARE in those folders. Not good. Now, I'm not a noob. The proper VST locations have been selected in "options". If they had not been NONE of my personal folders would be visible.

And it has absolutely nothing to do with any plugins being blacklisted. I know this because the really strange thing about this nonsense is that, when I switch to VENDOR view, ALL of my 3rd party plugins are accessible in their respective companies' folders. This is NOT an acceptable workaround as it's EXTREMELY disruptive to my established work flow to be forced to search through VENDOR folders to find plugins I need for sessions.

And it's DEFINITELY an S1 issue. I also use Plogue Bidule as both a standalone host and VST plugin. Bidule sees my folders and plugins EXACTLY as I have them organized. It sees ALL my folders, subfolders and ALL of my plugins are right there where they should be. So opening Bidule in S1 is a possible workaround but it an extra layer of BS I shouldn't have to deal with.

I don't recall this behavior in previous versions of S1. Do I need to roll back to an earlier verion just to access my plugins or has someone else experienced this issues and resolved it? VERY frustrating!!

I purchased the upgrade to 6 as soon as it was released. I leap frogged from 4 to 6. This wasn't an issue in any version of 4 and I don't recall it being a problem in 6.0 or 6.1 but I'm not sure as I was getting sick at that point. Also I can't really be sure as this was not an upgrade from a previous version. This is a clean install....fresh SSD, OS, plugins etc.

I can see maybe some plugins not showing perhaps due to VST2/3 conflicts. But that doesn't explain why some enitire folders are missing or why the problem isn't replicated in Bidule which sees and displays all folders, subfolders, VST2 & VST3 plugins properly.

Soooo.....I did some digging and....It would seem that the problem was stemming from duplicate ID's. Apparently S1 can't handle having both a VST2 instance AND a VST3 instance of the same plugin without screwing up my VST2 folder system. This REALLY sucks. Bidule and other hosts don't lose their minds over this. But apparently, I'm going to have to go thru my plugin cache with a fine-toothed comb and eliminate ALL VST3 plugins that also have VST2 instances installed JUST so I can use Studio One in the way that best suits my workflow....as I have for years.

VST3 plugins are ridiculously hard to organize in any way that suits my flow. That, of course, is Steinberg's fault. That being said, Studio One's inability to handle co-existing instances VST2/VST3 plugins without making a big mess of my, once orderly, file structure of the lies squarely with Presonus. If even a simple standalone host like Bidule can handle it......there's no excuse for Studio One not to be able to handle plugins in a more sensible manner.

Ok....did some more digging.....Well that was only a partial fix. After deleting all VST3 duplicates of VST2 plugins, (which...BTW...I should NOT have had to do!), and after adding EACH and EVERY one of my folders & subfolders manually to VST plugin paths in "options", the folders are all now visible. But nearly half of my VST2 plugins are not showing up in their folders. This JUST a Studio One problem. Every other host I've tried sees ALL of my VST2 plugins exactly where they live. Cubase? No problem. Reaper? No problem. Bidule? No problem. Even crappy little VSTHost & SaviHost have no problem seeing and instantiating ALL of my plugins.

I've invested a LOT of my time AND money in Presonus. I'd really hate to have to switch to another DAW now but having to open another host inside my main DAW JUST so I can access my plugins is simply not a viable workaround.

You're no newb, but make sure that none of your plugins are hidden. I had a problem where random plugs would be "hidden" after install. Also, make sure that the folders that you're putting your plugs in don't have the same name as the plugin. This wasn't a problem in the past, but seems to be now. After the latest update I had to go through and redo my folders and plugins since some were randomly set to hidden. Studio One is supposed to have the tightest VST3 spec of all DAWs, and the latest update was supposed to put them in full compliance with the VST3 spec.

One way to get hidden folders to populate is to make a folder with the exact same name as the one you're looking for, but add an extra character to it. I usually just added a "1". Then, drag the plugin to the new folder. When the plug registers with that new folder, the old folder will appear. You can then drag the plug to the old folder, and delete the new one.

But, there is something funky going on. S1 was the only DAW that is showing certain problems with VST3 plugins. One example is Reaktor 6. You can't open the extra outputs in the VST3. It simply doesn't work. The VST2 version of Reaktor will open the extra outputs, but you can't see the VST2 version unless you uninstall/move out of the Common Files location the VST3 plugin. I pulled my hair out for a while with that one. In every other DAW that I own there's no issue with either the VST2 or VST3 version of Reaktor 6.

[Resonant- Serpent]

Some have switched over to using VST2 plugins instead of VST3 because of this issue:

https://forums.presonus.com/viewtopic.p ... 92a0ebf9de

[Digivolt]

When the pugin browser is set to FOLDER view, Some of my personal folders are NOT showing up.

That is how folder view works, it doesn't take the folder structure you have on your system, you need to manually setup your own folder structure within studio one in that browser by right click -> new folder, to find plugins to sort you can search for them by name then right click -> show context to see where they are, then you just drag them to the new folder you created, there are some default folders where the plugs will be either by type, for instance compressor, synth, eq etc or by manufacturer depending on how the devs have tagged the plugs, if the plugs are showing up in Vendor view, they should be somewhere in the default folders in folder view

[Trancit]

nevermind...

[harddaysnight]

I actually used to work for Presonus. I switched to Studio One after many years of using various flavors of Cubase/Nuendo. When I made the switch S1 was still at V2. It worked well for me for a long time. I still have a lot of Presonus hardware.

Due to health issues, I had to step away from the game for a while. Now that I'm past that, I decided to jump back in. I just installed the latest version of Studio One Pro: 6.6.2.100548. Installation and activation went fine. Plugin scanner saw all my 3rd party plugins no problem.

But here's the problem....and it's pretty damn big one for me. I spent a long time organizing a VST folder tree with various folder & subfolders oragnized by type and my workflow preferences. When the pugin browser is set to FOLDER view, Some of my personal folders are NOT showing up. And worse still, the folders that ARE visible are missing many of the individual plugins that ARE in those folders. Not good. Now, I'm not a noob. The proper VST locations have been selected in "options". If they had not been NONE of my personal folders would be visible.

And it has absolutely nothing to do with any plugins being blacklisted. I know this because the really strange thing about this nonsense is that, when I switch to VENDOR view, ALL of my 3rd party plugins are accessible in their respective companies' folders. This is NOT an acceptable workaround as it's EXTREMELY disruptive to my established work flow to be forced to search through VENDOR folders to find plugins I need for sessions.

And it's DEFINITELY an S1 issue. I also use Plogue Bidule as both a standalone host and VST plugin. Bidule sees my folders and plugins EXACTLY as I have them organized. It sees ALL my folders, subfolders and ALL of my plugins are right there where they should be. So opening Bidule in S1 is a possible workaround but it an extra layer of BS I shouldn't have to deal with.

I don't recall this behavior in previous versions of S1. Do I need to roll back to an earlier verion just to access my plugins or has someone else experienced this issues and resolved it? VERY frustrating!!

I purchased the upgrade to 6 as soon as it was released. I leap frogged from 4 to 6. This wasn't an issue in any version of 4 and I don't recall it being a problem in 6.0 or 6.1 but I'm not sure as I was getting sick at that point. Also I can't really be sure as this was not an upgrade from a previous version. This is a clean install....fresh SSD, OS, plugins etc.

I can see maybe some plugins not showing perhaps due to VST2/3 conflicts. But that doesn't explain why some enitire folders are missing or why the problem isn't replicated in Bidule which sees and displays all folders, subfolders, VST2 & VST3 plugins properly.

Soooo.....I did some digging and....It would seem that the problem was stemming from duplicate ID's. Apparently S1 can't handle having both a VST2 instance AND a VST3 instance of the same plugin without screwing up my VST2 folder system. This REALLY sucks. Bidule and other hosts don't lose their minds over this. But apparently, I'm going to have to go thru my plugin cache with a fine-toothed comb and eliminate ALL VST3 plugins that also have VST2 instances installed JUST so I can use Studio One in the way that best suits my workflow....as I have for years.

VST3 plugins are ridiculously hard to organize in any way that suits my flow. That, of course, is Steinberg's fault. That being said, Studio One's inability to handle co-existing instances VST2/VST3 plugins without making a big mess of my, once orderly, file structure of the lies squarely with Presonus. If even a simple standalone host like Bidule can handle it......there's no excuse for Studio One not to be able to handle plugins in a more sensible manner.

Ok....did some more digging.....Well that was only a partial fix. After deleting all VST3 duplicates of VST2 plugins, (which...BTW...I should NOT have had to do!), and after adding EACH and EVERY one of my folders & subfolders manually to VST plugin paths in "options", the folders are all now visible. But nearly half of my VST2 plugins are not showing up in their folders. This JUST a Studio One problem. Every other host I've tried sees ALL of my VST2 plugins exactly where they live. Cubase? No problem. Reaper? No problem. Bidule? No problem. Even crappy little VSTHost & SaviHost have no problem seeing and instantiating ALL of my plugins.

I've invested a LOT of my time AND money in Presonus. I'd really hate to have to switch to another DAW now but having to open another host inside my main DAW JUST so I can access my plugins is simply not a viable workaround.

..it might suck if you've got infinite plugins, but what about just making your folders and organizing them within S1 itself?

Works perfectly.

[Dumpster Fire]

I had finally made the decision to switch to Studio One Pro v6 from Cubase 13 Pro. However, the performance of Studio One Pro on my M1 Max MacBook Pro with 64GB of RAM when using the internal audio (i.e., the headphone jack connected via a USB-C adapter) at a buffer size of 128 samples is terrible compared to Cubase. I have tried every combination of Studio One's "Processing" settings within the Audio Setup preferences and I can't seem to get the CPU consumption under control. Here are my current Processing settings:

Dropout Protection: High
Process Block Size: 1,024 samples
Process Precision: Single (32 Bit)

If I decrease the Dropout Protection to Medium, for instance, I will occasionally hear dropouts and crackles. It doesn't matter whether I close my Chrome browser (or any other application running on my Mac). I can run 2X to 5X more plugins in Cubase 13 Pro than I can in Studio One Pro v6.6, all things being equal.

So even though I have owned a copy of Studio One Pro since v2, I "left" Studio One Pro v6.6 after a week of dismal performance and begrudgingly went back to Cubase. I suppose there is always Logic (which I used for a couple of decades before switching to Cubase).

[jamcat]

However, the performance of Studio One Pro on my M1 Max MacBook Pro with 64GB of RAM when using the internal audio (i.e., the headphone jack connected via a USB-C adapter) at a buffer size of 128 samples is terrible compared to Cubase.

I’m on an M1 Pro with 32gb of RAM. I’m using a lot of plugins in Studio One 6, and once I ditched the IK Tape Machines on every track (16+), I haven’t had to worry about CPU at all. I can tell you for sure that your audio routing is going to have a huge impact on CPU use. For example, if you have a CPU heavy plugin in your Master Buss, that is going to impact your performance a lot more than if it’s on a normal audio channel. But that should be the case with any DAW.

How many plugins on how many channels are you running before you start getting drop outs in Studio One?

I do think this is an issue you could resolve with help from PreSonus tech support.

Also, a trick I discovered when I first tried Studio One, (and a major reason why I switched from Cubase) is that you can change your sample rate on the fly without any destructive conversions, unlike Cubase. So if you’re working at 96kHz, you can just change it to 48kHz in the audio settings, and your CPU usage will drop by half, but your source audio will remain 96kHz for mixdown.

[syntonica]

It doesn't matter whether I close my Chrome browser (or any other application running on my Mac).

You should always close ANY browser. They speed things up by caching in memory, basically using as much memory as they can get their digital hands on. Many web pages continue to run in the background, using a large number of CPU cycles doing things that are completely unrelated to displaying information to you. This includes Safari, Chrome, Firefox, etc.