In Windows when I quit VDJ it still remains running in the background and I have to End Task the process using Task Manager.
Using the appropriate commands in Command Line or Powershell does not kill the process.
This has been an issue for me for close to a year now. VDJ 2026 also acts the same as VDJ 2025.
Any and all thoughts and sugeestions are welcome. Thanks bunches.
Using the appropriate commands in Command Line or Powershell does not kill the process.
This has been an issue for me for close to a year now. VDJ 2026 also acts the same as VDJ 2025.
Any and all thoughts and sugeestions are welcome. Thanks bunches.
Posted yesterday @ 3:51 pm
Any controller connected, and if so, does it also happen without the controller connected?
Posted yesterday @ 3:59 pm
I've just learned to live with it. VDJ has done this for so many years now (on Windows anyway).
This PC stays on 24/7 and I run VDJ on it mainly to check out tracks or do some tag editing.
Sometimes when I close VDJ it shuts down fully. Often it doesn't - yet there's no difference in the setup or things connected/not connected. Occasionally it gets so stuck that only a reboot will kill it.
This PC stays on 24/7 and I run VDJ on it mainly to check out tracks or do some tag editing.
Sometimes when I close VDJ it shuts down fully. Often it doesn't - yet there's no difference in the setup or things connected/not connected. Occasionally it gets so stuck that only a reboot will kill it.
Posted yesterday @ 4:07 pm
groovindj wrote :
I've just learned to live with it. VDJ has done this for so many years now (on Windows anyway).
This PC stays on 24/7 and I run VDJ on it mainly to check out tracks or do some tag editing.
Sometimes when I close VDJ it shuts down fully. Often it doesn't - yet there's no difference in the setup or things connected/not connected. Occasionally it gets so stuck that only a reboot will kill it.
This PC stays on 24/7 and I run VDJ on it mainly to check out tracks or do some tag editing.
Sometimes when I close VDJ it shuts down fully. Often it doesn't - yet there's no difference in the setup or things connected/not connected. Occasionally it gets so stuck that only a reboot will kill it.
It's been like that for me for years now !!!
Posted yesterday @ 4:29 pm
This sounds like a Windows only issue (although I've never seen this on the MSI laptop I trialled occasionally) - process seem to always end on Mac for me, and quickly.
That behavior still sounds wrong though, quitting the app should always eventually quit the process/release any resources it held.
Is there any kind of auto backup setting that you guys are using?
That behavior still sounds wrong though, quitting the app should always eventually quit the process/release any resources it held.
Is there any kind of auto backup setting that you guys are using?
Posted yesterday @ 4:53 pm
Will mention that VDJ always shuts down cleanly and completely for me. (both Win 10 and now Win 11)
The only cases that it does not shut down completely:
1) are those few times that VDJ hangs. In which case requires an "end task" in task manager.
Or, very, very rarely, a hang which is already rare, will require a OS reboot.
2) a crash where VDJ restarts on its own, (starting to analyze all tracks).
Just requires a normal VDJ restart, (clicking the X in the upper right corner)
And with the these last 2 situations, once reported, the dev team, quickly updates with a fix.
(unless it is something unique to my system/configuration/setup)
The only cases that it does not shut down completely:
1) are those few times that VDJ hangs. In which case requires an "end task" in task manager.
Or, very, very rarely, a hang which is already rare, will require a OS reboot.
2) a crash where VDJ restarts on its own, (starting to analyze all tracks).
Just requires a normal VDJ restart, (clicking the X in the upper right corner)
And with the these last 2 situations, once reported, the dev team, quickly updates with a fix.
(unless it is something unique to my system/configuration/setup)
Posted yesterday @ 4:59 pm
No issues with VDJ shutting down for me across 4 different Windows machines.
Posted yesterday @ 5:10 pm





