Quick Sign In:  

Forum: VirtualDJ Technical Support

Questions, bugs or comment related to the latest version of VirtualDJ

(NOTE: VirtualDJ continuously updated, so many older topic on this forum are most probably already fixed in the current build)
If you need extended support, contact our Support Team.
Topic: Stems not working/crash when changing math engine settings
Hi,

I am having a problem with stems.

I have just upgraded my windows computer from an Intel i7-770k & nvidia RTX 2080, to an AMD Ryzen 5900x and nvidia RTX 3080.

Stems worked perfectly fine on my old system, using an MC6000 controller to control them (inner knobs as stems, outer as EQ).

Now though, stems just don't work at all. When VDJ first loads up the knobs on the screen are showing as vocal/instrument/beat, but after a few seconds they change to high/mid/low, and the inner and outer knobs on my MC6000 control the EQ, the stems don't appear at all.

Additionally, the hot buttons in the stems section do nothing either. turning any of the 5 of them on or off doesn't affect the music in any way. I have also tried loading songs that have pre computed stems and they don't work either.

I tried changing the math engine in the settings from GPU (which is what it was on by default) to any of the other options, but that just crashed VDJ. I manually changed the setting in the settings.xml file to CPU, stems still don't work. Automatic doesn't work either.

Another thing I have noticed is that When I close VDJ, if I then open task manager it's still running, and if I try to open VDJ again it won't load my library, which seems like VDJ isn't shutting down properly either.

I think there may be some compatibility issues with my new CPU/GPU. Stems is a great feature and I'm really lost without it!

Anybody got any ideas what might be the problem here?

Thanks.
 

Posted Wed 06 Jan 21 @ 12:32 pm
AdionPRO InfinityCTOMember since 2006
 Best Answer Could you try to open VDJ, wait until stems work normally, then change mathEngine to CPU and then restart to see if they work faster that time?
If it would be related to the nVidia it should initialize fast when using CPU.
If not fast, could you check agian in process explorer where it is stuck?

Posted Mon 11 Jan 21 @ 6:05 pm[ selected best answer by Adion on Fri 15 Jan 21 @ 3:29 pm ]
Just been doing some more playing around trying to get this to work.

I was using a backup of my Virtual DJ folder in documents, so I decided to do a fresh install of VDJ to see if that solved it, and it worked absolutely fine until I closed VDJ down. As I said above, it doesn't actually close, just goes into background processes and I have to force close it before I can start VDJ again. Upon starting up VDJ again, stems don't work again.

I did notice there was a text file in the folder called 'Log Report', which contained a load of references to the mathEngineInit freezing:

[19:38] Thread mathEngineInit freezed.
--- 2021/01/05 - 22:33 (6156)
[22:33] Thread mathEngineInit freezed.
--- 2021/01/05 - 22:34 (6240)
[22:34] Thread mathEngineInit freezed.
--- 2021/01/05 - 22:35 (6242)
[22:35] Thread mathEngineInit freezed.
--- 2021/01/06 - 10:42 (6242)
[10:42] Thread mathEngineInit freezed.
--- 2021/01/06 - 12:26 (6242)
[12:26] Thread mathEngineInit freezed.
--- 2021/01/06 - 12:33 (6242)
[12:33] Thread mathEngineInit freezed.
--- 2021/01/06 - 15:22 (6242)
[15:22] Thread mathEngineInit freezed.

These times correspond to the times when I close down VDJ and it doesn't close properly. Looks like the math engine is crashing when I am exiting VDJ.
 

Posted Wed 06 Jan 21 @ 3:37 pm
AdionPRO InfinityCTOMember since 2006
Did you install the latest nVidia drivers?
 

Posted Wed 06 Jan 21 @ 4:02 pm
Yes, I am on the latest version of the Nvidia GPU drivers (460.89). Is there a problem with these?
 

Posted Wed 06 Jan 21 @ 4:06 pm
So, I just left VDJ open for a while as I noticed that it was using quite a bit of CPU power for it not actually doing anything. Went away for about half an hour, came back and stems are working! The waveform had changed form the multicoloured to the one colour, and the eq knobs/pads are working. Loaded up a few songs from tidal that I know I would have never played before (so no precomputed stems) and it analysed them in a couple of seconds.

I then closed VDJ, and it didn't hang around in the task manager like it did before.

I opened it up again, and stems were not working again. Left it open on my monitor and watched it, after about 15 minutes the waveforms changed and it's working now. CPU usage dropped from about 6% down to less than 1%. Seems like it's doing some kind of background task that is taking a long time, then once that finishes everything else works fine.

It's a good workaround for now, but would be good if this could get solved so stems work when VDJ first starts! Happy to provide any log files needed.
 

Posted Wed 06 Jan 21 @ 4:51 pm
I'm having the same problem. I got video of it happening too with open on process looking at the threads. I'm on a 3900x and rtx 3090 so this leads me to believe it's a 3000 gpu problem with VDJ

https://www.virtualdj.com/forums/239095/General_Discussion/EQ_auto_switches_to_disabled_on_track_load_.html

edit, getting the same error in log report:
--- 2021/01/06 - 22:14 (6242)
[22:14] Thread mathEngineInit freezed.
--- 2021/01/06 - 22:37 (6242)
[22:37] Thread mathEngineInit freezed.
--- 2021/01/06 - 22:37 (6242)
[22:37] Thread mathEngineInit freezed.
--- 2021/01/06 - 22:39 (6242)
[22:39] Thread mathEngineInit freezed.
--- 2021/01/06 - 23:31 (6242)
[23:31] Thread mathEngineInit freezed.
--- 2021/01/07 - 00:35 (6242)
[00:35] Thread mathEngineInit freezed.
 

Posted Thu 07 Jan 21 @ 8:49 am
Does yours also start working again if you leave it for 15 mins or so?

Definitely seems like it's a 30xx problem then seeing as we have different processors.

Edit: just seen your thread. Sounds identical to my issue.

There was an Nvidia Driver update out today (461.09) but installing them hasn't changed anything. I tried downgrading to an earlier version (457.30) to see if that solved it but it didn't.
 

Posted Thu 07 Jan 21 @ 6:42 pm
DJNemobob wrote :
Does yours also start working again if you leave it for 15 mins or so?

Definitely seems like it's a 30xx problem then seeing as we have different processors.

Edit: just seen your thread. Sounds identical to my issue.

There was an Nvidia Driver update out today (461.09) but installing them hasn't changed anything. I tried downgrading to an earlier version (457.30) to see if that solved it but it didn't.


It is kind of random about it's around 15-19 mins every time I've timed it using the in software timer (click the clock). Yeah I saw the notice but sad that does not fix it so must be something calling the API to use cuda processing.
 

Posted Thu 07 Jan 21 @ 8:10 pm
So I streamed a set last night after leaving VDJ open for 15 mins beforehand to get the stems working.

I noticed that stems just aren't even working properly! I'm using the EZRemix option for the EQ knobs, but they aren't doing what they are meant to do, and even using the stems pads isn't working properly either.

Using the pads:

Turning off Vocal doesn't seem to do anything
Turning off the kick mutes both the kick and the vocals, but then turning off the HiHat as well brings the vocals back
Turning off the Instru and Bass buttons just seems to mute random frequencies!

Tested this with a few different songs, so it's not just the 1 song I tried. Video here of proof: https://1drv.ms/v/s!AirDBud1EdbfsPR_h5jlBIXD7Gcx1g?e=TebXYS

I've played Killing in the name many times before and I know the stems worked properly on it before.

I also tried setting the MathEngine setting in the settings.xml file to CPU to see if this made a difference, but it's exactly the same either way.
 

Posted Fri 08 Jan 21 @ 10:45 am
AdionPRO InfinityCTOMember since 2006
Could you try to open VDJ, wait until stems work normally, then change mathEngine to CPU and then restart to see if they work faster that time?
If it would be related to the nVidia it should initialize fast when using CPU.
If not fast, could you check agian in process explorer where it is stuck?
 

 Selected as best answer Posted Mon 11 Jan 21 @ 6:05 pm
Chiming in to say that I also have this issue running a 3090
 

Posted Tue 12 Jan 21 @ 5:31 am
Adion wrote :
Could you try to open VDJ, wait until stems work normally, then change mathEngine to CPU and then restart to see if they work faster that time?
If it would be related to the nVidia it should initialize fast when using CPU.
If not fast, could you check agian in process explorer where it is stuck?


I waited for 15 mins till it finished doing everything and brought up the single coloured waveform/stems buttons started doing something. Changed the Math Engine setting to CPU and VDJ didn't crash like it was doing before. Stems still sound like they did in my video above though.

So I restarted VDJ, and the MathEngine setting has stayed on CPU. Loaded up Killing in the name but it still sounded like the video above, so I tried a different song that didn't already have a pre-computed stem.

SUCCESS! It works like it should. I went back and recomputed the stem for Killing in the name and that also works ok now as well.

Restarted it again after and no slowdown, stems take a bit longer to compute but it's still only 10 seconds or so.

For reference, I ran Process explorer while I was waiting the 15 mins for it to start, and there was 1 process (virtualdj.exe+0x26caef8) that was using nearly 5% of my CPU. Digging into it further and double clicking on the line that was using all the CPU in the properties window showed it was using this below:

0x0000000000000000
nvptxJitCompiler64.dll!nvLinkerGetLinkedCubinSize+0x48cb63
nvptxJitCompiler64.dll!nvLinkerGetLinkedCubinSize+0x48c2c5
nvptxJitCompiler64.dll!nvLinkerGetLinkedCubinSize+0x48b81e
nvptxJitCompiler64.dll!nvLinkerGetLinkedCubinSize+0x48aee1
nvptxJitCompiler64.dll!_cuda_CallJitEntryPoint+0xcff0
nvptxJitCompiler64.dll!_cuda_CallJitEntryPoint+0x49186
nvptxJitCompiler64.dll!_cuda_CallJitEntryPoint+0x529f8
nvptxJitCompiler64.dll!_cuda_CallJitEntryPoint+0x47db6
nvptxJitCompiler64.dll!_cuda_CallJitEntryPoint+0x4790f
nvptxJitCompiler64.dll!_cuda_CallJitEntryPoint+0x567ed
nvptxJitCompiler64.dll!_cuda_CallJitEntryPoint+0x5260b
nvptxJitCompiler64.dll!_cuda_CallJitEntryPoint+0x45cbd
nvptxJitCompiler64.dll!_cuda_CallJitEntryPoint+0x42a80
nvptxJitCompiler64.dll!_cuda_CallJitEntryPoint+0x50726
nvptxJitCompiler64.dll!_cuda_CallJitEntryPoint+0x56c0f
nvptxJitCompiler64.dll!nvLinkerGetLinkedCubinSize+0x474f4c
nvptxJitCompiler64.dll!_cuda_CallJitEntryPoint+0x5716a
nvptxJitCompiler64.dll!_cuda_CallJitEntryPoint+0x56e7a
nvptxJitCompiler64.dll!nvLinkerGetLinkedCubinSize+0x474f4c
nvptxJitCompiler64.dll!_cuda_CallJitEntryPoint+0x57b69
nvptxJitCompiler64.dll!_cuda_CallJitEntryPoint+0x5900
nvptxJitCompiler64.dll!_cuda_CallJitEntryPoint+0x236f
nvptxJitCompiler64.dll!_cuda_CallJitEntryPoint+0x45f5
nvptxJitCompiler64.dll!_cuda_CallJitEntryPoint+0xcd19
nvptxJitCompiler64.dll!_cuda_CallJitEntryPoint+0xec
nvcuda64.dll!cuProfilerStop+0x22aecb
nvcuda64.dll!cuProfilerStop+0x22b17b
nvcuda64.dll+0x1881ed
nvcuda64.dll+0x188b93
nvcuda64.dll+0x16ddf1
nvcuda64.dll+0x9a33f
nvcuda64.dll+0x9a78b
nvcuda64.dll+0x9b2fc
cuf101.dll!cufftXtMakePlanGuru64+0x267593
cuf101.dll!cufftXtMakePlanGuru64+0x26e679
cuf101.dll!cufftXtMakePlanGuru64+0x2667cb
cuf101.dll!cufftXtMakePlanGuru64+0x268eb9
cuf101.dll!cufftXtMakePlanGuru64+0x268ad1
cuf101.dll!cufftXtMakePlanGuru64+0x26ee03
cuf101.dll!cufftXtMakePlanGuru64+0x26281b
cuf101.dll!cufftXtMakePlanGuru64+0x2645e9
cuf101.dll+0x5c7e
cuf101.dll+0x7525
cuf101.dll+0x6a1d
cuf101.dll!cufftXtMakePlanMany+0x2c0
cuf101.dll!cufftMakePlanMany64+0xb8
cuf101.dll!cufftMakePlanMany+0x1af
cuf101.dll!cufftMakePlan1d+0x62
virtualdj.exe+0x95afab
virtualdj.exe+0x96650a
virtualdj.exe+0x9626e7
virtualdj.exe+0x6670f9
virtualdj.exe+0x26caf48
KERNEL32.DLL!BaseThreadInitThunk+0x14
ntdll.dll!RtlUserThreadStart+0x21


So it's definitely a CUDA issue with nvidia 30xx series cards by the looks of it. Hope this helps, and if you need me to do any other troubleshooting/provide you with any more info let me know!




 

Posted Tue 12 Jan 21 @ 6:34 pm
 

Posted Tue 12 Jan 21 @ 7:51 pm
AdionPRO InfinityCTOMember since 2006
Unfortunately your previous video doesn't contain audio so can't compare the sound
 

Posted Tue 12 Jan 21 @ 7:57 pm
Huh, I have no idea why that doesn't have sound!

Either way it's working with CPU as the MathEngine now rather than GPU.

Unless you specifically want a video of it not working? I can reupload it if you need me to.
 

Posted Tue 12 Jan 21 @ 8:18 pm
AdionPRO InfinityCTOMember since 2006
Might be useful to hear the difference in stems yes.
 

Posted Wed 13 Jan 21 @ 7:13 am
I recorded another video with sound this time, demonstrating that stems do nothing when VDJ has just loaded and is using loads of CPU, stems not working using GPU as the MathEngine, and stems working fine using CPU as the MathEngine.

For reference, my hardware is:

AMD Ryzen 5900x
ASUS Strix X570-F Mobo
ASUS RTX 3080 TUF OC GPU
32gb corsair vengance ram 1600mhz

Video link: https://1drv.ms/v/s!AirDBud1EdbfsPh6wBeb4KxzTcU9dw

Timeline:

00:00 - Loading VDJ, showing MathEngine set to GPU
00:12 - Demonstrating stems buttons doing nothing (the first few bars sound weird in the video but they sounded normal on my system. Probably just the video compression). Waveform is coloured at this point which I guess indicates that stems haven't been created. EQ still works as normal.
00:36 - starting timer in top right hand corner
00:40 - showing that VDJ is using about 6% of my cpu
00:48 - Sped up footage of me waiting for VDJ to finish doing whatever it's doing
01:26 - VDJ loads the stems in, waveform changes from coloured to all blue. CPU usage goes down to about 0.5%
01:47 - Demonstrating stems not working properly with MathEngine set to GPU
02:41 - load a different track into Deck 1
02:44 - Change MathEngine setting from GPU to CPU
02:51 - Reload Killing in the name into Deck 1. Stem is calculated again by VDJ
03:01 - Demonstrating Stems working fine with MathEngine set to CPU


If you need any more info/videos please let me know!
 

Posted Wed 13 Jan 21 @ 1:54 pm