DC-Choppah wrote:OneWorld wrote:
Imagine being sat at the computer and moving the mouse rapidly from left to right, every 2 or 3 seconds the mouse 'freezes' momentarily. Imagine the mouse cursor being in the centre of the screen and you want to move to the menu along the top of the screen, the mouse 'stalls' for a moment on the journey from the centre of the screen to the menu bar. OK it's not big deal, but when in Cubase and doing some intense editing, a lot of mousing about, it really is an inconvenience.
Now in sync with the mouse error, the progress line in Cubase stops too. Imagine playing a tune and the scroll bar is moving from left to right as the tune plays. The scroll bar stops every few seconds, only for a moment, then it starts moving again and catches up with itself, but again after a few seconds, stalls for a moment.
What makes this even stranger is that I can start Cubase and the fault does not show up until about after an hour or so of use. I am completely baffled by this behaviour. I have downloaded new/older drivers, I have even tried swapping out my Fireface 800 for my Liquid 56 interface, as I knew I definitely never had the problem before I got the FF800, but, no difference. And because it is relatively random, it's hard to track down when the problem first surfaced. I have tried every setting I can think of but no solution.
The fix was far far simpler, but one that foxed me for weeks
My DAW (ProTools) acted that way recently too. Just like you, if I left it on for some time, it would become laggy like this. Turned out the problem was the CMOS battery on the mobo had run out and the system clock was wrong. When your system clock is off and/or the CMOS battery is out you get weird Windows problems on anything time critical like a DAW or the mouse. Please replace your mobo CMOS battery, make sure your bios is updated and the system time is set properly. Note this is not a 'Windows' issue if it is the case since WIndows just runs on top of your system and trusts the system clock. If your system clock is unreliable, Windows will be unreliable too.
The fix was far far simpler, and had it been the MOBO battery, the fault would have been consistent not internetmittent, but it was a fix so simple I could slap myself in the face with a wet fish, but was so hard to isolate, but here goes....
I have 2 PCS (PC A - Office PC) and (PC B - for music) I have 2 4K monitors Mon 1, Mon2
PC A --> Mon 1
PC B --> Mon 2, + Mon 1 (Music PC can be displayed over 2 monitors)
I don't always have PC B displaying to Mon 1 + Mon2, only when I am doing some in depth editing
If I am not using PC A, but it is switched on, Mon 1 will go to sleep, and depending on use, it can go to sleep intermittently
At the same time PC B will be turned on, but not actually displaying to Mon1 + Mon2, as PC A is displaying to it, but if I choose to have PC B displaying to both monitors then I can select the input I want to display on both.
When the problem (the stalling scroll bar + jittery mouse) first arose, or more precisely, when I first noticed it as a re-occurring problem but one that occurred intermittently, WIn10 had updated, I had bought a new mouse + keyboard, I had bought a new MIDI controller and had updated some software.
Because of my layout, I don't see both monitors at the same time, they are at 90 degrees to each other, I like to keep the second monitor as a mixing monitor, I don't need to see Cubase scroll going along, I treat the monitor as a mixing desk, in conjunction with hardware MIDI controller - I have a virtual console. And if I want to use email, MS Office etc, I use PC A anyway. Point is, when it goes to sleep, I might be looking the other way and not notice the instant it went to sleep.
Seeing as Win10 had updated, I had bought new equipment, new keyboard + mouse, new software and noticed the 'fault' I suspected one of these changes was the culprit, the usual garden path logic. It turned out to be purely coincidental that I noticed the fault. And tried the logical route - go back t the old keyboard + mouse, swapped out the new MIDI controller etc, rolled back my WIndows image etc etc etc
For a day, everything went well, then I would go and get a cuppa, came back, set play going on Cubase and the problem was back grrrrrr I even changed my tea from Yorkshire to Typhoo.
Then the other day I got up and thought I am going to nail this once and for all. I sort of stress tested each hardware keyboard, each MIDI controller etc etc and after about 7 hours all was still working well!!!!! Yipeee
I went to make a cuppa, set Cubase going and DAMN!!!! the problem was back again. I sat back, and supped my tea and asked myself, what has changed in the time it takes to make a cup of tea - just one thing, I had turned off PC A had been turned off and so no signal coming in and as such gone to sleep, even though PC 2 was sending a signal to it, though coming into Mon1 (HDMI 1 fed from PC B)
So I reckoned that must be it. So I got the monitor remote, switched to HDMI 2 (fed from PC B (music PC monitor 2)) and then of course the music 2 displays were displaying and lo and behold, scroll bar operated as it should and so does the mouse - it was as simple as that.
I guess with the music PC using 2 monitors, the display card syncs them together? so when one monitor went off sync was lost, but why that should affect the mouse (and the qwerty keyboard) goodness knows, but I don't really care anyway, it works and that'll do me,
And I guess I owe Win10 an apology, it just happened to come to the party when the trouble started
