Search results

Meanwhile, I found the answers :)

Here's the datasheet I'm referring to: https://www.mouser.de/datasheet/2/291/NHD-0420CW-AY3-587980.pdf

Question to iniitu Hi iniitu, I'm an electronics newbie and was very glad to find your post. I try to get this display to run and would like to understand your reasoning. I try to understand your setup based on the data sheet. Most of it is clear. I have three little questions though: 1...

Michael, thanks again for your help. It took me some time to get to the project, but it worked like a charm, TeensyView on Teensy 4.1 with audio shield :)

Yes Frank, that would indeed be incredibly helpful. Display with onboard Teensy, SD slot and headphones out would be an amazing package...

Well, I don't have to use the SD card on the audio board at all. So if I read the schematic right, I "just" need to remove the 10k resistor that connects Pin 10 to 3.3V, and not call SD.begin(10) in my code.

One more thing after studying your pin suggestions: According to the Audio Board pin list for Teensy 4.x, pin 20 is used for audio data. Does it make sense to move the CS pin of the TeensyView to the other option, pin 10, in that case? Or am I getting something wrong?

Awesome! I think I get an understanding how that works, will give it a try with the TeensyView. Thanks again!

Hi Michael, thank you very much for your reply! Just to be sure, the pin assignments you wrote above are meant for the TeensyView, correct? I'm trying to match that with the hookup guide. Then I guess MOSI is the same as DATA, but which would be the correct pin for RST? 15 or 2? Using these...

Hi all, first off, I'm not a hardware guy and try to avoid cables, connectors and stuff like that as much as possible to reduce the number of things that can break when performing on stage. In the past, I've used a Teensy 3.6 with the Audio Shield and the TeensyView display as my MIDI...

I can confirm: the MIO-XL can host the Teensy 4.0 with 4 virtual ports no problem, and even reprogramming works without hitting the physical programming switch. Nice!

Let me state here for future reference, that all these issues are fixed with a Teensy 4.0. The MIO-XL can host the Teensy with 4 virtual ports no problem, and even reprogramming works without hitting the physical programming switch. Nice!

@PaulStoffregen, is there a way to disable the SEREMU_INTERFACE in a USB descriptor for the sake of compatibility without breaking code at other places (e.g. Serial being undefined in libraries/SD/utility/SdFile.cpp)?

I have updated my patch for the 2-MIDI-port Teensy at the mio-M/XL to match the current Teensy 3.6 software, please see this newer thread.

Updated patch for a 2-MIDI-Port Teensy on Mio-M/XL Hello, friends of the mio-Interfaces, A change in the Teensy 3.6 software broke my patch that made the Teensy work with the iConnectivity mioXL. I'd even say it's a new bug in the Teensy software, since disabling the SEREMU_INTERFACE define...

Hi Martin, I've played with your solution but could not get it to work. Even worse, after updating Teensyduino, my solution of stripping the MIDIx4 down to two ports doesn't work either. I noticed that USB_MIDI4 now also includes the serial emulation, although it shouldn't. If I comment the...

Hi Martin, sounds like you got some deep insights there! Do you have a fix that you could share? Best, Boris

Hi, yes, that's consistent with my experience. After lots of experimenting, the best I could achieve for the Teensy as USB MIDI client was 2 virtual ports with the serial protocol deactivated. Loosing the serial is an annoyance, because the physical reset switch must be in reach, which sucks if...

Just a short update - the July-2020 firmware upgrade (v 1.2.0) for the MIO-XL or MIO-XM doesn't help. Still only 2 port MIDI, no serial.

This is devastating me... I've connected another 4-port MIDI interface to the MIO-XL, it's recognized without problems. Then I tuned the Teensy's USB descriptor to match the one of the 4-port interface as close as possible. This involved changing the order and ids of jacks and endpoints, adding...

I noticed something else: the Teensy is lacking both the "AudioControl Interface Descriptor" as well as the "Standard AC Interface Descriptor" contained in it. Quoting from the specs (B.3): And indeed we see the Audio Control descriptor not only in the Yamaha descriptor, but also in the other...

You're right, the USB MIDI specification demands that wTotalLength in the Interface Header descriptor is the And the size of the endpoints seem to miss in the calculation, just as you said. So line 691 of cores/teensy3/usb_desc.c must be: LSB(7+(6+6+9+9)*MIDI_NUM_CABLES +...

Thanks, I'll look into that!

Hi all, following up on this thread (https://forum.pjrc.com/threads/57569-Does-Serial-Midi-%E2%89%A0-Class-Compliant), I did some more investigations to get clear on what the connectivity problem is. I really like the MIO-XL for its plethora of USB host ports. I want to use it as centerpiece...

There we go, this is "lsusb -v" for the MIO-XL: Bus 001 Device 005: ID 2321:0026 Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface...

Another small step forward: While reducing NUM_CABLES to 3 caused the MIO-XL to detect the Teensy and send MIDI data from MIO-XL to the Teensy (but not vice versa), reducing NUM_CABLES even to 2 gives me bi-directional traffic! Very nice. But how could I increase the NUM_CABLES without loosing...

Hi Pat, were you able to solve this problem? I'm working on it, see https://forum.pjrc.com/threads/57569-Does-Serial-Midi-%E2%89%A0-Class-Compliant Best, Boris

One step forward: While trying to bring the USB setup of the Teensy MIDIx4 closer to my Yamaha MODX, I switched MIDI_NUM_CABLES from 4 to 3 in line 390 of usb_desc.h. This helped, the MIO-XL detects the teensy and shows all three ports. Even with the other USB protocol used for programming the...

Here are some new insights: I have edited usb_desc.h and commented out the line 382, which adds the SEREMU_INTERFACE to the USB_MIDI4 definition: #elif defined(USB_MIDI4) ... #define NUM_INTERFACE 1 // <-- also tried the previous value 2 here //#define SEREMU_INTERFACE 1 //...

Alright, here's the lsusb -v from the Yamaha MODX. It's substantially longer than the one of the Teensy USB-MIDIx4, probably because it also has USB-Audio capabilities besides the 3 USB-Midi Ports. Which is interesting, since this is an example of a device that's not MIDI-only and still works...

It does, but I need the multiport (MIDIx4) functionality for my project. Alright, I'll look into the file, thanks!

Hi Paul, thanks for getting back so quickly. I think you're right, I believe that the company is referring to this on one of their support pages...

Hi guys, any news on this issue? I just got the new iConnectivity MIO-XL and it has the same issue: the teensy is not recognized in MIDIx4 mode, only in MIDI mode (single port). My Yamaha ModX keyboard works fine (3 ports recognized). Is there any way I can help fix this? I know some C, but no...