This has to be a midi read error with things drawn on the bar. I've worked out a pattern as to which notes are dropped. Read it as a standard 4/4 beat, B =bass drum, S = Snare, 0 = Dropped note. So, fist play through of a loop B, S, B, S, B, S, B, S, B, S, B, S, B, S, B, S. Works fine. Next loop being, B, S, B, S, 0, S, B, S, B, S, B, S, B, S, B, S. Drops that note. Next, B, S, B, S, B, S, 0, S, B, S, B, S, B, S, B, S. Drops the next bass drum. Next B, S, B, S, B, S, B, S, 0, S, B, S, B, S, B, S, and on the chain goes until full circle, then the pattern repeats. If I humanise so not every note is exactly on the beat, it all goes away. Has to be a problem with the new update. I'm just going to sit and wait for the next one... But still.

But for real, thank you all for suggestions, help, and your time! Very, VERY much appreciated! Love this site and you guys!

 

yep, same problem now here. odd sh%t.. also crashing vst alerts and crashed exe.

never had this problems with S1 before.

 

Wow this MIDI issue started happening to me as well. Just happened yesterday for the first time a couple of hours after reading this post. I also never had any issues with S1

 

@shortikno it's an update issue, buddy. Not much you can do to rectify it apart from offsetting the drawn in notes by milliseconds. Really hope this issue gets addressed in the next update. As you can see by my prior posts, I've tried everything, but sadly nothing else works apart from that. Bit of a pain, no doubt, but at least it's a fix until the next update comes out. Hope my suggested method works for you, man!

Edit. I shouldn't outright say it's an update issue, as not everyone has been having it. There's got to be a common denominator, but I have no idea what it could be.

 

Ok, I said I'd push it until it breaks, LOL. And it did! ;) First @Parasite-B I tried the pattern you proposed and did not get any problems. (Also switched on screen capture; but it doesn't matter now.)
Edit: now I have to agree /w you.. it's prob the update

Then @The_Disturbed I dragged in a simple .mid pop-rock drum loop, like you said and it was still ok (the loop wasn't quantized). Then I Q-ed the (8th) loop to a quarter note grid, so it was "wrong", but should still play.. and BAM - the beats started dropping. I selected all and deleted doubles and shorts, but still now and then BD+HH allined on grid didn't trigger (Kontakt vst).

Tried the official Presonus solution, which The_Disturbed already mentioned. HERE is the link to their page about it (delete the contents of the settings folder with the exception of the user.license file and the "Extensions" folder) and it worked.. Also rendering - dragging the midi on an audio track - was working just fine, even before the "fix".

That doesn't mean that if I drag in the Beethoven's 9th .mid and quantize, it will work, lol. Pres will have to look into this, as it's far from rock solid. Pls, report if the "fix" fixed it for you..

 

Last edited: Oct 23, 2017

@Matt777 man, really admirable that you'd keep on pushing it, until it breaks, man! I know it's a ball ache to replicate, but the fact that you've persisted... This is why I love this site, and the people here, so much. SO much wealth of knowledge.

I've tried the solution suggested by The_Disturbed before, but no harm in trying again! Thankfully have everything backed up, so nothing to lose. But yeah, kind of glad in one aspect that it's not just me, but at the same time, it's a pain that it's amongst other users... Wait for the next update it is.

I'll give the info in link that you've provided a shot soon, and post the outcome. There's no way I'm going to play with that right now. Too drunk... It will not end well... But thank you for that link, man!

I shall definitely not be dragging in the midi for... It'll send me on a random tandem of distortion, glitch and noise... I need sleep.. I'm ust gong to bypass that right now, despite my temptation...

 

@Matt777 for real though, man, thank you for keeping on looking into this. Really appreciate it, man.

 

@Parasite-B No problem.. In fact, the fact you spotted it early is useful for me/us too. Just started a project on the updated S1 and really wouldn't like to spend time on it in vain. Will see how much it interferes with my workflow..

We're here to learn and help each other ..can see you're in search of inspiration

 

I have strong belief that this issue will definitively be fixed within a few weeks through a software update.

Thanks for experimenting with the bug!

 

Last edited: Oct 23, 2017

Guys I have a trick that works....... when starting a project make sure your MIDI event clip don't start from Bar 0 ( i.e the first bar) start from the 2nd bar in the project window.... this should fix your problem till the next update

 

Last edited by a moderator: Oct 24, 2017

@mickey - Avoid writing in ALL CAPS in the future. This makes it feel as if you're shouting.

 

Lol

 

I had to roll back to 3.5.1 as nothing seemed to help. Tried starting the arrangement from bar 2 or even further in and still dropping notes. Even notes not quantized played from my keyboard were dropping after a few reps. Tried to bounce the track and still dropped notes. Quite frustrating. Rolled back and all was fine. Hope this is worked out soon. I love S1. This is my first workflow stopping bug since switching DAWs.

 

@shortikno did you try the fix The_Disturbed posted? You also have the link to the official Presonus response in my post above (#25). It solved things here. You can also send me the midi sequence that gives you trouble so I can check..