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

[oneway]

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

What is your device block size and what are your Dropout Protection settings? If you’re running dropout protection above Minimum you might be running your instruments at a higher buffer than you think which can contribute to problems like this in some hosts and also in some plug-ins.

[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

What is your device block size and what are your Dropout Protection settings? If you’re running dropout protection above Minimum you might be running your instruments at a higher buffer than you think which can contribute to problems like this in some hosts and also in some plug-ins.

Focusrite 18i20 Gen3
512 Samples
48kHz
Input/output: 22.2ms / 1056 samples

Minimum Dropout Protection
Process Block Size 512 Samples
Process Precision 64bit
Monitor Latencies both are 55ms / 2642samples

But I doubt any of this is an issue as, like I said, using a different sampler fixes the issue yet the built in samplers are bad at being consistent

[oneway]

I mean logically it shouldn’t be an issue, but the S1 audio engine has a little more jitter with instrument playback (in some cases) above 256 sample buffers so perhaps its stock plug-ins are exhibiting a similar issue.

You’re not monitoring so it shouldn’t be that, but the way to tell if that’s it for sure would be to mixdown the output of SampleOne or Impact at different buffers and compare the results in an audio editor. Basically seeing whether this phase issue only affects playback or rendering.

Not saying you have to or anything, it’s just what I would do if I had this issue and wanted to point it out to get it fixed. Loading up another sampler may be the most efficient choice

[EnGee]

I'll try to duplicate it. I don't use Impact or sampler one, but it might be a bug. Let's see. What's KbBB pattern?

[MuzikFreq]

I'll try to duplicate it. I don't use Impact or sampler one, but it might be a bug. Let's see. What's KbBB pattern?

Pretty much 16th note pattern for psytrance.

I just tried Sampleone and it seems to not give the issue anymore while impact still does

[EnGee]

I don't do psy. Is it Kick bass bass bass about 127 tempo?

[MuzikFreq]

I don't do psy. Is it Kick bass bass bass about 127 tempo?

yes but my tests i do at 140

[EnGee]

I don't do psy. Is it Kick bass bass bass about 127 tempo?

yes but my tests i do at 140

Sorry, I tried but I don't hear anything abnormal (I'm ignorant about psy though!).

If you do it like the guy here in the video, can you also hear phase fluctuation? Or only when you use Impact?



There is a helpful guy here who is making psy using S1. His username is "recursive one". I hope he can help you here or you maybe can send him a PM.

[BONES]

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

WTF!?! What are you doing, writing an opera for a full symphony and 120 voice choir as individual instruments? What I honestly believe you need to do is learn how to be more efficient, how to plan your projects so that you don't get up to 200 plugins in the first place. I doubt I use 20 plugins on any song I work on and, whilst that's probably at the other end of the scale, you must surely be able to simplify your projects without losing anything significant? I don't see how you can get a decent result with a set-up that complex.

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?

Who cares? If you need an oscilloscope to see the "issue", then I'd suggest it's not an issue at all. Seriously, you really don't need to worry about minutiae like this, it's just bullshit.

[antic604]

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?

Who cares? If you need an oscilloscope to see the "issue", then I'd suggest it's not an issue at all. Seriously, you really don't need to worry about minutiae like this, it's just bullshit.

Sorry to break it to you, but for the more rhythmical EDM genres - like psytrance - using oscilloscope to match / tune kick & bass is a pretty standard technique, so it's not "bullshit". If you want tight, punchy groove at 145BPM on a big sound system this is just a necessity

[Digivolt]

What I honestly believe you need to do is learn how to be more efficient, how to plan your projects so that you don't get up to 200 plugins in the first place.

Every channel has at least a ProQ3 and Mvmeter on, so it's quite easy to get 200 plugs (this includes the synths) on a 62 track song

[antic604]

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

Looks & sounds fine here.

Check your audio settings, because - at least with v4 - I remember there were cases where some tighter patterns sounded "funky" with high dropout protection and in particular when low latency monitoring was enabled.

[AdvancedFollower]

I've had nothing but problems when using Dropout Protection. It causes plugins like Kickstart to go completely out of time, too. I just keep it at the minimal setting and adjust the device buffer size instead.

In fact I'm getting rather frustrated with the constant timing and jitter issues with Studio One. There's always some big problem with the mixing engine, automation, latency, jitter, timing etc, and it takes some sensationalist article from Admiral Bumblebee or some other higher publicized source before PreSonus even take notice and acknowledge the issue. They should hire some beta testers who focus on the core mixing features of the software so you don't always have to worry about something fundamental breaking every time they release an update. Still waiting for a fix for the sidechain APDC issue, which has basically made my normal mixing template unusable.

[chk071]

I just keep it at the minimal setting and adjust the device buffer size instead.

Anything else uses too much CPU here anyway...

[EnGee]

What I honestly believe you need to do is learn how to be more efficient, how to plan your projects so that you don't get up to 200 plugins in the first place.

Every channel has at least a ProQ3 and Mvmeter on, so it's quite easy to get 200 plugs (this includes the synths) on a 62 track song

I would render or bounce the Synths tracks before adding any EQ or compressor so I get raw audio I can mix comfortably later if I were you.
I think this is the traditional way for mixing and will free lots of CPU resources for the mixing stage