Interesting. I tested it a couple of times at 120 bpm (don’t know how to set ppqn 
). Results (see attachments):
I haven’t tested with tempo changes (I rarely do theses so they are not relevant for me).
System: Cubase Artist 8.0.10, home-built i7 4790K, Win 8.1, Steinberg UR28M, itsy-bitsy Korg mini-keyboard thru a powered USB-hub.
Win 7 64
Presonus Firestudio Mobile
M-Audio Oxygen 61 mkIV keyboard (also tried a different, non-USB keyboard, plugged into my interface’s midi port. No difference.)
Old mobo was Asus p8z77. I built a new computer with an Asus x99-a, fresh Windows install, nothing but Cubase on it, but no difference.
Interesting, thanks. To me it looks like the “good” version is still somewhat the same just not as bad. The randomness of how bad the bug is part of the strangeness - if it was always equally broken that might be easier to fix.
It would be great if more people could test this. So far everyone who’s tried has the bug.
Let’s just collect some data here, and not debate or try to prove the issue one way or another. if you could, please refrain from drawing conclusions.
I don’t know which mod changed the thread title but it would be easier to collect more data if you changed it back. The current thread title works well if the goal is for Steinberg to keep ignoring the problem.
It was me. @Mike3345, I took this issue up on my own time. I am going to look at this issue objectively, collect data, and I see to it that right people hear about it. I can do this with or without your help.
The only thing that is on topic for this thread is replies with screen shots of the list editor and system specs.
Hmm. I wonder if this might have something to do with something I experienced a few days ago with UVI Workstation. I was doing some live playing in Cubase 8 with UVI Mello, and frequently notes would get stuck “ON” as if the note on/note off messages were getting dropped or shuffled. I don’t remember ever seeing that before in Cubase, and this was the first time I’d used Mello in Cubase 8.
No, this is very specific, and easily missed. It’s about this: Note start OR end times are quantized to a very small value, around 10 ticks @480 ppq.
I’m just looking to get for screen grabs of the list editor of a midi performance, around 16 measures long.
You mean 10 ticks @ 120 ppqn, or about a 32nd note I think (really quite choppy and audible.) Yes, more screen grabs would be great. I started said Gearslutz thread:
One user said he didn’t have the bug, and posted a screen grab. He of course had the bug, full-blown too, affecting note starts and everything.
No, you are mistaken. ‘ppq’ stands for Pulses Per Quarter note, and Cubase is set by default to 120 per 16th note. around 120 ticks per 16th note, or about one twelfth of a 16th note- somewhere between a 128th note and a 256th note.
It is odd that you have the aural acuity to hear these timing errors, yet would think that they are as four times as coarse as they actually are.
Ok, here goes my try, sent as an attachment (how do I upload an image here, since the attempt below failed?):
Cubase version 8.0.20
Opinions/suggestions most welcome.
Ah, I stand corrected. Was just trying to figure the numbers off the top of my head. Do you know how many milliseconds the 10 ticks at default 120 display/tempo is?
You don’t need special aural acuity to hear this bug, though! 10 ticks at default display settings is huge! Even one or two ticks will change the feel of the groove enough to hear it.
Musical timing is such a beautiful human thing, Steinberg! Please let us have the real thing like in Cubase 7!
Your image did get attached to your post. It shows in your case the same as on my system, note lengths are affected (after the first measure). Note starts are not.
Do you see how almost all the lengths end with 6 or 7? This is what the OP is talking about.
Thanks. You’ve got the note lengths bug, which it appears everyone does. If you do the test in Cubase 7, the note lengths won’t have that “only every 10-ish ticks” pattern.
Now, the only way note lengths can be corrupted is for the note starts and ends to be corrupted. But I guess it divides up the error between the two, because in your test the note starts appear random enough so as not to seem buggy. But they likely have to be it’s just harder to see at this point. That was how Cubase behaved for me for several months, and I never noticed because who closely examines note lengths?
But then one day my note starts all became corrupted as you can see, and I’m surely not the only one.
You could I suppose live with the corrupted note lengths, and after every take check the List editor to examine whether your note starts are now corrupted too.
To me the much better alternative is to do all midi work in Cubase 7. I plan to keep mixing audio in Cubase 8, but I guess now I’ll have to test it to make sure this bad jitter doesn’t affect audio too.
@120 bpm there are 960 ticks per second. So 10 milliseconds.
Thanks. 10 milliseconds?! Welcome to 1979, indeed.
Wow. Just wow.
While you´re at it, is it significant that the Manual says, under MIDI Display Resolution (p 1069), that “This only affects how MIDI events are displayed ande not how they are recorded”?
All new stuff to me, but I did recently experience a serious problem of note starts while recording a keyboard playing friend. We both heard him play perfectly to the click, and on replay it was sharply off, at random, such that, say, I could not have programmed a drum track to that keyboard. In today’s test, note starts seem ok, though.
I think that’s limited to the display resolution and couldn’t explain the random nature of the bug as demonstrated in my 2nd screen grab. Steve?
Is this issue something that people are hearing (I know the OP can, I’m wondering about others), or is it a technical issue only?
(I could have sworn I posted something like this earlier today, but I don’t see it now …)
Mike3345, thanks for bringing this issue up.
I’m going to ask you a favor please … if you might be so kind as to delete the part of your post that I replaced with “…” in the above quote. I’m concerned that words like that will get the thread locked down, and further understanding of the issue will suffer as a result.
Thanks in advance for your consideration!
