How often does your DAW crash?

Audio Plugin Hosts and other audio software applications discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

Sonar crashes about once a year for me, always related to a plugin. Latest crash was because of Replika. I solved that by returning to the previous version of Replika.

Mitch I.

Post

TheoM wrote:
t3toooo wrote:DAW crashes are most likely related to the used soundcard-driver,so buy a better one with better driver support.

bzzzz... wrong.
:lol:

Yeah in fact it could be one of 5 billion things. Now, on windows, BLUE screens are almost certainly a driver issue (who has those anymore? )

Post

Nuendo 6.5 + Nek6.5
Windows 7 (64x)
RME Raydat
UAD PCIe (Almost exclusively)
Running about 6-10 hours/day 5-6 days a week.

Can't remember the last time it crashed. No Joke.

Post

Voice303 wrote:
whet wrote:Sadly reaper in the recent years, had a few bluescreens.
A user land program like REAPER and other DAWs can't cause a blue screen.

Your drivers / hardware on the other hand can.
Agreed, in concept, but not experience. Why does Deus Ex Human Revolution Director's Cut (the technically inferior buggy edition) reboot my computer? Vista would just give me a GPU driver crash notice after then restarting the GPU driver. Win 8.1 spontaneously reboots. Just Cause 2 doesn't reboot the system but can cause a kernel panic. If this problem is GPU focused, why did Vista behave correctly and Win 8.1 decide to reboot instead of restarting the GPU driver? It's funny how everyone hates on Vista, but it didn't hard crash the system like the newer OS does.

Userland software should never do this crap but it still does anyway. The OS doesn't do its job.
- dysamoria.com
my music @ SoundCloud

Post

TheoM: Damn. That sounds extremely frustrating. It figures that the DRM would be the problem. It always is.
- dysamoria.com
my music @ SoundCloud

Post

Since upgrading my laptop computer (i7 2.8 quadcore 24GB RAM) and OS (Win 8.1) I have had very few crashes ... I'm on Live 9.2. The crashes I have had are often down to dodgy plugins (Replika for example).

Post

Everytime when I close Cubase I'm gettin info about error. But it's after closing it so I can live with that

Post

Sonar - just about every time I try to use it
Cubase - never

Post

Y'all need to stay off them porn sites.



Dammit Reaper just crashed! What's this banner... Oh... oh hell yeah (Fap) :evil:

Post

just a small hint of "wake the dead" :D

Still no crashes. A wee tad of freeze a couple of days ago (which I think was win10 doing an update) but it passed quickly.

@bluescreen/drivers: Bingo (did I already say that? Can't remember, too lazy to check)

Post

Since I disabled my Wi-Fi driver, I've had zero crashes. Before that, I was getting ridiculous amounts of crashes due to the wifi driver causing huge DPC Latency.

Post

vintagevibe wrote:Sonar - just about every time I try to use it
Cubase - never

Same.
vespesian (sean)

You're in an amazing state - so stay there.

Post

I use mostly Renoise, Reaper, and FL Studio, with a splash of Mulab. I don't recall any of them ever crashing on a Windows 8.1 machine with a Focusrite interface (and drivers).

Post

If I close a project and load a different project in the still opened Cubase... in 95% it crashes Cubase 8 (and this since some versions). Without avoiding this, I would have crashes every day.

I know that some plugins don't work very well as the 64Bit version... so I bridge this plugins (64Bit to 64Bit) and they running now in its own process... without this I would have multiple crashes every day.
(this are for me ArtAcoustic BigRock and Samplemagic Magic AB)

IMO 99% of all crashes are because of poor implemented plugins (I speak about DAWs with at least 1 to 2 service updates because major DAW updates with a lot new features having also often some of this bugs which could crash the DAW or make the DAW very unstable...)

Post

4damind wrote: IMO 99% of all crashes are because of poor implemented plugins
I often read that. But imagine plugin XY crashes one host, but works perfectly on another. Is it really the plugin's fault then? I mean, obviously it seems the VST implementation, or something else about the DAW, maybe the way the graphical interface is done, seems to differ, otherwise one plugin wouldn't crash the one, but not the other? Really always the plugin's fault?

Post Reply

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”