There is a major bug regarding midi events in Studio One 5.4
1. Open the piano roll
2. draw in C notes across 3 octaves. C1, C2, C3 (C notes in any octave will work)
3. Attempt to simply move or ALT+ drag the midi event (not the midi notes)
Studio One will crash. This bug is repeatable.
Hopefully Presonus can jump on this, because the performance enhancements in this version are seriously welcome improvments.
Last edited by starkid84 on Fri Sep 17, 2021 7:02 pm, edited 1 time in total.
Have you raised a support ticket with a video showing this - and submitted your crash logs?
Please note that I may express opinions that are different from yours but I do not intend to cause offence.
iMac 27" 3.3 GHz Intel Core i5, 32 GB Ram, Catalina OS 10.15.7, 64 bit, Studio One 5.4 Professional (always the latest) , Reason 11, Melodyne 5 Editor, Digital Performer 10, Korg Legacy Wavestation and M1, Arturia minimoog V, Helix Native 1.93, Bias FX 2 Elite, Superior Drummer 3, EZkeys, EZbass, Alesis Q49, Audient iD14, Faderport 2018, Gibson Les Paul Standard, James Tyler Variax JTV-59 and other gear.
Are you trying to move the EVENT it self or are you just trying to move the midi notes?
Because I can recreate this every time (Win 10) Add notes C1 C2 C3 and on the track move the event - it does not move and will crash. Change one of the notes to D2 and it works!
How do you test for this ??
Some developer really worked hard at screwing this up. What kind of code works on everything but you put multiple C's in and it crashes?
Clearly, I do not understand this. Hope you don't mind me saying so, but why would anyone do this? And, as someone who gives a rats, why can't I reproduce it?
Those with issues please create support tickets.
Please add your specs to your SIGNATURE.
Search the STUDIO ONE 5 ONLINE MANUAL. Access your MY.PRESONUS account.
OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET.
Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce.
OS: Win 10 x64 Home, Studio One Pro 5.x, Notion 6, Series III 24, Studio 192, Haswell CPU: i7 4790k @ 4.4GHz, RAM: 16GB, Faderport 8/16, Central Station +, PreSonus Sceptre S6, Eris 3.5, Temblor 10, ATOM, ATOM SQ
reggie1979beatz wroteClearly, I do not understand this. Hope you don't mind me saying so, but why would anyone do this? And, as someone who gives a rats, why can't I reproduce it?
Are you copying steps shown in the video posted? this crash happens on every system I have tried it on.
It would defintely be an issue for anyone who happens to play C in 3 ocatves, I know that in many arrangements I will easily play C in at least two octaves. Some one might have 3 drum sounds mapped to C in 3 octaves triggered as one hit, or keygroups when during a part of the arrangement 3 Cs will sound at the same time. There are many situations where one might use 3 C's spaned out across octaves. .
That is not something you'd expect from a professional workstation. Even if many people would not play C in 3 octaves, the few that would should be able to do so with out experincing a app-breaking bug.
Also, looking into this bug may expose other bugs that have yet to be found. And so far it looks to be a program specific bug, not one that is system dependant.
Last edited by starkid84 on Sat Sep 18, 2021 12:18 pm, edited 1 time in total.
Playing three C’s on my 88 note controller, fine. As soon as I click to open piano roll, crash! Same when entering three C’s manually and clicking piano roll…
***Rolled back to 5.3 and was unable to create a ticket on my account??
Last edited by patricebrousseau on Fri Sep 17, 2021 7:57 pm, edited 1 time in total.
I'm pissed about not being able to reproduce, but that so many have. The only logical solution is that it's a thing for sure, and for some odd reason I cannot reproduce. I cannot just be the one person, I'm doing something wrong.
But as have been mentioned, even though it will be next week, support ticket away!
reggie1979beatz wroteI'm pissed about not being able to reproduce, but that so many have.
Have you tried Horny Goat Weed?
Been testing it more:
I will show notes with value and where that note is in relation to 4/4 beats of the bar ( )
C1(1) C2(1) C3(1) = Crash
C1(1) D2(1) C3(1) = OK
C1(1) D2(2) C2(3) C3(1) = OK
C1(1) C2(2) D2(3) C3(1) = Crash
C1(1) C2(3) C3(4) = Crash
C1(2) C2(3) C3(4) = Crash ##
Conclusion: If you have any 3 C's as the first notes anywhere in the event = CRASH
Any note that separates them = OK
## Note: It Doesn't have to be on the first beat of the bar !!
Also 2 C's is OK but three or more C's only = crash
Confirmed - Windows 10.
PC: AMD Ryzen 3900X, 32GB RAM DDR4 3600MHz CL16, ASUS ROG Strix X570-F, Gigabyte Radeon RX 570 8GB, SSD CORSAIR SSD MP510 960GB M.2 NVMe (OS)
OS: Windows 10 Pro x64
DAW: Studio One Professional x64
Gear: RME Fireface 802 + RME Advanced Remote, ATC SCM25A PRO, Avantome Mixcubes, JBL 305p, Softube Console 1, Presonus Faderport, AKAI MPC Touch, AKAI Advance 61, Presonus Faderport, Beyerdynamic DT-990 Pro
So C is for Crash?
Users browsing this forum: robertgray3 and 15 guests