Frequently when I close Tracktion (all versions AFAIK), Task Manager shows the process keeps running. I've tried testing the behaviour, and notice that if I simply open Tracktion and close it again, the process stops when I close the program. So whether or not the process keeps running seems to depend on certain actions or events while Tracktion is open, possibly something related to certain plugins and/or changing audio interface settings. When the process keeps running like this the PC may keep running for some time - short or long - but eventually I get a BSOD. This is suboptimal.
Any ideas?
Win7 64bit, EMU 0404 USB
Task Manager shows Tracktion process continues after closing
-
- KVRAF
- 4896 posts since 3 Jan, 2003 from Vancouver
BSOD would almost certainly be hardware-related. That doesn't mean unrelated to Tracktion, though. My best guess would be Tracktion is unable to disconnect itself properly from whatever hardware is handling the sound.
Surely there must be consensus by now...
-
- KVRAF
- Topic Starter
- 1674 posts since 22 Oct, 2004 from Schmocation
Thanks pough. Perhaps I should try running T7 with the internal soundcard and see if I can provoke the error. The EMU 0404B hasn't been supported for years and wasn't even properly supported from the start, so that's a likely culprit. Will upgrade some other dodgy PC components this week, so hopefully somewhere along the line I will get it straightened out.
-
- KVRist
- 113 posts since 4 Mar, 2016
It's fairly easy (usually) to tell what the cause of the BSOD is.
If your computer is set to automatically restart, you can still find out what the error message from the BSOD is by going to Start -> Run and typing in "eventvwr" then OK. Now it's been a long time since I saw a BSOD so I can't remember precisely in which category you'll find it, but you need to go to "Windows Logs" on the left and then it will be under either "System" (I think that's it) or "Application".
The BSOD information should contain a few helpful things, such as an error message like "IRQL_NOT_LESS_THAN_OR_EQUAL", and you'll also get memory references such as 0x0000000C which commonly will occur if there has been an attempt to access invalid memory.
Once you have this information you can either post the contents of the log here (I can usually help out with this sort of thing) or run a Google or otherwise search on the error information to try and find out exactly what has caused it.
If your computer is set to automatically restart, you can still find out what the error message from the BSOD is by going to Start -> Run and typing in "eventvwr" then OK. Now it's been a long time since I saw a BSOD so I can't remember precisely in which category you'll find it, but you need to go to "Windows Logs" on the left and then it will be under either "System" (I think that's it) or "Application".
The BSOD information should contain a few helpful things, such as an error message like "IRQL_NOT_LESS_THAN_OR_EQUAL", and you'll also get memory references such as 0x0000000C which commonly will occur if there has been an attempt to access invalid memory.
Once you have this information you can either post the contents of the log here (I can usually help out with this sort of thing) or run a Google or otherwise search on the error information to try and find out exactly what has caused it.
-
- KVRist
- 473 posts since 1 Feb, 2006
check for plugins! they can cause this effect in correlation with hosts.
known for this behaviour in samplitude (as an example and maybe startingpoint for experimentation) are these atm:
NI Battery, NI Kontakt (5 i believe, not sure bout that), Acustica Audio Nebual and Acqua Plugins
in samp it happens, when you directly close the program without closing a project beforehand (and wait some seconds before then closing the program itself).
may be worth checking in tracktion too. i always close edits in tracktion before i close the program and have never seen stuck processes.
known for this behaviour in samplitude (as an example and maybe startingpoint for experimentation) are these atm:
NI Battery, NI Kontakt (5 i believe, not sure bout that), Acustica Audio Nebual and Acqua Plugins
in samp it happens, when you directly close the program without closing a project beforehand (and wait some seconds before then closing the program itself).
may be worth checking in tracktion too. i always close edits in tracktion before i close the program and have never seen stuck processes.
-
- KVRAF
- Topic Starter
- 1674 posts since 22 Oct, 2004 from Schmocation
Thanks, I've got some things to work on now. I've had lots of problems with plugins, but the Tracktion developers agree with pough (see above) that shouldn't normally lead to a BSOD. I'm going to make a habit of closing edits before closing the program, though.