Yes I agree, in general, this warning message alone doesn’t provide enough information to diagnose the root cause of a crash or issue. It’s often necessary to look at other information and logs to determine why the debugger is unable to verify the timestamp and whether it’s related to the crash. But could it be that vst connect is associated with the amd, the licensing and the synsoacc warnings if the senario is like this:
In this case, I get the wrong profile, the reinitialized one. What I did is a duplicate of the ‘Default’ one and this allowed me to retrieve exactly my settings as they were before attempting the profile manager use.
I ressurect this thread becasue I have a problem which is covered by this topic (and i don’t want to start a new, only slighetly different thread)
In the studio complex where my studio room is located, there is a large live room to which a total of three control rooms are connected. Each control room has different outboard and sound cards configuration. All three engineers use Cubase or Nuendo as their main DAW. That’s why it often happens that an engineer wants to record or mix in a different control room. Ideally, everyone would simply load their user profile in each room, and Cubase / Nuendo would look and behave as they do in their own control room. Unfortunately, the preset for input and output busses is always loaded as well. This is different in every control room, as the outboard and sound cards are different. In such a case, it would be good if you could exclude these (or other) parameters from the user profile so that the user profile can also be loaded in such a situation. Otherwise you have to redo the preset for input and output busses every time, which is very time-consuming.