Everything was fine yesterday, but when I reopened the file, all messed up.
One problem is that the events are in the second measure, but the sound doesn’t come out until the third measure; in short, the events on the screen don’t match at all.
Another problem is the rhythm. It should be four eighth notes: 8 8 8 8, but when played, it becomes 16+16+(8 rest) 16+16+(8 rest), and the time values are also off.
What could be the reason? I feel like the “playback style” is off; is there such a setting? Because the data is correct and hasn’t been modified, but it’s playing wrong.
Okay, I just figured that one out . What happened to humanity that language usage has been reduced to this sort of lazy, ugly, worthless, sorry excuse for communication?
“WYSIWYG” (“wizzy-wig”) has been used since the first desktop publishing apps showed up on early Mac, Xerox, and other computers, if not earlier where you could see the actual rendered fonts instead of imagine them based on symbols on a text display. We’re talking like 40+ years ago, long before mobile phones were really a thing, and before the Internet was public.
Yes, comic relief. I get it. But can we respect @girlsati 's request for help by not derailing their topic while we wait for info on their audio interface?
From the 1st post it sounds like something was hogging resources and causing mistimed MIDI and audio playback. It could be lots of things: running out of RAM, failing drive(s), overactive antivirus, overheating, etc.
We could use some more information.
What computer? What OS?
Has this happened before? Did restarting fix it then too? Were there any other issues besides audio? Did the graphical interface become unresponsive or glitchy?
What does the Cubase performance meter show when this happens? Do you see excessively high CPU and RAM use in Task Manager (Windows) or Activity Monitor (MacOS)?
Which sound card? Are you using a dedicated driver? What is the buffer size set to?
If you’re on Windows, what is your GPU? Is its driver up to date? If using Nvidia, are you using the Studio or Game Ready driver?
Is the project stored on an external drive? If so, how is it connected? Have you tried a different data cable or plugging into a different port?
Are there any other programs running (e.g. web browser)? Are you connected to WiFi?
Are you using VST instruments? Do you have any external MIDI devices?
I realize that this is a lot. You don’t need to answer everything, but anything you can provide will help us help you.
Yeah, sorry about bringing on the sidetrack. I did initially have interest in the setup of the user and how restarting the computer seemed to have solved the problem. We have absolutely no information about the system in use. Therefore, if @girlsati can’t provide more info it’s a dead thread.
So … curious minds want to know how restarting your computer solved the problem!
More curious minds want even more info about your system specs, your Cubase version, etc.
The more info you can share means the more details others can use to help solve mysterious problems .
Restarting the machine is the best, most basic troubleshooting action one can take when faced with a software issue. If the issue isn’t recurring or reproducible, there’s not much to discuss.
See this every single day at work haha. Sometimes the math just isn’t mathing, and there’s no rhyme or reason.. Reboot and everything is back to the way it should be and we call it ‘ticket closed’ at that point!
I’m not a computer tech guy, but, respectfully, I might modify this, at least I do at home, to:
For random-seeming Cubase weirdness:
Close re-open project. ITDWT (if that doesn’t work then) …
Close re-open Cubase. ITDWT …
Then reboot computer.
I guess it’s debatable whether following these steps saves any time, I think it does, but I might be wrong (full disclosure, I actually was wrong once. Spring of 1993. I’ll never forget it )
It doesn’t hurt to try it in incremental steps either..
For all we know at the time, it could be the particular projects memory space that got corrupted somehow, could be Cubase’s, or who knows might be something to do with the OS. Might take a bit longer if you have to do all three, but you never know. You may solve it at the very first step and find out its just the project causing the wonkiness and save yourself the headache of rebooting, setting everything back up, etc.