Presonus Studio One 6.1.2 Released

[qtheerearranger]

I did a second test and couldn't reproduce the issue like I could before. Might be intermittent? I'll do some more testing and let you know. Any good tips for a PDC stress test?

bus fx, sidechain busses, time based automation such as lfo, beats, volume shaping etc, and a larger track count where you have all your cores at 50%+ stress but doesn't need to be more.

[greententacle]

I've been reading that PDC is broken in S1. I **think** I may have confirmed it.

I created 32 tracks with the same short click audio file. I created folders/busses and added different fx as inserts and send on the busses and tracks. I routed everything to a parent folder track. The tracks are OUT OF SYNC.

This is a critical error that makes the software unusable...

I'm using v5 (latest). Is the issue still there in v6? I was about to get Sphere, this is a huge disappointment.

i can confirm this, since v5.
s1 is falling apart in complex setups with alot of tracks even if the cpu and ram isn't even sweating.
switched back to cubase because of this, cannot work with it.

[jamcat]

That could be due to certain 3rd party plugins not reporting their latency properly.

[Igro]

Version 4 had these bugs. One of the most annoying one was when you had a looping region and then suddenly the cursor jumped out of that region. Didn't bother to upgrade further.

[Bartone]

That could be due to certain 3rd party plugins not reporting their latency properly.

Any idea if these same plugins make similar issues with other DAWs?

[Danilo Villanova]

I've been reading that PDC is broken in S1. I **think** I may have confirmed it.

I created 32 tracks with the same short click audio file. I created folders/busses and added different fx as inserts and send on the busses and tracks. I routed everything to a parent folder track. The tracks are OUT OF SYNC.

This is a critical error that makes the software unusable...

I'm using v5 (latest). Is the issue still there in v6? I was about to get Sphere, this is a huge disappointment.

i can confirm this, since v5.
s1 is falling apart in complex setups with alot of tracks even if the cpu and ram isn't even sweating.
switched back to cubase because of this, cannot work with it.

Mac or PC?

[chk071]

I've been reading that PDC is broken in S1. I **think** I may have confirmed it.

I created 32 tracks with the same short click audio file. I created folders/busses and added different fx as inserts and send on the busses and tracks. I routed everything to a parent folder track. The tracks are OUT OF SYNC.

This is a critical error that makes the software unusable...

I'm using v5 (latest). Is the issue still there in v6? I was about to get Sphere, this is a huge disappointment.

i can confirm this, since v5.
s1 is falling apart in complex setups with alot of tracks even if the cpu and ram isn't even sweating.
switched back to cubase because of this, cannot work with it.

Hm, not good. And I thought they actually fixed that with v5, but, I'm probably confusing things.

[Danilo Villanova]

Ok I did another stress test and wasn't able to make it go out of sync to the same level that I could the first time. Bouncing a quantized instrument track with Impact XT playing quarter notes using a very short perc sound is NOT perfect. Each note is *very* slightly out of sync but nothing that you could hear, and nothing like my first test.

Automation timing is awful though, much worse than REAPER (which is still not perfect).

I used a short perc sound, put a LP filter plugin as an insert, and wrote "pulse" automation, alternating each beat on and off. The envelope is always late in S1. Not usable for fast automation.

EDIT: I'm staying with S15 for now as my daily driver while keeping my eye on any potential PDC issues and being careful when using fast automation.

[AdvancedFollower]

My trial is expired. I can't believe people don't care about something so critical.

That's something which has always baffled me about Studio One. For long periods of time the program has had serious bugs/issues relating to automation, timing, MIDI jitter etc. that should in theory make the program completely unusable but it seems people just don't care or don't notice the problems.

Many such issues have been fixed, but it has often taken them many months for something that should have been an emergency hotfix. For example side-chain PDC was confirmed to be completely unfunctional for at least 5-6 months some time during the v5 cycle. There's a bug dating back to at least Version 3.5, still present in v6 AFAIK, where the program will *sometimes* simply ignore automation partway through when rendering a mixdown.

I used SO for several years and really enjoyed the workflow and features, but the way both the developer and users stuck their head in the sand in regards to serious, critical issues was very tiring.

[Bartone]

My trial is expired. I can't believe people don't care about something so critical.

That's something which has always baffled me about Studio One. For long periods of time the program has had serious bugs/issues relating to automation, timing, MIDI jitter etc. that should in theory make the program completely unusable but it seems people just don't care or don't notice the problems.

Many such issues have been fixed, but it has often taken them many months for something that should have been an emergency hotfix. For example side-chain PDC was confirmed to be completely unfunctional for at least 5-6 months some time during the v5 cycle. There's a bug dating back to at least Version 3.5, still present in v6 AFAIK, where the program will *sometimes* simply ignore automation partway through when rendering a mixdown.

I used SO for several years and really enjoyed the workflow and features, but the way both the developer and users stuck their head in the sand in regards to serious, critical issues was very tiring.

Yes, that is very bad problem. Especially if it doesn't show up until the rendering the mix down. So you have no idea there is that type of problem. Any ideas is this just on Mac or PC or effecting both? I remember reading about this some time ago, but don't remember was it efefcting both sides PC and Mac.

[greententacle]

I've been reading that PDC is broken in S1. I **think** I may have confirmed it.

I created 32 tracks with the same short click audio file. I created folders/busses and added different fx as inserts and send on the busses and tracks. I routed everything to a parent folder track. The tracks are OUT OF SYNC.

This is a critical error that makes the software unusable...

I'm using v5 (latest). Is the issue still there in v6? I was about to get Sphere, this is a huge disappointment.

i can confirm this, since v5.
s1 is falling apart in complex setups with alot of tracks even if the cpu and ram isn't even sweating.
switched back to cubase because of this, cannot work with it.

Mac or PC?

pc win10

[jamcat]

I’ve noticed that timing issues can be resolved by changing the audio buffer size (at least on Mac.)

Oddly, larger buffer sizes seem to introduce the timing issues.

[Bartone]

Does Studio One upgrades usually go on sale in summer time (like many companys have some summer sale offerings)? Or is it mostly in the Black Friday time?

[jamcat]

Studio One just had a sale that included upgrades in late March when version 6.1 was released.

Last Black Friday did NOT include the upgrade in the sale, only full version and crossgrade.

I wouldn't count on a Summer sale this year.

[bilrobins]

Loving the latest Studio One. I have a small issue - I'm on Windows 11 Pro, pretty powerful PC everything running well and up-to-date. Studio One runs well but strangely the Studio One 'native' instruments and effects cause a slight frame rate lag when they are displayed. It does not affect the sound or functionality but it is as if the frame rate goes from smooth (say 30 fps) to laggy (say 10 fps). This does not happen when external VSTs/plugins are displayed (they are all fast/smooth).

The more powerful instruments/effects seem to cause more lag - e.g. Presence, Mai Tai.

It seems odd as I would expect the Studio One native stuff to be very efficient within Studio One.

I have an Nvidia 1660 super GPU, 32GB RAM, SSD, etc. Everything runs very well otherwise.

Any ideas?