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.Danilo Villanova wrote: ↑Sun Jun 04, 2023 3:28 am 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?
Presonus Studio One 6.1.2 Released
-
qtheerearranger
- KVRian
- 606 posts since 26 Mar, 2014 from Denver, Co
• Studio One 6.5 is my primary DAW.
• Ventura 13.0
• MacBook Pro 2023
• M2 Max
• 96 GB Ram
• 2x Daisy-Chained Universal Audio Apollo Quads
• Ventura 13.0
• MacBook Pro 2023
• M2 Max
• 96 GB Ram
• 2x Daisy-Chained Universal Audio Apollo Quads
-
greententacle
- KVRist
- 341 posts since 30 Nov, 2008
Danilo Villanova wrote: ↑Thu Jun 01, 2023 6:26 am 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
- KVRAF
- 4372 posts since 2 Sep, 2019
That could be due to certain 3rd party plugins not reporting their latency properly.
THIS MUSIC HAS BEEN MIXED TO BE PLAYED LOUD SO TURN IT UP
-
Igro
- KVRAF
- 4757 posts since 26 Apr, 2007 from Noosphere
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.
-
Danilo Villanova
- KVRian
- 917 posts since 30 Apr, 2018
Mac or PC?greententacle wrote: ↑Sun Jun 04, 2023 11:49 amDanilo Villanova wrote: ↑Thu Jun 01, 2023 6:26 am 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.
-
chk071
- KVRAF
- 33909 posts since 11 Apr, 2010 from Germany
Hm, not good. And I thought they actually fixed that with v5, but, I'm probably confusing things.greententacle wrote: ↑Sun Jun 04, 2023 11:49 amDanilo Villanova wrote: ↑Thu Jun 01, 2023 6:26 am 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.
-
Danilo Villanova
- KVRian
- 917 posts since 30 Apr, 2018
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.
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
- KVRian
- 1184 posts since 8 May, 2018 from Sweden
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.Danilo Villanova wrote: ↑Fri Jun 02, 2023 4:08 am My trial is expired. I can't believe people don't care about something so critical.
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
- KVRist
- 289 posts since 4 Apr, 2021
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.AdvancedFollower wrote: ↑Wed Jun 07, 2023 3:03 amThat'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.Danilo Villanova wrote: ↑Fri Jun 02, 2023 4:08 am My trial is expired. I can't believe people don't care about something so critical.
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.
-
greententacle
- KVRist
- 341 posts since 30 Nov, 2008
pc win10Danilo Villanova wrote: ↑Mon Jun 05, 2023 3:57 amMac or PC?greententacle wrote: ↑Sun Jun 04, 2023 11:49 amDanilo Villanova wrote: ↑Thu Jun 01, 2023 6:26 am 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
- KVRAF
- 4372 posts since 2 Sep, 2019
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.
Oddly, larger buffer sizes seem to introduce the timing issues.
THIS MUSIC HAS BEEN MIXED TO BE PLAYED LOUD SO TURN IT UP
-
Bartone
- KVRist
- 289 posts since 4 Apr, 2021
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
- KVRAF
- 4372 posts since 2 Sep, 2019
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.
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.
THIS MUSIC HAS BEEN MIXED TO BE PLAYED LOUD SO TURN IT UP
-
bilrobins
- KVRist
- 283 posts since 7 Mar, 2020
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?
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?