For everyone uploading Nuendo or Cubase logs here. If you used the uploader coming with Cubase/Nuendo 13, there is little use to put them here too. They will simply by identified as duplicate in our bugtracker and eat up our time until then (downloading here, upload to analyzer, close ticket if duplicate etc.).
Another thing to keep in mind is that these dumps can sometimes contain data you do not want to expose to the public. Using the uploader provides the same information to us, helping with identification of issues and bugs, but invisible to the public. If the uploader does not show up (ie. standalone instruments) you might consider sending the crashdumps/logs via PM to @Gerrit_Junge or to me (@Philippe_Bono ) and we will take it from there. Even if we can not reply to every query (some developing and testing has to be done too ) crashdumps will always end up in our analyzer toolchain after we put them there.
In any case, as seen above, make sure the crashes where reproduced with the latest version. There is no use uploading a crashdump from an old version.
It is part of the Cubase/Nuendo safe start dialogue, since Cubase 13.
If the sequencer encountered a crash, it will show this dialogue on the next startup, with an option to upload the files directly to us.
Here is an example, after I just crashed my previous Cubase session on purpose:
If you click “Send log files to Steinberg”, the files will be sent to us and automatically treated in our bugtracker. No need for you to open a ticket, try to get in touch with support or whatever. Convenient and safe.
As stated above, HALion Standalone does NOT have this feature. There you need to get in touch with support or post here and send a pm with the crashlog via PM.
EDIT: The same applies for using HALion etc. in 3rd party hosts.
Ok great , I do that going forward , I have also in the passed been having a lot of crash and ask here is anyone could help me pin point what making things unstable Martin has helped me a lot !!! last years is was a lot of Eucon and HALion . I am now Beta testing Eucon and things have really become stable . but is was very helpful to get feedback I could share with Avid .
What I’m saying is simply logging this with Steinberg would possibly not have helped me in that respect.
Sorry for beeing unclear, not saying you should not post at all or get in touch. This is the purpose of this forum and support.
My post was meant as a reminder about:
that it makes no sense do duplicate information, if it was already sent.
Forums are public and crashdumps etc can contain sensitive information.
If you are aware of this and it is ok with you, sure, go ahead. The case you mentioned is a great example and getting @Martin.Jirsak involved is very helpful, as he is pretty talented in solving problems
As I can see, you have a freeze, not a crash, and you used the __crash__ trick to get the *.ips file. Great!
It’s tricky to resolve these files, because it’s not clearly visible, where the freeze really happened.
What I can see is, there is mediaclient mentioned in thread 0 quite on top. There is also the license-engine-access mentioned in thread 4 quite on top.
From these, I would try to:
Start Steinberg Download Assistant. MediaBay component will be updated automatically. Which might help with the possible mediaclient issue.
Start Steinberg Activation Manager. Make sure, there is no antivirus or firewall blocking communication with the Steinberg servers.
If you are using iLok, make sure, the Pace software and driver is up to date.
Can someone please try this for me. Load a template arrangement with a copy of Halion, an Eagle Patch loaded in it. Go to mediabay, tag a few hundred samples, poof there goes Cubase. Load same template, remove Halion no more crashes in media bay.
) crashdumps will always end up in our analyzer toolchain after we put them there.
