martyghen
Hey team, firstly STEMS 2.0 is amazing / borderline witchcraft. Love it!
However, it seems that on my setup, all versions after v2023 b7388 aren't using the GPU either at all or to its full potential to compute the STEMS (i.e., this version works fine, more recent ones do not). Somtimes I see CPU utilisation go through the roof instead, while GPU sits idle. Other times GPU only appears to have a small amount of activitiy on it. Either way, the result is that the STEMS 2.0 computation isn't moving along as fast as it should be. I have tried the various STEMS compute settings in the most recent version, but nothing solves it. Might be something to do with dual GPU configurations (display + renderer) confusing the software? In v2023 b7388 the (high powered renderer) GPU is maxed immediately after load and things work beautifully as shown below. I've rolled back to this version for now.
Other things to note is that I am using Tidal as my track library, so STEMS are computed a lot. And I'm using VDJ with a Reloop Mixon 4, though that's probably not relevant here.
Here are my PC specs...
However, it seems that on my setup, all versions after v2023 b7388 aren't using the GPU either at all or to its full potential to compute the STEMS (i.e., this version works fine, more recent ones do not). Somtimes I see CPU utilisation go through the roof instead, while GPU sits idle. Other times GPU only appears to have a small amount of activitiy on it. Either way, the result is that the STEMS 2.0 computation isn't moving along as fast as it should be. I have tried the various STEMS compute settings in the most recent version, but nothing solves it. Might be something to do with dual GPU configurations (display + renderer) confusing the software? In v2023 b7388 the (high powered renderer) GPU is maxed immediately after load and things work beautifully as shown below. I've rolled back to this version for now.
Other things to note is that I am using Tidal as my track library, so STEMS are computed a lot. And I'm using VDJ with a Reloop Mixon 4, though that's probably not relevant here.
Here are my PC specs...
------------------
System Information
------------------
Time of this report: 2/26/2023, 07:19:48
Machine name: MSI
Machine Id: {875DF5AB-FF9C-4B53-BAB5-B063C52FF923}
Operating System: Windows 11 Home 64-bit (10.0, Build 22000) (22000.co_release.210604-1628)
Language: English (Regional Setting: English)
System Manufacturer: Micro-Star International Co., Ltd.
System Model: Creator M16 A12UD
BIOS: E1584IMS.30E (type: UEFI)
Processor: 12th Gen Intel(R) Core(TM) i7-12700H (20 CPUs), ~2.7GHz
Memory: 16384MB RAM
Available OS Memory: 16086MB RAM
Page File: 13936MB used, 4581MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 120 DPI (125 percent)
System DPI Setting: 144 DPI (150 percent)
DWM DPI Scaling: UnKnown
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Supported
DirectX Database Version: 1.4.5
DxDiag Version: 10.00.22000.0653 64bit Unicode
---------------
Display Devices
---------------
Card name: Intel(R) Iris(R) Xe Graphics
Manufacturer: Intel Corporation
Chip type: Intel(R) Iris(R) Xe Graphics Family
DAC type: Internal
Device Type: Full Device (POST)
Device Key: Enum\PCI\VEN_8086&DEV_46A6&SUBSYS_13371462&REV_0C
Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 8170 MB
Dedicated Memory: 128 MB
Shared Memory: 8042 MB
Current Mode: 2560 x 1600 (32 bit) (60Hz)
HDR Support: Not Supported
Display Topology: Internal
Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
Color Primaries: Red(0.639648,0.330078), Green(0.299805,0.599609), Blue(0.149414,0.059570), White Point(0.312500,0.329102)
Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000
Monitor Name: Generic PnP Monitor
Monitor Model: unknown
Monitor Id: BOE0A0F
Native Mode: 2560 x 1600(p) (60.001Hz)
Output Type: Internal
Monitor Capabilities: HDR Not Supported
Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
Advanced Color: Not Supported
Driver Name: <>,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_f931e07ed594c02e\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_f931e07ed594c02e\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_f931e07ed594c02e\igd12umd64.dll
Driver File Version: 30.00.0101.1029 (English)
Driver Version: 30.0.101.1029
DDI Version: 12
Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
Driver Model: WDDM 3.0
Hardware Scheduling: DriverSupportState:AlwaysOff Enabled:False
Graphics Preemption: Triangle
Compute Preemption: Thread group
Miracast: Not Supported by Graphics driver
Detachable GPU: No
Hybrid Graphics GPU: Integrated
Power P-states: Not Supported
Virtualization: Paravirtualization
Block List: DISABLE_HWSCH
Catalog Attributes: Universal:False Declarative:True
Driver Attributes: Final Retail
Driver Date/Size: 3/11/2021 10:00:00 AM, 31987512 bytes
WHQL Logod: n/a
WHQL Date Stamp: n/a
Device Identifier: {D7B78E66-05E6-11CF-D773-5233A3C2D335}
Vendor ID: 0x8086
Device ID: 0x46A6
SubSys ID: 0x13371462
Revision ID: 0x000C
Driver Strong Name: oem357.inf:5f63e5343e91ba36:iADLPD_w10_DS:30.0.101.1029:PCI\VEN_8086&DEV_46A6&SUBSYS_13371462
Rank Of Driver: 00CF0001
Video Accel:
DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeVC1_D2010 {E07EC519-E651-4CD6-AC84-1370CCEEC851} {BCC5DB6D-A2B6-4AF0-ACE4-ADB1F787BC89} DXVA2_ModeWMV9_IDCT DXVA2_ModeVC1_IDCT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_Multiview_NoFGT {C528916C-C0AF-4645-8CB2-372B6D4ADC2A} {91CD2D6E-897B-4FA1-B0D7-51DC88010E0A} {97688186-56A8-4094-B543-FC9DAAA49F4B} {1424D4DC-7CF5-4BB1-9CD7-B63717A72A6B} {C346E8A3-CBED-4D27-87CC-A70EB4DC8C27} {FFC79924-5EAF-4666-A736-06190F281443} {464BDB3C-91C4-4E9B-896F-225496AC4ED6} {9B31316B-F204-455D-8A8C-9345DCA77C01} {AFE4285C-AB63-4B2D-8278-E6BAACEA2CE9} {277DE9C5-ED83-48DD-AB8F-AC2D24B22943} {04C5BA10-4E9A-4B8E-8DBF-4F4B48AFA27C} {0ACEF8BC-285F-415D-AB22-7BF2527A3D2E} {24D19FCA-C5A2-4B8E-9F93-F8F6EF15C890} {353ACA91-D945-4C13-AE7E-469060FAC8D8} {28566328-F041-4466-8B14-8F5831E78F8B} {6B4A94DB-54FE-4AE1-9BE4-7A7DAD004600} {B8B28E0C-ECAB-4217-8C82-EAAA9755AAF0} {8732ECFD-9747-4897-B42A-E534F9FF2B7A} {E139B5CA-47B2-40E1-AF1C-AD71A67A1836} {056A6E36-F3A8-4D00-9663-7E9430358BF9} {5415A68C-231E-46F4-878B-5E9A22E967E9} {161BE912-44C2-49C0-B61E-D946852B32A1} {D6D6BC4F-D51A-4712-97E8-750917C860FD} {7FEF652D-3233-44DF-ACF7-ECFB584DAB35} {580DA148-E4BF-49B1-943B-4214AB05A6FF} {CEE393AB-1030-4F7B-8DBC-55629C72F17E} {87B2AE39-C9A5-4C53-86B8-A52D7EDBA488} {10E19AC8-BF39-4443-BEC3-1B0CBFE4C7AA} {2DEC00C7-21EE-4BF8-8F0E-773F11F126A2} {C35153A0-23C0-4A81-B3BB-6A1326F2B76B} {A33FD0EC-A9D3-4C21-9276-C241CC90F6C7} {310E59D2-7EA4-47BB-B319-500E78855336} {036DFF40-94A6-45B3-A0B3-71F0CDF35129} {8C56EB1E-2B47-466F-8D33-7DBCD63F3DF2} DXVA2_ModeHEVC_VLD_Main {75FC75F7-C589-4A07-A25B-72E03B0383B3} DXVA2_ModeHEVC_VLD_Main10 {E484DCB8-CAC9-4859-99F5-5C0D45069089} {41A5AF96-E415-4B0C-9D03-907858E23E78} {6A6A81BA-912A-485D-B57F-CCD2D37B8D94} {E4E3CF5B-97D2-4658-AACB-366E3EE2CEEE} {FD9D9559-0FD3-4917-A9A7-07E714EE9EF9} {0E4BC693-5D2C-4936-B125-AEFE32B16D8A} {2F08B5B1-DBC2-4D48-883A-4E7B8174CFF6} {5467807A-295D-445D-BD2E-CBA8C2457C3D} {AE0D4E15-2360-40A8-BF82-028E6A0DD827} {8FF8A3AA-C456-4132-B6EF-69D9DD72571D} {C23DD857-874B-423C-B6E0-82CEAA9B118A} {5B08E35D-0C66-4C51-A6F1-89D00CB2C197} {07CFAFFB-5A2E-4B99-B62A-E4CA53B6D5AA} DXVA2_ModeVP9_VLD_Profile0 DXVA2_ModeVP9_VLD_10bit_Profile2 {76988A52-DF13-419A-8E64-FFCF4A336CF5} {68A21C7B-D58F-4E74-9993-E4B8172B19A0} {80A3A7BD-89D8-4497-A2B8-2126AF7E6EB8} {1D5C4D76-B55A-4430-904C-3383A7AE3B16} {A7F759DD-5F54-4D7F-8291-42E883C546FE} {F34FA92F-DC79-474C-B0DB-B7BD4522DF77} {B8BE4CCB-CF53-46BA-8D59-D6B8A6DA5D2A} {CA44AFC5-E1D0-42E6-9154-B127186D4D40} {F9A16190-3FB4-4DC5-9846-C8751F83D6D7} {50925B7B-E931-4978-A12A-586630F095F9} {B69C20E0-2508-8790-0305-875499E0A2D0} {49761BEC-4B63-4349-A5FF-87FFDF088466}
Deinterlace Caps: {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate
{E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate
{E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate
{E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate
{E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,0x31434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,0x31434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate
{E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(IMC1,0x31434d49) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,0x32434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,0x32434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate
{E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(IMC2,0x32434d49) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,0x33434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,0x33434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate
{E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(IMC3,0x33434d49) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,0x34434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,0x34434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate
{E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(IMC4,0x34434d49) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,0x30343353) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,0x30343353) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate
{E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(S340,0x30343353) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,0x32343353) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,0x32343353) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate
{E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(S342,0x32343353) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive
D3D9 Overlay: Not Supported
DXVA-HD: Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
MPO MaxPlanes: 3
MPO Caps: ROTATION,HORIZONTAL_FLIP,RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3)
MPO Stretch: 21.000X - 0.334X
MPO Media Hints: colorspace Conversion
MPO Formats: NV12,YUY2,R16G16B16A16_FLOAT,R10G10B10A2_UNORM,R8G8B8A8_UNORM,B8G8R8A8_UNORM
PanelFitter Caps: ROTATION,HORIZONTAL_FLIP,RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3)
PanelFitter Stretch: 21.000X - 0.334X
Extension Drivers:
Driver Name: C:\Windows\System32\DriverStore\FileRepository\iigd_ext.inf_amd64_682eaf0489f3283c\iigd_ext.inf
Driver Version: 30.0.101.1029
Driver Date: 11/03/2021
Driver Provider: Intel Corporation
Catalog Attributes: Universal:False Declarative:True
Component Drivers:
Driver Name: Unknown
Driver Version: Unknown
Driver Date: Unknown
Driver Provider: Unknown
Catalog Attributes: N/A
Card name: NVIDIA GeForce RTX 3050 Ti Laptop GPU
Manufacturer: NVIDIA
Chip type: NVIDIA GeForce RTX 3050 Ti Laptop GPU
DAC type: Integrated RAMDAC
Device Type: Render-Only Device
Device Key: Enum\PCI\VEN_10DE&DEV_25A0&SUBSYS_13371462&REV_A1
Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 12035 MB
Dedicated Memory: 3993 MB
Shared Memory: 8042 MB
Current Mode: Unknown
HDR Support: Unknown
Display Topology: Unknown
Display Color Space: Unknown
Color Primaries: Unknown
Display Luminance: Unknown
Driver Name: C:\Windows\System32\DriverStore\FileRepository\nvmisi.inf_amd64_f3eb638cdc1bd0c3\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmisi.inf_amd64_f3eb638cdc1bd0c3\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmisi.inf_amd64_f3eb638cdc1bd0c3\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmisi.inf_amd64_f3eb638cdc1bd0c3\nvldumdx.dll
Driver File Version: 31.00.0015.1694 (English)
Driver Version: 31.0.15.1694
DDI Version: 12
Feature Levels: 12_2,12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
Driver Model: WDDM 3.0
Hardware Scheduling: DriverSupportState:Stable Enabled:True
Graphics Preemption: Pixel
Compute Preemption: Dispatch
Miracast: Not Supported by Graphics driver
Detachable GPU: No
Hybrid Graphics GPU: Discrete
Power P-states: Not Supported
Virtualization: Paravirtualization
Block List: No Blocks
Catalog Attributes: Universal:False Declarative:True
Driver Attributes: Final Retail
Driver Date/Size: 21/07/2022 10:00:00 AM, 1130032 bytes
WHQL Logod: n/a
WHQL Date Stamp: n/a
Device Identifier: Unknown
Vendor ID: 0x10DE
Device ID: 0x25A0
SubSys ID: 0x13371462
Revision ID: 0x00A1
Driver Strong Name: oem557.inf:0f066de327339162:Section198:31.0.15.1694:pci\ven_10de&dev_25a0&subsys_13371462
Rank Of Driver: 00CF0001
Video Accel: Unknown
DXVA2 Modes: {86695F12-340E-4F04-9FD3-9253DD327460} DXVA2_ModeMPEG2_VLD {6F3EC719-3735-42CC-8063-65CC3CB36616} DXVA2_ModeVC1_D2010 DXVA2_ModeVC1_VLD {32FCFE3F-DE46-4A49-861B-AC71110649D5} DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeHEVC_VLD_Main DXVA2_ModeHEVC_VLD_Main10 {20BB8B0A-97AA-4571-8E99-64E60606C1A6} {15DF9B21-06C4-47F1-841E-A67C97D7F312} DXVA2_ModeMPEG4pt2_VLD_Simple DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC {9947EC6F-689B-11DC-A320-0019DBBC4184} {33FCFE41-DE46-4A49-861B-AC71110649D5} DXVA2_ModeVP9_VLD_Profile0 DXVA2_ModeVP9_VLD_10bit_Profile2 {DDA19DC7-93B5-49F5-A9B3-2BDA28A2CE6E} {B8BE4CCB-CF53-46BA-8D59-D6B8A6DA5D2A} {6AFFD11E-1D96-42B1-A215-93A31F09A53D} {914C84A3-4078-4FA9-984C-E2F262CB5C9C} {8A1A1031-29BC-46D0-A007-E9B092CA6767}
Deinterlace Caps: n/a
D3D9 Overlay: Unknown
DXVA-HD: Unknown
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
MPO MaxPlanes: 0
MPO Caps: Not Supported
MPO Stretch: Not Supported
MPO Media Hints: Not Supported
MPO Formats: Not Supported
PanelFitter Caps: Not Supported
PanelFitter Stretch: Not Supported
-------------
Sound Devices
-------------
Description: Speakers (Mixon 4)
Default Sound Playback: No
Default Voice Playback: Yes
Hardware ID: USB\VID_26AD&PID_8EB6&REV_0200&MI_00
Manufacturer ID: N/A
Product ID: N/A
Type: N/A
Driver Name: USBAUDIO.sys
Driver Version: 10.0.22000.1219 (English)
Driver Attributes: Final Retail
WHQL Logod: n/a
Date and Size: 3/11/2022 10:00:00 AM, 266240 bytes
Other Files:
Driver Provider: Microsoft
HW Accel Level: Emulation Only
Cap Flags: 0x0
Min/Max Sample Rate: 0, 0
Static/Strm HW Mix Bufs: 0, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Description: Speakers (Realtek(R) Audio)
Default Sound Playback: Yes
Default Voice Playback: No
Hardware ID: INTELAUDIO\FUNC_01&VEN_10EC&DEV_0256&SUBSYS_1462137F&REV_1000
Manufacturer ID: N/A
Product ID: N/A
Type: N/A
Driver Name: RTKVHD64.sys
Driver Version: 6.0.9344.1 (English)
Driver Attributes: Final Retail
WHQL Logod: n/a
Date and Size: 26/04/2022 10:00:00 AM, 6198728 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Emulation Only
Cap Flags: 0x0
Min/Max Sample Rate: 0, 0
Static/Strm HW Mix Bufs: 0, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
---------------------
Sound Capture Devices
---------------------
Description: Microphone Array (Intel® Smart Sound Technology for Digital Microphones)
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: IntcDMic.sys
Driver Version: 10.29.0.7767 (English)
Driver Attributes: Final Retail
Date and Size: 30/05/2022 10:00:00 AM, 747544 bytes
Cap Flags: 0x0
Format Flags: 0x0
---------------------
Video Capture Devices
Number of Devices: 1
---------------------
FriendlyName: HD Webcam
Category: Camera
SymbolicLink: \\?\usb#vid_5986&pid_211c&mi_00#6&19e246ad&0&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\global
Location: Front
Rotation: 0
SensorOrientation: 0
Manufacturer: Microsoft
HardwareID: USB\VID_5986&PID_211C&REV_0311&MI_00,USB\VID_5986&PID_211C&MI_00
DriverDesc: USB Video Device
DriverProvider: Microsoft
DriverVersion: 10.0.22000.1042
DriverDateEnglish: 6/21/2006 00:00:00
DriverDateLocalized: 21/06/2006 12:00:00 AM
Service: usbvideo
Class: Camera
DevNodeStatus: 180200A[DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
ContainerId: {00000000-0000-0000-FFFF-FFFFFFFFFFFF}
ProblemCode: No Problem
BusReportedDeviceDesc: HD Webcam
Parent: USB\VID_5986&PID_211C\5&12d6c288&0&6
DriverProblemDesc: n/a
UpperFilters: n/a
LowerFilters: WdmCompanionFilter
Stack: \Driver\ksthunk,\Driver\usbvideo,\Driver\ACPI,\Driver\usbccgp
ContainerCategory: n/a
SensorGroupID: n/a
MFT0: n/a
DMFT: n/a
CustomCaptureSource: n/a
DependentStillCapture: n/a
EnablePlatformDMFT: n/a
DMFTChain: n/a
EnableDshowRedirection: True
FrameServerEnabled: n/a
AnalogProviders: n/a
MSXUCapability: n/a
ProfileIDs: n/a
geposted Sat 25 Feb 23 @ 9:29 pm
wickedmix
the problem is you GPU only has -> Dedicated Memory: 3993 MB
30 series cards require 6 gb or more
30 series cards require 6 gb or more
geposted Sun 26 Feb 23 @ 12:30 am
Sepatro
And why should that be a problem as all worked smoothly before?
I have the same problem.
Something is wrong with the last updates. Let's not deny it.
I have the same problem.
Something is wrong with the last updates. Let's not deny it.
geposted Sun 26 Feb 23 @ 7:34 am
bazzio68
Agreed... like I said earlier in another topic there should be an option to force the use of GPU instead of CPU...
geposted Sun 26 Feb 23 @ 11:03 am
martyghen
Indeed, the force GPU option is what we need. As mentioned, it worked like a charm previously, so no reason for new versions to get rid of what was excellent functionality. Will be great to see it up and working again!
geposted Mon 27 Feb 23 @ 12:59 am
wickedmix
geposted Mon 27 Feb 23 @ 1:23 am
martyghen
Thanks mate, saw that, but "recommended" shouldn't preclude the use of hardware that has been proven to work perfectly fine for the application. As mentioned, laptop GPU was handling STEMS 2.0 just fine as at the quoted version :)
geposted Mon 27 Feb 23 @ 11:19 am
locoDog
so you want to play with an non-recommanded set up and run the risk of a crash? So who are you going to blame if it does?
geposted Mon 27 Feb 23 @ 11:23 am
Sepatro
It should run with the required configuration, not with the recommended configuration. Moreover, he clearly stated that Stems 2.0 worked perfectly well before.
Besides, my laptop does meet the recommended configuration, and I experience the same problems.
VDJ is NOT working right anymore. Something is off. Needs to be fixed.
Besides, my laptop does meet the recommended configuration, and I experience the same problems.
VDJ is NOT working right anymore. Something is off. Needs to be fixed.
geposted Mon 27 Feb 23 @ 8:54 pm
martyghen
Yes exactly right, I would like the option to run with a non recommended setup that I have personally tested, has proven to work reliably, and I am confident with. Thanks for understanding!
geposted Tue 28 Feb 23 @ 11:40 am
martyghen
Also, if you're not rolling up to gigs with a plan B / C in your back pocket for when things go wrong (recommended setup or not) then that's the real madness here, not using a couple of GB less of GPU memory on a well tested and proven reliable setup lol. Shit happens, you pivot, and you move on like a professional.
geposted Tue 28 Feb 23 @ 11:47 am
PhantomDeejay
How is a "non recommended" configuration proven reliable ?
RTX 3050Ti is NOT reliable for Stems 2.0 and that's mostly because of it's low VRAM.
Stems Engine requires about 3.5 GB of VRAM to initialize on RTX series. Also the amount of VRAM used when Stems Engine initializes is mostly up to the drivers of nVidia to figure out. VirtualDJ doesn't have any real control over that.
So, when Stems Engine initializes, an RTX 3050Ti may seem to work ok. However, as soon as the VRAM usage goes above 4GB, the card fails to compute stems fast enough for realtime operation.
This has been explained a few times now. So, RTX3050Ti is unreliable for realtime stems 2.0 separation, exactly because sometimes it works, and sometimes it doesn't.
PS: I don't want to go too technical here. But the main issue is that VirtualDJ tells the GPU to load up a set of instructions (engine) so that VirtualDJ can use it to perform Stems analysis.
This set of instructions (engine) takes different amount of VRAM when loaded on GTX series, and different amount when loaded to RTX series. Also VirtualDJ can optimize it's own code, but it can't "optimize" what happens "inside" the nVidia drivers and "engine"
For RTX3050Ti, it may work in the future if with a future nVidia drivers update the amount of VRAM used by the "engine" drops a little. Or it may never work again if the amount of VRAM increases further more with a future drivers update.
So, as a PERSONAL advise, I would recommend you to just accept the fact that RTX3050 is unreliable for Stems 2.0 realtime separation and find/invest on a machine that' reliable for the task.
However if you still want to stick with RTX 3050, it's ok, but don't try to put the blame on the software that clearly suggests that you need 6GB of VRAM or more for realtime stems 2.0 separation.
With minimum requirements you can still use stems 2.0. But not in realtime. You have to prepare the files first.
RTX 3050Ti is NOT reliable for Stems 2.0 and that's mostly because of it's low VRAM.
Stems Engine requires about 3.5 GB of VRAM to initialize on RTX series. Also the amount of VRAM used when Stems Engine initializes is mostly up to the drivers of nVidia to figure out. VirtualDJ doesn't have any real control over that.
So, when Stems Engine initializes, an RTX 3050Ti may seem to work ok. However, as soon as the VRAM usage goes above 4GB, the card fails to compute stems fast enough for realtime operation.
This has been explained a few times now. So, RTX3050Ti is unreliable for realtime stems 2.0 separation, exactly because sometimes it works, and sometimes it doesn't.
PS: I don't want to go too technical here. But the main issue is that VirtualDJ tells the GPU to load up a set of instructions (engine) so that VirtualDJ can use it to perform Stems analysis.
This set of instructions (engine) takes different amount of VRAM when loaded on GTX series, and different amount when loaded to RTX series. Also VirtualDJ can optimize it's own code, but it can't "optimize" what happens "inside" the nVidia drivers and "engine"
For RTX3050Ti, it may work in the future if with a future nVidia drivers update the amount of VRAM used by the "engine" drops a little. Or it may never work again if the amount of VRAM increases further more with a future drivers update.
So, as a PERSONAL advise, I would recommend you to just accept the fact that RTX3050 is unreliable for Stems 2.0 realtime separation and find/invest on a machine that' reliable for the task.
However if you still want to stick with RTX 3050, it's ok, but don't try to put the blame on the software that clearly suggests that you need 6GB of VRAM or more for realtime stems 2.0 separation.
With minimum requirements you can still use stems 2.0. But not in realtime. You have to prepare the files first.
geposted Tue 28 Feb 23 @ 12:11 pm
kradcliffe
This is exactly what I found when testing the 3050ti. It would work on a fresh reboot calculating stems in around 15 seconds but as soon as the vram started getting used by other things the stems would detect the lack of vram and revert to CPU.
I then got an i9, 32gb, RTX3080ti and it wotks flawlessly at approx 30x calculating an average 3 minute track in around 7 seconds.
@Adion did state he was previously looking at a solution for the 4gb RTX3050 so they may be working on it.
I guess if you want the full power of stems 2.0 you need to invest in hardware to run it.
I then got an i9, 32gb, RTX3080ti and it wotks flawlessly at approx 30x calculating an average 3 minute track in around 7 seconds.
@Adion did state he was previously looking at a solution for the 4gb RTX3050 so they may be working on it.
I guess if you want the full power of stems 2.0 you need to invest in hardware to run it.
geposted Tue 28 Feb 23 @ 12:31 pm
martyghen
Not putting blame on anyone, just asking the devs to consider that it can actually work perfectly fine on lower spec machines for some people's use cases. The devs can't be expected to test every single configuration, so while it is helpful to make "recommendations" (different to mandatory system requirements), it would also be helpful to continue giving people the functionality to figure out how to get the most from this absolute banger software on their own system.
To simply say "buy bigger hardware" is gatekeeping and I dare say not consistent with VDJ's own philosophy as a software company offering up their platform entirely for free to some users. It's how I started, and I'm forever grateful for it.
Thanks all btw for keeping this bumped. Hoping it will help it get some love from the clever devs at VDJ :)
To simply say "buy bigger hardware" is gatekeeping and I dare say not consistent with VDJ's own philosophy as a software company offering up their platform entirely for free to some users. It's how I started, and I'm forever grateful for it.
Thanks all btw for keeping this bumped. Hoping it will help it get some love from the clever devs at VDJ :)
geposted Tue 28 Feb 23 @ 12:31 pm
Sepatro
kradcliffe wrote :
This is exactly what I found when testing the 3050ti. It would work on a fresh reboot calculating stems in around 15 seconds but as soon as the vram started getting used by other things the stems would detect the lack of vram and revert to CPU.
I then got an i9, 32gb, RTX3080ti and it wotks flawlessly at approx 30x calculating an average 3 minute track in around 7 seconds.
@Adion did state he was previously looking at a solution for the 4gb RTX3050 so they may be working on it.
I guess if you want the full power of stems 2.0 you need to invest in hardware to run it.
I then got an i9, 32gb, RTX3080ti and it wotks flawlessly at approx 30x calculating an average 3 minute track in around 7 seconds.
@Adion did state he was previously looking at a solution for the 4gb RTX3050 so they may be working on it.
I guess if you want the full power of stems 2.0 you need to invest in hardware to run it.
That's an interesting discovery... may I ask how you noticed this, and what in your case caused this extra VRAM usage?
My card should be sufficient (RTX 3060 with 6GB), and it worked super-great for months (doing gigs of several hours without any problem including wild STEMS 2.0 usage on the fly), but since a few weeks, all is going wrong. Crackling, distortion, interruptions, and slow STEMS calculation. So I am trying to optimse, but without much success....
geposted Tue 28 Feb 23 @ 12:41 pm
PhantomDeejay
Before RTX3050Ti come out, we would recommend "any" RTX card as all of them had sufficient VRAM.
When RTX3050Ti come out with only 4GB of VRAM the problem was apparent.
As I said above, stems 2.0 still work. But not with realtime GPU separation.
Also as I said above, the amount of VRAM used by the "engine" (the instructions set loaded byt he GPU to do the calculations) is not up to VirtualDJ. It's up to nVidia.
When RTX3050Ti come out with only 4GB of VRAM the problem was apparent.
As I said above, stems 2.0 still work. But not with realtime GPU separation.
Also as I said above, the amount of VRAM used by the "engine" (the instructions set loaded byt he GPU to do the calculations) is not up to VirtualDJ. It's up to nVidia.
geposted Tue 28 Feb 23 @ 12:41 pm
PhantomDeejay
Sepatro wrote :
My card should be sufficient (RTX 3060 with 6GB), and it worked super-great for months (doing gigs of several hours without any problem including wild STEMS 2.0 usage on the fly), but since a few weeks, all is going wrong. Crackling, distortion, interruptions, and slow STEMS calculation. So I am trying to optimse, but without much success....
RTX3060 (with 6GB VRAM) is also what I use on a Windows 11 Asus ROG laptop and it still works perfectly.
geposted Tue 28 Feb 23 @ 12:43 pm
Sepatro
PhantomDeejay wrote :
RTX3060 (with 6GB VRAM) is also what I use on a Windows 11 Asus ROG laptop and it still works perfectly.
Sepatro wrote :
My card should be sufficient (RTX 3060 with 6GB), and it worked super-great for months (doing gigs of several hours without any problem including wild STEMS 2.0 usage on the fly), but since a few weeks, all is going wrong. Crackling, distortion, interruptions, and slow STEMS calculation. So I am trying to optimse, but without much success....
RTX3060 (with 6GB VRAM) is also what I use on a Windows 11 Asus ROG laptop and it still works perfectly.
Hence my question: why does it not work in my case? What was changed in recent versions of VDJ? and if nothing was changed that could have impacted that... what do you recommend to make VDJ work again? I have re-installed windows, re-installed NVidia drivers, ... you know, all the usual stuff.
geposted Tue 28 Feb 23 @ 12:47 pm
PhantomDeejay
I cannot recommend something specific, other than trying to troubleshoot the issue "step by step"
If you formated your machine and reinstalled everything and you still have issues, I would suspect that a driver is the root of that behavior.
For starters I would try to roll back nVidia drivers to previous versions. I would also try both downloads directly from nVidia and my laptop manufacturer.
Then if the problem persisted, I would keep an older version of nVidia drivers (like one released 4 months ago or so) and then I would try to see what happens with the rest components of my PC.
I would even try older VirtualDJ builds as a means to see if it's indeed VirtualDJ, or something on my system that's causing this.
If you can sucessfully find a build that doesn't have the issue and then the next update has the issue, then it's easier for both you and us to find out where your issue may derrive.
It may be a completely unrelated change in software that only affects your own machine (special case).
Or you may be able to find that even by going back to builds that worked ok with your system they no longer do so, and therefore it's definately not the software but a windows/driver/other update/change that causes the issue.
PS: Please start a new thread for your issue. It's not nice to hijack a completely different thread that's for a known "non working" case. Thanks.
If you formated your machine and reinstalled everything and you still have issues, I would suspect that a driver is the root of that behavior.
For starters I would try to roll back nVidia drivers to previous versions. I would also try both downloads directly from nVidia and my laptop manufacturer.
Then if the problem persisted, I would keep an older version of nVidia drivers (like one released 4 months ago or so) and then I would try to see what happens with the rest components of my PC.
I would even try older VirtualDJ builds as a means to see if it's indeed VirtualDJ, or something on my system that's causing this.
If you can sucessfully find a build that doesn't have the issue and then the next update has the issue, then it's easier for both you and us to find out where your issue may derrive.
It may be a completely unrelated change in software that only affects your own machine (special case).
Or you may be able to find that even by going back to builds that worked ok with your system they no longer do so, and therefore it's definately not the software but a windows/driver/other update/change that causes the issue.
PS: Please start a new thread for your issue. It's not nice to hijack a completely different thread that's for a known "non working" case. Thanks.
geposted Tue 28 Feb 23 @ 1:00 pm
Sepatro
Thanks! I will try with an older version of the Nvidia drivers.
geposted Tue 28 Feb 23 @ 1:06 pm
