I've just upgraded from Waveform 9 to Waveform 10 (v10.2.1) and am having major problems with Waveform 10 crashing virtually everytime I try to export or render.
It's also it is crashing sometimes when I close down an edit. (i.e. it doesn't return to the projects page.)
I'm using files that were originally created using Waveform 9 which has absolutely no issues rendering or exporting them on the same PC.
I still have both versions installed, Waveform 9 works perfectly, but Waveform 10 is driving me crazy.
I've tried installing previous versions (10.1 & 10.2) but the results are exactly the same as with the latest version (10.2.1).
I'm running Windows 10 (64bit) v1903 with an i5 CPU & 16Gb RAM and have more than 120Gb free on my main SSD where my projects are located.
I've checked the Waveform 10 logs but they don't seem to indicate that anything is wrong, the last entry on the session is the lame encoder being loaded (i.e. there's no shutdown entries).
Either WAV or MP3 exports both result in the same outcome.
No crash reports have been generated, despite numerous ones happening.
Also verified all the plugins used in the edit, they all report as OK.
I'm not a newbie to Tracktion - I've been using it on a daily basis over the last 18 months and migrated through versions T6, T7, W8 & W9 without any major issues.
Please can anyone help?
Export/Render crashing Waveform 10
-
- KVRian
- 544 posts since 24 Jan, 2004 from Sweden
I have a similar setup to yours and on my system Waveform has never crasched while exporting. There surely has to be an issue with your setup. Maybe a plugin is causing it?
-
- KVRer
- Topic Starter
- 9 posts since 6 Jul, 2019
ISSUE SOLVED
==========
Stuttaton ... Thanks for your prompt reply - You've pointed me in the right direction.
Although I've already done a full validation of all the plugins I used (ALL TESTS PASSED for all of them), the crashing was indeed down to just one plugin. (Dead Duck Delay v1.0)
The problem now appears to be resolved and since updating that plugin to the latest version (1.58), I've not had a single crash.
I'll outline below how I determined the exact cause, just in case anyone faces a similar problem with other plugins.
1. I made a copy of the edit.
2. I deleted each track, one by one until Waveform crashed (Noting which plugins were being used on that track).
3. I reloaded the edit and then deleted each plugin on that track, one by one until Waveform crashed again.
4. The last deleted plugin was then determined to be the cause of the problem.
5. I disabled that plugin (by moving it out of the VSTplugins folder or renaming the suffix to .zzz or similar)
6. I retested the edit for any further problems.
In my case replacing the plugin with the updated version solved the issue.
It's still very strange that the Waveform Plugin Validator passed the faulty plugin as OK.
It would be nice if plugins could be globally enabled/disabled from within Waveform's plugin settings.
I thought this option already existed, but it's not obvious how to do it, if so.
==========
Stuttaton ... Thanks for your prompt reply - You've pointed me in the right direction.
Although I've already done a full validation of all the plugins I used (ALL TESTS PASSED for all of them), the crashing was indeed down to just one plugin. (Dead Duck Delay v1.0)
The problem now appears to be resolved and since updating that plugin to the latest version (1.58), I've not had a single crash.
I'll outline below how I determined the exact cause, just in case anyone faces a similar problem with other plugins.
1. I made a copy of the edit.
2. I deleted each track, one by one until Waveform crashed (Noting which plugins were being used on that track).
3. I reloaded the edit and then deleted each plugin on that track, one by one until Waveform crashed again.
4. The last deleted plugin was then determined to be the cause of the problem.
5. I disabled that plugin (by moving it out of the VSTplugins folder or renaming the suffix to .zzz or similar)
6. I retested the edit for any further problems.
In my case replacing the plugin with the updated version solved the issue.
It's still very strange that the Waveform Plugin Validator passed the faulty plugin as OK.
It would be nice if plugins could be globally enabled/disabled from within Waveform's plugin settings.
I thought this option already existed, but it's not obvious how to do it, if so.