Hi,
it never failed here regardless of the Cubase version. Is this also happening in straight projects with no tempo/signature changes or anything beyond the usual?
I’ve never had an issue with this either. Any chance the audio file that hosts the click is on a removable drive or dropbox or something like that? If not, could you post a photo of your Metronome setup window?
I have got no idea how to narrow it down if it also happens in empty projects and it’s fixed after closing/relaunching Cubase.
My best bet are corrupted preferences - have you tried to reset them by renaming the preference folder and importing your settings/presets afterwards?
Maybe someone else has got a better idea?
Good luck!
in fact, a couple of weeks ago I reset all my preferences and I only kept my keyboard commands and my Plugin manager, thinking that this could solve my serious Pool problem (it’s in another thread) in fact it doesn’t solve it, but that It’s another topic.
like I said, the metronome settings are by default, I’ve just changed the sound itself.
another aspect that happens to me, and for years, is that sometimes, when recording, and using the pre-account, it eats up the first click (which confuses the artist I have recording)
Just a FYI, you probably know that already: If you rename/delete your current preference folder then the factory defaults will be restored BUT previous settings from two Cubase versions down are automatically migrated to your new preference folder. That is, if these versions still reside on your system. The only way to prevent this from happening is to rename older preference folders, too.
I already had several cases (I use Cubase since version 8) where I assumed a Cubase bug (I was “sure” about that, because I started with my empty template, and that meant for me a clean environment), just to find that my template was - let’s call it “outdated”.
It was not corrupt per se, as the respective behaviour was correctly working in certain (older) Cubase versions. But in some cases, a new creation of my template (just creating it from the current Cubase version’s “Empty” template) was the solution to the “assumed bug”.
that would make sense to me. I don’t expect Cubase to be perfect and error-free, but I do expect Steinberg to at least show some interest in fixing these types of errors.
let’s say, this one in particular is not a serious mistake, I could live with it. but there is another one that I do not forgive.
even so, and returning to this particular error, if recreating the template is the solution, I will do it without any problem.
Before creating a new template, which can be quite some effort (depending on your requirements), check whether a new test project, created from Cubase’s actual “Empty template” solves your assumed bug.
Only then it’s worth to invest effort into a new template.