125 postsPage 1 of 7
1, 2, 3, 4, 5 ... 7
I have problems with bus volume automation when updating the master file. I have a plain normal volume fader automation in one of my buses. The graph goes like -inf -> 0 -> -inf -> -1.4 -> 0 during my four minute song, i.e. there are four changes in the song. The first two work all right, but the second one does not show in the master file. In real time everything works fine, but master file update does not.

Is this a bug or is there something I do not understand?
User avatar
by karismolander on Mon Apr 02, 2018 4:36 am
Real time mixdown loses the automation totally, i.e. the fader does not follow it. In real time playing everything works fine.
User avatar
by karismolander on Mon Apr 02, 2018 4:45 am
This seems to be a long time known problem: viewtopic.php?f=151&t=18235

Most of the other threads are for some reasons locked or disabled. The thread above is also closed.

I have the most latest version of S1, and the problem still persists.
User avatar
by karismolander on Mon Apr 02, 2018 8:35 am
My conclusion, after hours of testing: volume automation does not work in 3.5.6. or it works just occasionally. I have tried it in buses and tracks and only some have appeared in mixdowns or mastering updates. I have deleted and recreated automation envelopes.

In real time live playing it works exactly right. In mixdowns and mastering not. This is a total show stopper. I cannot complete my tasks.
User avatar
by sebastianholtzer on Mon Apr 02, 2018 11:13 am
Yeah! Welcome in da Club :P :D
Does the Mixdown-Box freeze while you export the audio file?
If yes, try to shake it to prevent freezing. Some Users had luck with this and it seems to help even me but i don`t use realtime rendering and i still notice some incorrect rendered things.
Then i read that you should set your Device Block Size to the highest Size once you export PlugIns and Automations.
And yes some threads seems to be locked. Thank you. I thought they banned me. Now i know i`m not alone.
User avatar
by robertgray3 on Mon Apr 02, 2018 11:23 am
sebastianholtzer wroteAnd yes some threads seems to be locked.


They weren’t locked, they were consolidated into a thread that was deleted! :P

Curious about this issue though, sorry to hear you’re dealin with that. I’ll do some bus volume automation when I’m back in the studio and see what happens.

Mac OS X Mojave 10.14
Mac Pro (Late 2013)
3 GHz 8-Core Intel Xeon E5
32 GB 1066 MHz DDR3
Dual AMD FirePro D500 3072 MB
User avatar
by karismolander on Mon Apr 02, 2018 11:26 am
Really? Yes, the box freezes in mixdown, in about 60%. Shake the dialog? And it is not April 1st any more. So this is a known bug and not fixed?
This totally prevents me from finishing my task. The only way that I can think to go around this is to create extra tracks for each event with different volumes. Luckily I have only one and not so important gradual change in my volume fader. How do people use automation in lead vocal channels or buses, if needed? These are often complex and gradual.
I wonder why these threads were locked and some even disabled. This is a serious bug.
User avatar
by robertgray3 on Mon Apr 02, 2018 12:08 pm
There's not a lot to go off here but I did some quick tests on 10.12.6 Mac OS X, Studio One 3.5.6

I could not replicate the behavior you mentioned of Master Files not updating and Mixdowns not reflecting Bus Volume Automation or Track Volume Automation.

It's likely that either the forum or Support will need more information on your individual situation and operational flow before anyone can duplicate what you're seeing. If the actual mixdown isn't reflecting your automation it might be productive to start with that. Can you show your routing in your mixer and your export mixdown settings?

My steps that produced a normal result, for reference:

1. create a project from a template
2. create an audio track with a test tone lined up at -6 db
3. loop this for 24 bars
4. put the end marker at 24 bars
5. assign the audio track to a bus
6. automate the volume on the bus.
7. Song -> Add to Project -> New Project

Here, the Project reflects the automation accurately

8. Went to the song
9. Made an adjustment to the bus automation
10. Made an adjustment to the audio track volume automation
11. Song -> Update Mastering File
12. Navigate to the Project

Here, the Project reflects the automation accurately

13. Go back to the song
14. Make changes to the bus and track volume automation
15. Navigate back to the project
16. Update Mastering Files from the Project window

Here, the Project reflects the automation accurately

17. Go back to the song
18. Export Mixdown between Start and End markers with "Import to Track" selected.
19. Imported Mixdown accurately reflects the automation.
Last edited by robertgray3 on Mon Apr 02, 2018 12:11 pm, edited 1 time in total.

Mac OS X Mojave 10.14
Mac Pro (Late 2013)
3 GHz 8-Core Intel Xeon E5
32 GB 1066 MHz DDR3
Dual AMD FirePro D500 3072 MB
User avatar
by jpettit on Mon Apr 02, 2018 12:11 pm
Presonus is aware of certain rendering issues.
The problem is the conditions to replicate are usually very complex as many here can testify to.

The problem with the threads that have been locked or removed is due to other forum rule issues.

Please try your best to keep the conversation to steps to replicate the wrong behavior.

Presonus would love to fix the issue if it can be reasonably be replicated.

Perhaps you have a new simpler case example?

My Website, Free Studio One Advance Training
SPECS:Win 10 64-bit, 12 Core i7: 32Gb DDR4 ram, 40" 4K monitor, StudioLive 24, Quantum, Faderport16, Central Station Plus, Sceptre 6,Temblor T10, Eris 4.5, HP60, Studio One Pro 4.0, Reaper 5.9, Sonar Platinum
User avatar
by robertgray3 on Mon Apr 02, 2018 12:12 pm
jpettit wrotePresonus is aware of certain rendering issues.
The problem is the conditions to replicate are usually very complex as many here can testify to.

The problem with the threads that have been locked or removed is due to other forum rule issues.

Please try your best to keep the conversation to steps to replicate the wrong behavior.

Presonus would love to fix the issue if it can be reasonably be replicated.

Perhaps you have a new simpler case example?


Good idea, you should save that song/project to a new folder as a test case and send it to Support.

Mac OS X Mojave 10.14
Mac Pro (Late 2013)
3 GHz 8-Core Intel Xeon E5
32 GB 1066 MHz DDR3
Dual AMD FirePro D500 3072 MB
User avatar
by karismolander on Mon Apr 02, 2018 12:21 pm
I have about 20 tracks, three VST synths, Superior 3, ten buses, 2 FX buses, Console 1 in each bus and channels, two sidechains, 1-5 plugins in each track and bus, Softube Tape MixFX with passthrough, a couple of normal tape plugins. How can I or you replicate this exactly? Creating this project has taken lots of hours. This is a complex project, but it can run easily in my Xeon with 128 sample buffer (MOTU 828ES).
User avatar
by jpettit on Mon Apr 02, 2018 12:32 pm
karismolander wroteI have about 20 tracks, three VST synths, Superior 3, ten buses, 2 FX buses, Console 1 in each bus and channels, two sidechains, 1-5 plugins in each track and bus, Softube Tape MixFX with passthrough, a couple of normal tape plugins. How can I or you replicate this exactly? Creating this project has taken lots of hours. This is a complex project, but it can run easily in my Xeon with 128 sample buffer (MOTU 828ES).

Bummer was hoping for a simpler case.

You will have to take smaller steps to workaround the issue like pre bouncing tracks or sections.

When you have time Sabastian is tracking down a trail on the side-chain as a possible cause to the issue.

Perhaps a test song with sidechain can demonstrate it in the future.

My Website, Free Studio One Advance Training
SPECS:Win 10 64-bit, 12 Core i7: 32Gb DDR4 ram, 40" 4K monitor, StudioLive 24, Quantum, Faderport16, Central Station Plus, Sceptre 6,Temblor T10, Eris 4.5, HP60, Studio One Pro 4.0, Reaper 5.9, Sonar Platinum
User avatar
by karismolander on Tue Apr 03, 2018 9:48 am
Here is an experiment that explains something, maybe.

I made a mixdown (mastering update) and constantly moved the position of the mixdown dialog.
The result: the automation worked exactly as it should have worked. All automation changes were recorded to the mastering file. Everything was fine. The dialog did not froze.

Then I made another mixdown (mastering update) without moving the mixdown dialog.
The result: The dialog froze in about 55% of progress, but the process completed after waiting. None of the automation changes were recorded. The track automated was silent.

This is really weird. Maybe you can now find the bug easier.
User avatar
by robertgray3 on Tue Apr 03, 2018 10:47 am
karismolander wroteHere is an experiment that explains something, maybe.

I made a mixdown (mastering update) and constantly moved the position of the mixdown dialog.
The result: the automation worked exactly as it should have worked. All automation changes were recorded to the mastering file. Everything was fine. The dialog did not froze.

Then I made another mixdown (mastering update) without moving the mixdown dialog.
The result: The dialog froze in about 55% of progress, but the process completed after waiting. None of the automation changes were recorded. The track automated was silent.

This is really weird. Maybe you can now find the bug easier.


That’s super weird! :) I still suspect support will want to look at the .song file to see how the project is routed and what effects are on what channels/buses. If you can save a backup of the affected song file and send it to Support when you have more time after the project that would probably be best. If routing plays a role in this it could offer much more information.

I’ve seen people post about this before but I haven’t seen a lot of confirmation that people sent their .song files to Support. That’s probably how it will get solved, just a thought. Anyhow thanks for posting about it :thumbup:

Mac OS X Mojave 10.14
Mac Pro (Late 2013)
3 GHz 8-Core Intel Xeon E5
32 GB 1066 MHz DDR3
Dual AMD FirePro D500 3072 MB
User avatar
by scottyo7 on Tue Apr 03, 2018 11:09 am
To the OP,
Your spec's would help. ;)
Please create a signature* with your PC, SW and HW specs and versions, so we know how to better help you... now and in the future.
See mine or another users at the *bottom of their posts for an example.
You can create one in your User Profile.

What's your 'Performance' meter percentage at?
Your 3 VI's may be loading down your CPU a lot... check out "Rendering" in the manual which may help?
Have you optimized your PC for audio recording... things like turning off your WiFi and Antivirus SW, minimizing HD interrupts file indexing, etc.?

"This is just my opinion... one of millions... so please only take it as such"

Add your Signature & Gear Spec's Here.
ASUS G75VX, i7 3820QM; 16GB; 2 Samsung 840 SSD's; NVIDIA GTX 670MX; Win 8.1.
S1 Pro v4.1.1; EZD2 2.1.7. Behringer UMC404HD USB A/I.
Synths: Alchemy, Air Tech Music Suite. Melodyne Studio 4.2. Ozone 5, (all 64bit).
Akai MPK249. Six guitars. 2 Line 6 POD's & an E-bow.
Rode NT1; Shure SM58. Faderport; KRK Rokit 8's; Dual 28" Monitors.

My Band: https://soundcloud.com/2guyzinabasement/tracks
Just Me: https://soundcloud.com/scott_pfeil
User avatar
by karismolander on Tue Apr 03, 2018 1:13 pm
I will post my specs when I have time. I have Windows 10, Xeon E3-1231 V3, Asus Z97-A, 8 Gb, couple of terabytes hard disk, MOTU 828ES.
S1 runs fine the song in real time, without glitches.
Actually in my latest experiments the VSTi:s, except Superior 3 were disabled.
I really have optimized my PC. I am an experienced software professional and I know what I do. I have built my own pc:s for the last 25 years.

If real time playing works without glitches, why asynchronous rendering does not? That does not make sense at all.

I need a bug fix. I can help myself.
User avatar
by robertgray3 on Tue Apr 03, 2018 1:28 pm
scottyo7 wroteHave you optimized your PC for audio recording... things like turning off your WiFi and Antivirus SW, minimizing HD interrupts file indexing, etc.?


The gist that I've gotten from the previous posts on this is that it is a complex issue that isn't as simple as the CPU being heavily taxed. There's a lot of data on how the session is setup that will help Support in the .song file, that'll hopefully clear some things up- hope you get it sorted out karismolander.

Mac OS X Mojave 10.14
Mac Pro (Late 2013)
3 GHz 8-Core Intel Xeon E5
32 GB 1066 MHz DDR3
Dual AMD FirePro D500 3072 MB
User avatar
by jpettit on Tue Apr 03, 2018 1:44 pm
karismolander wroteHere is an experiment that explains something, maybe.

I made a mixdown (mastering update) and constantly moved the position of the mixdown dialog.
The result: the automation worked exactly as it should have worked. All automation changes were recorded to the mastering file. Everything was fine. The dialog did not froze.

Then I made another mixdown (mastering update) without moving the mixdown dialog.
The result: The dialog froze in about 55% of progress, but the process completed after waiting. None of the automation changes were recorded. The track automated was silent.

This is really weird. Maybe you can now find the bug easier.

Yes, Sabastian has found this out as well.

He calls it "shaking the box"
It seems to keep your computer from going into low power mode or screen shutting off.
and might just be the core of the problem.

My Website, Free Studio One Advance Training
SPECS:Win 10 64-bit, 12 Core i7: 32Gb DDR4 ram, 40" 4K monitor, StudioLive 24, Quantum, Faderport16, Central Station Plus, Sceptre 6,Temblor T10, Eris 4.5, HP60, Studio One Pro 4.0, Reaper 5.9, Sonar Platinum
User avatar
by sebastianholtzer on Tue Apr 03, 2018 1:58 pm
karismolander wroteHere is an experiment that explains something, maybe.

I made a mixdown (mastering update) and constantly moved the position of the mixdown dialog.
The result: the automation worked exactly as it should have worked. All automation changes were recorded to the mastering file. Everything was fine. The dialog did not froze.

Then I made another mixdown (mastering update) without moving the mixdown dialog.
The result: The dialog froze in about 55% of progress, but the process completed after waiting. None of the automation changes were recorded. The track automated was silent.

This is really weird. Maybe you can now find the bug easier.


...so yes...shaking that box really helps...

May I ask you something?
1. Are you sidechaining the Presonus Compressor(s) (not the Fat Channel) with a Send?
2. Is one or more Compressor(s) receiving more than one Source of a Sidechain Trigger?
3. Are you using a Noise Gate to trigger some Instruments?

I wanted to do a test with my song and removing them, because 1, 2 and 3 are the case here at my side and I think the Bug is in the DAW and it`s PlugIns and not somewhere else.
User avatar
by sebastianholtzer on Tue Apr 03, 2018 2:00 pm
jpettit wrote
karismolander wroteHere is an experiment that explains something, maybe.

I made a mixdown (mastering update) and constantly moved the position of the mixdown dialog.
The result: the automation worked exactly as it should have worked. All automation changes were recorded to the mastering file. Everything was fine. The dialog did not froze.

Then I made another mixdown (mastering update) without moving the mixdown dialog.
The result: The dialog froze in about 55% of progress, but the process completed after waiting. None of the automation changes were recorded. The track automated was silent.

This is really weird. Maybe you can now find the bug easier.

Yes, Sabastian has found this out as well.


I read this somewhere in the forum here before. A guy was talking about that before i had this bug and i was reminding then. But that explains why I was so confused in the 3.5.5 thread when it worked a few times and then not. Think you remember.

Btw.: Is shaking wrong? Really moving in english? Excuse me I´m german :D
Last edited by sebastianholtzer on Tue Apr 03, 2018 2:01 pm, edited 1 time in total.

125 postsPage 1 of 7
1, 2, 3, 4, 5 ... 7

Who is online

Users browsing this forum: benschmidt1 and 18 guests