[New Device] MSI MEG X399 CREATION

Name of device:

MSI MEG X399 CREATION (MS-7B92)

Link to manufacturer's product page:

https://www.msi.com/Motherboard/MEG-X399-CREATION/support

Please select what type of device/interface the device uses:

DeviceTypeUSB

ID information:

USB\VID_1462&PID_7B92

Please attach screenshots of the device's official control application here:

Please attach device captures here:

Setting all red

USB URB
    [Source: host]
    [Destination: 1.1.0]
    USBPcap pseudoheader length: 28
    IRP ID: 0xffffbe0c2ccee9c0
    IRP USBD_STATUS: USBD_STATUS_SUCCESS (0x00000000)
    URB Function: URB_FUNCTION_CLASS_INTERFACE (0x001b)
    IRP information: 0x00, Direction: FDO -> PDO
    URB bus id: 1
    Device address: 1
    Endpoint: 0x00, Direction: OUT
    URB transfer type: URB_CONTROL (0x02)
    Packet Data Length: 170
    [Response in: 580]
    Control transfer stage: Setup (0)
    [bInterfaceClass: HID (0x03)]
Setup Data
    bmRequestType: 0x21
    bRequest: SET_REPORT (0x09)
    wValue: 0x0352
    wIndex: 0
    wLength: 162
    Data Fragment […]: 1c00c0e9ce2c0cbeffff000000001b0000010001000002aa00000000210952030000a2005200000000000032008000000000002800320082000000000028003200824c000000002800ff00804c00000000a80032008100000000000000320080000000000000003200800000000000000032008000000000000000320080000000000000003200800000000000000032008000000000000000320080000000000000003200800000000000000032008000000000002800320082000000000028003200820000

Aditional Information

This motherboard some design overlap with the MSI Z390-based boards, and as of such it seems to use the same Mystic Light Controller with a 162-byte packet. Onboard LED 0-7 are mapped to Bottom Right as they are a row of LEDs, while PCH and IO Cover are mapped to LED 8 and 9.

I've been running a modified version of OpenRGB with added detection and configuration for this board without problems for 2-3 months. I will create a Merge Request with those changes.

Checklist for Step2

• Name of device
• A link to the vendors product page has been included
• The transport bus has been identified and the appropriate label added to the issue.
• The device ID's have been included for USB or PCI
• Screenshots of the OEM Application are included
• There is either, appropriate code examples linked or suitable device captures attached