Posts by jwinarske

jwinarske · Feb 27th 2023

Quote from schoko

so this c module can later on be used to send in plain sysex and it communicates via usb to the kemper (as if you used rig manager)?

the usb commands would be the really interesting thing (use them instead of midi maybe) i have to try the install

Yes that would be one outcome.

These are the use cases I have on my radar:
1. Multi-platform (Linux/Mac/Windows)
2. Rust - requires upstream PR to usbr to support async / faster to mock up in C++
3. Use as generic MIDI device with host
4. Basic Android app (field support - backup/restore)

jwinarske · Feb 25th 2023

Decoder stuff pushed. Next is to accept plain SysEx, add transport, and transmit. I'll refactor packets.h into logical SysEx packets as part of that process.

It's not 100% stable yet, as I need to sort out how I want to do sync vs async packets.

jwinarske · Feb 24th 2023

Quote from Samjones

As far is i know the Profiler uses a NXP LPC2468 Processor and a NXP DSP56720

Thanks, that save me having to open my unit.

jwinarske · Feb 23rd 2023

I am at this point able to decode all the System Exclusive messages that happen as part of the RigManager exchange. Which the structure of all the packets are documented in the Midi guide. I'm printing out the raw (non-normalized) controller values.

What's not clear yet is what the blobs are used for. Maybe a DSP cache state.

Does anyone know of a hardware bill of materials (BOM) for the Profiler / Stage Profiler? I'm mostly interested in the SoC/CPU/DSP used.

jwinarske · Feb 23rd 2023

Looks like the function code data encoding matches the docs, the only difference is the function code response byte itself has swapped nibbles. Meaning the "functionality" of the function code response is determined by the high nibble - X0h. Lower nibble is fixed to 0h. Should be fairly straight forward to decode them all, as it's well documented in the MIDI manual.

jwinarske · Feb 22nd 2023

Quote from schoko

jwinarske
I am not sure if i can follow...
(EP1 is the part after "Access Music Electronics" and EP2 is after these,...?)
Access Music Electronics is some kind of standard...

As for Sysex messages and their length...
you can request multi paramters, which is quite essential(when requesting paramter and fx.. you want so save calls, but have to do more work on the receiving side.. -> especially if you want to collect a whole rig)

Did you record which action caused these messages, or is this at startup?

Display More

Search for "Access Music Electronics" in this link, and notice the byte sequence:
https://www.midi.org/specifica…m/manufacturer-id-numbers

The packet exchange I'm using is from Mac M1 USB Wireshark capture of RigManager connecting to Stage Profiler, wait until idle traffic, then close the RigManager. It syncs all of the parameters/strings/settings. The packets are in this header file:
https://github.com/jwinarske/kemprof/blob/main/packets.h#L22

The messages in this header are packed (more than one SysEx packet per USB bulk transfer in most cases) and it also includes a transport layer.

I'm planning to add a simple command line shell to test sending and receiving of SysEx messages. The library will add the transport layer, and queue transfers on the bus. You would just type in the string of the SysEx packet, and it would print the SysEx response. This makes discovering the SysEx packet structure easier.

jwinarske · Feb 22nd 2023

schoko After removing transport framing, and looking at your MIDI constants in . I'm now parsing 7-bit SysEx strings with SysEx ID equal to "Access Music Electronics". EP1 is "encoded" MIDI SysEx, not clear what EP2 is talking yet. Similar pattern as the ElevenRack.

A snippet of parsed receive packets:

Code

f00020330200600006158000000100000000000000000000000000000000000000000000000000000000000000000000000000000000000000f7

f000203302006000061340000000000000000010000000000000000100000000000000000000000000000000000000000000000000000001000000000000000000000000000000000f7

f000203300002007c4e0000000000000767a000000000f7

fbb17f01

f0002033000070000c1a404d7950726f66696c657200f7

f0002033000070000c1a414a6f656c2057696e6172736b6500f7

f000203300001007f7d0000f7

f000203300001007d30001f7

f000203300001007d30000f7

f000203300002007c4e00000000000000006000000000f7

f00020330000300003000f7

f00020330000300003000f7

f00020330200600006211000000030036000f7

f000203300001007f7d0000f7

f000203300001007f7e0002f7

f00020330200600006125d0000001f7

f00020330200600006125e0000002f7

f000203302006000060d2000000010005e0000031f7

f00020330200600006125c000000000010000002f7

f000203300002007f7f7f7f7f533a7f7f7f7f400004000f7

f000203300002007f80001f7

f000203300002007fc4000400040400004040004000407f7f900c00000000000000f7

f000203300002007f1f0000f7

f000203300002007f20000000000f7

Display More

A bit more work until I check that parsing in.

jwinarske · Feb 21st 2023

Cool. I have the transport pattern somewhat figured out. So grouping of logical packets (multiple USB packets) for TX/RX is next.

jwinarske · Feb 14th 2023

I have a basic cli app to start with:
https://github.com/jwinarske/kemprof

It mocks a rig manager connection, and receives real time packets from the profiler stage until closed.

Example output
```

$ ./profiler_cli

Using libusb v1.0.25.11692

Opening device 133e:0001

Device properties:

bus number: 3

port path: 3 (from root hub)

speed: 12 Mbit/s (USB FullSpeed)

Device descriptor:

length: 18

device class: 0

S/N: 3

VID:PID: 133E:0001

bcdDevice: 0100

iMan:iProd:iSer: 1:2:3

nb confs: 1

Reading string descriptors:

String (0x01): "Kemper"

String (0x02): "Profiler"

String (0x03): "..........."

Configuration descriptor:

total length: 46

descriptor length: 9

nb interfaces: 1

interface[0]: id = 0

interface[0].altsetting[0]: num endpoints = 4

Class.SubClass.Protocol: FF.FF.FF

endpoint[0].address: 01

max packet size: 0040

polling interval: 00

endpoint[1].address: 81

max packet size: 0040

polling interval: 00

endpoint[2].address: 02

max packet size: 0040

polling interval: 00

endpoint[3].address: 82

max packet size: 0040

polling interval: 00

04030904

String (0x04): "APP=PROFILINGAMP"

String (0x05): "OS=Release: 8.7.15.42312"

String (0x06): "CPUID=XXXXXXXX.XXXXXXXX.XXXXXXXX.XXXXXXXX"

String (0x07): "MAC=XXXXXXXXXXXX"

String (0x08): "MGR={XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}"

String (0x09): "DEF={XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}"

Configuration: 1

Interface claimed.

[Rx.1] length:64, actual_length:4

0x000000: fb b1 7f 01 ....

[Rx.1] length:64, actual_length:4

0x000000: fb b1 7f 01 ....

[Rx.1] length:64, actual_length:36

0x000000: 14 f0 00 20 14 33 00 00 14 07 00 00 14 00 0c 1a ... .3..........

0x000010: 14 40 4d 79 14 50 72 6f 14 66 69 6c 14 65 72 00 [email protected].

0x000020: 15 f7 00 00 ....

[Rx.1] length:64, actual_length:40

0x000000: 14 f0 00 20 14 33 00 00 14 07 00 00 14 00 0c 1a ... .3..........

0x000010: 14 41 4a 6f 14 65 6c 20 14 57 69 6e 14 61 72 73 .AJo.el .Win.ars

0x000020: 14 6b 65 00 15 f7 00 00 .ke.....

[Rx.1] length:64, actual_length:20

0x000000: 14 f0 00 20 14 33 00 00 14 01 00 7f 14 7d 00 00 ... .3.......}..

0x000010: 15 f7 00 00 ....