4 posts
Page 1 of 1
Dear Studio One Users,

Studio One 3.3.4 is now available.
This little maintenance update contains some minor technical fixes in different areas.
Additional there is a new spanish manual.

Have a nice pre- spring!
Ari

________________________________________________________

Version 3.3.4 Release Notes (February 21, 2017):

New features and improvements:


• Trim start/end to cursor works for selected track if no event is selected
• Unpack layers to tracks in the context menu on range selection.
Also for specific layers (via range selection on layers)
• Templates for StudioLive 32, Studio 2|6 and Studio 6|8
• spanish manual


The following issues have been fixed:

• [macOS] Crash when re-adding VST instruments
• [macOS] AU automation broken for large param IDs
• [macOS] Hang when zooming reference manual to small (mobile) view
• [Win] Improved Direct 2D error handling
• VST3 context menu position wrong on Windows High DPI

• Audio engine error when activating Fat Channel
• Global FX off can’t be switched ON when a track is deactivated
• Fatal error in DDP export
• Embedded Melodyne not working in Artist version
• Crash when loading projects with missing media files
• Channel splitter exposes noise of analog-style plug-ins

Ari Ahrendt - Quality Assurance Specialist
PreSonus Software Ltd. - Hamburg
http://www.presonus.com/products/studio-one

Modern electronic Synth Pop........../..........Musicproduction, Support & coaching
http://www.denoisary.de/................./...........http://www.arimusik.de/

Windows 10 64-Bit, i7 6700k 4.0 GHz, 16GB RAM, 4TB SSD, Studio One 5 Professional
User avatar
by Steve Carter on Tue May 23, 2017 2:45 pm
Skaperverket wroteCool, that's pretty neat. It's really great that Presonus pays attention to our feature requests.


Watched the livestream, well sort of, with some delay due to Chrome crashing trying to log into chat! What happened to the old but easy login proceedure? Anyway...

A big deal was made of Presonus 'listening to its users' and responding to the number One feature request 'fader undo' but failed to address numbers 2 & 3, which were both to do with CPU efficiency! Is that because the new 'low latency' stuff enables S1 to utilise cores more effectively? Maybe I missed something whilst messing around logging in to chat...

Not sure I fully understand the consequences and complexities of 3.5 yet (not sure I'll ever understand fully) guess time will tell.

Regards....

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 Funkybot on Tue May 23, 2017 2:54 pm
Steve Carter wroteA big deal was made of Presonus 'listening to its users' and responding to the number One feature request 'fader undo' but failed to address numbers 2 & 3, which were both to do with CPU efficiency! Is that because the new 'low latency' stuff enables S1 to utilise cores more effectively? Maybe I missed something whilst messing around logging in to chat...


They improved they CPU balancing and performance. Haven't tried it yet, but it's in the release notes and is being talked about. Not only is balancing improved, they've taken steps to reduce dropouts and glitches too by the looks of things. Very pleased to see that stuff! :thumbup:

AMD Ryzen 3950X, ASUS Creator x570 Mobo, 32GB HyperX Predator RAM (3600mhz), Radeon™ RX 5500 XT 4GB GDDR6 graphics card, RME Fireface 800, Windows 10 Pro, Studio One 5, Reaper 6, Cubase 10.5, Avid Artist Mix (EuCon please), Behringer X-Touch One, MIDI Fighter Twister, various other MIDI control surfaces and hardware instruments
User avatar
by Mucusman on Tue May 23, 2017 8:53 pm
garryknight wroteSomeone posted over on KVR:

I've been trying it out for the last hour or so and the global undo/redo works flawlessly in S1 itself and all the plugins I've tried (if the changes are made with a keyboard or a mouse, but not when the parameters are moved with a MIDI controller)


I wanted to test this out but when I installed Studio One 3.5, it lost my Nektar Impact LX49+ device. I tried reinstalling the LX49+ "drivers" (the .surfacedata files buried in my AppData folder) but S1 still doesn't recognise the controller. (Yes, I did switch it on, and yes, I did try 'Reconnect').

Anyone else had this happen? Anyone else confirm that changes by controller can't be undone?


I had a similar experience as a Nektar Impact LX49 owner. I updated to 3.5, and forgot to reinstall the Nektar drivers (sadly, a requisite action after every Studio One update). Oops. So I shut Studio One down, and reinstalled the drivers. Yet, still the Nektar's MIDI input wasn't recognized by Studio One. Drat! I reinstalled the Nektar driver again. I shut down S1, turned my LX49 on and off, and restarted S1. And then... it worked.

Not sure what I did right, other than be persistent. You're not alone... but it can work.

Windows 10 Home (64 bit), 24 GB RAM, Dell XPS 8920 (i7), Studio One 3 Professional, PreSonus AudioBox 44VSL, Nektar Impact LX 49, Behringer X-Touch One

4 posts
Page 1 of 1

Who is online

Users browsing this forum: No registered users and 31 guests