4/29/2023 0 Comments Midi monitor raspberry pi![]() ![]() So if I have both the OP-Z and the Octatrack on pattern 2, when I press “previous” the OP-Z will understand the message and switch to pattern 1, and also issue a program change message to the Octatrack, switching it to 1 as well. But I have the Chocolate sending next/previous CC messages to the OP-Z, and the OP-Z will issue the corresponding program change to the Octatrack. Similarly, the Octatrack doesn’t support switching to the “next” or “previous” pattern you need to specify the pattern number. Without the Octatrack I wouldn’t be able to control the OP-Z transport, since you can’t send from the Chocolate the start/pause/stop messages that the OP-Z expects. This will start/restart and stop the Octatrack, and I have the Octatrack configured to send the transport to the OP-Z. To control the transport I have buttons A and B sending MIDI notes (34 and 33) on channel 16. I played with it today, and I was able to configure it to control both my OP-Z and my Octatrack:Ī: play/pause the transport on OP-Z and Octatrackī: stop the transport on OP-Z and OctatrackĬ: previous pattern on the OP-Z, corresponding pattern on the Octatrackĭ: next pattern on the OP-Z, corresponding pattern on the Octatrack Just thought I'd post this in case anyone else is crazy (read: stupid) enough to try to debug teensy USB stuff on the mac.I just got my Chocolate M-Vave, ordered from Aliexpress. I guess a USB protocol analyzer would be easier, but they're like $400. Since making USB devices is part of the reason I was interested in the Teensy, I suppose I need to figure out way to get Wireshark working. I'm going to try running Wireshark on my raspberry pi (as my primary development machine is a mac and I imagine that running Wireshark inside a virtual machine will just complicate matters). For instance, this one is I believe saying that the Teensy failed to send the HID raw report descriptor. My strategy so far has been to grep this output for the address assigned to the Teensy by the mac (which can very between pluggings) and then stare at it for along time to read the tea leaves. ![]() Thanks to Paul for all the effort and for providing such a great development environment with full source code.Ĭode: 2.097 IOUSBHIDDriver(IOUSBHIDDriver)::GetHIDDescriptor Final request failed err = 0xe000404fĢ.097 IOUSBHIDDriver(IOUSBHIDDriver)::start - super::start returned false!Ģ.097 IOUSBHIDDriver(IOUSBHIDDriver)::start - 0圆200000 aborting startupĢ.097 IOUSBPipe::AbortPipe I feel like I'm learning a ton just by hacking on it at this level. I noticed this post about debugging USB under linux, so maybe I'll just hook the teensy up to my raspberry pi and use that. I'm hoping for something that would let me see the raw USB traffic from/to my Mac for a specific device. I found USB Prober on the Mac and that's somewhat useful. I assume there's no real debugging tools at the teensy level (like remote gdb or something). I'd appreciate any suggestions on debugging tips. I'm again in this state where the teensy is recognized by the USB host but no data is transmitted (hid_listen just prints dots).ĭebugging this stuff is a bit of a pain. I'm now trying to get the USB-debug HID RAW stuff working (aka hid_listen). ![]() I'm honestly not sure what took so long, but I think ultimately I just needed to insert some delay before I started sending usb messages.Ĭode is here. I "borrowed" the code from teensy2 and massaged (read: hacked) it to work with the new usb mechanism. I succeeded in getting MIDI transmit to work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |