13 posts
Page 1 of 1
I've been with S1 since the beginning and this I'm seeing for the first time: The blue progress bar below the CPU usage bar is constantly growing larger and then reducing as songs play; and sometimes, if I jump far enough ahead, only some tracks play until S1 "catches up" and loads the remaining tracks. The song in question has about 20 tracks total, yet I mixed a song in 6.0.2 that had ~80 tracks with no such issue.

Is anyone else seeing this?

Windows 10 64-bit | Studio One Pro (newest update at time of posting the message) | 8 cores | 16GB Ram | Focusrite Scarlett 18i20 interface (2nd Gen) | Presonus Eris E44 Monitors | Atom SQ | Roland VG-99 | EZBass, EZKeys 2, Superior Drummer 3, EZ Drummer 3, various other virtual instruments | a surfeit of guitars and third-party plugins :)

Newest release, using Studio One

Other music created in Studio One
User avatar
by PreAl on Sun Mar 26, 2023 9:26 am
You should be able to drill down into the CPU section is studio one and see what specific plugins are using a lot of CPU. Consider updating your plugins esp those with high CPU, or optimizing the setup of that plugin within the song (if possible).

Also check your disk space.

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 SMcNamara on Sun Mar 26, 2023 10:39 am
Thanks, PreAI, but it's not the plugins causing the problem (the CPU usage %age is fine), it's the track usage (for lack of a better term); sorry if that was confusing. The CPU bar stays constant, and the other one jumps around a lot. All new to 6.1

Windows 10 64-bit | Studio One Pro (newest update at time of posting the message) | 8 cores | 16GB Ram | Focusrite Scarlett 18i20 interface (2nd Gen) | Presonus Eris E44 Monitors | Atom SQ | Roland VG-99 | EZBass, EZKeys 2, Superior Drummer 3, EZ Drummer 3, various other virtual instruments | a surfeit of guitars and third-party plugins :)

Newest release, using Studio One

Other music created in Studio One
User avatar
by PreAl on Sun Mar 26, 2023 11:13 am
SMcNamara wroteThanks, PreAI, but it's not the plugins causing the problem (the CPU usage %age is fine), it's the track usage (for lack of a better term); sorry if that was confusing. The CPU bar stays constant, and the other one jumps around a lot. All new to 6.1


You might want to install a copy of process explorer. Check your read/write speeds, maybe your bus is maxing out (assume you are using SSD and not got your drives plugged into USB or slow ports). Latency monitor also gives important information as well (not just latency) everybody should be using it/should know how to use it, it's a vital utility.

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 SMcNamara on Sun Mar 26, 2023 11:19 am
I'll check out a process explorer but the inescapable fact is that everything worked smoothly the day before 6.1 (no bus issues, and I am using an internal SSD, an "E" drive for S1 projects).

As I wrote that one thing came to mind, and if you or anyone has insight on this: I did backup (to several locations) and then delete a very significant amount of data from this "E" drive (~150GB out of 1TB), which drive has since been optimized, and it's possible something further needs to be done (though the issue seems chronologically tied to the 6.1 download). Any suggestions?

Thanks,

P.S. The "E" drive is only about 50% full, so a near-full SSD is not the issue

Windows 10 64-bit | Studio One Pro (newest update at time of posting the message) | 8 cores | 16GB Ram | Focusrite Scarlett 18i20 interface (2nd Gen) | Presonus Eris E44 Monitors | Atom SQ | Roland VG-99 | EZBass, EZKeys 2, Superior Drummer 3, EZ Drummer 3, various other virtual instruments | a surfeit of guitars and third-party plugins :)

Newest release, using Studio One

Other music created in Studio One
User avatar
by PreAl on Sun Mar 26, 2023 1:01 pm
And please check out latency monitor, that's probably the more important tool here.Often upgrades can bring out issues with the operating system that never were an issue before (and it may be the case other elements of the OS or drivers may need upgrading).

Software works on dependencies. Linear logic would dictate that if you upgrade an application, and then something bad happens, then it must be the application at fault, however that is not necessarily the case and often isn't.

You do not need.to defrag SSD's, upgrading their firmware may help and perhaps even the motherboard BIOS. If you have a Samsung SSD then Samsung magician software is a must.

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 stefanrauch1 on Sun Mar 26, 2023 2:44 pm
Would you mind testing, if the issue goes away, after you bounced in place all audio events of the song?
If so, then I'd recommend to be patient and not yet potentially ruin your computer with deep system changes.

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 Sun Mar 26, 2023 3:07 pm
Well I wouldn't do anything until I've attempted to diagnose the problem with Process Explorer/Latency Monitor first. There is not enough information here to diagnose any issue.

I'm not saying my advice is definitive either, I don't have all the answers. These are forums and we should be getting several opinions and suggestions, however more info is necessary.

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 alexmorris6 on Mon Apr 03, 2023 9:36 am
I have same issue and more in Studio One 6.1. It is not usable in this state with any plugs enabled or not. Playback is dropping and skipping every 5 seconds, before the update. everything was fine.

my PC is good enough to run two of these with many V-instruments and plug-ins. This needs to be fixed or let us revert back to 6.0
User avatar
by SwitchBack on Mon Apr 03, 2023 10:21 am
Cache Activity.png
Cache Activity maybe? Watch the Cache Activity meter when the stuttering occurs.

S1 stores any cache work like stretching, transposing, etc. with the songs so that it doesn't have to do it again when reopening the song. Maybe moving to a new version requires 're-caching'. Also, make sure that the S1 version you use has read/write rights to the Cache directory of the song you're working on.

NB. When you open a song and caching occurs then (you can) wait until that's done before starting to work on/with the song.
User avatar
by PreAl on Mon Apr 03, 2023 10:44 am
6.1.1 is here.
Otherwise please see previous responses giving advice and asking for further information, no point in repeating (and please put your specs in your signature).

I have no issue with 6.1.1

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 Mon Apr 03, 2023 12:31 pm
alexmorris6 wroteI have same issue and more in Studio One 6.1.

alexmorris6 wroteThis needs to be fixed or let us revert back to 6.0

Why do you use 6.1 if a maintenance update that fixes many potential issues has been released already?

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 Blame Karma on Wed Apr 05, 2023 9:38 am
PreAl wroteYou do not need.to defrag SSD's, upgrading their firmware may help and perhaps even the motherboard BIOS. If you have a Samsung SSD then Samsung magician software is a must.

Windows Defragger (W10 +W11) does not defrag SSDs but rather executes several optimization commands such as TRIM. If OP or anyone else has issues with drive speed, this is the first thing to do. If that doesn't work, use other tools to verify drive integrity.

BTW, is this issue fixed with 6.1.1? I'm curious, as it sounds like it could be the cache issue.

Mac Mini M1 / Ryzen 1700X - W10 / Sphere / 1810c / Apollo Twin

13 posts
Page 1 of 1

Who is online

Users browsing this forum: davidlarson6 and 55 guests