I've created some macro's that made it easier for me to read what was shared amongst the reports, and modified the reports slightly, as several of the USB Reports are shared between the collection once defined.
I have no idea if this causes any functional differences in captured data from the streamdeck pedals, as I do not own one, (but do own a StreamDeck XL) and havn't set up a test circuit yet.
However the device now recognizes under windows 10, and shows up in the Stream Deck software.
I have not yet created the circuits to test button or LED function yet, but will be doing that shortly.
What I found (by finding someone else in a USB hacking discord who had the same issue 9 years ago) is that Windows is far fussier when it comes to USB reports then Mac OSX.
Every main item must have a usage defined, but the usage page can be shared.
As I don't have the real hardware to test against, I guessed based on the existing code, in that HID_USAGE_CONSUMER_CONTROL was likely the usage that should be applied to each main item, since the some of the other macro's are 'sticky' that perhaps that MACOSX interprets missing usages as the previous one? or that your intention was that it would cascade through all the main items.
I've created some macro's that made it easier for me to read what was shared amongst the reports, and modified the reports slightly, as several of the USB Reports are shared between the collection once defined.
I have no idea if this causes any functional differences in captured data from the streamdeck pedals, as I do not own one, (but do own a StreamDeck XL) and havn't set up a test circuit yet.
However the device now recognizes under windows 10, and shows up in the Stream Deck software.
I have not yet created the circuits to test button or LED function yet, but will be doing that shortly.
What I found (by finding someone else in a USB hacking discord who had the same issue 9 years ago) is that Windows is far fussier when it comes to USB reports then Mac OSX.
Every main item must have a usage defined, but the usage page can be shared.
As I don't have the real hardware to test against, I guessed based on the existing code, in that HID_USAGE_CONSUMER_CONTROL was likely the usage that should be applied to each main item, since the some of the other macro's are 'sticky' that perhaps that MACOSX interprets missing usages as the previous one? or that your intention was that it would cascade through all the main items.