djcel
By doing so, don't you have some freeze (waveform lag for example) with the skin when it computes stems?
发表时间 Thu 02 Mar 23 @ 11:40 am
martyghen
djcel wrote :
By doing so, don't you have some freeze (waveform lag for example) with the skin when it computes stems?
Haven't noticed any yet. But I do agree, it would be nice to have the skin rendering on the integrated graphics and stems computed on the GPU, but it seems the stems compute on the GPU leaves enough headroom for the skin rendering anyway (which I assume is intentional).
发表时间 Thu 02 Mar 23 @ 12:00 pm
martyghen
Adion wrote :
Which cpu do you have?
12th Gen Intel(R) Core(TM) i7-12700H (20 CPUs), ~2.7GHz
Adion wrote :
And which amount of memory does it show for the iris in task manager?
Not sure about in task manager but in my original post on page 1 there's a full dx readout, which says 128MB dedicated / 8 GB shared. I've never changed it since owning the laptop so whatever it is, is a default setting.
发表时间 Thu 02 Mar 23 @ 12:08 pm
bazzio68
Last evening i saw something strange happening in VDJ (7474). I was changing the SkinUseLowPowerGPU settings to Low Power (like recommended here) to see if it would make a difference in stems computing speed. Alse changed the realtime preparation to Always.
When loading a track it first looked liked VDJ froze when computing the stems but seconds later it loaded the stems in 10-15 seconds for a 5 minte song. Tried several tracks and all loaded that quick. So i deceided to restart VDJ and ever since its all slow again (4 minutes for a 5 minute track).
Normally VDJ uses only 2,9G of my 4G VRAM, but last night it used 3,9g. I accidentally had PS also open wich uses GPU memory also but after closing it, it looked like all the reserved VRAM stayed active for VDJ.
Tried to replicate it this morning but still no luck :(
But promising thing is that it seems that VDJ stems 2.0 can work quick in Always mode with my system (RTX3050ti 4GB VRAM and AMD Ryzen 7 6800H and 16Gig RAM).
When loading a track it first looked liked VDJ froze when computing the stems but seconds later it loaded the stems in 10-15 seconds for a 5 minte song. Tried several tracks and all loaded that quick. So i deceided to restart VDJ and ever since its all slow again (4 minutes for a 5 minute track).
Normally VDJ uses only 2,9G of my 4G VRAM, but last night it used 3,9g. I accidentally had PS also open wich uses GPU memory also but after closing it, it looked like all the reserved VRAM stayed active for VDJ.
Tried to replicate it this morning but still no luck :(
But promising thing is that it seems that VDJ stems 2.0 can work quick in Always mode with my system (RTX3050ti 4GB VRAM and AMD Ryzen 7 6800H and 16Gig RAM).
发表时间 Thu 02 Mar 23 @ 12:38 pm
bazzio68
Hmmmz, strange... tested some more and after initially being slow, i noticed that after letting VDJ open with 2 tracks loaded but rest for a while and after some surfing via chrome (already open and which also uses the GPU), that lading tracks became faster. Not as fast as last night but ok, 35 seconds for a 5 minute track.
After i changed to another Chrome tab it became slow again, but after changing to another page wich used more VRAM it became quicker again (35s).
After that it didn't matter if i closed Chrome, computing still 35 seconds and VRAM around 3G...
So closed VDJ...and after opening again computing very slow, changed some pages (with video) in Chrome doesn't matter... Reopened Chrome and some page changing still the same slow speed... Then let deck A and B fully load (slow) and play both tracks and voila the third track loading on deck B again computed in 20 seconds (btw Chrome still open). But then again after stopping the tracks it loaded slow again to go fast again after some more page changing in Chrome and loading tracks...
I know it's sounding abacadabra... but maybe the programmers can do something with the ifo.
So i guess it's still something to do with the amount of VRAM VDJ is using... but convinced that VDJ can work fast enough with loading stems 2.0 in realtime on a RTX3050 with 4 GB VRAM.
*Edit: Tried to recreate same situation with Closing VDJ, then Chrome and reoping only VDJ... Slow results, reopening Chrome and changing pages... still slow... Been busy for an hour now and still no results... i give up for now, sigh....
After i changed to another Chrome tab it became slow again, but after changing to another page wich used more VRAM it became quicker again (35s).
After that it didn't matter if i closed Chrome, computing still 35 seconds and VRAM around 3G...
So closed VDJ...and after opening again computing very slow, changed some pages (with video) in Chrome doesn't matter... Reopened Chrome and some page changing still the same slow speed... Then let deck A and B fully load (slow) and play both tracks and voila the third track loading on deck B again computed in 20 seconds (btw Chrome still open). But then again after stopping the tracks it loaded slow again to go fast again after some more page changing in Chrome and loading tracks...
I know it's sounding abacadabra... but maybe the programmers can do something with the ifo.
So i guess it's still something to do with the amount of VRAM VDJ is using... but convinced that VDJ can work fast enough with loading stems 2.0 in realtime on a RTX3050 with 4 GB VRAM.
*Edit: Tried to recreate same situation with Closing VDJ, then Chrome and reoping only VDJ... Slow results, reopening Chrome and changing pages... still slow... Been busy for an hour now and still no results... i give up for now, sigh....
发表时间 Thu 02 Mar 23 @ 3:28 pm
IIDEEJAYII
While you are testing... It would be interesting to know if after a fresh system reboot, check VRAM use to get base level.
Then to open and close chrome to see if the VRAM is back to the initial low level.
(that maybe just closing chrome does NOT free up all the VRAM, and be available to VDJ.)
Can do the same type of test with VDJ, also.
seems that VDJ requires "x" amount of VRAM available (depending on the vid driver & maybe GPU) to not switch over to the CPU, when calculating the 2.0 stems.
And if other apps are using portions of VRAM, one still needs, I am guessing, 4GB -6GB of available VRAM for VDJ to calculate 2.0 stems.
In my case I have 11GB of VRAM and if I allow other apps to use too much VRAM, (7.5-8+GB), VDJ will switch to the CPU. And have found the only way to get the VRAM use down, at times, is to reboot and not allow those other GPU intensive apps to run or at least have them tamed a bit, when they run/start.
IE always allowing VDJ to have the necessary VRAM it requires to compute the 2.0 stems.
win 10
7474
Then to open and close chrome to see if the VRAM is back to the initial low level.
(that maybe just closing chrome does NOT free up all the VRAM, and be available to VDJ.)
Can do the same type of test with VDJ, also.
seems that VDJ requires "x" amount of VRAM available (depending on the vid driver & maybe GPU) to not switch over to the CPU, when calculating the 2.0 stems.
And if other apps are using portions of VRAM, one still needs, I am guessing, 4GB -6GB of available VRAM for VDJ to calculate 2.0 stems.
In my case I have 11GB of VRAM and if I allow other apps to use too much VRAM, (7.5-8+GB), VDJ will switch to the CPU. And have found the only way to get the VRAM use down, at times, is to reboot and not allow those other GPU intensive apps to run or at least have them tamed a bit, when they run/start.
IE always allowing VDJ to have the necessary VRAM it requires to compute the 2.0 stems.
win 10
7474
发表时间 Thu 02 Mar 23 @ 8:55 pm
bazzio68
I understand what you mean...but VDJ is not using all the available VRAM there is. With only VDJ open it uses 2,3 GB dedicated memory, so 1,7 GB is not used by VDJ.
VDJ is set to only use GPU and it does so (sometimes need to answer no to the low system question).
stemsRealTimeSeperation is set to Always and skinUseLowPower is set to default
VRAM is low without VDJ (or any other programmes) and only Chrome open, now it's using 0,5GB dedicated, 0,6 of 11,6 GB GPU memory and 0,0 of 7,7 GB shared memory.
When i start VDJ, it's 1,5/4GB - 2,0/11,6GB and 0,5/7,6GB.
When loading a track it's 3,5/4GB - 5,1/11,6GB and 1,7/7,6GB
Tested after restart and killing all programs i could, no surprise...still slow.
But i think i finally found the tricker now for VDJ...
Tested it twice now and VDJ is only becoming fast with computing stems if i stretch out the VRAM first by also opening Chrome with a 4k movie and a video editing program (dedicated memory is going to 3,9/4GB) and then close both programs while computing a track. Now it's becoming fast again, with about 10 seconds for a 3,5 minute track...
*Edit: tested with restarting Chrome again and VDJ became slow again, after letting the video program take some VRAM and closing it while computing a track, it's fast again (with Chrome still open...)
Some data: 3,8/4GB - 4,7/11,6GB and 0,9/7,6GB after closing Chrome and video editor (stems fast)
3,4/4GB - 5,2/11,6GB and 1,7/7,6GB after video editor closed and Chrome open (stems fast)
Hopefully the VDJ programmers can find a fix with this info!
VDJ is set to only use GPU and it does so (sometimes need to answer no to the low system question).
stemsRealTimeSeperation is set to Always and skinUseLowPower is set to default
VRAM is low without VDJ (or any other programmes) and only Chrome open, now it's using 0,5GB dedicated, 0,6 of 11,6 GB GPU memory and 0,0 of 7,7 GB shared memory.
When i start VDJ, it's 1,5/4GB - 2,0/11,6GB and 0,5/7,6GB.
When loading a track it's 3,5/4GB - 5,1/11,6GB and 1,7/7,6GB
Tested after restart and killing all programs i could, no surprise...still slow.
But i think i finally found the tricker now for VDJ...
Tested it twice now and VDJ is only becoming fast with computing stems if i stretch out the VRAM first by also opening Chrome with a 4k movie and a video editing program (dedicated memory is going to 3,9/4GB) and then close both programs while computing a track. Now it's becoming fast again, with about 10 seconds for a 3,5 minute track...
*Edit: tested with restarting Chrome again and VDJ became slow again, after letting the video program take some VRAM and closing it while computing a track, it's fast again (with Chrome still open...)
Some data: 3,8/4GB - 4,7/11,6GB and 0,9/7,6GB after closing Chrome and video editor (stems fast)
3,4/4GB - 5,2/11,6GB and 1,7/7,6GB after video editor closed and Chrome open (stems fast)
Hopefully the VDJ programmers can find a fix with this info!
发表时间 Thu 02 Mar 23 @ 11:34 pm
Adion
Can you try early access build 7481,enable the createMidiLog option and restart virtualdj.
Then check the VirtualDJ folder for a file called Log Report.txt and report which gpu it detected and how much memory it has.
You can also manually change the GPU now by using the stemsGPU option.
By default the first one in the list would be used, so this should be the RTX already.
Then check the VirtualDJ folder for a file called Log Report.txt and report which gpu it detected and how much memory it has.
You can also manually change the GPU now by using the stemsGPU option.
By default the first one in the list would be used, so this should be the RTX already.
发表时间 Sun 05 Mar 23 @ 6:02 am
Sepatro
Adion wrote :
Can you try early access build 7481,enable the createMidiLog option and restart virtualdj.
Then check the VirtualDJ folder for a file called Log Report.txt and report which gpu it detected and how much memory it has.
You can also manually change the GPU now by using the stemsGPU option.
By default the first one in the list would be used, so this should be the RTX already.
Then check the VirtualDJ folder for a file called Log Report.txt and report which gpu it detected and how much memory it has.
You can also manually change the GPU now by using the stemsGPU option.
By default the first one in the list would be used, so this should be the RTX already.
Hello, where is this Log Report located? I tried the early acces build but still extremely sluggish and unworkable...
发表时间 Sun 05 Mar 23 @ 10:32 am
Adion
You can open Options and press the Cog on the right-bottom to open your VirtualDJ folder
发表时间 Sun 05 Mar 23 @ 12:38 pm
bazzio68
Adion wrote :
Can you try early access build 7481,enable the createMidiLog option and restart virtualdj.
Then check the VirtualDJ folder for a file called Log Report.txt and report which gpu it detected and how much memory it has.
You can also manually change the GPU now by using the stemsGPU option.
By default the first one in the list would be used, so this should be the RTX already.
Then check the VirtualDJ folder for a file called Log Report.txt and report which gpu it detected and how much memory it has.
You can also manually change the GPU now by using the stemsGPU option.
By default the first one in the list would be used, so this should be the RTX already.
Thanks, here the requsted info:
[15:04:42] GPU NVIDIA GeForce RTX 3050 Ti Laptop GPU - 4169138176
[15:04:42] GPU AMD Radeon(TM) Graphics - 509374464
Btw, selected the Nividia manual in options but still slow... 5,3 minute track in 4 minutes.
but strange thing... if i select the AMD Radeon with low memory (512MB dedicatid) the same track loads in 57 seconds??
*Edit: With the same trick (Stretch VRAM by opening program and close again), same track loads in 25-30 seconds... (Nvidia selected in options).
发表时间 Sun 05 Mar 23 @ 2:07 pm
Adion
That is interesting indeed, what cpu is the AMD?
发表时间 Sun 05 Mar 23 @ 2:39 pm
bazzio68
Adion wrote :
That is interesting indeed, what cpu is the AMD?
CPU is AMD Ryzen 7 6800H
GPU is AMD Radeon(TM) Graphics
发表时间 Sun 05 Mar 23 @ 2:44 pm
bazzio68
Tried some more...
After deinstall of Nvidia driver to try an older driver, i started VDJ and selected the now generic video (because no Nvidia driver installed) in options, computing stems was fast enough, About 25-30 seconds.
Tried installing a few older Nvidea drivers but the computing became and stayed slow again (100% GPU use).
Switching to the AMD Radeon in the options, the computing becomes fast again but strange thing is that if i look at the performance monitor, the Radeon GPU uses only 4% with only 512MB dedicated memory.
The Nvidia GPU use is also low (about 14%) with low dedicated memory (but is only usesd for skin?)
btw, Skin is on high power option.
After deinstall of Nvidia driver to try an older driver, i started VDJ and selected the now generic video (because no Nvidia driver installed) in options, computing stems was fast enough, About 25-30 seconds.
Tried installing a few older Nvidea drivers but the computing became and stayed slow again (100% GPU use).
Switching to the AMD Radeon in the options, the computing becomes fast again but strange thing is that if i look at the performance monitor, the Radeon GPU uses only 4% with only 512MB dedicated memory.
The Nvidia GPU use is also low (about 14%) with low dedicated memory (but is only usesd for skin?)
btw, Skin is on high power option.
发表时间 Tue 07 Mar 23 @ 11:20 pm
djcel
user18822178 wrote :
but strange thing is that if i look at the performance monitor, the Radeon GPU uses only 4% with only 512MB dedicated memory.
Maybe it swiched to CPU to compute stems.
You can also check with "GPU-Z" software -> Sensors. It also gives some indicators on the use of GPU.
In the VirtualDJ settings file, you can also activate the log file for stems
<stemsFixExtra>log</stemsFixExtra>It can give some useful data but I advise you to disable it after your tests.
发表时间 Wed 08 Mar 23 @ 7:07 am
bazzio68
Thanks, i'll try that.
CPU usage is also very low while computing stems on the AMD Radeon.
*Edit: Where do i need to put that line of code in the settings file, pasted it before the </settings> but don't see any difference in the Log Report file?
CPU usage is also very low while computing stems on the AMD Radeon.
*Edit: Where do i need to put that line of code in the settings file, pasted it before the </settings> but don't see any difference in the Log Report file?
发表时间 Wed 08 Mar 23 @ 10:49 am
kradcliffe
I have it in the performance section and it works there
发表时间 Wed 08 Mar 23 @ 11:30 am
bazzio68
Thanks!
发表时间 Wed 08 Mar 23 @ 11:34 am
bazzio68
Ok here we go:
This is the log with stems using the Nvidia (slow):
--- 2023/03/08 - 12:46 (7482)
[12:46:23] WASAPI device without vid/pid: AI Noise-cancelling Output (ASUS Utility) : {2}.\\?\root#media#0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\wave
[12:46:23] WASAPI device without vid/pid: AI Noise-cancelling Input (ASUS Utility) : {2}.\\?\root#media#0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\wave
[12:46:23] Audio device found: name="2- DDJ-FLX6" vid="0x2B73" pid="0x0038" hardwareID:"{0.0.0.00000000}.{5b0f46a9-7929-4084-afaf-fa723eeb46b6}"
[12:46:23] Audio device found: name="C-Media(R) Audio" vid="0x0B05" pid="0x6210" hardwareID:"{0.0.0.00000000}.{c137b8dd-f3d8-497c-bf66-2f2177b2d37b}"
[12:46:23] Audio device found: name="ASUS Utility" hardwareID:"{0.0.0.00000000}.{eca08ee3-e4a6-4c38-b777-30a5f9e3dec1}"
[12:46:23] Audio device found: input name="ASUS Utility" hardwareID:"{0.0.1.00000000}.{2d40c36f-7a2d-45db-9919-244aa7a085da}"
[12:46:23] Audio device found: input name="C-Media(R) Audio" vid="0x0B05" pid="0x6210" hardwareID:"{0.0.1.00000000}.{6ea70d98-3975-40e3-819d-a0e610533655}"
[12:46:23] GPU NVIDIA GeForce RTX 3050 Ti Laptop GPU - 4169138176
[12:46:23] GPU AMD Radeon(TM) Graphics - 2119987200
[12:46:23] Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
[12:46:23] MIDI Device Identifying: \\?\usb#vid_2b73&pid_0038&mi_02#7&33d7cb14&0&0002#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global (in:0 out:1) (name: DDJ-FLX6)
[12:46:23] MIDI Device Identified by PID/VID: \\?\usb#vid_2b73&pid_0038&mi_02#7&33d7cb14&0&0002#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global : Pioneer DDJ-FLX6
[12:46:23] Assigned Keyboard, type:0, index:1
[12:46:23] Assigned Pioneer DDJ-FLX6, type:0, index:1
[12:46:23] MIDI Device Identifying: Microsoft GS Wavetable Synth (in:-1 out:0) (name: Microsoft GS Wavetable Synth)
[12:46:23] MIDI Device Not Identified: Microsoft GS Wavetable Synth
[12:46:23] HID Device found: VID:0x048D PID:0x8051 path:\\?\hid#ite5570#4&23012347&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:46:23] HID Device found: VID:0x2B73 PID:0x0038 path:\\?\hid#vid_2b73&pid_0038&mi_04#8&e7c8cbb&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:46:23] HID Device found: VID:0x093A PID:0x2003 path:\\?\hid#asup1205&col03#4&1daeddd1&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:46:23] HID Device found: VID:0x093A PID:0x2003 path:\\?\hid#asup1205&col04#4&1daeddd1&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:46:23] HID Device found: VID:0x0B05 PID:0x6210 path:\\?\hid#vid_0b05&pid_6210&mi_03#8&3273e4a7&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:46:23] HID Device found: VID:0x3938 PID:0x1031 path:\\?\hid#vid_3938&pid_1031&col02#7&23134972&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:46:23] Assigned Keyboard, type:0, index:1
[12:46:23] Assigned Pioneer DDJ-FLX6, type:0, index:1
[12:46:38] GPU speed: x1.3
[12:46:47] GPU speed: x1.4
[12:46:56] GPU speed: x1.4
[12:47:05] GPU speed: x1.3
[12:47:14] GPU speed: x1.3
[12:47:22] GPU speed: x1.4
[12:47:31] GPU speed: x1.3
[12:47:40] GPU speed: x1.4
[12:47:49] GPU speed: x1.4
[12:47:57] GPU speed: x1.4
[12:48:06] GPU speed: x1.4
[12:48:15] GPU speed: x1.3
[12:48:24] GPU speed: x1.3
[12:48:33] GPU speed: x1.4
[12:48:42] GPU speed: x1.3
[12:48:50] GPU speed: x1.3
[12:48:59] GPU speed: x1.3
[12:49:08] GPU speed: x1.4
[12:49:17] GPU speed: x1.3
[12:49:26] GPU speed: x1.4
[12:49:35] GPU speed: x1.3
[12:49:43] GPU speed: x1.3
[12:49:52] GPU speed: x1.4
[12:50:01] GPU speed: x1.4
[12:50:10] GPU speed: x1.3
[12:50:19] GPU speed: x1.4
[12:50:28] GPU speed: x1.3
[12:50:36] GPU speed: x1.3
[12:50:45] GPU speed: x1.3
[12:57:31] Set not stored because length below 20 minutes
[12:57:31] Midi In Closed (\\?\usb#vid_2b73&pid_0038&mi_02#7&33d7cb14&0&0002#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global)
[12:57:31] Midi Out Closed (\\?\usb#vid_2b73&pid_0038&mi_02#7&33d7cb14&0&0002#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global)
[12:57:32] Performance stats (session duration: 11:00)
[12:57:32] avg peak audio cpu: 1% - low skin fps avg: 22 fps - periods with skin drops (<24fps): 41% - periods with skin drops (<15fps): 32%
[12:57:32] low controller fps avg: 58 fps - periods with controller drops (<10fps): 2%
This is with AMD (fast enough):
--- 2023/03/08 - 12:59 (7482)
[12:59:11] WASAPI device without vid/pid: AI Noise-cancelling Output (ASUS Utility) : {2}.\\?\root#media#0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\wave
[12:59:11] WASAPI device without vid/pid: AI Noise-cancelling Input (ASUS Utility) : {2}.\\?\root#media#0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\wave
[12:59:11] Audio device found: name="2- DDJ-FLX6" vid="0x2B73" pid="0x0038" hardwareID:"{0.0.0.00000000}.{5b0f46a9-7929-4084-afaf-fa723eeb46b6}"
[12:59:11] Audio device found: name="C-Media(R) Audio" vid="0x0B05" pid="0x6210" hardwareID:"{0.0.0.00000000}.{c137b8dd-f3d8-497c-bf66-2f2177b2d37b}"
[12:59:11] Audio device found: name="ASUS Utility" hardwareID:"{0.0.0.00000000}.{eca08ee3-e4a6-4c38-b777-30a5f9e3dec1}"
[12:59:11] Audio device found: input name="ASUS Utility" hardwareID:"{0.0.1.00000000}.{2d40c36f-7a2d-45db-9919-244aa7a085da}"
[12:59:11] Audio device found: input name="C-Media(R) Audio" vid="0x0B05" pid="0x6210" hardwareID:"{0.0.1.00000000}.{6ea70d98-3975-40e3-819d-a0e610533655}"
[12:59:12] GPU NVIDIA GeForce RTX 3050 Ti Laptop GPU - 4169138176
[12:59:12] GPU AMD Radeon(TM) Graphics - 2119987200
[12:59:12] stems GPU engine changed to card 1
[12:59:12] Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
[12:59:12] MIDI Device Identifying: \\?\usb#vid_2b73&pid_0038&mi_02#7&33d7cb14&0&0002#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global (in:0 out:1) (name: DDJ-FLX6)
[12:59:12] MIDI Device Identified by PID/VID: \\?\usb#vid_2b73&pid_0038&mi_02#7&33d7cb14&0&0002#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global : Pioneer DDJ-FLX6
[12:59:12] Assigned Keyboard, type:0, index:1
[12:59:12] Assigned Pioneer DDJ-FLX6, type:0, index:1
[12:59:12] MIDI Device Identifying: Microsoft GS Wavetable Synth (in:-1 out:0) (name: Microsoft GS Wavetable Synth)
[12:59:12] MIDI Device Not Identified: Microsoft GS Wavetable Synth
[12:59:12] HID Device found: VID:0x048D PID:0x8051 path:\\?\hid#ite5570#4&23012347&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:59:12] HID Device found: VID:0x2B73 PID:0x0038 path:\\?\hid#vid_2b73&pid_0038&mi_04#8&e7c8cbb&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:59:12] HID Device found: VID:0x093A PID:0x2003 path:\\?\hid#asup1205&col03#4&1daeddd1&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:59:12] HID Device found: VID:0x093A PID:0x2003 path:\\?\hid#asup1205&col04#4&1daeddd1&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:59:12] HID Device found: VID:0x0B05 PID:0x6210 path:\\?\hid#vid_0b05&pid_6210&mi_03#8&3273e4a7&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:59:12] HID Device found: VID:0x3938 PID:0x1031 path:\\?\hid#vid_3938&pid_1031&col02#7&23134972&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:59:12] Assigned Keyboard, type:0, index:1
[12:59:12] Assigned Pioneer DDJ-FLX6, type:0, index:1
[12:59:20] GPU speed: x6.3
[12:59:22] GPU speed: x5.7
[12:59:24] GPU speed: x5.5
[12:59:27] GPU speed: x5.6
[12:59:29] GPU speed: x5.6
[12:59:31] GPU speed: x6.2
[12:59:33] GPU speed: x5.6
[12:59:35] GPU speed: x5.5
[12:59:37] GPU speed: x5.6
[12:59:39] GPU speed: x5.6
[12:59:41] GPU speed: x6.4
[12:59:43] GPU speed: x5.5
[12:59:45] GPU speed: x5.5
[12:59:48] GPU speed: x5.6
[12:59:50] GPU speed: x5.5
[12:59:52] GPU speed: x5.5
[12:59:54] GPU speed: x5.6
[12:59:56] GPU speed: x6.2
[12:59:58] GPU speed: x5.6
[13:00:00] GPU speed: x5.5
[13:00:02] GPU speed: x5.6
[13:00:04] GPU speed: x5.5
[13:00:06] GPU speed: x6.6
[13:00:08] GPU speed: x5.6
[13:00:11] GPU speed: x5.5
[13:00:13] GPU speed: x5.6
[13:00:15] GPU speed: x5.5
[13:00:17] GPU speed: x5.6
[13:00:19] GPU speed: x5.6
[13:01:45] Set not stored because length below 20 minutes
[13:01:45] Midi In Closed (\\?\usb#vid_2b73&pid_0038&mi_02#7&33d7cb14&0&0002#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global)
[13:01:45] Midi Out Closed (\\?\usb#vid_2b73&pid_0038&mi_02#7&33d7cb14&0&0002#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global)
[13:01:45] Performance stats (session duration: 02:30)
[13:01:45] avg peak audio cpu: 2% - low skin fps avg: 29 fps - periods with skin drops (<24fps): 7% - periods with skin drops (<15fps): 0%
[13:01:45] low controller fps avg: 55 fps - periods with controller drops (<10fps): 7%
And here the GPU-Z results:
Nvidia results with Nvidia selected
AMD results with Nvidia selected
AMD Radeon results with AMD selected (as you can see 100% GPU usage, but WIN11 performance monitor shows 0-4% ??)
Nvidia results with AMD selected
This is the log with stems using the Nvidia (slow):
--- 2023/03/08 - 12:46 (7482)
[12:46:23] WASAPI device without vid/pid: AI Noise-cancelling Output (ASUS Utility) : {2}.\\?\root#media#0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\wave
[12:46:23] WASAPI device without vid/pid: AI Noise-cancelling Input (ASUS Utility) : {2}.\\?\root#media#0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\wave
[12:46:23] Audio device found: name="2- DDJ-FLX6" vid="0x2B73" pid="0x0038" hardwareID:"{0.0.0.00000000}.{5b0f46a9-7929-4084-afaf-fa723eeb46b6}"
[12:46:23] Audio device found: name="C-Media(R) Audio" vid="0x0B05" pid="0x6210" hardwareID:"{0.0.0.00000000}.{c137b8dd-f3d8-497c-bf66-2f2177b2d37b}"
[12:46:23] Audio device found: name="ASUS Utility" hardwareID:"{0.0.0.00000000}.{eca08ee3-e4a6-4c38-b777-30a5f9e3dec1}"
[12:46:23] Audio device found: input name="ASUS Utility" hardwareID:"{0.0.1.00000000}.{2d40c36f-7a2d-45db-9919-244aa7a085da}"
[12:46:23] Audio device found: input name="C-Media(R) Audio" vid="0x0B05" pid="0x6210" hardwareID:"{0.0.1.00000000}.{6ea70d98-3975-40e3-819d-a0e610533655}"
[12:46:23] GPU NVIDIA GeForce RTX 3050 Ti Laptop GPU - 4169138176
[12:46:23] GPU AMD Radeon(TM) Graphics - 2119987200
[12:46:23] Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
[12:46:23] MIDI Device Identifying: \\?\usb#vid_2b73&pid_0038&mi_02#7&33d7cb14&0&0002#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global (in:0 out:1) (name: DDJ-FLX6)
[12:46:23] MIDI Device Identified by PID/VID: \\?\usb#vid_2b73&pid_0038&mi_02#7&33d7cb14&0&0002#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global : Pioneer DDJ-FLX6
[12:46:23] Assigned Keyboard, type:0, index:1
[12:46:23] Assigned Pioneer DDJ-FLX6, type:0, index:1
[12:46:23] MIDI Device Identifying: Microsoft GS Wavetable Synth (in:-1 out:0) (name: Microsoft GS Wavetable Synth)
[12:46:23] MIDI Device Not Identified: Microsoft GS Wavetable Synth
[12:46:23] HID Device found: VID:0x048D PID:0x8051 path:\\?\hid#ite5570#4&23012347&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:46:23] HID Device found: VID:0x2B73 PID:0x0038 path:\\?\hid#vid_2b73&pid_0038&mi_04#8&e7c8cbb&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:46:23] HID Device found: VID:0x093A PID:0x2003 path:\\?\hid#asup1205&col03#4&1daeddd1&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:46:23] HID Device found: VID:0x093A PID:0x2003 path:\\?\hid#asup1205&col04#4&1daeddd1&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:46:23] HID Device found: VID:0x0B05 PID:0x6210 path:\\?\hid#vid_0b05&pid_6210&mi_03#8&3273e4a7&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:46:23] HID Device found: VID:0x3938 PID:0x1031 path:\\?\hid#vid_3938&pid_1031&col02#7&23134972&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:46:23] Assigned Keyboard, type:0, index:1
[12:46:23] Assigned Pioneer DDJ-FLX6, type:0, index:1
[12:46:38] GPU speed: x1.3
[12:46:47] GPU speed: x1.4
[12:46:56] GPU speed: x1.4
[12:47:05] GPU speed: x1.3
[12:47:14] GPU speed: x1.3
[12:47:22] GPU speed: x1.4
[12:47:31] GPU speed: x1.3
[12:47:40] GPU speed: x1.4
[12:47:49] GPU speed: x1.4
[12:47:57] GPU speed: x1.4
[12:48:06] GPU speed: x1.4
[12:48:15] GPU speed: x1.3
[12:48:24] GPU speed: x1.3
[12:48:33] GPU speed: x1.4
[12:48:42] GPU speed: x1.3
[12:48:50] GPU speed: x1.3
[12:48:59] GPU speed: x1.3
[12:49:08] GPU speed: x1.4
[12:49:17] GPU speed: x1.3
[12:49:26] GPU speed: x1.4
[12:49:35] GPU speed: x1.3
[12:49:43] GPU speed: x1.3
[12:49:52] GPU speed: x1.4
[12:50:01] GPU speed: x1.4
[12:50:10] GPU speed: x1.3
[12:50:19] GPU speed: x1.4
[12:50:28] GPU speed: x1.3
[12:50:36] GPU speed: x1.3
[12:50:45] GPU speed: x1.3
[12:57:31] Set not stored because length below 20 minutes
[12:57:31] Midi In Closed (\\?\usb#vid_2b73&pid_0038&mi_02#7&33d7cb14&0&0002#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global)
[12:57:31] Midi Out Closed (\\?\usb#vid_2b73&pid_0038&mi_02#7&33d7cb14&0&0002#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global)
[12:57:32] Performance stats (session duration: 11:00)
[12:57:32] avg peak audio cpu: 1% - low skin fps avg: 22 fps - periods with skin drops (<24fps): 41% - periods with skin drops (<15fps): 32%
[12:57:32] low controller fps avg: 58 fps - periods with controller drops (<10fps): 2%
This is with AMD (fast enough):
--- 2023/03/08 - 12:59 (7482)
[12:59:11] WASAPI device without vid/pid: AI Noise-cancelling Output (ASUS Utility) : {2}.\\?\root#media#0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\wave
[12:59:11] WASAPI device without vid/pid: AI Noise-cancelling Input (ASUS Utility) : {2}.\\?\root#media#0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\wave
[12:59:11] Audio device found: name="2- DDJ-FLX6" vid="0x2B73" pid="0x0038" hardwareID:"{0.0.0.00000000}.{5b0f46a9-7929-4084-afaf-fa723eeb46b6}"
[12:59:11] Audio device found: name="C-Media(R) Audio" vid="0x0B05" pid="0x6210" hardwareID:"{0.0.0.00000000}.{c137b8dd-f3d8-497c-bf66-2f2177b2d37b}"
[12:59:11] Audio device found: name="ASUS Utility" hardwareID:"{0.0.0.00000000}.{eca08ee3-e4a6-4c38-b777-30a5f9e3dec1}"
[12:59:11] Audio device found: input name="ASUS Utility" hardwareID:"{0.0.1.00000000}.{2d40c36f-7a2d-45db-9919-244aa7a085da}"
[12:59:11] Audio device found: input name="C-Media(R) Audio" vid="0x0B05" pid="0x6210" hardwareID:"{0.0.1.00000000}.{6ea70d98-3975-40e3-819d-a0e610533655}"
[12:59:12] GPU NVIDIA GeForce RTX 3050 Ti Laptop GPU - 4169138176
[12:59:12] GPU AMD Radeon(TM) Graphics - 2119987200
[12:59:12] stems GPU engine changed to card 1
[12:59:12] Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
[12:59:12] MIDI Device Identifying: \\?\usb#vid_2b73&pid_0038&mi_02#7&33d7cb14&0&0002#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global (in:0 out:1) (name: DDJ-FLX6)
[12:59:12] MIDI Device Identified by PID/VID: \\?\usb#vid_2b73&pid_0038&mi_02#7&33d7cb14&0&0002#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global : Pioneer DDJ-FLX6
[12:59:12] Assigned Keyboard, type:0, index:1
[12:59:12] Assigned Pioneer DDJ-FLX6, type:0, index:1
[12:59:12] MIDI Device Identifying: Microsoft GS Wavetable Synth (in:-1 out:0) (name: Microsoft GS Wavetable Synth)
[12:59:12] MIDI Device Not Identified: Microsoft GS Wavetable Synth
[12:59:12] HID Device found: VID:0x048D PID:0x8051 path:\\?\hid#ite5570#4&23012347&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:59:12] HID Device found: VID:0x2B73 PID:0x0038 path:\\?\hid#vid_2b73&pid_0038&mi_04#8&e7c8cbb&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:59:12] HID Device found: VID:0x093A PID:0x2003 path:\\?\hid#asup1205&col03#4&1daeddd1&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:59:12] HID Device found: VID:0x093A PID:0x2003 path:\\?\hid#asup1205&col04#4&1daeddd1&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:59:12] HID Device found: VID:0x0B05 PID:0x6210 path:\\?\hid#vid_0b05&pid_6210&mi_03#8&3273e4a7&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:59:12] HID Device found: VID:0x3938 PID:0x1031 path:\\?\hid#vid_3938&pid_1031&col02#7&23134972&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
[12:59:12] Assigned Keyboard, type:0, index:1
[12:59:12] Assigned Pioneer DDJ-FLX6, type:0, index:1
[12:59:20] GPU speed: x6.3
[12:59:22] GPU speed: x5.7
[12:59:24] GPU speed: x5.5
[12:59:27] GPU speed: x5.6
[12:59:29] GPU speed: x5.6
[12:59:31] GPU speed: x6.2
[12:59:33] GPU speed: x5.6
[12:59:35] GPU speed: x5.5
[12:59:37] GPU speed: x5.6
[12:59:39] GPU speed: x5.6
[12:59:41] GPU speed: x6.4
[12:59:43] GPU speed: x5.5
[12:59:45] GPU speed: x5.5
[12:59:48] GPU speed: x5.6
[12:59:50] GPU speed: x5.5
[12:59:52] GPU speed: x5.5
[12:59:54] GPU speed: x5.6
[12:59:56] GPU speed: x6.2
[12:59:58] GPU speed: x5.6
[13:00:00] GPU speed: x5.5
[13:00:02] GPU speed: x5.6
[13:00:04] GPU speed: x5.5
[13:00:06] GPU speed: x6.6
[13:00:08] GPU speed: x5.6
[13:00:11] GPU speed: x5.5
[13:00:13] GPU speed: x5.6
[13:00:15] GPU speed: x5.5
[13:00:17] GPU speed: x5.6
[13:00:19] GPU speed: x5.6
[13:01:45] Set not stored because length below 20 minutes
[13:01:45] Midi In Closed (\\?\usb#vid_2b73&pid_0038&mi_02#7&33d7cb14&0&0002#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global)
[13:01:45] Midi Out Closed (\\?\usb#vid_2b73&pid_0038&mi_02#7&33d7cb14&0&0002#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global)
[13:01:45] Performance stats (session duration: 02:30)
[13:01:45] avg peak audio cpu: 2% - low skin fps avg: 29 fps - periods with skin drops (<24fps): 7% - periods with skin drops (<15fps): 0%
[13:01:45] low controller fps avg: 55 fps - periods with controller drops (<10fps): 7%
And here the GPU-Z results:
Nvidia results with Nvidia selected
AMD results with Nvidia selected
AMD Radeon results with AMD selected (as you can see 100% GPU usage, but WIN11 performance monitor shows 0-4% ??)
Nvidia results with AMD selected
发表时间 Wed 08 Mar 23 @ 12:12 pm
IIDEEJAYII
kradcliffe wrote :
I have it in the performance section and it works there
shouldn't the
<stemsFixExtra>log</stemsFixExtra>
be a modify of the existing empty, settings line
<stemsFixExtra />
and NOT adding the additional line,
(creating a 2nd line specifying the state of stemFixExtra setting)
maybe in this case the second instant (or empty setting, is ignored)
发表时间 Wed 08 Mar 23 @ 7:18 pm
