Konami playstation keyboard-- usable for midi??

Optimize your system for ultimate performance.

Moderators: MattKingUSA, khz

User avatar
briandc
Established Member
Posts: 1442
Joined: Sun Apr 29, 2012 3:17 pm
Location: Italy
Has thanked: 58 times
Been thanked: 28 times
Contact:

Konami playstation keyboard-- usable for midi??

Post by briandc »

Hi all,
as the title indicates, I came across what turned out to be a playstation usb device, looks like this:
Konami

I'm wondering, could it be used as a midi controller? It shows up with

Code: Select all

lsusb
as

Code: Select all

Bus 003 Device 003: ID 0507:0010 Hosiden Corp.
.

But it doesn't appear as a midi device. So is there no use for it as a potential midi controller?

Any input appreciated!


brian
Have your PC your way: use linux!
My sound synthesis biome: http://www.linuxsynths.com
CrocoDuck
Established Member
Posts: 1133
Joined: Sat May 05, 2012 6:12 pm
Been thanked: 17 times

Re: Konami playstation keyboard-- usable for midi??

Post by CrocoDuck »

briandc wrote:But it doesn't appear as a midi device. So is there no use for it as a potential midi controller?

Any input appreciated!
I think it depends on what the thing actually turns out to be. use dmesg to understand what kernel module is being used for the device. Chances are it is either a keyboard or a game pad. In both cases there should be programs to map their output to MIDI events.
User avatar
briandc
Established Member
Posts: 1442
Joined: Sun Apr 29, 2012 3:17 pm
Location: Italy
Has thanked: 58 times
Been thanked: 28 times
Contact:

Re: Konami playstation keyboard-- usable for midi??

Post by briandc »

CrocoDuck wrote:
briandc wrote:But it doesn't appear as a midi device. So is there no use for it as a potential midi controller?

Any input appreciated!
I think it depends on what the thing actually turns out to be. use dmesg to understand what kernel module is being used for the device. Chances are it is either a keyboard or a game pad. In both cases there should be programs to map their output to MIDI events.
I think it's a type of game pad (but having a mod wheel on the right is cool!).
What is the command to use with dmesg to get the necessary information?
And, how do I get it to connect as a midi controller if it doesn't appear as a midi device?


brian
Have your PC your way: use linux!
My sound synthesis biome: http://www.linuxsynths.com
CrocoDuck
Established Member
Posts: 1133
Joined: Sat May 05, 2012 6:12 pm
Been thanked: 17 times

Re: Konami playstation keyboard-- usable for midi??

Post by CrocoDuck »

briandc wrote:
I think it's a type of game pad (but having a mod wheel on the right is cool!).
What is the command to use with dmesg to get the necessary information?
And, how do I get it to connect as a midi controller if it doesn't appear as a midi device?
Boot up your computer with the device disconnected. Open a terminal and enter this command:

Code: Select all

dmesg -wH
This will show you the kernel ring buffer up the time you opened the console. The prompt will stay on and automatically update after each event. Insert your device in a port. You will see a bunch of new messages popping up at the bottom. Copy and paste them here. Fore example, this is what I get when I plug my wireless keyboard:

Code: Select all

[Feb 9 18:55] usb 2-2: new full-speed USB device number 13 using xhci_hcd
[  +0.184907] input: Compx 2.4G Receiver as /devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0/0003:25A7:FA61.0007/input/input25
[  +0.065738] hid-generic 0003:25A7:FA61.0007: input,hidraw0: USB HID v1.10 Keyboard [Compx 2.4G Receiver] on usb-0000:00:14.0-2/input0
[  +0.003974] input: Compx 2.4G Receiver as /devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.1/0003:25A7:FA61.0008/input/input26
[  +0.075949] hid-generic 0003:25A7:FA61.0008: input,hiddev0,hidraw1: USB HID v1.10 Mouse [Compx 2.4G Receiver] on usb-0000:00:14.0-2/input1
CrocoDuck
Established Member
Posts: 1133
Joined: Sat May 05, 2012 6:12 pm
Been thanked: 17 times

Re: Konami playstation keyboard-- usable for midi??

Post by CrocoDuck »

briandc wrote:And, how do I get it to connect as a midi controller if it doesn't appear as a midi device?
If it ends up being recognized as a joystick, maybe this will help:

https://github.com/osune/MidiJoystick

Or something here:

https://wiki.linuxaudio.org/apps/catego ... rtual_midi
ssj71
Established Member
Posts: 1294
Joined: Tue Sep 25, 2012 6:36 pm
Has thanked: 1 time

Re: Konami playstation keyboard-- usable for midi??

Post by ssj71 »

I maintain a userland driver for rockband drumkits and guitars and I implemented partial support for the rockband keyboard. This keyboard may work the same way or may only require simple changes. The first big thing is just getting it to connect.

If you copy this line: https://github.com/rbdrum2midi/rbdrum2m ... ain.c#L120

and add 0x0507, 0010 as the arguments and build you should be able to connect (read the readme about permissions, you can use sudo or create a udev rule).

Once its connecting you can try running with the -dbg flag and it will output whatever comes over the USB. From there we can figure out how the buttons respond.

I don't have a ton of time to work on this, but I'll try to help you through it. I'm pretty confident we could make it work as a midi device with rbdrum2midi, its just a question of how much additional development it will take.
_ssj71

music: https://soundcloud.com/ssj71
My plugins are Infamous! http://ssj71.github.io/infamousPlugins
I just want to get back to making music!
User avatar
briandc
Established Member
Posts: 1442
Joined: Sun Apr 29, 2012 3:17 pm
Location: Italy
Has thanked: 58 times
Been thanked: 28 times
Contact:

Re: Konami playstation keyboard-- usable for midi??

Post by briandc »

CrocoDuck wrote:
briandc wrote:
I think it's a type of game pad (but having a mod wheel on the right is cool!).
What is the command to use with dmesg to get the necessary information?
And, how do I get it to connect as a midi controller if it doesn't appear as a midi device?
Boot up your computer with the device disconnected. Open a terminal and enter this command:

Code: Select all

dmesg -wH
This will show you the kernel ring buffer up the time you opened the console. The prompt will stay on and automatically update after each event. Insert your device in a port. You will see a bunch of new messages popping up at the bottom. Copy and paste them here. Fore example, this is what I get when I plug my wireless keyboard:

Code: Select all

[Feb 9 18:55] usb 2-2: new full-speed USB device number 13 using xhci_hcd
[  +0.184907] input: Compx 2.4G Receiver as /devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0/0003:25A7:FA61.0007/input/input25
[  +0.065738] hid-generic 0003:25A7:FA61.0007: input,hidraw0: USB HID v1.10 Keyboard [Compx 2.4G Receiver] on usb-0000:00:14.0-2/input0
[  +0.003974] input: Compx 2.4G Receiver as /devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.1/0003:25A7:FA61.0008/input/input26
[  +0.075949] hid-generic 0003:25A7:FA61.0008: input,hiddev0,hidraw1: USB HID v1.10 Mouse [Compx 2.4G Receiver] on usb-0000:00:14.0-2/input1
Got it!
Here's what the terminal gave me:

Code: Select all

[Feb10 09:39] usb 3-2: new low-speed USB device number 2 using uhci_hcd
[  +0.162852] usb 3-2: New USB device found, idVendor=0507, idProduct=0010
[  +0.000010] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  +0.000007] usb 3-2: Product: USB Multipurpose Controller
[  +0.000005] usb 3-2: Manufacturer: KONAMI
[  +0.191850] hidraw: raw HID events driver (C) Jiri Kosina
[  +0.046615] usbcore: registered new interface driver usbhid
[  +0.000004] usbhid: USB HID core driver
[  +0.043049] input: KONAMI USB Multipurpose Controller as /devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2:1.0/0003:0507:0010.0001/input/input17
[  +0.052729] hid-generic 0003:0507:0010.0001: input,hidraw0: USB HID v1.10 Gamepad [KONAMI USB Multipurpose Controller] on usb-0000:00:1a.0-2/input0
[  +0.179166] [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:a292:bbfe:258a:d034 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=592034 PROTO=UDP SPT=8612 DPT=8612 LEN=24 
[  +0.000039] [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:a292:bbfe:258a:d034 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=776446 PROTO=UDP SPT=8612 DPT=8610 LEN=24 
[  +0.010391] [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:a292:bbfe:258a:d034 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=592034 PROTO=UDP SPT=8612 DPT=8612 LEN=24 
[  +0.000040] [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:a292:bbfe:258a:d034 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=776446 PROTO=UDP SPT=8612 DPT=8610 LEN=24
--Too bad it calls it a "low-speed device". Hopefully not *that* low! :lol:

brian
Have your PC your way: use linux!
My sound synthesis biome: http://www.linuxsynths.com
User avatar
briandc
Established Member
Posts: 1442
Joined: Sun Apr 29, 2012 3:17 pm
Location: Italy
Has thanked: 58 times
Been thanked: 28 times
Contact:

Re: Konami playstation keyboard-- usable for midi??

Post by briandc »

ssj71 wrote:I maintain a userland driver for rockband drumkits and guitars and I implemented partial support for the rockband keyboard. This keyboard may work the same way or may only require simple changes. The first big thing is just getting it to connect.

If you copy this line: https://github.com/rbdrum2midi/rbdrum2m ... ain.c#L120

and add 0x0507, 0010 as the arguments and build you should be able to connect (read the readme about permissions, you can use sudo or create a udev rule).

Once its connecting you can try running with the -dbg flag and it will output whatever comes over the USB. From there we can figure out how the buttons respond.

I don't have a ton of time to work on this, but I'll try to help you through it. I'm pretty confident we could make it work as a midi device with rbdrum2midi, its just a question of how much additional development it will take.
Hi ssj71, I really appreciate your input too. As you say, let's hope this doesn't require a lot of attention. Initially, when I figured out that it was a Playstation device, I thought I'd just get rid of it. But if it can connect, why not keep it? It's got mod wheels on both sides, and being just 2-octaves, it would be perfect for basic preset testing even while working on the couch! :D

Now I'm trying to build. (I added the line in the the "main.c" file as you recommended.)
I made a directory called "build" in the src directory, and did cmake, but maybe I'm in the wrong directory??
This is what I got:

Code: Select all

brian@brian-F9E:~/Tarballs/rbdrum2midi-master/src/build$ cmake ..
-- The C compiler identification is GNU 5.4.0
-- The CXX compiler identification is GNU 5.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1") 
CMake Error at CMakeLists.txt:11 (find_package):
  By not providing "FindJack.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "Jack", but
  CMake did not find one.

  Could not find a package configuration file provided by "Jack" with any of
  the following names:

    JackConfig.cmake
    jack-config.cmake

  Add the installation prefix of "Jack" to CMAKE_PREFIX_PATH or set
  "Jack_DIR" to a directory containing one of the above files.  If "Jack"
  provides a separate development package or SDK, be sure it has been
  installed.


-- Configuring incomplete, errors occurred!
See also "/home/brian/Tarballs/rbdrum2midi-master/src/build/CMakeFiles/CMakeOutput.log".

brian
Have your PC your way: use linux!
My sound synthesis biome: http://www.linuxsynths.com
CrocoDuck
Established Member
Posts: 1133
Joined: Sat May 05, 2012 6:12 pm
Been thanked: 17 times

Re: Konami playstation keyboard-- usable for midi??

Post by CrocoDuck »

briandc wrote:
Got it!
Here's what the terminal gave me:

Code: Select all

[Feb10 09:39] usb 3-2: new low-speed USB device number 2 using uhci_hcd
[  +0.162852] usb 3-2: New USB device found, idVendor=0507, idProduct=0010
[  +0.000010] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  +0.000007] usb 3-2: Product: USB Multipurpose Controller
[  +0.000005] usb 3-2: Manufacturer: KONAMI
[  +0.191850] hidraw: raw HID events driver (C) Jiri Kosina
[  +0.046615] usbcore: registered new interface driver usbhid
[  +0.000004] usbhid: USB HID core driver
[  +0.043049] input: KONAMI USB Multipurpose Controller as /devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2:1.0/0003:0507:0010.0001/input/input17
[  +0.052729] hid-generic 0003:0507:0010.0001: input,hidraw0: USB HID v1.10 Gamepad [KONAMI USB Multipurpose Controller] on usb-0000:00:1a.0-2/input0
[  +0.179166] [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:a292:bbfe:258a:d034 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=592034 PROTO=UDP SPT=8612 DPT=8612 LEN=24 
[  +0.000039] [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:a292:bbfe:258a:d034 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=776446 PROTO=UDP SPT=8612 DPT=8610 LEN=24 
[  +0.010391] [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:a292:bbfe:258a:d034 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=592034 PROTO=UDP SPT=8612 DPT=8612 LEN=24 
[  +0.000040] [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:a292:bbfe:258a:d034 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=776446 PROTO=UDP SPT=8612 DPT=8610 LEN=24
--Too bad it calls it a "low-speed device". Hopefully not *that* low! :lol:
Looks like we have a gamepad over there. Let's have a look at your loaded modules:

Code: Select all

lsmod
To make it work as a gamepad we will need to load usbhid (looks like it is already loaded and taking the device) and joydev (https://wiki.archlinux.org/index.php/Ga ... _joysticks).
ssj71 wrote:I maintain a userland driver for rockband drumkits and guitars and I implemented partial support for the rockband keyboard. This keyboard may work the same way or may only require simple changes. The first big thing is just getting it to connect.
Will loading joydev possibly conflict with your driver?
User avatar
briandc
Established Member
Posts: 1442
Joined: Sun Apr 29, 2012 3:17 pm
Location: Italy
Has thanked: 58 times
Been thanked: 28 times
Contact:

Re: Konami playstation keyboard-- usable for midi??

Post by briandc »

CrocoDuck wrote: Looks like we have a gamepad over there. Let's have a look at your loaded modules:

Code: Select all

lsmod
To make it work as a gamepad we will need to load usbhid (looks like it is already loaded and taking the device) and joydev (https://wiki.archlinux.org/index.php/Ga ... _joysticks).
Here are the modules:

Code: Select all

brian@brian-F9E:~/Tarballs/rbdrum2midi-master/src/build$ lsmod
Module                  Size  Used by
snd_hrtimer            16384  1
snd_seq_dummy          16384  32
snd_usb_audio         147456  5
snd_usbmidi_lib        28672  1 snd_usb_audio
hid_generic            16384  0
usbhid                 49152  0
hid                    98304  2 hid_generic,usbhid
drbg                   28672  1
ansi_cprng             16384  0
ctr                    16384  2
ccm                    20480  2
bnep                   20480  2
uvcvideo               77824  0
arc4                   16384  2
videobuf2_vmalloc      16384  1 uvcvideo
coretemp               16384  0
videobuf2_memops       16384  1 videobuf2_vmalloc
videobuf2_v4l2         28672  1 uvcvideo
btusb                  36864  0
videobuf2_core         36864  2 uvcvideo,videobuf2_v4l2
btrtl                  16384  1 btusb
iwl4965               114688  0
iwlegacy               90112  1 iwl4965
mac80211              671744  2 iwl4965,iwlegacy
btbcm                  16384  1 btusb
v4l2_common            16384  1 videobuf2_v4l2
cfg80211              507904  3 iwl4965,iwlegacy,mac80211
btintel                16384  1 btusb
bluetooth             479232  24 bnep,btbcm,btrtl,btusb,btintel
videodev              155648  4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2
joydev                 20480  0
asus_laptop            24576  0
media                  24576  2 uvcvideo,videodev
input_leds             16384  0
snd_hda_codec_hdmi     49152  1
sparse_keymap          16384  1 asus_laptop
serio_raw              16384  0
lpc_ich                20480  0
input_polldev          16384  1 asus_laptop
snd_hda_codec_si3054    16384  1
snd_hda_codec_realtek    73728  1
snd_hda_codec_generic    69632  1 snd_hda_codec_realtek
tpm_infineon           20480  0
snd_hda_intel          36864  0
snd_hda_codec         118784  5 snd_hda_codec_realtek,snd_hda_codec_si3054,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel
snd_hda_core           61440  6 snd_hda_codec_realtek,snd_hda_codec_si3054,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
shpchp                 32768  0
snd_hwdep              16384  2 snd_usb_audio,snd_hda_codec
binfmt_misc            20480  1
mac_hid                16384  0
ip6t_REJECT            16384  1
nf_reject_ipv6         16384  1 ip6t_REJECT
nf_log_ipv6            16384  5
xt_hl                  16384  22
ip6t_rt                16384  3
nf_conntrack_ipv6      20480  8
nf_defrag_ipv6         28672  1 nf_conntrack_ipv6
ipt_REJECT             16384  1
nf_reject_ipv4         16384  1 ipt_REJECT
nf_log_ipv4            16384  5
nf_log_common          16384  2 nf_log_ipv4,nf_log_ipv6
xt_LOG                 16384  10
xt_limit               16384  13
xt_tcpudp              16384  18
xt_addrtype            16384  4
nf_conntrack_ipv4      16384  8
cuse                   16384  3
nf_defrag_ipv4         16384  1 nf_conntrack_ipv4
xt_conntrack           16384  16
snd_aloop              24576  0
snd_pcm                94208  9 snd_hda_codec_si3054,snd_usb_audio,snd_aloop,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_core
snd_seq_midi           16384  2
snd_seq_midi_event     16384  1 snd_seq_midi
snd_rawmidi            28672  2 snd_usbmidi_lib,snd_seq_midi
snd_seq                57344  43 snd_seq_midi_event,snd_seq_dummy,snd_seq_midi
snd_seq_device         16384  3 snd_seq,snd_rawmidi,snd_seq_midi
snd_timer              32768  3 snd_hrtimer,snd_pcm,snd_seq
snd                    69632  21 snd_hda_codec_realtek,snd_hda_codec_si3054,snd_usb_audio,snd_aloop,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec_generic,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,snd_seq_device
soundcore              16384  1 snd
ip6table_filter        16384  1
ip6_tables             20480  1 ip6table_filter
parport_pc             32768  0
ppdev                  20480  0
nf_conntrack_netbios_ns    16384  0
nf_conntrack_broadcast    16384  1 nf_conntrack_netbios_ns
nf_nat_ftp             16384  0
lp                     20480  0
nf_nat                 24576  1 nf_nat_ftp
nf_conntrack_ftp       16384  1 nf_nat_ftp
nf_conntrack           98304  8 nf_nat_ftp,nf_conntrack_netbios_ns,nf_nat,xt_conntrack,nf_conntrack_broadcast,nf_conntrack_ftp,nf_conntrack_ipv4,nf_conntrack_ipv6
parport                45056  3 lp,ppdev,parport_pc
iptable_filter         16384  1
ip_tables              20480  1 iptable_filter
x_tables               24576  13 ip6table_filter,xt_hl,ip_tables,xt_tcpudp,xt_limit,xt_conntrack,xt_LOG,iptable_filter,ip6t_rt,ipt_REJECT,ip6_tables,xt_addrtype,ip6t_REJECT
autofs4                40960  2
ums_realtek            20480  0
uas                    20480  0
usb_storage            57344  2 uas,ums_realtek
i915                 1134592  3
ahci                   36864  2
r8169                  77824  0
psmouse               118784  0
libahci                32768  1 ahci
i2c_algo_bit           16384  1 i915
drm_kms_helper        139264  1 i915
syscopyarea            16384  1 drm_kms_helper
sysfillrect            16384  1 drm_kms_helper
sysimgblt              16384  1 drm_kms_helper
fb_sys_fops            16384  1 drm_kms_helper
pata_acpi              16384  0
drm                   311296  5 i915,drm_kms_helper
mii                    16384  1 r8169
fjes                   28672  0
video                  40960  2 i915,asus_laptop
I'll wait before using joydev to see what ssj71 says, if you think that's best. :)

brian
Have your PC your way: use linux!
My sound synthesis biome: http://www.linuxsynths.com
CrocoDuck
Established Member
Posts: 1133
Joined: Sat May 05, 2012 6:12 pm
Been thanked: 17 times

Re: Konami playstation keyboard-- usable for midi??

Post by CrocoDuck »

briandc wrote:I'll wait before using joydev to see what ssj71 says, if you think that's best.
joydev is already loaded by your system if you look at lsmod output. If it turns out that the module can handle the controller, then you can use one of the utilities I linked above to turn gamepad events into MIDI in case ssj71 driver fails to work.
ssj71
Established Member
Posts: 1294
Joined: Tue Sep 25, 2012 6:36 pm
Has thanked: 1 time

Re: Konami playstation keyboard-- usable for midi??

Post by ssj71 »

briandc wrote: Now I'm trying to build. (I added the line in the the "main.c" file as you recommended.)
I made a directory called "build" in the src directory, and did cmake, but maybe I'm in the wrong directory??
brian

ah yes you either need to make a build directory in rbdrum2midi-master OR use the one you already made in src by invoking

Code: Select all

cmake ../..
since its an extra directory in. Either way works.
_ssj71

music: https://soundcloud.com/ssj71
My plugins are Infamous! http://ssj71.github.io/infamousPlugins
I just want to get back to making music!
User avatar
briandc
Established Member
Posts: 1442
Joined: Sun Apr 29, 2012 3:17 pm
Location: Italy
Has thanked: 58 times
Been thanked: 28 times
Contact:

Re: Konami playstation keyboard-- usable for midi??

Post by briandc »

ssj71 wrote:
briandc wrote: Now I'm trying to build. (I added the line in the the "main.c" file as you recommended.)
I made a directory called "build" in the src directory, and did cmake, but maybe I'm in the wrong directory??
brian

ah yes you either need to make a build directory in rbdrum2midi-master OR use the one you already made in src by invoking

Code: Select all

cmake ../..
since its an extra directory in. Either way works.
Ok. Sorry for the delay!
Cmake went fine, then I tried sudo make install but got this:

Code: Select all

brian@brian-F9E:~/Tarballs/rbdrum2midi-master/build$ sudo make install
[sudo] password for brian: 
Scanning dependencies of target rbdrum2midi
[ 11%] Building C object src/CMakeFiles/rbdrum2midi.dir/jackdriver.c.o
[ 22%] Building C object src/CMakeFiles/rbdrum2midi.dir/main.c.o
/home/brian/Tarballs/rbdrum2midi-master/src/main.c: In function ‘find_rbdrum_device’:
/home/brian/Tarballs/rbdrum2midi-master/src/main.c:120:13: error: too many arguments to function ‘libusb_open_device_with_vid_pid’
     *devh = libusb_open_device_with_vid_pid(NULL, 0x1bad, 0x3330, 0x0507, 0010)
             ^
In file included from /home/brian/Tarballs/rbdrum2midi-master/src/mididrum.h:12:0,
                 from /home/brian/Tarballs/rbdrum2midi-master/src/main.c:21:
/usr/include/libusb-1.0/libusb.h:1381:36: note: declared here
 libusb_device_handle * LIBUSB_CALL libusb_open_device_with_vid_pid(
                                    ^
/home/brian/Tarballs/rbdrum2midi-master/src/main.c: In function ‘print_keys’:
/home/brian/Tarballs/rbdrum2midi-master/src/main.c:239:16: warning: format ‘%X’ expects argument of type ‘unsigned int’, but argument 2 has type ‘long unsigned int’ [-Wformat=]
         printf("Keys: %08X %02x\n",MIDI_DRUM->key_state,MIDI_DRUM->velocity);
                ^
src/CMakeFiles/rbdrum2midi.dir/build.make:86: recipe for target 'src/CMakeFiles/rbdrum2midi.dir/main.c.o' failed
make[2]: *** [src/CMakeFiles/rbdrum2midi.dir/main.c.o] Error 1
CMakeFiles/Makefile2:85: recipe for target 'src/CMakeFiles/rbdrum2midi.dir/all' failed
make[1]: *** [src/CMakeFiles/rbdrum2midi.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
brian
Have your PC your way: use linux!
My sound synthesis biome: http://www.linuxsynths.com
ssj71
Established Member
Posts: 1294
Joined: Tue Sep 25, 2012 6:36 pm
Has thanked: 1 time

Re: Konami playstation keyboard-- usable for midi??

Post by ssj71 »

sorry the line should read:

Code: Select all

*devh = libusb_open_device_with_vid_pid(NULL, 0x0507, 0x0010);
add that and try the build. Thanks for the persistence!
_ssj71

music: https://soundcloud.com/ssj71
My plugins are Infamous! http://ssj71.github.io/infamousPlugins
I just want to get back to making music!
User avatar
briandc
Established Member
Posts: 1442
Joined: Sun Apr 29, 2012 3:17 pm
Location: Italy
Has thanked: 58 times
Been thanked: 28 times
Contact:

Re: Konami playstation keyboard-- usable for midi??

Post by briandc »

ssj71 wrote:sorry the line should read:

Code: Select all

*devh = libusb_open_device_with_vid_pid(NULL, 0x0507, 0x0010);
add that and try the build. Thanks for the persistence!
Worked!
But... it looks like I have to be root to run it. :( And of course that means that I can't connect to Jack or access my home folder.
Maybe I should have run "make install" instead of "sudo make install?"
How can I fix it?


brian

PS. sorry for my perpetual newbie-ness!
Have your PC your way: use linux!
My sound synthesis biome: http://www.linuxsynths.com
Post Reply