Wondering if anyone pays attention to VRAM usage in task manager while running VDJ and STEMS with videos.
Here's my scenario:
Windows 11, all updates
nVidia 4060ti dedicated GPU with 8gb VRAM
Intel ARC Graphics internal GPU with 128mb VRAM, 18gb shared/integrated
i9 cpu
32gb RAM
VDJ settings:
Video FPS: 60
Skin FPS:120
SkinUseLowPowerGPU: Default
StemsRealTimeSeparation: On-Demand
Layout: Pro
Windows Settings:
GPU Preference: High Performance
Optimizations For Windows Games: On
Currently using WASAPI drivers for audio output
As observed through the Performance tab of Task Manager
GPU0 is the nVidia GPU
GPU1 is the Intel GPU
Before I start VDJ, nVidia GPU0 Dedicated GPU Memory is 0gb
After I start VDJ, nVidia GPU0 Dedicated GPU Memory is 1.8gb
After I turn on the video output to a 1080p display at 60hz refresh rate, nVidia GPU0 Dedicated GPU Memory is 1.8gb
After I load a 1080p video onto a deck, nVidia GPU0 Dedicated GPU Memory ramps to 2.6gb
After I start playing the video, nVidia GPU0 Dedicated GPU Memory slowly ramps up from 2.6 to about 5.3.
GPU Utilization is about 30%
If I click 'save prepared stems on playing video, nVidia GPU0 Dedicated GPU Memory ramps to about 7gb and stays there regardless of what videos I play going forward or regardless of preparing more stems.
When I unload the video from the deck, nVidia GPU0 Dedicated GPU Memory drops to about 4.8gb.
When I turn off video, nVidia GPU0 Dedicated GPU Memory stays at 4.8gb.
Is this normal? It seems like VDJ should be releasing some of the VRAM. It doesn't release any of it until and unless I shut down VDJ.
Another issue I've been having lately is, after awhile, the video skin starts to lag, (Jog wheels, scratch indication and beat grid LL lag) making it difficult to use visuals to mix. The controller buttons trigger the audio instantaneously, and the audio is ok, but the skin lags a half second behind. It almost seems like it has something to do with most of the dedicated VRAM being used, but I don't know if the VRAM usage I've described above is normal.
I've tried using the intel video card (low power card) for the skin but I ran into other problems doing that.
Anyone have any insight on this?
Here's my scenario:
Windows 11, all updates
nVidia 4060ti dedicated GPU with 8gb VRAM
Intel ARC Graphics internal GPU with 128mb VRAM, 18gb shared/integrated
i9 cpu
32gb RAM
VDJ settings:
Video FPS: 60
Skin FPS:120
SkinUseLowPowerGPU: Default
StemsRealTimeSeparation: On-Demand
Layout: Pro
Windows Settings:
GPU Preference: High Performance
Optimizations For Windows Games: On
Currently using WASAPI drivers for audio output
As observed through the Performance tab of Task Manager
GPU0 is the nVidia GPU
GPU1 is the Intel GPU
Before I start VDJ, nVidia GPU0 Dedicated GPU Memory is 0gb
After I start VDJ, nVidia GPU0 Dedicated GPU Memory is 1.8gb
After I turn on the video output to a 1080p display at 60hz refresh rate, nVidia GPU0 Dedicated GPU Memory is 1.8gb
After I load a 1080p video onto a deck, nVidia GPU0 Dedicated GPU Memory ramps to 2.6gb
After I start playing the video, nVidia GPU0 Dedicated GPU Memory slowly ramps up from 2.6 to about 5.3.
GPU Utilization is about 30%
If I click 'save prepared stems on playing video, nVidia GPU0 Dedicated GPU Memory ramps to about 7gb and stays there regardless of what videos I play going forward or regardless of preparing more stems.
When I unload the video from the deck, nVidia GPU0 Dedicated GPU Memory drops to about 4.8gb.
When I turn off video, nVidia GPU0 Dedicated GPU Memory stays at 4.8gb.
Is this normal? It seems like VDJ should be releasing some of the VRAM. It doesn't release any of it until and unless I shut down VDJ.
Another issue I've been having lately is, after awhile, the video skin starts to lag, (Jog wheels, scratch indication and beat grid LL lag) making it difficult to use visuals to mix. The controller buttons trigger the audio instantaneously, and the audio is ok, but the skin lags a half second behind. It almost seems like it has something to do with most of the dedicated VRAM being used, but I don't know if the VRAM usage I've described above is normal.
I've tried using the intel video card (low power card) for the skin but I ran into other problems doing that.
Anyone have any insight on this?
geposted 17 hours ago
Use the inbuilt ARC graphics for skin and video out then keep the RTX for stems only. What problem did you encounter doing that? Why do you need the skin FPS so high?
geposted 17 hours ago
kradcliffe wrote :
Use the inbuilt ARC graphics for skin and video out then keep the RTX for stems only. What problem did you encounter doing that? Why do you need the skin FPS so high?
The skin FPS at 120 is silky smooth. At 60, there is noticeable choppiness.
I've tried doing what you said. For some reason, when using the Intel ARC, some video transitions get hung up and I end up having to turn video off and back on.
geposted 17 hours ago
Maybe check the Intel control panel to see if any power saving features are on as they tend to be by default.
geposted 17 hours ago
OK. In the Intel graphics command panel, I disabled variable refresh rate, moved the power efficiency slider to 1 (it was at 2). This should make it less power efficient and make for better graphics.
I reduced the skin fps back to 60. It's smooth unless I open task manager, so that's ok.
Before VDJ starts, nVidia GPU memory is at 0, but increased to 1.7gp upon start.
The Intel GPU VRAM is at 0.8 after VDJ starts and pretty much stays there no matter what I do with videos or stems.
When I create a stems file, nVidia GPU ramps up to 4.7gb and just stays there, even after it's done creating the stems file. That concerns me. I'm not convinced that's normal.
I reduced the skin fps back to 60. It's smooth unless I open task manager, so that's ok.
Before VDJ starts, nVidia GPU memory is at 0, but increased to 1.7gp upon start.
The Intel GPU VRAM is at 0.8 after VDJ starts and pretty much stays there no matter what I do with videos or stems.
When I create a stems file, nVidia GPU ramps up to 4.7gb and just stays there, even after it's done creating the stems file. That concerns me. I'm not convinced that's normal.
geposted 16 hours ago
What is your stemsMode set to?
geposted 16 hours ago
I just tested here with mobile RTX4080. I have stems set to fully disabled as I precompute them when required for export to my low powered DJ machine.
Created stems for 4 files, and memory used as per shot below. It was zero before I started calculating the stems. When it finished calculating the memory did not go back to zero and was locked. Only when I closed down VDJ did it clear back to zero. You can see that the utilization on the card was zero but the memory was still being used with no stems being processed.
Created stems for 4 files, and memory used as per shot below. It was zero before I started calculating the stems. When it finished calculating the memory did not go back to zero and was locked. Only when I closed down VDJ did it clear back to zero. You can see that the utilization on the card was zero but the memory was still being used with no stems being processed.
geposted 16 hours ago
Adion wrote :
What is your stemsMode set to?
On demand. I don't think STEMS is the issue. Kradcliffe just confirmed below that his machine is doing the same thing as mine.
geposted 15 hours ago
kradcliffe wrote :
I just tested here with mobile RTX4080. I have stems set to fully disabled as I precompute them when required for export to my low powered DJ machine.
Created stems for 4 files, and memory used as per shot below. It was zero before I started calculating the stems. When it finished calculating the memory did not go back to zero and was locked. Only when I closed down VDJ did it clear back to zero. You can see that the utilization on the card was zero but the memory was still being used with no stems being processed.

Created stems for 4 files, and memory used as per shot below. It was zero before I started calculating the stems. When it finished calculating the memory did not go back to zero and was locked. Only when I closed down VDJ did it clear back to zero. You can see that the utilization on the card was zero but the memory was still being used with no stems being processed.

OK, interesting. Thanks for doing this. I wonder why it locks up the memory after computing stems. Wonder if it's a Windows reporting error or if VDJ is actually hanging on to that memory after it computes stems.
So now I just have to figure out why the skin sometimes lags. This just started. It may have something to do with having the skin set to high power but I won't know until tomorrow when I am using it at an event.
geposted 14 hours ago





