Skip Jones wroteThe skipped MIDI note behavior has been logged and currently under review.I confirmed it as well.

Thank you for your input. If it is indeed a reproducible bug it will be addressed.

Skip

Came here to report this as well - good to see that it's being looked into, it's a bit annoying to say the least.

For me it's easy to reproduce. Make a simple 4 bar loop of a few chords. Load some VST (I've had it with ANA 1.5 and Spire (whatever the latest version is) at least, but I suspect any will do). Play it in a loop and it will skip notes every now and then at random.
This happens to old and brand new songs alike. Even if it's the only instrument in the song as well.

Not using low latency. Dropout protection set to high. Wasn't an issue before this update.

Loop recording has become unusable. It seemed to work for a very shot time but now, if I record several takes, only the first take records and sometimes , not even that. The loop recording a big problem a few versions back and it was finally working OK prior to 3.5. Now it's regressed and worse than ever. It even crashed Studio One when I was using it yesterday.

Hi,

Loop playback is not functioning correctly. If I have several midi tracks with Komplete Kontrol, and I play the project with loop enabled, some notes are not played after the first loop. It resembles a project with the block size set too low (lots of skips). However, if I disable loop playback the project plays correctly.

Note: I never had this issue in previous versions.

Thanks

christopherb wroteHi,

Loop playback is not functioning correctly. If I have several midi tracks with Komplete Kontrol, and I play the project with loop enabled, some notes are not played after the first loop. It resembles a project with the block size set too low (lots of skips). However, if I disable loop playback the project plays correctly.

Note: I never had this issue in previous versions.

Thanks

The random missing MIDI notes have been reported to the developers.

I'm not experiencing anything unusual regarding dropping of notes with instruments anywhere whether that's in loop mode or not with high or low latency modes, in Kontakt or any other synth in this 3.5.2 version. I'm using Windows 7 64 Bit edition, with a Focusrite Pro 14, firewire based interface.

So I imagine this issue is restricted to certain interface/s.

jpettit wrote

christopherb wroteHi,

Loop playback is not functioning correctly. If I have several midi tracks with Komplete Kontrol, and I play the project with loop enabled, some notes are not played after the first loop. It resembles a project with the block size set too low (lots of skips). However, if I disable loop playback the project plays correctly.

Note: I never had this issue in previous versions.

Thanks

The random missing MIDI notes have been reported to the developers.

Good to know. I see it happening on my Win 10 64 with my UR44 interface.
Thanks.

Glad / annoyed that others are reporting the missed MIDI notes issue. I would assume something so basic would have been tested prior to release. Guess not.

!%&$! :p

I've got a drum track (Slate Drums) that's dropping notes always at the same place when playing back in 3.52 yet it plays back flawlessly in version 3.51 of S1 (I keep older versions of S1, just for times like this).

I would recommend an emergency release to fix this and not have us wait the requisite 2-3 months for the next official release. I'm sure others would appreciate this kind of prioritization as well because few of us can work on a project without looping and consistently working MIDI drum tracks.

PS. Win 10 / i7 7700 / 16 GB Ram / SSD & HD combo / Focusrite interface

Rest assured, the developers are already working on it.

It would be nice if they release a hotfix but I have only seen that once in 6 years.

Although there is no excuse for such a base capability having an unforeseen issue, in fairness the point release was focused on StudioLive Series III rack mixers and adding significant functionality to Prime/Artist as well as a few nasty and hard to find bugs. They did also fix 45 other issues.

With the scope of the product greatly enhanced in terms of integration and complexity of the engine buffering, 100% regression testing can be more challenging than say a few years ago.

IMHO: I think they will take other efforts to improve testing in the future.

jpettit wroteRest assured, the developers are already working on it.

It would be nice if they release a hotfix but I have only seen that once in 6 years.

Good to hear they are working on fix. At first I thought it was an issue with my Quantum, but I quickly realized it was the software. The odd thing is it doesn't happen with every project.

Here's the funny thing. I experienced this missing MIDI note issue in v. 3.5 and it disappeared when I installed the 3.51 update. Now it's back in 3.52 as of the last few days. So that's a good place to start — what was changed in 3.51, code-wise, and reverted back to its original state in 3.52?

That's a rhetorical question. I'm not expecting an answer, obviously, except maybe a tweet from Donald. That would make things great again. :p

jpettit wroteIt would be nice if they release a hotfix but I have only seen that once in 6 years.

I'd think that the question of whether to release a hotfix or not depends on the likelihood of this happening. The bug description certainly seems large enough to warrant one IMO. It's just a matter of how many users/projects would be impacted under the current state. I haven't done any MIDI work this week, so I haven't seen it, but if I were to run into it, I'd absolutely downgrade to 3.5.1. MIDI notes dropping is definitely a big deal and absolutely shouldn't wait a month or two if this is common.

Funkybot wrote

jpettit wroteIt would be nice if they release a hotfix but I have only seen that once in 6 years.

I'd think that the question of whether to release a hotfix or not depends on the likelihood of this happening. The bug description certainly seems large enough to warrant one IMO. It's just a matter of how many users/projects would be impacted under the current state. I haven't done any MIDI work this week, so I haven't seen it, but if I were to run into it, I'd absolutely downgrade to 3.5.1. MIDI notes dropping is definitely a big deal and absolutely shouldn't wait a month or two if this is common.

Thanks, Funkybot. As someone who works a lot in MIDI, losing a kick or snare while tracking a guitar or bass is like losing your balance and tipping over. Totally disorienting in that it causes you to lose the feel of the song.

So yeah, I'm not in the mood for a "it would be nice" approach from Presonus, even if they have bigger priorities or new products to launch instead. MIDI recording in loop mode is an important aspect of modern recording that is now malfunctioning in Studio One. And I'm not going to pretend that it's all good just because other bugs were fixed.

I can't effectively record tracks with v 3.52 right now because my drums drop out.

Due to all the bug reports I'm still at version 3.4.4. Works great. Also looking forward to the new features when the time is right.

Perhaps the beta testing team could be expanded? Don't know if politics will allow for this, but if in-depth users like niles, Funkybot or others would be interested in doing this, I'm sure they'd have a lot to contribute with.

Skaperverket wrotePerhaps the beta testing team could be expanded? Don't know if politics will allow for this, but if in-depth users like niles, Funkybot or others would be interested in doing this, I'm sure they'd have a lot to contribute with.

I recently resigned the beta team because of the politics.

niles wrote

Skaperverket wrotePerhaps the beta testing team could be expanded? Don't know if politics will allow for this, but if in-depth users like niles, Funkybot or others would be interested in doing this, I'm sure they'd have a lot to contribute with.

I recently resigned the beta team because of the politics.

Ah, I understand.

I highly value having you here with us independents on the outside, then.

This keeps getting worse - now whenever I record or play in a loop I get random buzzer sounds. I have been an avid fan of Studio One since version 2 when I migrated from Logic because of crashes and glitches. I've used it to record several CDs and was very happy with it until the 3.5 release. The development team seems to have forgone stability for the sake of new features. In my eyes, that was a bad tradeoff. This is actually even worse than Logic was then. I just spent a half hour trying to record a 10 second retake but I couldn't successfully record it. I regressed to 3.5.1 and the same problem persists. This is extremely disappointing.

If I started a project in 3.5.2 can I safely open it in 3.3.4? At least that seems to be a stable version.

I have found another problem and it's to do with EZ Drummer VST or AU. When I go to the mixer section of EZ Drummer and then try to set separate channel outs for the individual percussion parts Studio One crashes instantly.

Anyone else having this problem?
I have the latest version of EZ Drummer and all kits are up to date.

guitarism wroteThe development team seems to have forgone stability for the sake of new features. In my eyes, that was a bad tradeoff.

No, of course they haven't forgone stability. I'm sure if someone had known about a loop playback bug it wouldn't exist in this release. So just wait until the next update and it will be fixed.

guitarism wroteIf I started a project in 3.5.2 can I safely open it in 3.3.4? At least that seems to be a stable version.

No. Since the song file format changed in 3.5 you can't open songs saved in S1 >= 3.5 with earlier S1 versions.