Using Cubase Pro 15.0.30. I started discover random disappearances of mainly audio events from tracks. I had to reload the same files over and over again for the past 5 days. They are still available in the Audio folder and pool but gets deleted from the track. And today out of nowhere a midi part was added at the end of the project. I know everyone will say I must have deleted them or added them by mistake but what are the odds of deleting the same events at least 7-8 times from a track over the course of 5 days. And why not others. I’m about to go nuts on this one.
In the Pool it shows the number of times an Audio Event is used in the Project. Does that number match what you see looking at the Project Page?
When this weird stuff happens, I suggest opening the Edit History window to see what it shows. It should at least show if something is deleted or added. If it doesn’t show operations, then that is REALLY weird. If it does show them, though, you at least know the operations are happening and have to figure out why. For example, is it possible you have some remote controller operations that could perform such operations, and maybe the controller is a bit flaky (e.g. sending controls spuriously – I’ve sometimes seen this with faders on mine, though not recently)? The other thing I’ve seen in my experience lies in the “user error” department where I’ve temporarily changed focus to another Cubase window (e.g. MixConsole), forgot to change it back to where I was (e.g. project window), and some keyboard shortcut I use is now working in the wrong context. (My most common one here is with the “g” and “h” to zoom in and out horizontally, where, instead of zooming out/in in the project view my MixConsole channels get narrower/wider because I moved a fader or did something with an insert and forgot to click back in the project window.) That one can be especially deadly when using the lower zone Key Editor or an ARA editor and going back and forth between the project window and the lower zone editor, where maybe you try to delete a note, thinking you’re in the key editor, but you’d done some quick something in the upper zone and forgot to click back. Or something like an undo/redo that is working at the clip level instead of the note level (or vice-versa).
The other helpful thing about the edit history window, beyond just checking what operations it sees, is that you can roll back or forward in the case of unintentional operations (e.g. to quickly recover deleted clips in your scenario), without the running blind with just using the keyboard shortcuts to try multiple undo/redo operations.
I’ll check but in any scenario I really don’t get how a user error can cause deleting of the same xact files every time. Beats me. Thank you for the advice. I’ll definately have a look into that.
Thank you for taking time to reply in such dept. User error factor is naturally the first thing that comes to mind but when I cross check that with probability math, me doing the same mistake for 5 times deleting the same short audio file in one particular track out of 48 would be a little bit off. I also get a similar thing what you are getting in terms of the sizing of the mix console. I hit something and all track heights are narrowed down where one gets ultra ultra wide. But why? Who would need such a key command. or is it again “a key stroke in the wrong window” problem.
I know Cubase has been around since Atari ST times (I’ve been a user since then) and kept updated by putting code over old codes then re-writes. I seriously think that things are becoming a bit clunky with patching holes and adding features constantly. User friendliness is becoming a problem lately. There should be a way to still keep old users like us in the loop but simplifying the workflow. By looking at the number of user problems in the forum I wish I haven’t purchased 15 pro only recently. 
Maybe. But not necessarily if it happens to be some repeated keystroke thing. But this is where reviewing the edit history comes in to figure out if it’s actually showing the delete operations, then, if it is, trying to figure out how those happened, be it some remote control thing, checking shortcut keys, or whatever.
Well, yes, it is a keystroke in the wrong window problem. If, for example, you’re working in the main project window, then click something in the MixConsole, for example to move a fader, add an insert, or whatever, then don’t remember to click back in the project window before issuing the G or H keystroke, the keystroke’s function applies to the MixConsole window instead of the project window.
If you haven’t experienced that in the past, is it possible you were using a single monitor in the past and multiple monitors now? I always have the MixConsole visible full-screen on my second monitor, so it makes it “easy” to tweak something there in the midst of mainly operating in the project window or a full-screen Key Editor window or whatever I may be doing on my primary monitor. And it’s also just as easy, when just hovering the mouse over the primary monitor to forget to click, thinking I’m already working in that same window.
I’ve only been using Cubase since V9.5, and only as my main DAW since V10.5. (I’d used SONAR for upwards of a decade and a half before that.) I can’t say, though, that I’ve regretted any upgrades along the way, even if there are still some window focus issues that trip me up, sometimes frequently in the case of applying a shortcut key when the focus isn’t in the window I’m thinking it is in.
For me, when that happens, the explanation is usually that something unexpected was selected when I did a delete. For example, I’m sometimes surprised by what is selected and where the focus is, like RickPaul says, after doing an undo. Unfortunately it is sometimes much later before I realize something was unintentionally deleted.
Yes, the “something unexpected was selected” is the thing I’ve seen in this scenario as well. As for the “realize much later”, this why I consistently make backups of tracks prior to any serious editing (e.g. cutting up prior to comping, doing the actual comping, moving the selected clips after comping to a dedicated comp track, applying a destructive process like de-reverb, etc.). That way, if I notice much later, I can just go to a backup copy of that track to find what I’d mistakenly deleted (or changed in a way that I find later isn’t really working) and grab whatever is needed from the backup.
I tend to do this at two levels. One is every time I save a project after some milestone (e.g. comped lead vocal in verse 1), I also copy the CPR file from that save and give it a meaningful name. This level lets me time travel if I need to import an entire track (or multiple tracks) from an older iteration of the project into the current project then do any fixes from there. The other is having backup folders (e.g. “old lead vocals”, “old instruments”), where I duplicate specific tracks at milestones, disable those duplicates, then just drag the duplicates to the folder. Short of some project-level disaster, this is usually the most likely place to recover some small element (e.g. too aggressively tuned vocal phrase, the accidentally deleted clip thing, etc.).
Once I dub a project finished and start the archival process, I get rid of all the backup elements prior to backing up the project itself for archival. (However, I still have the older versions of the project, including one at the final mix level, that I can access if a sanity check on the archived project turns up issues that necessitate redoing the archive. I don’t delete those until after I’m satisfied the archives have all been sufficiently quality-checked.)