Version 5.1.2 Release Notes (January 19, 2021):

New features and improvements:
● Updated ARA integration for VocAlign
The following issues have been fixed:
● Wrong audio may play from cache on soloed track when changing song tempo
● Potential freeze when editing Event FX
● [macOS] Graphics hardware acceleration option shown active even when unavailable
● [macOS] Plug-in window not resizing correctly when switching tabs among Audio Units
● [macOS] Key switch dialog “OK” and “Cancel” button positions swapped
● [macOS] Main window may exit fullscreen mode when a plug-in window is pinned
● [Auto Filter] Filter closes when cutoff is set to high and LFO is engaged
● [FaderPort] Manual page count incorrect after returning from autofill mode
● [FaderPort] Page left/right buttons get stuck in UI when remote-controlled
● [Control Link] Paged static mappings do not respect non-pageable controls
● [Slate Raven] Potential crash on adding tracks
● [ProEQ2] Piano keyboard overlay missing after switching among multiple instances
● [Macro Organizer] Hitting a letter repeatedly will lose keyboard focus
● [Ampire] Sound changes while swapping inactive stomps’ positions
● [Ampire] Cabinet image "M65" is upside down
● Potential crash when using MMC Record
● Potential crash on opening multiple events with Melodyne or VocAlign
● Potential crash when rapidly enabling and disabling multiple folder tracks
● Loop length tooltip is showing wrong values
● Copy sends from the Track Inspector does not work
● Deleting automation via range selection creates unwanted node at start of selection
● Potential crash on removing plug-in via drop-down menu
● Tuner shows wrong octave
● Potential crash on instantiating Fat Channel
● Wrong behavior with "No Overlaps" when moving two audio events simultaneously
● Mai Tai UI key bed and music playback may freeze when playing a note
● Crash on executing "Expand Folder Track" command when “Group Tracks” is enabled

 

Stupid MF Presonus! 6 moths broken sidechain and still no fix! 5.0.2 is last half working version

 

What's the issue exactly? I'm still using version 4. From what I read in Forums, Presonus are notorious for leaving bugs unfixed over looooong periods of times.

 

Just like other DAW providers they sell you a licence, that's it, to use their bug ridden software and wonder why "piracy" of their software is so prevalent, in some cases fixing the issue for them and making it run better!

 

what problem? ive used sidechain on 5.1 with no problems

 

Yes, but he has 6 moths. Maybe they have something to do with it?

 

Broken sidechain??? Please explain.

 

This:

 

Just route the Ghost track to main output, turn it down and set the send to prefader. Solved.

 

@karatebaka
Thank you. Impressive, that does look like a serious issue. I especially despise how old projects will sound different all of a sudden. Such a shame they this goes on unfixed. Looks like the S1 code is so complicated that bugs accumulate over time and all attempts to fix something breaks something else. Very disappointing. And then they take soo long for their updates.

PS Wasn't the Jitter issue fixed in one of the patches though?

 

I'm still on ver 4

 

what?

 

Presonus

They confirm bug and didn't fix it more than 6 months! No update in changelog, and i test myself everything is broken. Projects with advanced routing can't play properly

 

Last edited by a moderator: Jan 21, 2021

cool that your sidechain is works good! Haha

 

Problemsolver

 

If completely basic things broken what i can say about advanced features, i don't need all that new fancy stuff with broken basic. Logic not working too. Only Reaper at the moment - but maaan it's gui so ugly.

 

Good news to know..

They still have not added the ASIO 2.0 Hardware Monitoring after all these years. It has been part of the ASIO 2.0 spec since 2003!!
I won't lie Reaper for all it's openness also does not have Asio 2.0 Hardware monitoring support. Only Cubase and Nuendo still have this feature ( for much older Firewire interfaces with no gui control).

This scam of "low latency monitoring- Direct monitoring" that Presonus is pulling is a scam because all they are doing is only allowing their interfaces to trigger the ASIO 2.0 Hardware monitoring ( Both the Daw and Asio device / drivers must support this feature) on Studio One. Older Firewire interfaces that rely on this feature do not work because Presonus only supports their own interfaces. This allows for directing the input to an output prior to entering the Firewire Bus and Driver stack thus it is real time ( what we hear with bone induction).

My edirol Fa101 has this mapped right on the top of the interface, anyone who sees this diagram can see the scam going on today with the interfaces having the DSP effects, they are just using Asio direct monitoring mixed the input signal and that is how they are doing the low latency monitoring. This is why they added DSP effects to it so that the signal is mixed prior to the USB or Firewire Bus thus creating the illusion that they somehow invented something new ;o)

Edirol FA101 with the Diagram exposing these companies.
Notice the yellow circles and how the signal is routed out via the Firewire direct connects internal bus on the interface then to the DA section in real time bypassing the Asio driver stack thus the Daw delay. This allows for direct hardware control monitoring inside the Daw ( Cubase and Nuendo only now)

https://ibb.co/GWts9tP

 

Last edited: Jan 21, 2021

@Blanco
damn, those emails from Presonus are really harsh. What are they thinking? OMG

 

Just reinstalling everything on my laptop and saw this....to just install 5.1.0 or to wait and see if a 5.1.2 drops on sister site?!?!