24 postsPage 1 of 2
1, 2
I have been getting the issue where automation does not work during the mixdown (the mixdown dialog window freezes). I know this was a problem, or maybe still is a problem of Studio One. Has this been fixed, and if so, what version was it fixed in? I'm currently running 4.1.1.

My specific problem is that I'm muting buses and automating those buses. It seems to not be a problem for the actual tracks.

Thank you.
Zach
Last edited by formula428 on Sun Aug 23, 2020 8:37 pm, edited 1 time in total.

Studio One Pro version 5.5.1
Win11 (i9 12900K)
64gb DDR4 RAM
M.2 Hard Drive
GeForce 3800
RME UFX+ (USB3.0)
Ferrofish Pulse 16 (ADAT)
Ferrofish Pulse16MX x2 (MADI)
Midas M32 (MADI)
User avatar
by Tacman7 on Sun Aug 23, 2020 5:56 pm
So if you mute and unmute the bus using automation
you won't make it through an export mixdown
but
if you disable that automation then you can?

Good to put your specs in your signature, might be useful info, click the word signature below:

Forum Moderator.
Please add your specs to your SIGNATURE.
Search the STUDIO ONE 6 ONLINE MANUAL. Access your MY.PRESONUS account.
OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET.
Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce.


Studio OnePro6 Melodyne Studio
Win10 Ryzen 5 3600 - Motu M2
Ventura Mac Mini M2 - Zen Go TB
User avatar
by PreAl on Sun Aug 23, 2020 8:34 pm
4.6.2 is the final 4.x version of Studio One, You should update to this regardless..

Version 5 is now out.

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 formula428 on Sun Aug 23, 2020 8:43 pm
I've updated my signature.

The mixdown will still happen, but those busses that were muted/unmuted via automation will not properly be incorporated.

Sometimes they will mute and not unmute. Sometimes vice versa. Sometimes they work fine. Sometimes nothing automates.

It depends on the buss to exactly what happens, but it is consistent everytime.

Studio One Pro version 5.5.1
Win11 (i9 12900K)
64gb DDR4 RAM
M.2 Hard Drive
GeForce 3800
RME UFX+ (USB3.0)
Ferrofish Pulse 16 (ADAT)
Ferrofish Pulse16MX x2 (MADI)
Midas M32 (MADI)
User avatar
by espenaure on Sun Nov 22, 2020 11:19 pm
Same here. Freezes towards the end and ignores the VCA automation.
Im on 4.6.2

Intel Core i7-7800X 3.5GHz / Asus Prime X299-A / GeForce GTX 960 / 32GB Corsair Vengeance DDR4 3000MHz
Fractal Design R5 Black Pearl / Fortron Hydro G 750W / Be Quiet! Dark Rock Pro 3 / Samsung M.2 NVMe 960 EVO 250GB
Samsung SSD 850 EVO 500GB x 4 / 4TB HDD Storage / Windows 10 x64 / RME UFX / RME ADI-8 DS MKIII / [b]Presonus Studio One 5 Pro
/ Presonus Faderport 8 / Adam Audio A77X /[/b]
// Synthesizers.com / Moog Sub 37 / Octatrack / Analog 4 / Korg MS20m / Beyerdynamics DT990 Pro / Logan SMII / Doepfer MAQ 16/3 / MacBook Pro 2015
User avatar
by Steve Carter on Mon Nov 23, 2020 12:20 am
Yup - posted recently with similar occurrences (v4.6..latest) with automation and tracks dropping out towards end of mixdown. Didn’t manage to solicit any solutions and I’m guessing that the developers are unlikely to be concerned as their focus is now v5....

Hoping for a Black Friday offer for the upgrade ‘cos we’re in lockdown again here in France and I’m self employed so gotta be careful with expenditure - keep safe out there!

Windows 10 Pro/i7 6800k @3.4Ghz/16Gb ram. Studio One 6 Pro, Melodyne Editor, Vocalign Project 5, Superior Drummer 3, Izotope Music Production Suite 6, Komplete 13 and various other plugins. Focusrite Saffire Pro 40, Faderport, Focal Alpha 50's, Korg Pa3x, Korg Pad Kontrol, numerous guitars, basses & other antiquated outboard gear.
Maybe one day I'll actually finish a project!
User avatar
by jeffreydemuth on Sun Dec 06, 2020 4:47 pm
Hello,
I have the same problem. When exporting and using automation the automation is not being rendered after 1:20. This happens every time and is very vexing. I'm using S1 version 5.1.1.61815 and I have noticed this problem since version 3. I will write to support and see if I get any help.

Windows 10
Intel Core i5-6600K CPU @ 3.50GHz
16.0 GB RAM

Geoff DeMuth
User avatar
by santtuforsstrm on Sat Jan 02, 2021 3:19 am
I am using version 4.6.2 and I have the same problem. Automation on all kinds of VSTi's doesn't work when exporting the project to one audio file. It seems to be random: some track automation works but every time some automation is not read during the exporting.

This problem should be a priority for Presonus, as it impacts the workflow and the whole end result of the user experience of the DAW. I haven't found a workaround on this, and bouncing every individual track and checking that the automation was bounced correctly is really time consuming and frustrating. I'm really considering changing to another DAW because of this.
User avatar
by rubennorg2 on Mon Jan 25, 2021 3:19 pm
Same problem here, using version Studio 5.1.2.
It mostly happens to 1 or 2 automation out of 200+ tracks, but everytime I bounce the faulty automation channels, the problem just begins with another channel suddenly.

I've been trying to bounce 1 track now for more than 1,5 hours, on a deadline for a big client, and have to explain them my DAW is glitching, which it utterly unprofessional.

Everytime you think Studio One fixed something, another big problem comes up...
User avatar
by wdkbeats on Tue Jan 26, 2021 2:29 pm
This bug is very old, shame it's still not fixed.

The only solution I found is to grab the export window every 1 minute (before it freezes) i just slightly move it. That keeps the rendering in the foreground and automation is rendered properly.

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 rubennorg2 on Tue Jan 26, 2021 3:34 pm
wdkbeats wroteThis bug is very old, shame it's still not fixed.

The only solution I found is to grab the export window every 1 minute (before it freezes) i just slightly move it. That keeps the rendering in the foreground and automation is rendered properly.


Boi that’s something I didn’t try yet, gonna try it tomorrow first hand, will keep you posted if it works for me!
User avatar
by wdkbeats on Wed Jan 27, 2021 9:42 am
rubennorg2 wroteBoi that’s something I didn’t try yet, gonna try it tomorrow first hand, will keep you posted if it works for me!


Cool, let me know if it works for you :thumbup:

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 formula428 on Sat Feb 27, 2021 10:29 am
Grabbing the window does seem to work for non-real-time mode, thought i haven't tried it in real time yet with my outboard gear.

At least there is a workaround so far.

Studio One Pro version 5.5.1
Win11 (i9 12900K)
64gb DDR4 RAM
M.2 Hard Drive
GeForce 3800
RME UFX+ (USB3.0)
Ferrofish Pulse 16 (ADAT)
Ferrofish Pulse16MX x2 (MADI)
Midas M32 (MADI)
User avatar
by ferdinanddemarezoyens on Thu May 06, 2021 5:05 pm
Wow. This problem has been frustrating me since version 3. Finally found this work around. What a relieve. Rather strange though that Presonus must know about this bug and somehow decided that it doesn't have enough priority to fix it for several years. It probably only affects a small minority of the users, but still..... I am going to send in another bug report. Hopefully this helps. Anyway, glad there is a work around.

W10 64 bit
Designare z390 motherboard
Intel I9 9900K
Apollo 6X Thunderbolt
Studio One 5.2.1 Professional
User avatar
by JimmiG on Fri May 07, 2021 3:27 am
formula428 wroteGrabbing the window does seem to work for non-real-time mode, thought i haven't tried it in real time yet with my outboard gear.

At least there is a workaround so far.


Also known among Studio One users as "Shaking the Box". PreSonus haven't yet figured out what causes this bug even though it has been around for 5+ years.
User avatar
by ferdinanddemarezoyens on Mon May 10, 2021 8:38 am
I've written a script that does the moving of the window automatically :-) Works really well for me.

If you have the free program Auto Hotkey installed, save the code below via Notepad and add the .ahk extension. If you double click this file before rendering it will run in the background and move the progress bar window every ten seconds. If you use Studio One in a language other than English, you will need to change the name of the window in the script.


CoordMode, Mouse, Screen
Z:=0
Loop
{
Sleep, 10000
WinWait, Please wait... ahk_exe Studio One.exe
WinGetPos, X, Y,,, Please wait...
X:=X+100 ; coordinates for empty spot in window title bar
Y:=Y+15
Click, %X% %Y% 0 ;move to coordinates but don't click
Click, Down
If Z = 0
{
X:=X+5
Y:=Y+5
Z:=1
}
else
{
X:=X-5
Y:=Y-5
Z:=0
}
Click, %X% %Y% 0
Click, Up
}
User avatar
by bailatosco on Thu May 13, 2021 7:09 am
Hahahahahaha. Niiiiiice.
A script to shake the little window, glad it works.
You have to admit this is really funny though.

PD: but also SAD. Sad Presonus. Presadnus. :lol:

Intel i7 - 11700k 5.0Ghz / 32Gb RAM
WIN 10 Pro 64bit
Studio One v5.4.0 Professional
Presonus Studio 192 USB 3.0
User avatar
by ezraboucher on Sun May 30, 2021 1:22 pm
I was having this problem + got it to work by rendering the mixdown in real time.
User avatar
by ferdinanddemarezoyens on Mon May 31, 2021 12:50 am
ezraboucher wroteI was having this problem + got it to work by rendering the mixdown in real time.


Glad this worked for you. I usually render in real time and more often than not I do experience the bug in that scenario.

In my experience the CPU load plays a role. The bigger the load the bigger the chance of the bug occuring. Real time rendering lowers the CPU demand in most cases so it may help, but it isn't a real solution, or at least not for me.
User avatar
by syscam on Sun Jul 11, 2021 9:03 am
hi all,

was the problem already solved with you ?I have a solution that works for 3 of my friends too

greetz Chris

Windows 10 pro 64-Bit, i7 6700k 4.0 GHz, 16GB RAM, nv 1060gtx 6gb, 2 x 120GB SSD, 1 x 1 TB, 1 x 2 TB HDD, Studio One 2-4 Professional 64-Bit NI KK S49 MK2

24 postsPage 1 of 2
1, 2

Who is online

Users browsing this forum: No registered users and 96 guests