I used the old guitar sniffer about 7 months ago and it worked fine on my rock band 4 guitar, and i wanted to get back into it today so i installed the new guitar sniffer and everything else. I set up vjoy and followed all the instructions yet clonehero isn't detecting any input from my guitar

When I open up the Guitar Sniffer program nothing ever shows up.
The PC seems to detect the guitar as if I hit the Xbox Button the Xbox GameBar Windows overlay thingy pops up.

It looks like Windows 1903 killed vJoy and the project is no longer supported. Anyway around it? Since it fails to install there is no way the sniffer actually recognizes the keystrokes

In games like Clone Hero, you can't use both sets since they're all each individual button input, have each color send the same button input like Button 1 for both small and large green fret buttons for example.

Tried using NPCap as a replacement for WinPCap since I’m seeing that it’s not supported on Windows 10. I haven’t been able to register a single input on guitar sniffer. It doesn’t even have that code at the bottom. I’m not sure if I’m just missing something, but if someone could put me on the right track, that would be amazing.

Hi, I've installed all applications needed, but when I launch guitar sniffer, it instantly opens and closes. What could it be? I have the guitar hero live xbox one dongle.

ran guitar sniffer for a few days everything goes well then it suddenly stops detecting my button inputs. i changed nothing but the old sniffer works fine. are other people experiencing this problem where is just stops working randomly?

I just bought an official Xbox wireless adapter for Windows and so far it seems like guitarsniffer doesn't detect it even if I switch usb ports. The GUI opens but no inputs appear on screen.

It seems like there won't be any more updates for this, so I was wondering if there's anyone else would be able to add support for it.

There's a program I use semi frequently that uses Npcap, so having to swap installs of WinPCap and Npcap back and forth gets a bit tedious.

I've found that when using winpcap from the download link in README.md, guitarsniffer doesn't even appear to start. If I install npcap install (with winpcap API compatibility enabled), guitarsniffer does start but doesn't display any button presses, nor does it display any packets.

I have a Guitar Hero Live for Xbox One controller connected to the PC. I'm using Windows 10.

I can play maybe one song, or get thorugh half of the song and the application will full on crash my pc.

Background Info

Why doesn't it just work?

Basically, the ps4 rb4 stuff works off bluetooth; totally insecure and works perfectly without doing anything 9/10 times. Our issue is that the Xbox One stuff uses the Xbox One Wireless Adapter which is a Proprietary 801.1 Wireless Adapter to connect to the pc.

If you look in the Xbox app, you may find that the rb4 Xbox stuff already appears to be supported (this is just a clever bit of work on Microsoft's part).

The rb4 Xbox stuff works by appearing to the system as usb hid devices - they aren't actually recognised as usb devices per say, the best description would be like a tv remote, so they'll navigate menus in supported apps, but that's about it.

So what do we do?

The basic idea is that, at the lowest level, it's a Wireless Adapter - we just can't interface with it like a Wireless Adapter since it's Proprietary.

So, with that in mind, we can see that the Packets must be coming into the system somehow; it's usb right?

There must be a way of seeing the Packets coming in.

This is where Wireshark comes in; we use a combination of WinPCap, the windows binding for the PCap library (Packet Capture), and USBPCap which allows us to capture USB Packets and we 'sniff' the USB Adapter (see here for what sniffing is).

Great, we can see the Packets, now what?

This basically leaves us at a point where we can see the Packets coming in but we have no idea what they map to.

It was at this point that I started triggering all the inputs available to me and logging the Packets I received on both the press & release, resulting a spreadsheet documenting each input and what I thought it mapped to on that byte of the Packet , leading me to understand 3 things;

1. There is ~20+ bytes on a header
2. A Packet containing data is 40 bytes long (for the rb4 guitar)
3. Which parts of the Packet are useable data and what they correlate to

From that, it was to write it in such a way that it was fast to action. I went through 3 stages with this process;

1. C#
   • This one was too slow though, took at least 200ms to action
2. Erlang
   • This one was nice and fast but the windows support was lacking and was impossible for people to use portably
3. Golang
   • This one is perfect; fast, compiles to a single binary, easy to write and read & very good performance wise + allows for C bindings through cgo

Development Requirements

• Golang
  • a GCC Compiler for the cgo stuff
• Wireshark
• WinPCap
• USBPCap

Basic Idea

This is the basic idea of USB Packet capture & it'll show you the basics of using Wireshark.

All the Packets will be in hex when you use Wireshark and that's how I treat them in golang too since I don't like random bytes (0xFF looks better to me than 255).

First, you'll want to log as many Packets of duplicate actions as you can; you'll want to Packet dump the activation of something, waiting a couple seconds then repeating multiple times to produce a folder of Packets similar to this one.

Second, you will want to filter out Packets that are obviously outliers - (i.e there might be a ping Packet in there that you caught - some will be obvious since the Packet will be a different length).

Thirdly, you'll want to document your findings in a spreadsheet.

NOTE: Some Packets may be duplicated and some may randomly change. Here's some info from my experience that may be the same for when you try;

• The first X duplicate bytes are the Packet header.
• Randomly changing bytes that only increment appear to be correlation bytes to guarantee that the Packet comes after the prior one.
• Any repeated duplicate patterns, (i.e a byte in the Packet is 0x00 & 0x01) typically means that it is that one you want

Eventually you'll be able to build up a spreadsheet like this one.

From here, it's a matter of programming support since you already have knowledge of the correct Packet positions.

Xbox One Drum Devs

• Dunkalunk

I followed the instructions, but for some reason the controller just turns on, then turns right back off again. It won't stay on. Using the newer Xbox One controller adapter for Windows 10, and the Jaguar controller. Using the WinPcap mentioned.
EDIT: Okay, figured out how to get it to stay connected, but now guitarsniffer just closes when I open it. Tried running as admin, but same result.
EDIT 2: Alright.. scratch all of that, I guess. Works fine now. Just had to restart, and guitarsniffer stopped closing. Works fine in Clone Hero. Only thing I'd like to try now... is getting it to work on Rock Band 3 through RPCS3. If I could make Xinput think it was a 360 guitar, I'd be pretty much golden. But I have no clue if such a program even exists. Unless there's a way to change which button is which in vJoy...?

I know there is already an issue open of this same problem, but it's old and I'm having the same problem, so I figured I'd make a new one.

Basically, Guitar Sniffer isn't recognizing any button inputs from my guitar. I'm using an XB1 Stratocaster with the Xbox wireless adapter. I've got WinPCap and USBPCap all installed, and just nothing works. I've uninstalled and reinstalled everything several times, and I've tried NPCap instead of WinPCap, but nothing has worked.

Everything used to work fine and without any problems. I just was trying to play Clone Hero today and found that nothing was working.

Edit: Forgot to mention that I have vJoy installed too, and have it set up correctly (at least to my knowledge).

I've installed vjoy, usbpcap and winpcap, configured vjoy and tried to open guitar sniffer but it refuses to open. I've tried reinstalling it, running as admin, restarting my pc, adding as exception in my virus protection, and i've tried older versions but nothing seems to work.

When I have guitar sniffer running in the background, it completely maxes out one of my CPU cores and ends up using about 20% of my i7-8750H. Is there a reason the program needs to run unrestrained?

I'd like to be able to play with friends on multiple guitars, but as it is, it recognizes button inputs from either guitar as button inputs for one, even with two instances of guitarsniffer.exe running

Think anyone can update this to support Windows 11? Doesn't seem to open at all. Works fine on Windows 10. Simple fix hopefully?

I followed the instructions for setup, and when I launched Guitar Sniffer it never responded to inputs on my Guitar.

I have tried uninstalling and reinstalling. I've tried using both WinPCap and NPCap, neither made a difference.

Running Windows 10 1903, Xbox One Stratocaster guitar, Xbox one wireless adapter. All installed software was the most recent (or stable) version.