![]() ![]() 40 8-Bit fields with range from 0 to 255 (Display?).10 8-Bit fields with range from 0 to 255 (Display?).27 8-Bit fields with range from 0 to 255 (Display?).39 8-Bit fields with range from 0 to 255.28 8-Bit fields with range from 0 to 255.3 8-Bit fields with range from 0 to 255.32 further 16-Bit fields with range from 0 to 4095 (could be Gain or EQ-Knobs).7 16-Bit fields with range from 0 to 4095 (most likely the faders and pitch sliders).6 4-Bit Inputs with Range from 0…15 (most likely the infinite rotary knobs for beatjump, loopsize and track selection).The HID Report Descriptor of the S4 MK3 tells us that there are: Does the shorter part of the split packet always start with the same byte? If not, it’s not a real HID packet and something weird is going on either at the OS level or in hidapi. On to your question about the split HID packets, the Kontrol S4 Mk2 has the same issue on Linux and the mapping has a workaround to concatenate the split packets together. That said, if you want to start on a mapping anyway and post it here, you’re welcome to do so. Second, the common-hid-packet-parser.js library is really messy code and if you try to make a mapping with it, the mapping code will be messy. So I don’t think we’d include a mapping for this controller in Mixxx until we solve that problem in the new mapping system. The speed of the audio would wobble with the wheel turning at a steady speed. First, the current implementation of jog wheel scratching is inadequate for motorized jog wheels. I am not going to map it with the current mapping system for a few reasons. However, I got it as motivation to work on the new controller mapping system, which is a long term project. I have had this controller sitting on my desk waiting to be reverse engineered for some months now. I’ve tried to find an example but was not sure what to look for. First byte is at the end of the 60 bytes packet, and the second byte at the beginning of the 15 byte packet. Now here’s the thing that confused me: the state of the leftmost mixer FX knob is split across the two packets. The 15 bytes packet contains: the Mixer knobs of the FX section in the middle and the top right FX knobs. When I use the sliders and closed knobs though, I think I get a 60 bytes packet (like the one that is constantly sent by the controller) plus a 15 bytes packet. So far, so good, looks like some effort but in general doable. ![]() If I press a button, I get a 23 bytes packet containing buttons and the open knobs (move, loop, browse). Now what I see it constantly spams 60 bytes wide packets which contain some ongoing changes (tick values? not sure at this point) as well as most of the slider/knob values. I’ve had a look at the HID packets from the controller. I’m not sure if anything will ever come from this with time being an issue all the time … but I’d like to ask a question. I’ve just had a bit of spare time this weekend and wanted to have a look if I can wrap my head around a mapping for the above. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |