50 postsPage 1 of 3
1, 2, 3
Dear Studio One users,

a new maintainance update is out there.
Please find all infos here:
viewtopic.php?f=151&t=51568


And happy discussion!
Ari

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 Vocalpoint on Thu May 25, 2023 9:02 am
Ari

Congrats (and thank you!) to you and the DEV team for this new update and a very extensive fix list.

Cheers

VP

DAW: Studio One Pro 6.5.1.96553 | Host OS: Windows 10 Pro 22H2 | Motherboard: ASUS PRIME z790-A | CPU: Intel(R) Core(TM) i5-13600K | RAM: Corsair Vengeance LPX 64GB | Graphics: Intel UHD 770 (HDMI) | Audio Interface: RME UCX II (v1.246) | OS Drive : Samsung 990 PRO (1TB) | Media Drive: Samsung 970 EVO Plus (500GB) | Libraries: Samsung 970 EVO+ (2TB) | Samples : Seagate FireCuda (2TB) | Monitoring: Presonus Monitor Station v2 + Presonus Eris 5 | MIDI Control: Native Instruments Komplete S61 & Presonus ATOM
User avatar
by wolfgerb on Thu May 25, 2023 9:09 am
Gain envelope bug seems fixed on first short tests! thank you!

kind regards
wolfger

Mac Book Air M2 15", Mac OS 14.3; RME Digiface USB, MOTU 828es + 8pre; Studio One 6.5.2; Faderport v2; Atom SQ
User avatar
by AAV on Thu May 25, 2023 9:23 am
Thank you Ari / Presonus!

Studio One 6.5.2 Pro, Audient ID4 mark II,
Gigabyte Designair Z390, 32GB DDR4 3200, Intel i9-9900K 4.8 GHZ, 2000 GB & 1000 GB SSD, 3 x 1TB 7200 rpm HDD, Windows 11 Pro 64 22H2
User avatar
by robertpaczkowski on Thu May 25, 2023 8:13 pm
Thank you for all the fixes, especially those that I was affected by:

● [Pro-EQ³] Threshold settings not saved in dynamic mode
● [Track Presets] Instrument tracks don't connect to inputs from inserts of other tracks
● Crash on transforming Audio Track back to Instrument Track with pattern

It works like a charm now!

Studio One 6 Pro; OS: Win.10 Pro
Computer: Dell Precision M4700 Mobile Workstation, i7-3740QM 16 GB RAM, 256GB System SSD; 2TB Library SSD; 1TB Projects SSD, 4TB Backup HDD
Audio Interface: M-Audio ProFire 2626; M-Audio Air 192-6
MIDI Controllers: Roland A49, Korg MicroKontrol, Korg PadKontrol, Peavey Studiomix, NI Kore 2
User avatar
by jpettit on Thu May 25, 2023 8:45 pm
Thanks
Lyrics now align properly in the Score Editor view suitable for printing.

My Website, Free Studio One Advance Training
SPECS: Win 11 22H2, 18 Core i9: 32Gb DDR4 ram, 42" 4K monitor, StudioLive 24/16, Faderport16, Central Station Plus, Sceptre 6, Sceptre 8, Temblor T10, Eris 4.5, HP60, Studio One Pro latest, Test Platforms Reaper latest, Cakewalk latest
wolfgerb wroteGain envelope bug seems fixed on first short tests! thank you!

kind regards
wolfger


I hope the same is true for MIDI curves / nodes. Will check.

Studio One Professional 6.1.1 | 64bit Melodyne Assistant 5.2.0.006

Faderport 8 | Focusrite Scarlett 2i2 3rd gen
Studiologic SL88 Grand | Yamaha YDP-163 | Yamaha HS8 & HS8S | Austrian Audio Hi-X65 | Beyerdynamic DT770 PRO

Windows 10 x64 | AMD Ryzen 9 3900x | Asus X570PRO | 64GB G.Skill DDR4 3600MHz | 6TB NVME SSD
User avatar
by PreAl on Fri May 26, 2023 7:56 am
Great to see a whole load of fixes on Studio One - good release thankyou and keep it up!


The below issues are also reproducable on 6.1.2 and I regard them as workflow killers.

Bug - Instrument output settings change from "none" (and instrument input clarity needs improving slightly):
viewtopic.php?f=151&t=51577

Smooth scrolling - PLEASE PLEASE sort this :)
viewtopic.php?f=151&t=34082

and this legacy issue makes things needlessly complex:
viewtopic.php?f=151&t=51517

======================================================

Also does anybody have the time to answer this? Note I have created a ticket #821148 pointing to these threads, maybe I'll get answers from support. I can't find any info in the manual or via google.

viewtopic.php?f=151&t=51538

And this (I don't understand how MIDI latency offset works here, maybe it isn't working):
viewtopic.php?f=151&t=51530

Thx...

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by ansolas on Fri May 26, 2023 10:04 am
Navigating the StudioOne browser still creates CPU Spikes here.

ProEQ seams to work better now here, no CPU spikes so far.
:thumbup:

Presonus StudioOne 6, Apple Logic Pro
__
macOS, macMini M1 1TB SSD / 16 GB RAM,
MOTU M2, Behringer X-Touch & 2*X-Touch Extender,
https://ansolas.de
User avatar
by jih64 on Fri May 26, 2023 10:27 pm
:thumbup:

For every Arthur C Clarke quoter, there is a know-all who likes to quote Arthur C Clarke
- unknown
User avatar
by PreAl on Sat May 27, 2023 5:29 am
Another ancient issue.

Custom Soundset/Instrument library folder path ("location") bug:
viewtopic.php?f=151&t=51582

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by PreAl on Mon May 29, 2023 7:58 am
EDIT - confirmed bug.

This is another big workflow issue for me. Not only can I not use dials to scroll the timeline with any decent accuracy, I can't use my controllers to arm record on certain tracks. Hopefully there is a solution?

If this doesn't actually work, then it is sadly yet another workflow killer for me, I want to stay away from my mouse and keyboard as much as possible.

Problem with controllers arming instrument tracks connected to hardware synths (not soft synths).
viewtopic.php?f=151&t=51589
Last edited by PreAl on Wed May 31, 2023 5:47 am, edited 1 time in total.

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by davidspencerbarker on Tue May 30, 2023 1:47 am
Thank you team Presonus,for your hard work :D

Great job with the fixes and updates!

Dell Optiplex, 64bit Windows 10 Pro, Intel Core i5-3570 CPU@ 3.40GHz 16GB RAM,
1 TB SSD main drive,500GB HDD storage,.
External drive of 6TB HDD for the libraries and a 1TB SDD for other stuff
Focusrite Scarlett 4i4 3rd gen audio interface, Beydynamic DT250 headphones, and Rode dynamic Podmic
Lots of Kontakt libraries and other gear,(too much to list here :)
User avatar
by donaldbaarns on Wed May 31, 2023 9:26 am
What I find interesting. Six days after release, the issues raised here appear to be relate to issues that were NOT documented as fixed in the release.

It was never released with a "we have fixed everything anybody has ever raised", but rather, here are specific issues/show stoppers that we could revise/test and put out there to deal with this set of issues, that have an effect on lots of people.

We all have our pet issues beyond what was addressed, but some of them are also edge cases.
I might have a workflow I like/prefer, but that doesn't mean the 95% plus can't get their creative work done...

Anybody have reports of issues noted as addressed, which are not working? or created other side effect issues directly related to what was addressed/documented?

Don

S1 v6.x Pro - latest version
PreSonus Studio 26, IO 24, Atom
Eris E5s
iZotope RX10 Advanced
Win 11 Pro-32GB RAM-AMD 3900x
AMD 5700XT
Windows 10 Pro-16 GB RAM
MacOS Ventura (13.4) iMac i5 w 8 GB RAM


FB group: Studio One Users-Audiobooks, VO and Podcaster focused:
https://www.facebook.com/groups/StudioOneNarrationVO/

Studio One and iZotope RX Courses for Narrators/Podcasters/VO:
https://www.VOJumpstart.com/

Studio One and iZotope RX Videos for Narrators/Podcasters/VO:
https://www.youtube.com/user/RedBaarnsAudio
User avatar
by PreAl on Wed May 31, 2023 9:57 am
donaldbaarns wroteWhat I find interesting. Six days after release, the issues raised here appear to be relate to issues that were NOT documented as fixed in the release.

It was never released with a "we have fixed everything anybody has ever raised", but rather, here are specific issues/show stoppers that we could revise/test and put out there to deal with this set of issues, that have an effect on lots of people.

We all have our pet issues beyond what was addressed, but some of them are also edge cases.
I might have a workflow I like/prefer, but that doesn't mean the 95% plus can't get their creative work done...

Anybody have reports of issues noted as addressed, which are not working? or created other side effect issues directly related to what was addressed/documented?


I am assuming this is directed towards me..

From what I see this is this official 6.1.2 discussion thread. This is to discuss issues with 6.1.2, nobody here said only new issues should be discussed.

If existing issues and bugs don't get posted here then nothing will ever get fixed, and they will always be brushed under the carpet.

If you are saying things like record arm on instrument tracks for external synths on controllers not working at all on hardware synths isn't a serious issue, or even some sort of "pet issue" then I'll get my coat.

Not being able to navigate with any degree of accuracy with the timeline on any controller is also a serious oversight. Up for debate if it's a bug or not, but it really needs to be addressed..Presonus sell hardware controllers like faderports, this sort of thing directly effects these sort of customers.

Everybody has their own idea of what is a serious issue or bug is, and what isn't. Ultimately I'm finding a lot of issues that are effecting devices and controllers, and in one case (maybe, nothing validated yet), midi latency offsets. These should not be regards as "niche" issues.

At the end of the day I'm finding a lot of basic legacy issues that haven't been fixed, most, in my view, shouldn't be that hard to address, but I'm not there at their scrum meetings nor do I have access to their codebase..I do not work for Presonus.

For me most of these issues.I have posted here are a total PITA. That's my opinion and I'm entitled to it. I'm totally in Presonus's ecosystem, I own 3 of their controllers, two of their audio interfaces, and use Studio One. I expect things to work without much hassle. If I do find an issue I regard as serious, I'm happy to wait for next release and get the fix. I'm not happy to wait years and years down the line. Bugs are not features, and stuff that halts workflow should be plugged as soon as possible.

..and as I said before, I think 6.1.2 is a fine release and I'm glad they've fixed a whole load of issues. I do not wish to play down the hard work they have put in..Many of these issues did not effect me, but they may do in future. I also like how transparent they are here in announcing these fixes.

I would encourage anybody to post validated bugs here, or workflow dead ends here, old and new. Or ask for help here in validating bugs by posting steps to repro by pointing to other threads for further discussion.

Then hopefully Presonus may take notice for the next release.

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by donaldbaarns on Wed May 31, 2023 12:22 pm
Wow, thin skin.

NOT directed at you at all. I was curious if anybody had issues with the specifics of what they released, addressing the issues they said were updated.

So far I can't find a reason people shouldn't upgrade to this version now.

You do you, no stress from me.

I'm still curious if anybody has issues that are related directly to what was released, rather than my wish list (or others wish lists) of features/workflows and/or other issues that were NOT explicitly addressed in this maintenance release.

Don

S1 v6.x Pro - latest version
PreSonus Studio 26, IO 24, Atom
Eris E5s
iZotope RX10 Advanced
Win 11 Pro-32GB RAM-AMD 3900x
AMD 5700XT
Windows 10 Pro-16 GB RAM
MacOS Ventura (13.4) iMac i5 w 8 GB RAM


FB group: Studio One Users-Audiobooks, VO and Podcaster focused:
https://www.facebook.com/groups/StudioOneNarrationVO/

Studio One and iZotope RX Courses for Narrators/Podcasters/VO:
https://www.VOJumpstart.com/

Studio One and iZotope RX Videos for Narrators/Podcasters/VO:
https://www.youtube.com/user/RedBaarnsAudio
User avatar
by donaldbaarns on Wed May 31, 2023 12:35 pm
PS: My gut is all the workflow issues you or me or others want, should live in their own thread(s), as I don't think they are related to a specific maintenance release. So what? That's my POV, others are free to post where they want.

Plus some things that are a big deal to me, are going to be a non-issue for others. That's life too.

Zero stress from me when others post what is a productivity killer for them. I may disagree, but it's all good. The PreSonus team will decide what's most important and doable, often based on what happens to the code base (backward/forward compatibility) and how many touch points a feature will have. Just because I think it should be easy, doesn't mean it is... (IF it was easy, many of the details I want would have been implemented a long time ago...)

Power users are rarely the sweet spot for what features are being added next. (I can work around almost everything if the core is solid, and the majority of my needs are handled.)

For example: I don't need/want to avoid the mouse/KB. So I don't care as much that we can't control the playhead at the level someone else wants via a dial or via a set of controllers.

I use the mouse. Highly productive for me and the vast majority of users who don't want/have additional control surfaces. (One size will rarely fit everybody, I hope they address your feature request soon.) I don't see it as a bug either, someone made a design decision, and I'd guess re-coding that is far more difficult than it appears.

If I have a KB shortcut in the future that gives me fine control of cursor placement, or via another control surface, then bonus for me, but NOT a deal or workflow killer.

I hope they fix/upgrade other issues long before they worry about that type of issue. They have an installed base of millions, it's nice to have details for the majority, and features that fill other gaps/ease of use.

That said, if it affects you, you should make it known. If it's me I prefer different threads for each suggestion/issue, but I'm not a mod here, I just follow whatever they want.

And as a side note: I don't work for them either. I work with S1 and audio daily. I do run some groups with thousands of S1 users, but we are in a totally different content creator context. So we have different wants/needs than music production. (I did cut master records back in the day, learned at an old Motown studio, from engineers who cut many of Motown's early hits...)

I actually want to know if the issues they say they addressed are actually solid at this point.

I still hope other discussions move to other threads, but over my pay grade to worry about who posts what, and where directly.

From my POV, this thread is the wrong place for suggestions, but I just ignore it when I see something that doesn't make sense to me. Life in all groups.

Others make the policies here, I simply contribute (and complain) occasionally.

Don

S1 v6.x Pro - latest version
PreSonus Studio 26, IO 24, Atom
Eris E5s
iZotope RX10 Advanced
Win 11 Pro-32GB RAM-AMD 3900x
AMD 5700XT
Windows 10 Pro-16 GB RAM
MacOS Ventura (13.4) iMac i5 w 8 GB RAM


FB group: Studio One Users-Audiobooks, VO and Podcaster focused:
https://www.facebook.com/groups/StudioOneNarrationVO/

Studio One and iZotope RX Courses for Narrators/Podcasters/VO:
https://www.VOJumpstart.com/

Studio One and iZotope RX Videos for Narrators/Podcasters/VO:
https://www.youtube.com/user/RedBaarnsAudio
User avatar
by PreAl on Wed May 31, 2023 1:06 pm
To be clear all the issues I've posted here have separate threads, all my posts here are markers pointing to these threads.

If people started discussing their issues on this thread at great length (and they do), then things get confusing pretty rapidly.

And to repeat, if I bought a desk which doesn't arm record an external instrument track, that desk is probably going to end up being returned, as being faulty. If that manufacturer continued to sell desks with exactly that same fault for years, you have to question whether it cares about its end users.

Much like if you or somebody else bought a drum machine and one of the pads didn't work when it plays middle C

No way would I say, hey, I don't own a drum machine therefore I don't care, and also not once would I claim my opinion is in the majority, the majority rule therefore forget it. So off you go and buy another improved drum machine with the same fault.

Regardless this is the big problem with agile development, stuff that is regarded as "minor" often does not get fixed, and then what happens is that all these apparent minor "insignificant" issues build up, making it all become a whack a mole swiss cheese experience for the user that is not fun or productive. Then people.stop buying and you rename the product "cakewalk".... Oops sorry my little joke, sorry about that.

And btw, there.is a big difference between a workflow improvement and a workflow killer. Workflow killers can be just as bad as bugs, sadly agile development often doesn't measure this as a factor.

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by jih64 on Thu Jun 01, 2023 5:58 am
PreAl wroteThen people.stop buying and you rename the product "cakewalk"....


:mrgreen:

For every Arthur C Clarke quoter, there is a know-all who likes to quote Arthur C Clarke
- unknown
User avatar
by juvandes on Thu Jun 01, 2023 10:28 am
This version is better, resolved some bugs that crash S1 a lot for me on the v6.1 and v6.1.1

But still have some spikes that I didn't have on the V5

Macbook Pro i9 32gb|Studio One 6.5.2|Protools 2023|Cubase Pro 12|Wavelab 11|Logic X|Apollo X8|2xUAD-2 Octo
UAD 11.0.1|Waves14| Soundtoys| Melodyne 5.3.1| Softube| PluginAlliance| Fabfilter| Sonnox| Eventide| Antares

50 postsPage 1 of 3
1, 2, 3

Who is online

Users browsing this forum: No registered users and 81 guests