Studio One 5 Available Now (5.3 Out June 29th, 2021)

[antic604]

Can you have it so an automation line shows over the track, but the clips don't get greyed out?

Settings / Automation / Disable Events Under Automation Envelopes <- untick that

[Digivolt]

Any tips for getting better CPU load spread across unused cores ?



I'm only at 31% usage yet because some single cores are near 90% I'm getting the clicks and pops occasionally

I know there's bouncing and the other option, to disable my acustica plugs but..... I bought my 3950x thinking I would be able to avoid this and be able to use acustica plugs without issue

[chk071]

Welll... that's the thing innit? Single core beats multi core.

I wonder how many plugin instances the project you show in the screenshot has though. Actually, it should be pretty evenly spread. Unless there's something wrong with Studio One.

Your CPU's single core performance should be very good though. Maybe you have some very expensive plugins in the project, which tax the single cores like that?

[Digivolt]

I don't know and I'm not counting but I'd say at least 200 plugs as that's a 62 track song including bus & sends

I did read the way S1 processes stuff is that it's all done on the same core when you do sends, so if I'm sending 10 tracks to a reverb send or delay send (or both) it will process them in series on the one core, not sure if this correct ? From the looks of things it is correct

Also something that has been bugging me for ages



If I were to merge these 2 sections I would lose the volume faders, how do I "merge" them together so it gives me a longer fader the size of the 2 sections merged ???

[chk071]

I don't know and I'm not counting but I'd say at least 200 plugs as that's a 62 track song including bus & sends

Sounds like a pretty heavy project though.

I don't know. Impossible to say really, unless you compare a similar project in another host.

[AdvancedFollower]

Regardless of the host used, a lot of it comes down to simple logic and physics.

If you have a long chain of plugins in series, it's physically impossible to break them up and process in parallel. The input into each plugin in the chain depends on the output of each previous plugin in the chain successively combined. E.g. If you have a chain of plugins A->B->C->D, A has to be calculated first, fed into B, then that result into C, and finally into D. You can't just calculate the results of A and B independently in parallel and feed both into C, because that would be parallel processing (of the actual audio signal), not serial. Of course if you have an actual parallel signal flow in your mix, even partially, that can and will be calculated in parallel in SO, just as in any other modern DAW.

Another issue is that most plugins are themselves not multi-threaded. A single-threaded plugin that uses a significant portion of a single core will skew the CPU load towards that core. If you have several other plugins in series after that plugin, it's possible to overload a single core even though other cores appear almost idle.

No DAW has solved those issues. Maybe when we get quantum computers.

[chk071]

Conclusion: Don't use so many sends?

[Funkybot's Evil Twin]

In part, this can be mitigated in a very unintuitive way: use more inserts and fewer sends. Or strategically split up your sends (e.g. one send for drum Reverb, another send for vocal Reverb, and don't stack sends). The goal is to set up your project in a way where the processing can be more evenly split across multiple channels. The old way of "run one Reverb and send multiple tracks to it to use less CPU" no longer applies the same way in the day of giant multi-core chips. With a large core count, more, smaller chains works better than fewer, larger chains.

[MuzikFreq]

Hmmm.... The samplers in studio one 5 are strange. Every other daw had rock solid playback but in studio one I see some phase fluctuations.
My test is
1. Load up a impact
2. Choose a kick sample and a bass sample
3. Layout a KbBB pattern
4. Load up Psyscope (oscilloscope)

Also tested this with individual samplers and studio one is the only one with phase issues

[oneway]

Hmmm.... The samplers in studio one 5 are strange. Every other daw had rock solid playback but in studio one I see some phase fluctuations.
My test is
1. Load up a impact
2. Choose a kick sample and a bass sample
3. Layout a KbBB pattern
4. Load up Psyscope (oscilloscope)

Also tested this with individual samplers and studio one is the only one with phase issues

Is monitoring engaged on the instrument while this is happening?

Do you see the same fluctuation when bouncing a Mixdown of the track?

[MuzikFreq]

Hmmm.... The samplers in studio one 5 are strange. Every other daw had rock solid playback but in studio one I see some phase fluctuations.
My test is
1. Load up a impact
2. Choose a kick sample and a bass sample
3. Layout a KbBB pattern
4. Load up Psyscope (oscilloscope)

Also tested this with individual samplers and studio one is the only one with phase issues

Is monitoring engaged on the instrument while this is happening?

Do you see the same fluctuation when bouncing a Mixdown of the track?

The problem isn't from the samples, the samplers are the main culprit. Currently in bitwig the phase hasn't shifted one and has a rock solid scope.
The phase issue is also in reason11 with the redrum but not kong. Ableton flat out sounded off to my ears.

[oneway]

I’m assuming the samples are fine. Is monitoring engaged on the instrument (the sampler) while this is happening?

Do you see the same fluctuation when bouncing a Mixdown of the track (the sampler playing back samples)?

I’m asking because most DAWs have some form of safety buffer during playback and it can get bigger when monitoring, which can make playback of instruments sound very slightly different than they will when rendered. A discerning ear (or an oscilloscope) can usually pick up on this.

[MuzikFreq]

I’m assuming the samples are fine. Is monitoring engaged on the instrument (the sampler) while this is happening?

Do you see the same fluctuation when bouncing a Mixdown of the track (the sampler playing back samples)?

I’m asking because most DAWs have some form of safety buffer during playback and it can get bigger when monitoring, which can make playback of instruments sound very slightly different than they will when rendered. A discerning ear (or an oscilloscope) can usually pick up on this.

Funny enough, I actually had a save file from Studio One which I tried a few other things.
I had opened ReasonRack and used the NNXT sampler from it which gave significantly better results. has 1 teeny tiny moment where it shows a super tiny part of the transient flipping phase but is so small I can't hear the difference.
Which this begs the question.
If a 3rd party can get a sampler right from ages ago, why can't a more modern DAW native plugin have similar or better results?

Impact and the Sampler are doing something funny when playing back audio which no one else really has going on

[EnGee]

Do you have this problem when you are playing a midi trigger and when you draw midi notes? Maybe there is a double triggering caused by your hardware. I had such problem before and it was very tricky but in the end it was my hardware setup which is triggering double midi notes.

[MuzikFreq]

Do you have this problem when you are playing a midi trigger and when you draw midi notes? Maybe there is a double triggering caused by your hardware. I had such problem before and it was very tricky but in the end it was my hardware setup which is triggering double midi notes.

No double triggers