Version 5.4.1 Release Notes (October 14, 2021):

The following issues have been fixed:
● [Apple Silicon Native] Tuner shows incorrect results
● [ATOM SQ] Fixed page numbers for Song, Instrument, and Editor buttons
● [macOS] Touch event is offset in plug-in select menu
● [Note Editor] Tab to next note not working consistently
● 32-bit float recording from Capture shows up as 16-bit in Studio One
● Alt+Drag in arrangement intermittently crashes S1
● BPM from WAV file not properly applied to audio part
● Can’t drag WAV files to browser to export events with FX
● Cancel mixdown keeps rendered part
● Crash when closing plug-in editor via touch
● Crash with Acustica Audio N4 plug-in

● "Cursor follows edit position” option fails when dragging chords from the chord track to the arrangement
● Dragging notes from note editor to arrangement delivers unexpected results
● Dragging time-stretched audio event with detected chords to instrument track creates event with wrong length
● Dragging Splitter from browser search result shows unwanted behavior
● Higher audio monitoring latency reported in certain cases

● Impact XT inside a multi-instrument creates unwanted noise
● Note On not sent to MIDI outputs when MPE enabled
● Pipeline ‘ping’ doesn’t work when transport is stopped
● Potential crash on system shutdown when Studio One is still open
● Scores from Notion using Jazz font are displayed incorrectly
● Some automation parameters may be linked to the wrong track with bus automation
● SoundCloud browser tab occasionally stays empty
● With Plug-in Nap active, reverb tail is cut from certain AU plug-ins
● With Show Page in Perform View, pressing space bar to play/stop doesn’t work when Setlist is in focus

 

ok just update it to get all these nice things

 

so far, the optimizations are a real deal

 

Can you update the k'd version, or just legit versions?

 

Never mind, it will have to be cracked, done tried it

 

Kudos to the developers.
Version 5.4 is like shit off a shovel now.
Loads faster than FL Studio for me...

 

does this update fix the issue with the ableton users jumping ship? you know though, i didnt realize how poor abletons midi was until i built an exact replica of the same project in both DAW. when i hit that space bar i saw the light

 

i was hoping we'd have this here by now..

 

please explain I am curious

 

Really hoping this comes to the sister site soon. N4 is one of my most used plugins and the crashes are frustrating and very unwelcomed in the studio one userbase. It has been rock solid till 5.4.

 

this daw only getting improvement/fix issues update. thats a good thing but... still there is no theme and color palette update.

https://answers.presonus.com/43618/please-update-the-color-palette

 

Is it safe to transition from 4.6.3 now?

 

it's here!

 

That was just a minor fix update. We are waiting for these features to be added in 5.5 which arrives probably at the end of spring or during summer.

 

hi moonlight, im talking about abletons cpu spikes. while s1 great job of optimizing theirs, i am reading alot of ableton users checking out the s1 optimization. my post was a word twist on presonus's good work, because that problem is actually ableton

 

Did you check the custom colortoolbar script?
It is huge.
Search Studio One Color Toolbar and you will get it.
That toolbar is a must, IMO.
(I am a pretty heavy S1 user and a Macro and Script monger)

Here, ENJOY.
https://s1scripts.wixsite.com/colortoolbar

 

This version still has the exporting issue since v5.3.

 

Last edited: Nov 3, 2021

I tried to low latency mode but when I use it one plugin is always processed twice which completely kills the CPU (demading plugins) and renders low latency mode useless. Is this a bug? Why does the CPU process each plugin twice in low latency mode?