Have you tried to reproduce the crash with a Cubase project that is not using the AmpleBass vst3 plugin? You dump seems to point on that direction.
1 Like
You have my last Element 13.0.30 version.
I don’t own the last Pro 13.0.30 Version, but it’s the same problem !
I wasn’t sure who your reply was to earlier. These reply tabs seem to have a mind of their own. Or maybe it’s just us?
Yes, my other projects are behaving the same. It’s all random. Sometimes the projects run all the way through other times C13 is just shutting down.
It has also shut down with AGT.
All these projects run perfectly in previous versions of Cubase with no problems what so ever.
I’m only just getting used to running procdump as Cubase is generating no dump files. It’s a problem for me as I’m not good with software stuff full stop.
Now I just can’t share anymore projects with friends using Cubase 13…
I know they own also Studio One Pro 6.6, so I have to swith DAW to keep on working…
Do you also get the crashes with an empty project with just a few audio tracks and no plugins instantiated at all?
To Jorge_Ruiz
Not with an empty project. I’ve had no need to run an empty project.
I was finding that - if I managed to render out my vst’s the projects would run with no problems. But rendering everything out is not a viable option for me. With over hundreds of projects waiting to be finalised. However, at present that may be my only option/solution
All I’m doing is pressing play and letting the project run. No editing while the project is running. No fader adjustments, etc.
Nearly all my projects are Amplesound basses and guitars. Superior drummer 3 or BFD3. With the occasional kontakt instrument. I have no more then 10 to 12 tracks with two vocal audio tracks and 2 to 4 backing vocal audio tracks. It’s all very primitive and mainly writing stuff. But that’s personal choice. I’m a minimalist.
I’m thunderbolt 3, Windows 11, all latest. I’m running Steinberg power scheme. Asio guard high.
Before C13 (The following never happened)
I could select each individual track in the project window and nothing visible or active would appear.
Now I’m finding that in C13 when I select a vst track in the project window, real time, asio-guard and peak metering are very erratic on the scale, anything from virtually nothing to half and above like a fiddlers elbo.
Now if I select any other track marker or audio the meters settle.
Whatever is happening now was not happening on any previous versions of Cubase.
That’s all I can let you know at present.
Do keep in mind that the performance of the meters in the Audio Performance Panel had a significant change starting with Cubase 12.
Unless you are experiencing any audio drop-outs, I would pay no attention to it.
What is your audio buffer set to? The ASIO Guard level should roughly reflect your buffer setting.
1 Like
Last I checked. The thunderbolt card is set to 128. But as I’m not recording anything it is usully to (not 100% on these figures off the top of my head) 512 or 10 something or other.
Set at any level has caused no problems. Windows seems to be happy with 128. I see no difference. No drop outs or cracks/pops etc. I only had the thunderbolt system on the pc for the round trip very low latency while doing my vocals, but they’re all complete now.
All these projects for me now are only playback and fader adjustments and possibly compression along the line. But Is I said before, none of these shut downs happened before C13.
“if” something has gone amiss with the PC. No other programs are showing any sign of failure.
NOTE.
I can check the exact figures later if it’s very important to the post?
EDIT
Same input and ouput latency etc. All figures match up in Cubase and Thunderbolt audio card/Interface by the way which is Presonus Quantum 2626
I just got the crash during loading Mix Console, with no dump file created.
I didn’t give the post it’s title. That was done when the post was moved into it’s own post/thread (not sure what it’s called). Anyway. All I was doing was pressing play, whilst in MixConsole (as I always do). I then still had the problem after running the same project but in project window. But the shut downs were/are random (always).
I’m still getting no dump files, but I’m trying to get used to procdump. How successful that will be, only time will tell.
What I am finding, more and more, is that when I manage to render the vst’s C13 is ok (hope I’ve not spoken too soon). This, for me, at present, seems to be the only way forward with the C13 shutting down problem.
It’s not ideal for me as I don’t want to commit to audio.
I hope for you it’s just a one off.
I can run a project several times, and then on a consecutive pass C13 just shuts down at random.
I cannot re create the fault.
I press play and hope.
But sadly hope just isn’t enough.
Render seems to be the only way.
(Is that a song title?)
EDIT
By the way, SF_Green are you on the BFD forum. I’m sure I’ve seen your name come up on there. And, while I’m here. BFD3 is running without a hitch with C13. Just saying.
Yes, I’m on the BFD forum too quite a bit. I’m running BFD3 in Cubase no problem, except the occasional reauthorization issue with Dark Farm.
1 Like
Six days on.
I’m still in the same boat.
Any update from anyone?
Life is wasting away? Or should I say enthusiasm towards Cubase (13) is wasting away at this point.
If it’s being looked into then that’s ok.
If not? then I guess we’re stuck.
Hi,
I’m sorry, without the DMP file, there hardly can be any update.
How did you proceed with it, please?
Btw, are you on the latest Cubase 13.0.30, please?
I now give up?
I’m on the latest 13.0.13.
I’ve provided several procdump files. In the earlier posts
Cubase is generating no dump files
Would you like me to continue banging my head against the wall. And try to produce some more procdump files?
Hi,
Do you mean 13.0.30?
Sorry, the last post I found from you is, there are no dumps. You were searching for the way, how to generate them. To do so, please see above.
From this, I read, you have no dumps from the current version. Unfortunately the dumps from an older versions don’t help. Please, find the way, how to generate a dump file above. Without the dump file, we cannot help, I’m sorry.
Typo - yes - 13.0.30
8 days ago included 3 zipped procdump files via Dropbox. And another 9 days ago, plus one file sent to you private message quite a few days before that.
All other suggestions have been followed.
EDIT.
Hello @Neil_Murt,
sorry to read about your issues.
I have checked the four procdumps you posted: two point to ABP, two to AGTC.
We can’t do much here because there is a call from the plugin (only the plugin engineers can see what that function is / does), then an fsetpos call, and ucrtbase throws an invalid parameter exception.
How the freezes occur may seem random, but all dumps show a recursive call to nvwgf2umx (NVIDIA driver) in the thread list, that is very likely where the breakpoint/freeze occurs.
If you’re running supported hardware (what CPU/GPU are you using?), I’d recommend to repair the Redistributables like mlib wrote and perhaps do a check with DISM / SCANNOW.
I’m not familiar with the plugins, but you could check if they offer graphics settings (e.g. GPU acceleration) and perhaps check with the developer, they might know about it or have a workaround.
3 Likes
Windows 11 AMD Ryzen 9 5950X 16 core 64gig ram
Nvidia ge force rtx 3070 (studio driver) (all ge force experience removed)
I’m pretty sure I’ve followed everything in all these reply posts.
For me this has now gone on too long. No problems like this before the C13 update/install. I’ve saved all my files now to C13 (and there are hundreds). They now crash/shut down Cubase in C11 and C12.
It’s become a very big problem now as I’m altering the projects beyond recognition.
I’m managing, very slowly to render out all the vsti’s in the projects, but I’m having to do them one track at a time (that’s down to my limited knowledge on the matter).
I wrote you a pretty detailed step-by-step on how to repair your MS C++ Redistributables. Did you try that?
I believe Fabio put the nail on the head here. You have two plugins from the same manufacturer that causes Cubase to crash.
Have you been in contact with Ample Sound about this?
2 Likes
Yes I followed the step by step.
All my guitar and bass plug ins are from Amplesound (ABP is one of the basses AGTC is a guitar plugin). They showed no problem until until C13. And all work with Ableton live suite 12 and propellerheads Reason 12
I’m going to try and contact Amplesound. But the only address for them I have at present is a facebook page. I don’t have and will not have facebook on my gadgets full stop.
Going to try and send them an email when I find their link?
EDIT
Managed to send them an email.
Maybe/hopefully I will get a reply.