I just installed the latest version of Waves Central and now I'm having all sorts of problems opening edits in Tracktion 6. First I got an error message from jBridge saying it was taking too long for auxhost.exe to initialize. Updating jBridge fixed that problem.
While I can open some edits now, there are others that simply hang on load and I can't get past the gray screen with the gear. The active CPU core gets stuck at maximum and RAM activity ceases in the Tracktion process. I eventually have to terminate Tracktion from Task Manager to close. This only happens to some files.
The peculiar thing is, I don't think I even have any Waves plugins in the project I'm loading. I tried taking a look at the log file to get some clues, but the log file in my Roaming/Tracktion 4/Temporary folder hasn't been written to in two years. Is there another log file somewhere I should be looking at?
Whatever Waves Central changed, it messed with jBridge and Tracktion both. Any thoughts on what's going on or how to fix it?
EDIT: Solution found (see last reply).
Problems loading edits after updating Waves Central
-
- KVRist
- Topic Starter
- 195 posts since 16 Feb, 2004
Well, I completely uninstalled all Waves plugins and Waves Central, and the problem still persists. Things were working fine a couple days ago and I haven't installed any other plugins since, so it would seem quite a coincidence for it not to have been Waves, but it'll be hard to say if my crash log isn't writing properly. Sigh...
-
- KVRist
- Topic Starter
- 195 posts since 16 Feb, 2004
A little sleuthing revealed that a record of Tracktion's dependencies during a crash can also be found in the crash dumps at C:\Users\Your_Name\AppData\Local\Microsoft\Windows\WER\ReportArchive\
The unlikely culprit turned out to be signaldust's IRDust, which I had just added during my most recent session the other day. Deleting the dll for the VST allowed all edits to open without problem.
It still doesn't explain the conflict with jBridge after updating Waves Central, but at least things appear to be working for now. The next step will be to see how things go if I reinstall Waves, but it's getting late, so that'll best be saved for tomorrow.
The unlikely culprit turned out to be signaldust's IRDust, which I had just added during my most recent session the other day. Deleting the dll for the VST allowed all edits to open without problem.
It still doesn't explain the conflict with jBridge after updating Waves Central, but at least things appear to be working for now. The next step will be to see how things go if I reinstall Waves, but it's getting late, so that'll best be saved for tomorrow.