Adion
I'm not sure what the Virtual Memory in the FPS plugin indicates exactly, so can't comment much on that.
VDJ uses video memory to buffer previous video frames. While this is not really necessary when just playing videos, it can help give a better video response when scratching or looping.
The amount of memory vdj will use depends on the amount of video memory detected (which is what the videoMaxMemory setting on automatic shows. The detection is limited to 3GB, which is why it showed 3064 even though you have 8GB of dedicated video memory).
While I'm not exactly sure why, what I think happened is that there is some bug in the nVidia drivers (perhaps a combination of driver version, video card and DirectX 9 application) that causes the driver to use system memory instead of video memory to store the frames. (Possibly temporarily while it uploads the frames to the video memory)
VirtualDJ on windows is compiled as a 32-bit application however, so it can't use more than 4GB of memory. So if the nVidia driver causes an additional 3GB of memory use, that can make it tight for vdj to work with causing the streaming warnings or eventually complete crashes when it runs out of memory.
I will make some additional checks to limit the amount of memory vdj uses automatically so that it should not cause any problems any more for these cards, but in the meantime it's safe to manually lower the videoMaxMemory to a lower value.
(Now that you know 100 works you could try to slowly increase it again in case you are in need of video scratching)
VDJ uses video memory to buffer previous video frames. While this is not really necessary when just playing videos, it can help give a better video response when scratching or looping.
The amount of memory vdj will use depends on the amount of video memory detected (which is what the videoMaxMemory setting on automatic shows. The detection is limited to 3GB, which is why it showed 3064 even though you have 8GB of dedicated video memory).
While I'm not exactly sure why, what I think happened is that there is some bug in the nVidia drivers (perhaps a combination of driver version, video card and DirectX 9 application) that causes the driver to use system memory instead of video memory to store the frames. (Possibly temporarily while it uploads the frames to the video memory)
VirtualDJ on windows is compiled as a 32-bit application however, so it can't use more than 4GB of memory. So if the nVidia driver causes an additional 3GB of memory use, that can make it tight for vdj to work with causing the streaming warnings or eventually complete crashes when it runs out of memory.
I will make some additional checks to limit the amount of memory vdj uses automatically so that it should not cause any problems any more for these cards, but in the meantime it's safe to manually lower the videoMaxMemory to a lower value.
(Now that you know 100 works you could try to slowly increase it again in case you are in need of video scratching)
Mensajes Wed 15 Mar 17 @ 4:50 pm
The Hofff 
Thanks for the infollowing Adion, appreciate it!
Mensajes Wed 15 Mar 17 @ 5:47 pm