Studio One 3.5 Released.

[aMUSEd]

I wish we could create categories for VST Fx and Instruments and organize them accordingly. Favourites/last used are nice, but not enough.

You can

http://www.studio-one.expert/studio-one ... r-features

[Funkybot's Evil Twin]

I wish we could create categories for VST Fx and Instruments and organize them accordingly. Favourites/last used are nice, but not enough.

You can

http://www.studio-one.expert/studio-one ... r-features

I did exactly this a week or two ago. Works like a charm. Been there since version 3.1.

[aMUSEd]

Yes it's a very well thought out implementation. I like how you can hide plugins too (eg I hid all my mono GRM Tools as I only use stereo)

[Aliens]

Nice update. Thanks PS.

[tapiodmitriyevich]

I wish we could create categories for VST Fx and Instruments and organize them accordingly. Favourites/last used are nice, but not enough.

You can
http://www.studio-one.expert/studio-one ... r-features

How could I miss that? Thanks so much.
EDIT: I didn't miss it. I always thought the folder view represents real folder structures, therefore I never really used to view.

[aMUSEd]

Been testing this with some of my more CPU intensive synth patches - there's one Serum patch I use that always caused glitches in the past in S1 and still does in every other host apart from Reaper and Logic (of course). Amazingly now S1 joins them in being able to run this patch glitch free (and other similarly intensive ones).

[aMUSEd]

One interesting thing I did find though is that both S1 and Logic seem to pull this off differently from Reaper. Using the system activity monitor to check CPU in most hosts this particular very CPU greedy patch uses between 60-90% of one core, depending how many voices are playing, which manages to choke all hosts other than S1 and Logic when it gets closer to the 80-90% (with more voices playing and long sustain). So it looks like S1 and Logic manage somehow to run the synth at high CPU levels but without it causing glitches in the audio engine.

On the other hand Reaper does something very different, it just uses CPU more efficiently in the first place. The same patch still running with lots of voices refuses to go over 50% (according to activity monitor) of one core in Reaper (in fact Reaper's own meter has it at 12-13% but I think it is aggregating it with other cores).

The worst performers btw are Reason and Waveform - they get glitchy even at around 60-70% CPU.

[beatmangler443]

One interesting thing I did find though is that both S1 and Logic seem to pull this off differently from Reaper. Using the system activity monitor to check CPU in most hosts this particular very CPU greedy patch uses between 60-90% of one core, depending how many voices are playing, which manages to choke all hosts other than S1 and Logic when it gets closer to the 80-90% (with more voices playing and long sustain). So it looks like S1 and Logic manage somehow to run the synth at high CPU levels but without it causing glitches in the audio engine.

On the other hand Reaper does something very different, it just uses CPU more efficiently in the first place. The same patch still running with lots of voices refuses to go over 50% (according to activity monitor) of one core in Reaper (in fact Reaper's own meter has it at 12-13% but I think it is aggregating it with other cores).

The worst performers btw are Reason and Waveform - they get glitchy even at around 60-70% CPU.

Of course reason is the worst performance it just came out with vst support. These users need to give them time to freakin fix it. How long did it take steinberg to fix the bug issues with cubase the cpu spikes, cpu overload. Ableton jacked up Live 8. Studio One 3 did not run well for a lot of people until this update.

[aMUSEd]

Yes I know - this is after the new update which should have improved things somewhat though

[incubus]

Reaper (at least on windows is the VERY BEST, PERIOD) Now I don't like other things about it, but it's the best BAR-NONE at handling cpu use. If you beg to differ, I'm calling bullshit.

Honestly, after all the flak I've taken from "fanbois" (and mods) it's a ashame that it's not universally better.

It cannot simply be "user error" or "specs" at this point in time.

I applaud the effort (greatly) but overall it seems that people with issues, are people with issues. If they could permanently get this one thing right, it's a terrific host.

[The Noodlist]

Yep, Reaper handles CPU heavy plug-ins like Acustica Acqua plug-ins efficiently compared to S1 3.5.
I can't see the point of upgrading, as guitarist, all the new features don't really appeal to me.
Now, if it was efficient as Reaper, it would be a different matter.
Currently evaluating Reaper, rather than upgrading S1, I would consider Reaper.

[THE INTRANCER]

Yep, Reaper handles CPU heavy plug-ins like Acustica Acqua plug-ins efficiently compared to S1 3.5.
I can't see the point of upgrading, as guitarist, all the new features don't really appeal to me.
Now, if it was efficient as Reaper, it would be a different matter.
Currently evaluating Reaper, rather than upgrading S1, I would consider Reaper.

We've long past version 3.5... 4.6 feels like a whole new extensively expanded application by comparison... not just in visual features but in ones you can't see such as further CPU optimisation and multithreaded processing of multi-instruments, and that of the native instruments included, such as Presence and Mai Tai...

This thread highlights the raft of changes and updates besides a lot more...so it's probably worth taking a look if you haven't already..

viewtopic.php?f=7&t=505021

[The Noodlist]

We've long past version 3.5... 4.6 feels like a whole new extensively expanded application by comparison... not just in visual features but in ones you can't see such as further CPU optimisation and multithreaded processing of multi-instruments, and that of the native instruments included, such as Presence and Mai Tai...

This thread highlights the raft of changes and updates besides a lot more...so it's probably worth taking a look if you haven't already..

viewtopic.php?f=7&t=505021

I installed the V4 demo, then uninstalled it and never really explored it in any depth.
The demo has expired for V4, might hold out till V5.

I'd like to know how much CPU Acustica Violet CM and similar use in S1 V4 compared to Reaper?
It didn't cross my mind to test during the trial period.

[THE INTRANCER]

The difference between Studio One and Reaper is negligible when it comes to CPU comparison and more than ever than there's ever been. If you were comparing with Reason, Ableton, and to somewhat less extent to Bitwig Studio then you would have a different story due to the underlying moving cogs they have or lack of optimisation they have had over the years. Studio One's plugins are tested to be CPU efficient, that's not always the case with third party ones and one has to question certain plugins that are given away free with magazines...maybe they are not as CPU friendly as they seem. In any case, there is a lengthy article about Acustica's plugins, which should shed some light and perhaps some wariness in using plugins created by them.

https://acusticaudio.freshdesk.com/supp ... erformance

A few weeks back, you could have grabbed S1 Pro 4.5 for just £130, and 12 months later bought the upgrade for around £59 to Studio One 5.XX during blackfriday. This provides a gap to allow any immediate issues on a big release to be largely resolved.

[The Noodlist]

Has anyone had issues with audio tracks with effects and transform to audio? It's not producing anything here, no waveform.
Post edit - answered my own question
Delete the files in the folder /User/AppData/Roaming/PreSonus/Studio One 3 with the exception of the Licenses Folder, Extension Folder and user license.