Ctrl+Z ain't working.... No undo via keyboard shortcut. 1st time I've ever made a mistake and I had to manually undo it. OH THE AGONY!
|
PreSonus is usually very good about releasing a follow up version to address any issues that weren't identified during Beta testing. I'm sure all this will get sorted out.
Peace!
Dan PreSonus Studio One Professional 6.0.1 Windows 11 Home Edition 64 bit Rocket Lake Z590 Desktop PC with Intel i5-11600K processor @ 4.60 GHz / 32G RAM Intel UHD Graphics 750 LG Full HD Monitor 1920 x 1080 at 60Hz 16:9 Aspect Ratio Toshiba HDWD110 1TB System Drive and HDWD110 1TB Audio File Drive, Samsung SSD 850 EVO 500GB and Samsung SSD 970 EVO Plus 1TB Samples Drives, Seagate BUP Slim BK 2TB USB Backup Drive PreSonus 1824C Audio Interface PreSonus Faderport 2018 PreSonus Studio Channel, Klark Teknik EQP-KT, KT-2A and 76-KT Check out my website http://www.dlsmusic.net |
taylorscott2 wrotestignielsen wrote This one. It keeps happening to me as well! So annoying! When I reported it to Support they said 'If it's a bug this critical, the Presonus team will certainly notice it'. Guess what, it's still there. Oh boy. Please submit a ticket if you can, thank you.
Presonus Featured Artist (Italy)
My Latest Feature Requests https://answers.presonus.com/73692/s1-essential-feature-plugin-racks https://answers.presonus.com/72506/zoom-to-selection-improvement-vote-if-you-agree Studio One Pro 6 Win10 - AMD Ryzen 9 5900X - 32gb ram DDR4 Gigabyte RTX 3060 Interface: Focusrite 18i20 3rd gen Prophet XL + KeyStep Pro Atom SQ Revelator |
taylorscott2 wrotej0001s wroteStrom wroteAnyone noticed the output is clipping @ 0 dB (Master & Listen Bus @ 0 dB). Didn't do that before update - I have to pull down the master -0.1 to be save?!? Reran the test with 5.5, and it's behaving properly now. Lucky me, not helpful for taylorscott2... |
taylorscott2 wroterisemix wroteAs reported elsewhere, midi draw doesn't work for me. Well, yes, of course they do. The triad scale settings are chords, you literally can't place any notes there except for the notes of that scale's triad. If that is how the setting is intended to work, it has been dramatically misrepresented. What is the benefit of drawing notes up a scale on a single cell? I think FLStudio could do that with the paint tool back when it was still called FruityLoops, and it wasn't that useful then either. Anyway, I'm almost sure this feature isn't working as intended, and that it wasn't working in the video they put on YouTube either, because if you hold alt after adding your base note and then drag over, you get an arpeggio that you can drag around to different chords from your root note, but when you move back into the first cell, it just stacks the whole scale on top of each other anyway. It looks like it's meant to stack the chord and doesn't. See attached video. This seems incredibly hastily implemented, or maybe the patch went gold before this feature was merged.
|
risemix wrotetaylorscott2 wroterisemix wroteAs reported elsewhere, midi draw doesn't work for me. Agreed |
BezowinZ wroteCan anyone confirm they disconnected track visibility in the Arranger from the Scenes in the Console. I believe it was a confirmed bug back in 5.0/5.1. Serious workflow killer for me. Nope - still an issue. Anytime you choose a Scene, it completely resets any track visibility you've set in the Arrange window (even with link track and console visibility set to off). I also had reported this a while ago. Guess not a priority. |
I'm not super excited about this update either but was hoping for little sneaky things they did that's not in the release note....
They labeled the automation lanes! The sends are now labeled and plugin parameters are labeled with the plugins they belong to! |
raushaunmitchell wroteI unfortunately had to go back to the previous version (5.4.1). For whatever reason with this update, I'm getting horrible crackling once the volume gets passed a certain loudness threshold. Absolute dealbreaker for me. Probably a plugin (which may need to be updated) if this isn't a common issue with others. Without troubleshooting it probably won't be fixed.
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. |
raushaunmitchell wroteI unfortunately had to go back to the previous version (5.4.1). For whatever reason with this update, I'm getting horrible crackling once the volume gets passed a certain loudness threshold. Absolute dealbreaker for me. I had the same problem. It was okay before with the same buffer settings etc.
Using Studio One 6 (Always the latest version)
System i9 9900K, 64GB RAM, 2080TI, 34" 4K Display & 55" 4K Professional Display, Windows 10 Studio I/O Lewitt LCT-440, Yamaha HS7, PreSonus Studio 1824c, Beyerdynamics DT1990, Audio Technica M50X Studio Gear Arturia Keylab 88 MK2, Atom Pad, Atom SQ Instruments Cordoba GK Studio, Takamine GJ72CE, Godin Session, Yamaha F310 R&B Singer / Songwriter / Producer Website |
5Lives wroteBezowinZ wroteCan anyone confirm they disconnected track visibility in the Arranger from the Scenes in the Console. I believe it was a confirmed bug back in 5.0/5.1. Serious workflow killer for me. That's not a bug but indeed this feature to use mixer scenes for switching channel visibility independently of the tracks in the arrangement doesn't exist anymore in version 5.0 or later.
Lukas Ruschitzka
Studio One Specialist Studio One Tutorials || Studio One Scripts & Add-ons || Studio One Tutorial Database || Studio One Toolbox [ s1toolbox.com ] Core i7 3.24 GHz, Windows 10, 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5 Clavia Nord Stage 3 - Moog Sub 37 - YAMAHA MoXF6 - M-Audio Axiom Pro 61 - Kawai ES-920 - Studio One 5 - Notion 6 - Orchestral Tools Junkie XL Horns, ProjectSAM Symphobia, Cinematic Studio Series, Strezov Sampling Afflatus, VSL Synchron Special Edition, KOMPLETE 9 Ultimate |
bensizer wroteSad to see that they didn't fix the bug where Project mode resets plugin state between tracks at export time. So they give us a default track pause of 0, but if you use it, you're gonna hear pops between tracks if you have any plugins with non-linear characteristics, like compressors, or time-dependent characteristics, like modulation. Hello Ben, can you provide detailed information please? We need a reproduction. So it would help if you could tell with which PreSonus Plug-ins this happens. And is the export format relevant to reproduce this? Thanks a lot! 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 |
I think you are doing a great job!!! Free 5.× update is a great and customer friendly move 👍.. sure there a bugs, new and old, but at least the wheels are once again moving forward. I really like the individual plugin nap for instance.. I know many of you are dealing with bigger issues and bugs which I hope there is a workaround for until it's sorted out happy 2022 and thanks for the update!
|
madsvigeholm wroteI think you are doing a great job!!! Free 5.× update is a great and customer friendly move 👍.. sure there a bugs, new...Which new bugs are you experiencing so far? Can you give more details about them?
Lukas Ruschitzka
Studio One Specialist Studio One Tutorials || Studio One Scripts & Add-ons || Studio One Tutorial Database || Studio One Toolbox [ s1toolbox.com ] Core i7 3.24 GHz, Windows 10, 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5 Clavia Nord Stage 3 - Moog Sub 37 - YAMAHA MoXF6 - M-Audio Axiom Pro 61 - Kawai ES-920 - Studio One 5 - Notion 6 - Orchestral Tools Junkie XL Horns, ProjectSAM Symphobia, Cinematic Studio Series, Strezov Sampling Afflatus, VSL Synchron Special Edition, KOMPLETE 9 Ultimate |
today - after a restart - I can't reproduce the error with stuck midi notes!
As Taylorscot2 said, he could occasionally still get the error, so it's still there, but it has definitely become much rarer to happen. edit: Ok,, it's still there on occasion - selecting some notes - closing the editor - entering editor again - the selected notes are frozen, and you have to delete them and insert them again to be able to edit them. But it doesn't happen ALL the time, maybe one in 10.
Last edited by stignielsen on Wed Jan 12, 2022 11:17 am, edited 1 time in total.
|
stignielsen wrotetoday - after a restart - I can't reproduce the error with stuck midi notes! I hope that's true! I'll report back if it happens again, thank you for letting us know!
Presonus Featured Artist (Italy)
My Latest Feature Requests https://answers.presonus.com/73692/s1-essential-feature-plugin-racks https://answers.presonus.com/72506/zoom-to-selection-improvement-vote-if-you-agree Studio One Pro 6 Win10 - AMD Ryzen 9 5900X - 32gb ram DDR4 Gigabyte RTX 3060 Interface: Focusrite 18i20 3rd gen Prophet XL + KeyStep Pro Atom SQ Revelator |
stignielsen wrotetoday - after a restart - I can't reproduce the error with stuck midi notes! Actually in my case all I have to do is press F2 twice (close editor, open editor) and it fixes it - probably a little bit faster than deleting and re-adding |
I think it's very nice that, thanks to the project automation, I can finally make fadeouts on my songs AFTER the song has run through the limiter and thus the fadeout curve is not falsified. However, after adding such an automation, I am not notified that the loudness has changed, which has always been the case until now when I placed the fadeout curve directly on the audio file, because the overall volume becomes quieter as a result of a fadeout. So there is no possibility to recalculate the LUFS after the fadeout using automation.
|
Users browsing this forum: bartbalint, Hommi and 24 guests