Hello,
It seems there is a bug with the zoom. When shift-option clic to get the magnify, it only zoom horizontally, not vertically like previous S1 versions. Same on PC and Mac. |
I have canceled my sphere subscription after this update
The new features, drawing chord stacks and strum. are horribly implemented. I want S1 to be awesome because there are a lot of useful production features that make my job easier. But when using them crashes the application, what's the point? I never hear on any of the competitor forums a user state, "this new feature doesn't work as advertised" and when you go to use it it crashes. S1 feels unstable to me, it crashes more times in a week then Billy Joel driving home from a party. Anyway, I still love presonus and own some of their hardware. But S1 is gotta go Sorry guys |
herbricco wroteI have canceled my sphere subscription after this update If stability is important to you never upgrade on a major point release ending in zero and stick with what you have. I won't be doing so, I read these posts to decide whether an incremental release is worth upgrading to or not. The next incremental release is likely to be in a month or earlier if there are serious problems. And crashes can't be resolved without steps to repro, bugs can't be fixed without detailed reports.
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. |
seanrowley wroteHaving a pretty serious problem right out of the gate and had to roll back to 5.4.This did not happen in 5.4 because it's a new feature/improvement in version 5.5: Improved handling of plug-in processing errors The sad smiley indicates pretty much what the message in the overlay says: This plug-in outputs invalid data and the new function protects you from audio bursts by muting the output and deactivating the plug-in temporarily. Click the smiley to enable it again. So if soothe2 or Cla MixDown produces bad audio, be lucky that the function prevents any audible artifacts. If this occurs more often, contact the plug-in manufacturers' tech support. S1 just give the information which plug-in caused these invalid samples that are detected in the output channel. herbricco wroteI want S1 to be awesome because there are a lot of useful production features that make my job easier. But when using them crashes the application, what's the point?I am not aware of any confirmed report of a crash related to any of the new features. If you follow the bug reports in forums etc., you know that crashes are usually related to 3rd party plugins or drivers. If you have specific crashes, please give us more details about the issue (OS, version number, plug-ins, steps to reproduce). Stating that there are problems but without further info is neither helpful for other users nor for the development.
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 |
PreAl wroteAnd crashes can't be resolved without steps to repro, bugs can't be fixed without detailed reports. Exactly. PreAl wroteIf stability is important to you never upgrade on a major point release ending in zero and stick with what you have. Things are not only black or white. You can easily install new updates of Studio One in a separate folder ("Studio One 5.5") and try them out while still working on existing projects in the old version. You can have installed as many different versions of Studio One as you like (but only one of them can run at a time). You don't have to wait until you have just finished all your projects.
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 |
Thanks. It's not much of an improved feature if it's bringing my sessions to a halt. I also can't reactivate all the affected plug-ins. Some of them just turn red again, even before playback.
jazzundso wroteseanrowley wroteHaving a pretty serious problem right out of the gate and had to roll back to 5.4. |
Thanks. It's not just Waves plugins, it's multiple plug-ins, including Soothe. I have had 666 issues in the past, but have no idea what's causing them, or how to fix! There's nothing weird with the audio files on those tracks. I did notice that some songs will play all the way through, but then give me the sad smiley or (666 when using 5.4). I've searched for solutions to this, but have only seen posts that point out the 666 problem, but no real workarounds.
|
seanrowley wroteThanks. It's not much of an improved feature if it's bringing my sessions to a halt. I also can't reactivate all the affected plug-ins. Some of them just turn red again, even before playback. Are there more plug-ins that cause this problem or just the two you have mentioned? I don't see this happening with any of my plug-ins - except for those that indeed output invalid data and would result in loud noise and I'm glad that Studio One now protects against this.... The sad smiley is basically the same as the 666 error before. 666 or sad smiley means: Invalid data detected. If this comes from a plug-in, then the plug-in developer needs to fix that. To help you with troubleshooting, the particular plug-in that caused the problem is now highlighted (if the plug-in could be determined).
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 |
taylorscott2 wrotehttps://www.youtube.com/watch?v=fcoxHw_N2ag Well spotted. |
seanrowley wroteThanks. It's not much of an improved feature if it's bringing my sessions to a halt And never upgrade your software in the middle of session!. Regardless make sure your plugins are up to date. Latest software is dependent on having the latest software libraries it hooks into. Studio One is actually doing a good thing by forcing you not to use a plugin that may have intermittent issues.
Last edited by PreAl on Thu Jan 13, 2022 2:23 pm, edited 2 times 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. |
taylorscott2 wroteAs seen in this video, Gregor double clicks to make a midi note, then holds Option (Alt on Windows), and drags up to create a chord. This only happens if you click and drag an already existing note. Gregor creates a new note while holding down Alt. Maybe it's easier to follow the way I show in my video (1:13 - 2:05). a) Hold down Ctrl+Alt (Cmd+Option on Mac) while drawing new notes. or b) Switch to the Paint tool (that's basically what Ctrl/Cmd does) and just hold down Alt while drawing new notes.
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 |
PreAl wrotekisnou wroteThat happens to me as well, even in quite lightweight projects.. I have actually done exactly that many times. Uninstall reinstall drivers.. reboot.. and I have completely deactivated my firewall/antivirus stuff but it still happens quite often.. but a couple taps on my spacebar and everything plays again.. annoying? yes - but not a showstopper 🙂 |
Just noticed that the video showcasing the new Editing features has pretty much doubled the amount of views of the Project page video, I guess we all need some workflow and editing improvements
No offense to the project page/mastering guys! but it should give a few hints about what most of the users are looking for.. Fingers crossed for what will come next.
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 |
AriAhrendt wrotebensizer 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. Ari, I provided a full reproduceable example in my support request for this almost a year ago: https://my.presonus.com/support/ticketdetail/648750 (probably not public, but hopefully that ID at the end is of use to you) But if anyone else wants to repro, it's this:
Sadly the response from support was poor due to continued misunderstanding of the problem and a refusal to escalate to technical staff, and at the end I was told it would be "logged with QA". This whole interaction left me thinking much more negatively of Presonus. |
To be honest, that isn't my only poor interaction with support. When I logged this bug - https://my.presonus.com/support/ticketdetail/594297 - "Rendering from Project view has different results to a mixdown from Song view" - I got a dismissive response saying that I shouldn't really expect song automation to work properly when project view is re-rendering a song for me, even though the automatic re-rendering is one of the main selling points of Project View.
Project View is far too bugged to be usable right now, but more importantly, support are not taking these problems seriously or escalating them to the people who can actually fix them. |
donaldbaarns 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?!? Hi Don, this occures during playback, not export. After updating I loaded a song I have been working on, that played back perfectly fine before. Now its output on main (and listen bus) is over 0 dB. The displayed level is still 0 dB and not clipping - BUT the display on my Presonus CentralStation is in the red (>0 dB) and my monitor speakers are crackling - until I reduce the output in Studio One by a few 0, dB I noticed that it differs with different limiters at the end of the chain in the main or listen bus. But all of them should limit @ 0 dB. This is displayed - but the actual output is hotter... Gonna try an export as WAV and see what happens... |
madsvigeholm wroteUninstall reinstall drivers.. reboot.. and I have completely deactivated my firewall/antivirus stuff but it still happens quite often.. but a couple taps on my spacebar and everything plays again.. annoying? yes - but not a showstopper 🙂 I would strongly recommend NOT deactivating your firewall
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. |
bensizer wrote but more importantly, support are not taking these problems seriously or escalating them to the people who can actually fix them. I have to admit that, sadly, I can share your opinion. I have encountered a great quantity of bugs so far, reported each one of them. All bugs were reported with steps to reproduce and videos, and they were sent to the technical team to fix them, which feels like a sort of "void" where your bug report is sent to and you really don't know if it will actually be fixed in the next update. You might even have to report it again, who knows.. To be completely honest, what's most annoying is the amount of time that I waste because of bugs. For example, setting up the ATOM SQ was a painful experience when it came out, so much confusion about the drivers (I still remember that time), and I recently experienced a new bug where the knobs just jump in large values instead of moving smoothly, but the support team was just able to tell me 'there seems to be a problem in your settings folder' but they couldn't find the cause. Meaning: I need to make several tests on my own, removing files one by one, until I find what's causing the bug, which however will be faster than waiting for another reply from the support team, but.. the point is I'm not here to do some beta testing, I'm here to make music! p.s. sorry for my tone here, but I have actually spent a lot of time understanding why bugs happen, trying to give the best reports possible because I like Studio One. Though at the end of the day I realize a good chunk of my freetime was spent dealing with bugs and not making music. It's a bit frustrating.
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 |
I'm so glad we finally got automation and the listen bus on project page, this was really off-putting as it was so obvious it needed to be there.
Anyways, I was trying out a test project and for some reason I can't "Update Loudness" anymore, no matter what changes I make on automation or a plugin, clicking on "Loudness Information" it just opens and collapses, with nothing on it. Can anyone confirm this behavior?
Artist Page
Latest album quick preview SPECS Audio: MOTU M4 | Yamaha HS8 Studio Monitors | Beyerdynamic DT 770 Pro 250 ohm | Komplete Kontrol S49 MIDI Keyboard | Roland FP-10 PC: Win 10 64 bit | i5-8600K 3.6Ghz | 24 Gb RAM | Nvidia GeforceRTX 2070 |
Users browsing this forum: No registered users and 13 guests