Subsections

- - Note 1
  - Note 2
  - Note 3
  - Note 4

##
Troubleshooting auxilliary information

In order to see if you hardware was recognized by the operating system, key in:

    lsusb -v -d 0b33:0030  # for the Shuttle Pro or PROv2\\
    lsusb -v -d 0b33:0020  # for the Shuttle Xpress

#### Note 1

Currently, the keys K14 and K15 do not function on the Contour Design ShuttlePro but do on the Contour Design ShuttlePRO v2 due to a Report Descriptor error. You can workaround this by uncommenting USB_DIRECT in your local .shuttlerc file. This directly uses libusb rather than the generic Linux hid driver. USB_DIRECT works for any of the currently tested shuttles.

#### Note 2

If you are not sure if your shuttle is fully functional, you can verify that the hardware device has been seen by your operating system with this procedure.

1. From a terminal window as an ordinary user key in: lsusb (the first character is a lower case L for list). You will see something like the following depending on which usb device you have the ShuttlePro plugged into:

       Bus 003 Device 002: ID 0b33:0030 Contour Design, Inc. ShuttlePro v2

2. To make sure you have usbmon installed key in:

       sudo modprobe usbmon

3. Next key in the following:

       sudo od -tx1 /dev/usbmon3

   where the last 3 is the same # as the Bus in above. If it lists Bus 002, then use /dev/usbmon2 instead.
4. Now with focus in that same terminal window, press any shuttle key just to see what happens and should see about 12 lines similar to these below – a new set every time you press a single key or the wheel. The lines are usually not important, just the fact that you get a response is. However if you have multiple devices on the same bus, you will get responses from any and all of them. Attempt to isolate your shuttle by temporarily unplugging unnecessary devices on the same bus or plug the shuttle into a different usb port that has fewer devices.

       0000000 80 70 99 75 53 8c ff ff 43 01 81 02 03 00 2d 00
       0000020 4e 61 5c 5c 00 00 00 00 8d 2c 06 00 00 00 00 00
       0000040 05 00 00 00 05 00 00 00 00 00 00 00 00 00 00 00
       0000060 01 ff 00 00 00 80 70 99 75 53 8c ff ff 53 01 81
       0000100 02 03 00 2d 3c 4e 61 5c 5c 00 00 00 00 b1 2c 06
       0000120 00 8d ff ff ff 05 00 00 00 00 00 00 00 00 00 00
       0000140 00 00 00 00 00 80 70 99 75 53 8c ff ff 43 01 81
       0000160 02 03 00 2d 00 4e 61 5c 5c 00 00 00 00 3d d7 09
       0000200 00 00 00 00 00 05 00 00 00 05 00 00 00 00 00 00
       0000220 00 00 00 00 00 00 ff 00 00 00 80 70 99 75 53 8c
       0000240 ff ff 53 01 81 02 03 00 2d 3c 4e 61 5c 5c 00 00
       0000260 00 00 64 d7 09 00 8d ff ff ff 05 00 00 00 00 00

5. Next press the key that you want to verify is functioning – if no new lines show up, then the key is non-functional so there is a hardware problem. If you get output, then perhaps there is a problem with your software setup.
6. Use Ctrl-C on the terminal window when done to get back to the prompt.

#### Note 3

Another method for testing to make sure your model of the Shuttle does not have different key definitions than the one that CINELERRA-GG was coded for is to do the following.

1. Locate the shudmp.C program in your CINELERRA-GG directory.
2. Compile that with the command: c++ shdmp.C -o shudmp
3. Make the file executable with the command: chmod +x shudmp
4. Execute:

       sudo ./shdmp /dev/input/by-id/usb-Contour\_Design\_ShuttlePro-event-if00 # substitute your shuttle

Then press your shuttle key that is having problems and check the results. They should look like:

Listing: Example for K7
    event: (4, 4, 0x90007)  #The last number, 7, is the expected Key number.
    event: (1, 262, 0x1)
    event: (0, 0, 0x0)
    event: (4, 4, 0x90007)
    event: (1, 262, 0x0)
    event: (0, 0, 0x0)

Listing: Example for K15
    Example for K15:
    event: (4, 4, 0x9000f)  #The last number f is 15 in hexadecimal and is the expected Key.
    event: (1, 270, 0x1)
    event: (0, 0, 0x0)
    event: (4, 4, 0x9000f)
    event: (1, 270, 0x0)
    event: (0, 0, 0x0)

When done, you will have to Ctrl-C to get out of the program.

#### Note 4

For developers, if you have a pre-UEFI Secure Boot kernel it is also possible to do the following for further in depth testing:

    ls /sys/kernel/debug/hid   \# to locate numerical value of the shuttle, e.g. 0003:0B33.0030.0006
    cat "/sys/kernel/debug/hid/0003:0B33.0030.0006/rdesc"  # substitute your own numerical value
    cat "/sys/kernel/debug/hid/0003:0B33.0030.0006/events"  # press keys to see the results