53 postsPage 2 of 3
1, 2, 3
PreAl wrote
wdkbeats wroteWere the automation and PDC issues ever fixed? These were (or maybe still are) very serious bugs in Studio One.


PreAl wroteWhat version are you running?
What issues are you experiencing?


wdkbeats wroteI have the latest version. Haven't been using S1 for a while now, since these bugs made it unfit for professional work. Just asking if these bugs were fixed. Were they?



Do you have steps to repro, links to the existing issue/s? References. Specifics and details please about the actual bug/s. Maybe research for yourself here in the releases readme files.


You have been on this forum for 5 years, written almost 3000 posts and yet you pretend you don't know what I'm talking about? Come on... This has been reported numerous times here, there are a few threads explaining these issues in great detail (with links to YT videos), just seach i.e. "PDC", "Automation latency", "Automation during rendering".

Automation is still not playing and rendering correctly, depending on what latency is introduced by plugins on a track you want to automate and on all the busses that track is routed to.

For example: you have a synth track routed to Synht Bus which is routed to All Music Bus routed to Master Bus. The track and all busses have some heavier plugins on, each introducing different latency (i.e. from 1.5ms to 500ms like Ozone 10 or Acustica Audio stuff). Open an automation track on that synth track and automate the Mute button in sync with the tempo of the project. The result is that Mute closes and opens not exactly on the beat but slightly later, depenting on the cumulative latency.

Confirmed it on 3 different systems, all running Windows 10.

PC: AMD Ryzen 3900X, 32GB RAM DDR4 3600MHz CL16, ASUS ROG Strix X570-F, Gigabyte Radeon RX 570 8GB, SSD CORSAIR SSD MP510 960GB M.2 NVMe (OS)
OS: Windows 10 Pro x64
DAW: Studio One Professional x64
Gear: RME Fireface 802 + RME Advanced Remote, Prometheus Acoustics monitors, Avantone Mixcubes, JBL 305p, Softube Console 1, Presonus Faderport, AKAI Advance 61, Presonus Faderport, Beyerdynamic DT-990 Pro
User avatar
by PreAl on Thu Mar 23, 2023 9:35 am
wdkbeats wroteYou have been on this forum for 5 years, written almost 3000 posts and yet you pretend you don't know what I'm talking about? Come on... This has been reported numerous times here, there are a few threads explaining these issues in great detail (with links to YT videos), just seach i.e. "PDC", "Automation latency", "Automation during rendering".

Automation is still not playing and rendering correctly, depending on what latency is introduced by plugins on a track you want to automate and on all the busses that track is routed to.

For example: you have a synth track routed to Synht Bus which is routed to All Music Bus routed to Master Bus. The track and all busses have some heavier plugins on, each introducing different latency (i.e. from 1.5ms to 500ms like Ozone 10 or Acustica Audio stuff). Open an automation track on that synth track and automate the Mute button in sync with the tempo of the project. The result is that Mute closes and opens not exactly on the beat but slightly later, depenting on the cumulative latency.

Confirmed it on 3 different systems, all running Windows 10.


Sorry but I do not have an amazing memory that keeps track of everything nowadays. I'm mostly busy working and I do not mind meld with these forums or indeed visit them that regularly. There are also a billion alleged, confirmed and fixed bugs on these forums.

If you are vague, somebody else may reply with what they think is the same or similar issue, when it is nothing of the sort.

I don't even have V6, I maintain an interest because I'm considering upgrading. If there are indeed serious bugs I wont bother. Just saying "PDC" issues isn't exactly helpful. The thread I read just now has a mixture of apparent PDC issues, it's entirely ambiguous whether they are all confirmed bugs, fixed or not fixed. So when we talk about about existing bugs it's important to be specific.

Did you pretend this issue exists? I highly doubt it, so please don't accuse me of "pretending", that's just silly and out of order, and somebody else here just now just asked for clarification. Also more or less impossible to search for somebodies specific issue when they don't give the specifics, I'm not playing Google whack a mole.

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by garybowling on Thu Mar 23, 2023 11:58 am
I'm still having problems with files that were in v5. If I load them into v6 I have timing issues. Previous to 6.1, I could toggle the audio engine from 32bit to 64bit or vice versa and the timing issues went away. But with 6.1, the timing issues are just there, nothing seems to resolve it.

It's not a huge problem right now, I just keep my old version in v5. But eventually I would like to remove v5 from my computer and this is going to be an issue.

Anything created from scratch in v6 seems to be ok. Another user reported that importing tracks to v6 also worked ok. But to do that I need to figure out how to get all my busses imported. Apparently there are some things you can do to a bus to make it appear in the "import song data" dialog. But I've yet to find an simple way I can quickly do that to all my bus's.

ASUS laptop (AMD 5900HX), 32G, 2x2TB SSD, Win11-64, RME UFX & BabyFace, Studio One Pro 6, Addictive Drums2, Izotope 10, Soothe2, Waves, many plugins, Melodyne Studio 5, all versions updated frequently

The Moderns,
https://open.spotify.com/artist/1x6Fd133GftlRyRYl0xgjf
User avatar
by stefanrauch1 on Thu Mar 23, 2023 12:34 pm
wdkbeats wroteWere the automation and PDC issues ever fixed? These were (or maybe still are) very serious bugs in Studio One.

The PDC in Sidechains got fixed, but I remember there were some scenarios where you can still break the PDC in general.
One example is if you use the LLC in Presonus ProEQ³ in High Quality mode after a sidechain-active plugin. PDC is then out of sync on (re)loading the song until you toggle "High Quality" off and on again.
Other examples (if I remember correctly) had to do with Monitoring and Routing Midi from one Instrument to another one..

Did not hear much about the automation offline render issue lately. Might be resolved. I had it happen with very long songs with many plugins and therefor slow offline render speeds, ..but I did not do such renders recently.

OS: Win10 x64 || Software: Studio One Pro [latest version]
Hardware: AMD Ryzen 9 3950X || Asus Prime X570-PRO || 64GB DDR4 RAM || Asus Dual-RTX2070S-A8G-EVO || UAD2 Octo & Duo PCIe
Peripherals: RME Fireface UFX II (+2x ADA8200) || Faderport Legacy || Atom || NI Komplete Kontrol A25
Audio Settings: 44,1/48kHz, 256 Samples, DP Off, 64 Bit
User avatar
by PreAl on Thu Mar 23, 2023 1:22 pm
I'm quite surprised there isn't a sticky thread with a price list. I did not realise Pro 6 upgrade was £89. That's a sweet spot, I may jump on the bandwagon tomorrow although I'll probably wait for 6.1.1 to upgrade, once the new bugs with new functionality have been ironed out (early days) or go with the previous patch.

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by bradch00 on Thu Mar 23, 2023 9:54 pm
Probably just a missing brain cell, but the "Audio Device Controls" seem to have disappeared from beside the Master fader. I have gone into "tools/spanner" but the option is "greyed" out. The previous release V6 worked fine with the Quantum.

Mac Studio M1 Max 64GB RAM 1TB Flash
5 x 2TB SSD Thunderbolt
2 x 1TB SSD USB
2 X 16TB spinning disk for backup
DAW: Studio One, Pro Tools Studio
Interface: Presonus Quantum, Black Lion (Red) Sparrow A/D
Nectar LX88, Yamaha DTX III Extreme
Control Surface: Faderport & Faderport 8
User avatar
by garyanderson5 on Fri Mar 24, 2023 4:09 am
stefanrauch1 wrote
wdkbeats wroteWere the automation and PDC issues ever fixed? These were (or maybe still are) very serious bugs in Studio One.

The PDC in Sidechains got fixed, but I remember there were some scenarios where you can still break the PDC in general.
One example is if you use the LLC in Presonus ProEQ³ in High Quality mode after a sidechain-active plugin. PDC is then out of sync on (re)loading the song until you toggle "High Quality" off and on again.
Other examples (if I remember correctly) had to do with Monitoring and Routing Midi from one Instrument to another one..

Did not hear much about the automation offline render issue lately. Might be resolved. I had it happen with very long songs with many plugins and therefor slow offline render speeds, ..but I did not do such renders recently.


Monitoring and Routing Midi from one Instrument to another one.. Was still present last i checked. Not sure if 6.1 cured this. Everything prints ok but playback is always out of sync by the latency introduced from the plugins in use. Unless you use zero latency plugins it's horrid during playback. It's been around sinse 2015, very easy to replicate the issue. I don't understand why it hasn't been addressed already it's been brought up enough times over the years.

The PDC in Sidechains got fixed for sure. I was one of the victims of this but it was fixed around 5.2 if i remember right. I am sure you had this issue as well if i remember :(

Like you i havn't seen the automation render issue for a while but i don't do long renders that much. I can't say i ever get render problems to be honest on a typical song project.

I never use Presonus ProEQ I have alternatives i prefer.

Windows Pro 11 22H2, 13900K, Z790 Aorus Master, 64GB 32x2 G.Skill Trident Z C30 RAM, 2X 2TB Samsung 980 PRO, ADATA XPG SX8200 PRO 2TB, RX6650XT GFX Card, Corsair RM1000X PSU, Studio One Latest Version & Older versions, Baby Face Pro FS. Nektar T6,
User avatar
by shanabit on Sat Mar 25, 2023 6:30 pm
Just upgraded to 6.1 from 5, so far all good.

StudioOnePro 6.1
UA Apollo Twin
OSX Sonoma 14.2

iMac 2013
User avatar
by DelTomix on Tue Mar 28, 2023 4:44 pm
I discovered that export mixdown on a multi-instrument omits some (sometimes all) sustain events. I had to go back to 6.0.2 to get a usable mixdown. The realtime playback has no issue so you wouldn't know until you review the mixdown result.

Moving the same event to direct (non-multi) instrument track has no issue. I tested repeatedly including a new song and exporting/re-importing the part as an audioloop

Would be so amazing some day to get bugs fixed without always introducing new ones at the same time. I wish they could just make a stable long-term support version with only bugfixes since I could care less about additional features at this point. What I care about is having a DAW that I can trust - and for the long term to recall and preserve my work.

Studio One Pro v6.x in Windows 10, AMD CPU, 32GB RAM, NVMe SSD(s), Focusrite Saffire Pro24 (firewire)
User avatar
by jazzundso on Tue Mar 28, 2023 5:36 pm
DelTomix wroteI discovered that export mixdown on a multi-instrument omits some (sometimes all) sustain events. I had to go back to 6.0.2 to get a usable mixdown. The realtime playback has no issue so you wouldn't know until you review the mixdown result.

Moving the same event to direct (non-multi) instrument track has no issue. I tested repeatedly including a new song and exporting/re-importing the part as an audioloop

Yes, it's a known issue which will be resolved in a next maintenance update.

Lukas Ruschitzka
Studio One Specialist
Advanced Studio One Tutorials || Free Studio One Scripts || Studio One Tutorial Database || Studio One Toolbox [ s1toolbox.com ]

Core i7 3.24 GHz, Windows 10, 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5

Clavia Nord Stage 3 - Moog Sub 37 - YAMAHA MoXF6 - M-Audio Axiom Pro 61 - Kawai ES-920 - Studio One 5 - Notion 6 - Orchestral Tools Junkie XL Horns, ProjectSAM Symphobia, Cinematic Studio Series, Strezov Sampling Afflatus, VSL Synchron Special Edition, KOMPLETE 9 Ultimate
User avatar
by PreAl on Tue Mar 28, 2023 5:44 pm
jazzundso wroteYes, it's a known issue which will be resolved in a next maintenance update.


I have no doubt you are telling the truth here, but was wondering how you found it would be fixed? (What was the source?). Is this a sphere thing or did you contact support?.(Maybe a thread I missed?).

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by jazzundso on Tue Mar 28, 2023 5:47 pm
Working closely with QA and development, I know :)

Lukas Ruschitzka
Studio One Specialist
Advanced Studio One Tutorials || Free Studio One Scripts || Studio One Tutorial Database || Studio One Toolbox [ s1toolbox.com ]

Core i7 3.24 GHz, Windows 10, 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5

Clavia Nord Stage 3 - Moog Sub 37 - YAMAHA MoXF6 - M-Audio Axiom Pro 61 - Kawai ES-920 - Studio One 5 - Notion 6 - Orchestral Tools Junkie XL Horns, ProjectSAM Symphobia, Cinematic Studio Series, Strezov Sampling Afflatus, VSL Synchron Special Edition, KOMPLETE 9 Ultimate
User avatar
by PreAl on Tue Mar 28, 2023 5:49 pm
jazzundso wroteWorking closely with QA and development, I know :)

Sorry - read your profile, wasn't clear to me
Have just spotted you are a mod however. Please don't harm me ;)

p.s. Anything else you care to spill the beans on?

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by jazzundso on Tue Mar 28, 2023 6:14 pm
PreAl wrotep.s. Anything else you care to spill the beans on?

Yes: There's an improvement in 6.1 that apparently nobody has found so far. Quite a nice little workflow feature. It will be featured in a video soon ;)

Lukas Ruschitzka
Studio One Specialist
Advanced Studio One Tutorials || Free Studio One Scripts || Studio One Tutorial Database || Studio One Toolbox [ s1toolbox.com ]

Core i7 3.24 GHz, Windows 10, 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5

Clavia Nord Stage 3 - Moog Sub 37 - YAMAHA MoXF6 - M-Audio Axiom Pro 61 - Kawai ES-920 - Studio One 5 - Notion 6 - Orchestral Tools Junkie XL Horns, ProjectSAM Symphobia, Cinematic Studio Series, Strezov Sampling Afflatus, VSL Synchron Special Edition, KOMPLETE 9 Ultimate
User avatar
by DelTomix on Tue Mar 28, 2023 8:35 pm
jazzundso wroteYes, it's a known issue which will be resolved in a next maintenance update.


Ah thats good to know. Thanks Lukas!
Also while we are here - Just want to say I appreciate your videos very much - your choice of focus and perspectives relate well to me.

Studio One Pro v6.x in Windows 10, AMD CPU, 32GB RAM, NVMe SSD(s), Focusrite Saffire Pro24 (firewire)
User avatar
by vasilypinchuk on Tue Mar 28, 2023 11:13 pm
Is the audio cache bug in 6.1 already reported?
User avatar
by PreAl on Wed Mar 29, 2023 3:07 am
vasilypinchuk wroteIs the audio cache bug in 6.1 already reported?


What exactly is that?

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by DF Music on Wed Mar 29, 2023 6:46 am
PreAl wrote
vasilypinchuk wroteIs the audio cache bug in 6.1 already reported?


What exactly is that?


Studio One feature “Use cache for timestretched audio files” is half broken in v6.1.0
This means that v6.1.0 is able to read those cache files created in previous versions of S1 but unable to create new ones. So all audio files with different tempo inserted in to project will always timestretched in real time and this project will quickly becomes unresponsive because of disc read overload. I’m on Mac, however at least on user of this forum already reported similar behavior on Windows viewtopic.php?f=151&t=51072

Here is how to reproduce:
1. Make sure that “Use cache for timestretched audio files” is checked in Preferences - Advanced - Audio
2. Create blank project and insert a couple audio files with different tempo
3. Click on Performance meter in transport bar and look in to Cache - Used - it should display a total size of cached audio files.
4. On my end It stays at 0 (Zero)
5. Now press on a little wrench icon and then press “Show cache folder”
6. Explorer/Finder window will open showing you Cache folder for this project
7. If it is blank means that S1 is unable to create cache files and will timestrecth in real time
8. Now save this project and reopen it in previous version, v6.0.2 for example, and look in to Cache folder again - it should be populated with files which names starts with @@0@@ - this means that S1 successfully created cache files
9. Save project and reopen it in v6.1.0, then look into Performance meter - Cache - Used again. It will show you a total size of cache folder
10. After that v6.1.0 is able to read those cache files and behave normally without disk overload.

This new bug is a real showstopper for those who like to use loops with different tempo or let’s say decided to change project tempo etc.
Hope it will be fixed in the next update and we don’t need to wait almost a year like fix for that famous PDC on Side-Chain bug
User avatar
by patricemazmanian on Wed Mar 29, 2023 8:24 am
DF Music wrote
PreAl wrote
vasilypinchuk wroteIs the audio cache bug in 6.1 already reported?


What exactly is that?


Studio One feature “Use cache for timestretched audio files” is half broken in v6.1.0
This means that v6.1.0 is able to read those cache files created in previous versions of S1 but unable to create new ones. So all audio files with different tempo inserted in to project will always timestretched in real time and this project will quickly becomes unresponsive because of disc read overload. I’m on Mac, however at least on user of this forum already reported similar behavior on Windows viewtopic.php?f=151&t=51072

Here is how to reproduce:
1. Make sure that “Use cache for timestretched audio files” is checked in Preferences - Advanced - Audio
2. Create blank project and insert a couple audio files with different tempo
3. Click on Performance meter in transport bar and look in to Cache - Used - it should display a total size of cached audio files.
4. On my end It stays at 0 (Zero)
5. Now press on a little wrench icon and then press “Show cache folder”
6. Explorer/Finder window will open showing you Cache folder for this project
7. If it is blank means that S1 is unable to create cache files and will timestrecth in real time
8. Now save this project and reopen it in previous version, v6.0.2 for example, and look in to Cache folder again - it should be populated with files which names starts with @@0@@ - this means that S1 successfully created cache files
9. Save project and reopen it in v6.1.0, then look into Performance meter - Cache - Used again. It will show you a total size of cache folder
10. After that v6.1.0 is able to read those cache files and behave normally without disk overload.

This new bug is a real showstopper for those who like to use loops with different tempo or let’s say decided to change project tempo etc.
Hope it will be fixed in the next update and we don’t need to wait almost a year like fix for that famous PDC on Side-Chain bug


Bug confirmed, S1 6.1 does not create a cache file, back to 6.0

S1 pro 6 -Vienna Ensemble Pro - Melodyne - Notion 6 - Win10 - jBridge 1.65 - Motherboard ASUS Z87-K - i7 4770K 3.5Ghz, 32 Go RAM - GeForce GT 610 1024MB - Audio interface RME Hammerfall multiface II - Faderport - ADAT Interface Focusrite Scarlett OctoPre - EWQL hollywood-orchestra...
User avatar
by jazzundso on Wed Mar 29, 2023 10:04 am
vasilypinchuk wroteIs the audio cache bug in 6.1 already reported?

Yes, and this as well will be fixed in an upcoming update.

Lukas Ruschitzka
Studio One Specialist
Advanced Studio One Tutorials || Free Studio One Scripts || Studio One Tutorial Database || Studio One Toolbox [ s1toolbox.com ]

Core i7 3.24 GHz, Windows 10, 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5

Clavia Nord Stage 3 - Moog Sub 37 - YAMAHA MoXF6 - M-Audio Axiom Pro 61 - Kawai ES-920 - Studio One 5 - Notion 6 - Orchestral Tools Junkie XL Horns, ProjectSAM Symphobia, Cinematic Studio Series, Strezov Sampling Afflatus, VSL Synchron Special Edition, KOMPLETE 9 Ultimate

53 postsPage 2 of 3
1, 2, 3

Who is online

Users browsing this forum: No registered users and 96 guests