Version 5.5.1 Release Notes (February 22, 2022):

Improvements:
● Chord strumming now works for multiple chords at once
● [ATOM SQ] Added touch strip to Control Link in device editor
● [Windows] Added new user VST3 plug-in location

The following issues have been fixed:
● [Apple Silicon] Certain wrapped AU plug-ins (e.g. NI Reaktor) don't audition
● [Apple Silicon] Rosetta2 dropout protection performance behavior is non-linear
● [macOS] No graphics hardware acceleration for High Sierra (10.13)
● [macOS ≤ 10.15] Ampire causing CPU spikes and drop-outs
● [macOS] Can’t move detached windows to another virtual desktop
● [macOS] Unexpected CPU load with all effects and instruments disabled
● [macOS] Local Notion 6 installation is not detected

● [Mixer] Group sends option overrides standard behavior
● [Note Editor] First note of chord stack follows grid instead of chosen note length
● [Presence XT] Can’t edit steps in Gater
● [Presence XT] Certain presets sound different than expected
● [Pro EQ²] Curves move when switching auto gain
● [Pro EQ²] Graphics glitch in LPF/HPF
● [Pro EQ²] New defaults are not correctly saved
● [Pro EQ²] No curves on Project Page when loading preset first time
● [Project Page] Error when replacing audio in project
● [Project Page] Event name not recalled after save and reopen project
● [Project Page] Loudness information not updated when using Clip Gain
● [Project Page] Progress may get stuck when burning a CD
● [Scratch Pad] Certain tempo nodes can't be deleted

● [Windows] Application window can’t be restored during operation after window is hidden by Win+D
● Can’t enter Am b13 in Chord Selector
● Chord Selector not detecting A13sus4 chord
● Clicking the minus button in the Time Signature track may delete events on other tracks in certain cases
● “Create Crossfades” macro argument allows invalid value range
● Editor not responding and lost dialog focus on second monitor
● Export dialog focus lost on second monitor
● Loading certain Songs doesn't open Note Editor
● Leading-tone of a minor key is not always sharp
● Misleading error notifications when playing audio files with PCM signal gaps
● Moving a Folder Track into another one causes unexpected behavior
● Paste in Score Editor creates overlapping notes at certain positions
● Progress bar doesn’t close after content installation
● “Snap To Events” must be activated when "Snap Event End" is enabled
● Sustain is cut off on playback when a different track is selected, and “Instrument input follows selection” is enabled
● Velocity values are shifted to wrong position when applying Groove Quantize
● Zoom Tool isn’t zooming vertically

 

Nice news
You may want to change the title "onlie" to "online".
Can be a bit misleading for uninformed people

 

Oops, my bad. LOL
Just fixed it ;)

 

the previous patch don't work on this version. it need a new keygen to match with the user licence lenght.

 

● [Windows] Application window can’t be restored during operation after window is hidden by Win+D
this one is annoying

 

After reading through the 5.5.1 Presonus forum topic, it is clear that issues thought to have been fixed, are still causing issues.
The Pro EQ3 glitch is still occurring along with corruption of presets as one example.

Also issues with MIDI functionality are still persisting.

 

I've seen a no install version somewhere, but not a regular one. Weird

 

I've been having an issue that I hope this update fixes (it wouldn't be the first time an update from them had a fix that wasn't listed in the release notes that I could find).

When I toggle mono on an aux channel on the mixer and then toggle it back again to stereo, the stereo line is just two left (mono channels). Does that make sense? I can try re-wording it or making a video, if not.

Can anyone else reproduce this?

I have been using v5.5.

EDIT: the update did not solve my issues (neither did therapy! )

 

Last edited: Mar 1, 2022

Here is an example of what occurs. Stereo, then I toggle mono (the figure eight symbol), then back to stereo... and it merely sums the left channel. Am I missing something or is this a bug?

 

By default..Studio One assigns no input/Stereo to newly created Aux channels. when you click the Stereo button, the assignment changes to Left channel input/Mono.

The L+R means both channels are being used in the default Stereo mode.

Under 'Channel Components' in the mixer settings (click on the wrench), activate the 'input controls' option. This gives you input trim & phase/channel mode (1 phase control for Mono, 2 for Stereo).

 

Thanks for your help! However, my problem remains...

I still can't figure out why I cannot change the input back to stereo once it has been switched to mono. It will display as a stereo signal but it is only a mono sum.

I have a stereo input going into the aux. I get a stereo signal until I switch to mono (of course), then I only get a mono signal. But the problem is that if I then toggle it back to stereo, I only get a mono sum no matter what I do and have to restart my session to hear stereo again.

Especially because of that last part, something doesn't seem right.

 

Last edited: Mar 2, 2022

So I spoke to tech support and they were able to reproduce this issue and said that it has been slated for the next update.

Still curious if anyone here can replicate the issue, because if some people cannot, it would be interesting to find out why.

 

Finally got around to inserting a hardware stereo source & found that Studio One routing does sum the left & right inputs. The work around is to create two Aux channels panned L60 R60 & route each aux to a stereo bus. This will allow proper Stereo/Mono switching.
From there you can hide the Aux channels once the panning & input level is set.

Now I have to test Pipeline to see if the same thing occurs. what a head scratcher...