etclabs/etcdmxtool

UNOFFICIAL - A free open source DMX/RDM controller/sniffer working with ETC's Gadget2 hardware platform

etcdmxtool's Issues

Dissectors don't load

v3.0.0.1 Windows 10 22H2

The dissectors don't load, this is because of

ETCDmxTool/src/dissectors.cpp

Line 29 in 23d208a

QDir dissectorDir(QDir::currentPath());

and the start menu shortcut referencing the whip driver folder for the "Start In"
due to the last SetOutPath before creation of the shortcut in the NSIS script

ETCDmxTool/install/install.nsi

Line 111 in 23d208a

SetOutPath "$INSTDIR\Whip_Drivers\amd64"

Using QCoreApplication::applicationDirPath() should likely be used in place of QDir:CurrentPath() as well as setting an appropriate SetOutPath before

ETCDmxTool/install/install.nsi

Line 140 in 23d208a

CreateShortcut '$SMPROGRAMS\${PRODUCT_NAME}\${PRODUCT_NAME}.lnk' '$INSTDIR\${PRODUCT_NAME}.exe'

Invalid Message

A controller generated message with a Port ID of 0 should indicate as invalid.

Windows MSVC x64 not supported

Cannot build using MSVC x64 toolchains as Gadget.dll is only available in x86, and the FTDI x64 build path is incorrect.
Upstream ETCLabs/libGadget has a Windows x64 build available

Unable to load Goddard Designs sniffer text dump

The header line is not read correctly

Filter Out RDM Discovery Messages

Using the "Sniffer" to interrogate RDM traffic I would love the ability to filter out discovery messages from the table so that I can easily see all the other messages more easily. This would be particularly useful when I have a controller doing device discovery pretty aggressively...

Sniffing won't display unless...

Sniffing results won't display unless the mode buttons are toggled to something else (i.e. "DMX Controller"), then back to "Sniffer".
m_mode is not initialised to a default

Does not include required hardware drivers

The installer should include drivers for the supported hardware interfaces.