Anmelden:     

Forum: VirtualDJ Technical Support

Topic: A couple of bugs spotted in b8645
I have a dual GPU Windows laptop - ASUS Rog Strix G15 with low power/high power CPUs (AMD Radeon on-chip and Nvidia GTX 3050 Ti) - But having just upgraded VirtualDJ I've just spotted that it's using the CPU to calculate STEMS, no matter what the settings are.

Any ideas?

Second bug is this one; https://virtualdj.com/forums/247185/VirtualDJ_Technical_Support/%3Cspan%20style=
Which was reported 5 months ago - I've now tried across 3 different PCs/laptops and they all demonstrate the same behaviour.

I'm losing faith in VirtualDJ with really basic out-of-the-box functions not working; I'm a developer myself and I'm actually shocked how many basic bugs are making it through QA.
 
geposted 3 days ago @ 9:43 pm
How much memory does your 3050 Ti have?
Unfortunately many come with only 4GB, which is on the limit of what might work, depending on driver and other software running, so we recommend 6GB or more for the 3000 and higher series.
https://virtualdj.com/wiki/Minimum-system-requirements.html

You can try again to turn off 'Don't use GPU' in the stemsfix options, and you could try manually switching stemsGPU between the nvidia and the integrated amd to see which one gives you best results
 
You're correct, it is only 4GB, but I have had STEMS 2.0 working on this laptop before, not unless the model is now too big to fit into 4GB.

So I had a quick play, and it appears you're right, I ran STEMS on the internal AMD card, and it processed them successfully. Let me try freeing up some VRAM on my Nvidia card and will try again.

Side note: Does VirtualDJ have a console log anywhere? Like when it's not able to allocate enough VRAM?
 
Thanks Adion - You were completely correct, freeing up VRAM on my Nvidia card has fixed my problem; I'll have to watch what I allocate to that card in future. Great advice, thankyou!

I think I'll need to launch a formal ticket about the track jumps using sandbox mode, it's odd, but I've seen it across 3 machines now.
 
If you have some step by step to reproduce along with your audio setup and controller used that could be helpful too to find the problem
 
 
What is the samplerate of the tracks you play, and what is the samplerate of your audio output?
 
I try and keep everything to 96khz at 24bit - Source, output, engine all set to this.
 
Ok, looks like the bug was indeed related to using songs in a samplerate different from 44100Hz.
I was able to reproduce, so will be fixed in the next update
 
That is fantastic news! That'll make my life so much easier. Thanks for investigating and fixing!