8 Aug
2015
8 Aug
'15
3:46 p.m.
Hi
I'm trying to spy on the SYSEX being send between the proprietary
Arturia software (Midi Control Center) running inside virtualbox and my
beatstep pro.
When I enable the device in virtualbox, it seems to disappear from the
linux file system, /proc/asound/card2 ceases to exist and the beatstep
pro disappears from qjackctl's alsa tab.
Is there a way to monitor the trafic traveling to/from the beatstep pro
or to/from virtualbox?
Cheers
--
Atte
http://atte.dk http://a773.dk
8 Aug
8 Aug
3:55 p.m.
Am 08.08.2015 um 15:46 schrieb Atte:
Is there a way to monitor the trafic traveling to/from
the beatstep pro
or to/from virtualbox?
Is there a way to select the MIDI interface within the Arturia midi
control center? If so, you could install some virtual MIDI device driver
in the VM, e.g. MIDI Yoke, and then use midi-ox to connect a virtual
MIDI cable to the MIDI interface and the the control center and monitor
the messages.
Chris
9 Aug
9 Aug
12:23 p.m.
On 08/08/2015 03:55 PM, Christopher Arndt wrote:
Am 08.08.2015 um 15:46 schrieb Atte:
No, it's a select box that has the options of various Arturia hardware,
at the top under "connected" it says BeatStep Pro, the others are
labeled "disconnected" (The beatstep pro is the only arturia gear I have).
Is there a way to monitor the trafic traveling
to/from the beatstep pro
or to/from virtualbox?
Is there a way to select the MIDI interface within the Arturia midi
control center? If so, you could install some virtual MIDI device
driver
in the VM, e.g. MIDI Yoke, and then use midi-ox to connect a virtual
MIDI cable to the MIDI interface and the the control center and monitor
the messages.
I also installed a midi monitor (midi-ox) in windows, but if I connect
the beatstep, the arturia MCC fails to find the beatstep pro.
--
Atte
http://atte.dk http://a773.dk
8 Aug
8 Aug
4:06 p.m.
Atte wrote:
I'm trying to spy on the SYSEX being send between
the proprietary
Arturia software (Midi Control Center) running inside virtualbox and my
beatstep pro.
When I enable the device in virtualbox, it seems to disappear from the
linux
USB devices cannot be shared between host and VM.
Please show the output of "lsusb -v" for this device.
Regards,
Clemens
9 Aug
9 Aug
12:30 p.m.
On 08/08/2015 04:05 PM, Clemens Ladisch wrote:
Atte wrote:
Ok. I was just hoping to "listen in" on the traffic. I imagined the bits
must be running somewhere in my linux system, even though it show up in
virtualbox.
I'm trying to spy on the SYSEX being send
between the proprietary
Arturia software (Midi Control Center) running inside virtualbox and my
beatstep pro.
When I enable the device in virtualbox, it seems to disappear from the
linux
USB devices cannot be shared between host and VM. Please show the output of "lsusb -v" for
this device.
Bus 002 Device 007: ID 1c75:0287
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1c75
idProduct 0x0287
bcdDevice 1.00
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 133
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 1 Audio
bInterfaceSubClass 1 Control Device
bInterfaceProtocol 0
iInterface 0
AudioControl Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 1 (HEADER)
bcdADC 1.00
wTotalLength 9
bInCollection 1
baInterfaceNr( 0) 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 1 Audio
bInterfaceSubClass 3 MIDI Streaming
bInterfaceProtocol 0
iInterface 0
MIDIStreaming Interface Descriptor:
bLength 7
bDescriptorType 36
bDescriptorSubtype 1 (HEADER)
bcdADC 1.00
wTotalLength 95
MIDIStreaming Interface Descriptor:
bLength 6
bDescriptorType 36
bDescriptorSubtype 2 (MIDI_IN_JACK)
bJackType 1 Embedded
bJackID 1
iJack 4
MIDIStreaming Interface Descriptor:
bLength 6
bDescriptorType 36
bDescriptorSubtype 2 (MIDI_IN_JACK)
bJackType 2 External
bJackID 2
iJack 0
MIDIStreaming Interface Descriptor:
bLength 6
bDescriptorType 36
bDescriptorSubtype 2 (MIDI_IN_JACK)
bJackType 1 Embedded
bJackID 5
iJack 6
MIDIStreaming Interface Descriptor:
bLength 6
bDescriptorType 36
bDescriptorSubtype 2 (MIDI_IN_JACK)
bJackType 2 External
bJackID 6
iJack 0
MIDIStreaming Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 3 (MIDI_OUT_JACK)
bJackType 1 Embedded
bJackID 3
bNrInputPins 1
baSourceID( 0) 2
BaSourcePin( 0) 1
iJack 3
MIDIStreaming Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 3 (MIDI_OUT_JACK)
bJackType 2 External
bJackID 4
bNrInputPins 1
baSourceID( 0) 1
BaSourcePin( 0) 1
iJack 0
MIDIStreaming Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 3 (MIDI_OUT_JACK)
bJackType 1 Embedded
bJackID 7
bNrInputPins 1
baSourceID( 0) 6
BaSourcePin( 0) 1
iJack 5
MIDIStreaming Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 3 (MIDI_OUT_JACK)
bJackType 2 External
bJackID 8
bNrInputPins 1
baSourceID( 0) 5
BaSourcePin( 0) 1
iJack 0
Endpoint Descriptor:
bLength 9
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
bRefresh 0
bSynchAddress 0
MIDIStreaming Endpoint Descriptor:
bLength 6
bDescriptorType 37
bDescriptorSubtype 1 (GENERAL)
bNumEmbMIDIJack 2
baAssocJackID( 0) 1
baAssocJackID( 1) 5
Endpoint Descriptor:
bLength 9
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
bRefresh 0
bSynchAddress 0
MIDIStreaming Endpoint Descriptor:
bLength 6
bDescriptorType 37
bDescriptorSubtype 1 (GENERAL)
bNumEmbMIDIJack 2
baAssocJackID( 0) 3
baAssocJackID( 1) 7
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 8
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 8
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 1 Keyboard
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.00
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 30
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
--
Atte
http://atte.dk http://a773.dk
4:44 p.m.
Atte wrote:
This is a plain MIDI device, and there is no other obvious mechanism to
access the device, so it is likely that the software uses MIDI for its
vendor-specific stuff.
Anyway, Virtualbox uses the Linux API to access the real USB controller,
so it should be possible to use usbmon:
https://www.kernel.org/doc/Documentation/usb/usbmon.txt
On 08/08/2015 04:05 PM, Clemens Ladisch wrote:
Virtualbox knows about that data, but it has no interface for you to
access it.
Atte wrote:
Ok. I was just hoping to "listen in" on the traffic. I imagined the bits
must be running somewhere in my linux system, even though it show up in
virtualbox. When I enable the device in virtualbox, it seems
to disappear from the
linux
USB devices cannot be shared between host and VM. Please show
the output of "lsusb -v" for this device.
AudioControl Interface Descriptor:
baInterfaceNr( 0) 1
Interface Descriptor:
bInterfaceClass 1 Audio
bInterfaceSubClass 3 MIDI Streaming
bInterfaceProtocol 0 bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bInterfaceNumber 0
I guess this is from some other device?
Regards,
Clemens
3396
days inactive
3397
days old
linux-audio-user@lists.linuxaudio.org
5 comments
3 participants
participants (3)
-
Atte -
Christopher Arndt -
Clemens Ladisch