Search results

Yeah I left it at zero for now, so it's compatible with existing code, and keeps it the same as the MIDI library. I also tested my Midi keyboards from Novation, and Arturia which don't transmit release velocity, and they all send out Note Off's with a velocity value of Zero, so I guess using...

For now, I've just simply added this function to usb_midi.h /* Handle Note On Velocity 0 events as Note off (default behaviour). convert - Sets whether Note On Velocity 0 is converted to a Note Off (default = true). off_velocity - Optionally sets the Release Velocity (0-127) of the...

Good point with the release velocity being 64! So a Midi receiver like a synth (which is capable of recognising Note Off velocity) receives a Note On Vel 0 it is supposed to treat that as a Note Off Vel 64 (as per Midi Spec) So I guess if the Midi libraries mentioned above are converting Note...

On a side note.... Is it possible using USBHost_t36 to determine how many virtual ports (or cables) a USB Midi device has? ...and also the port names perhaps? TIA

Nevermind, think I figured it out..... Looks like it uses the same cable numbering system that's used for usbMidi so all good.

Hello, Is it possible to use the USBHost_t36 library with USB Midi devices that have multiple ports? So for instance I have a single USB Midi Interface device that when plugged into my PC it shows up as multiple ports (or virtual cables). I've not much experience with using USBHost_t36 for...

It's actually part of the Midi Spec that Note On Vel 0 will always be considered as a Note Off event, and all Midi devices 'should' be able to cope with it, and treat it as such. It is to help with 'Running Status' (which isn't really relevant though for USB Midi). For the Midi library you can...

I was looking at this the other day.... I think Kurt's table is correct. If you scroll down further on that Spark Fun webpage, there is the larger complete pin out table for the MicroMod connector which does match Kurt's pin out. This also contradicts that SparkFun table that you posted, which...

There's an option in the settings on the Digitakt to set it's USB out to Midi Only: System>>USB config You could try that if you haven't already. Think by default it's set to Audio/Midi

Is it the Red or Orange LED that flashes? I had a situation recently where the program button seemed to randomly not function when trying to upload something. It started working again after a reboot of my PC... Might be worth trying if you haven't already.

@jmarsh Awesome thanks! That looks much neater. I also must of forgot to put the break in there.

Hello again. I seem to have this all working. Slightly modified so I can keep track of held notes across all Midi Channels, and added a couple of defensive checks in there. Also double checked about Note On Velocity Zero, and both the MIDI & usbMidi libraries automatically account for this...

Thanks everyone! @jmarsh Thank you. I will definitely give this a go, but it looks like this is the trick that I was missing. @MarkT I will definitely be adding some defensive code in there. I know how finicky MIDI can be sometimes, and have been caught out before, so I will be adding a few...

Hello, So I have a MIDI project where I need to keep track of what MIDI notes are currently being held down. For instance if notes 40, 50, 60 were pressed (in that order) I would like to be able to quickly retrieve this info. Then say if note 50 was released, then I would get just notes 40 &...

Indeed.... Which is why I would expect getChannel() to return zero for any System Real Time Midi message. This is how it works with the regular MIDI library..... from MID.hpp: /*! \brief Get the channel of the message stored in the structure. \return Channel range is 1 to 16. For non-channel...

Ok.... it seems that usbMidi.c treats reatime Midi messages (start, stop, clock etc) as regular channel messages , and uses their byte value to try to determine a Midi channel.... int usb_midi_read(uint32_t channel) { uint32_t n, ch, type1, type2, b1; n = usb_midi_read_message()...

Hello, Been having some trouble getting realtime Midi messages (clock, stop, start etc) from USB Midi working as expected. Basically my code was looking for what channel a Midi Message is sent on. I use usbMidi.read followed by usbMidi.getChannel() to check for a realtime message like clock...

Thanks for this.... Unfortunately this didn't work... I replaced the DMA core files you posted, and tried your ST7735_t3 library, but it kinda made things worse. Whilst I could still see what I had originally on the display, it was mixed with a lot of static snow, and lots of noticeable screen...

Hello, I'm working on a project that uses both the ST7735_t3 & OctoWS2811 library. I've setup the ST7735 to use a frame buffer, I'm using Async updates using updateScreenAsync(), and I've got a few Led's being controlled using the Octo library. For the most part everything works fine. The...

Thanks.... Looks like all Serial ports are available then... Just Serial 2 & 4 are swapped. 👍🏼

Hello, Looking at the MicroMod for my next project, but I need as many hardware Serial Ports as possible. The MicroMod pinout only shows 2 Serial Ports: Serial1: UART_RX1 (Teensy Pin 0) UART_TX1 (Teensy Pin 1) Serial2: UART_RX2 (Teensy Pin 16 Serial4 on Teensy4) UART_TX2 (Teensy Pin 17 Serial4...

What you've got should be good I think. You may have to monitor the Midi input so you don't switch whilst a Midi message is being received, and maybe send an all notes off message after the switch, or you could potentially get stuck notes. You could also do all the switching In code too and...

Looks great! Just a thought... but wouldn't a 74HCT14N be a better choice instead of the HC variant if you are powering it from 5v and feeding it 3v3 logic?

I had similar issues recently with the same DIYMore display. I could never figure out what the problem was but my Teensy 4.0 did not seem to like it. I put it down to a defective display in the end, as I had no previous issues using Waveshare SSD1309 displays using the same code from the u8g2...

Forgot to mention that Microsoft should be releasing an updated Midi Driver soon that will hopefully allow assigned port names to show up in MIDI programs (fingers crossed) https://devblogs.microsoft.com/windows-music-dev/announcing-windows-midi-services-customer-preview-1/

From my experience I believe that the port names not showing is down to Windows. My Teensy Midi projects that have Port names assigned do not display the Port names on Windows machines, but they do correctly display in Linux (and I assume Macs too). The Windows format will always be: MidiDevice...

Did you change the PID/VID? Might be worth posting the config of your custom USB device, just in case there could be an issue there.

I did ask the same question recently: https://forum.pjrc.com/index.php?threads/how-do-i-disable-the-seremu-usb-interface.75849/ It seems that a lot of other places rely on SEREMU_INTERFACE (or CDC) being defined in usb_desc.h or you will get the sort of errors that you are getting. I did...

Hello.. I'm working on a Teensy based Midi device, and I'm looking for suitable buffer IC's for the Midi out circuit. Typically for prototyping I'd just use a 74HC14 inverter, and just double up on the inputs, but I'm potentially gonna have 8 Midi outputs, which would mean three 74HC14's. I've...

My goal is to have just a USB MIDI Device, without any other additional interfaces added. The SEREMU interface (HID) gets added automatically when selecting the USB type as Midi. Like I said I've already tried just commenting out the #define SEREMU_INTERFACE in the Midi section of usb_desc.h...

I'm working on a Teensy4 USB MIDI device, and I would to disable the SEREMU USB interface, but I'm not sure what's the best way to do this? I've tried commenting out #define SEREMU_INTERFACE in the usb_desc.h file, but that will cause lots of errors like...

Also spotted another slight discrepancy between Teensy4's MIDI descriptor & MIDI 1.0 In this file, on lines 931 & again at 1945: https://github.com/PaulStoffregen/cores/blob/master/teensy4/usb_desc.c LSB(7+(6+6+9+9)*MIDI_NUM_CABLES), // wTotalLength MSB(7+(6+6+9+9)*MIDI_NUM_CABLES), The...

So I noticed that this file (on line 122): https://github.com/PaulStoffregen/cores/blob/master/usb_midi/usb.c It says that adding the AC interface has caused MIDI to fail on Linux. So I guess the AC interface has continually been omitted because of this. So just for my own personal curiosity...

Had a quick look at the schematic for the OLED, and I don't think you should be powering it by 5v at VIN. The i2c lines are connected to VIN via a resistor, and I'm pretty sure the Teensy won't like that. That OLED can be powered by 3.3v (at VIN) so I would stick with that to be safe. Hopefully...

Do you have a link to the OLED display that you have? Might be a powering issue. You're also using software i2c (SW_I2C), not hardware (HW_I2C). Is that intended? Also: Pin 18 is usually data. Pin 19 is usually clock. Not sure if that would matter with software i2c though.

Hello, I'm trying to get my head around theUSB descriptors for my Teensy 4, particularly for a MIDI device. I think I'm getting there, but I have a quick question.... I've read the MIDI 1.0 USB Device class definition, and on the example device it gives, it says to also include an Audio...

Firstly....I'm no expert, but do both Teensy's share the same USB vid/pid? Are they both programmed as the same USB device in the tools menu? Windows seems to sometimes get confused if you plug two usb devices with the same VID/PID. I haven't explored this extensively, but have seen this with...

Thank you! That worked perfectly!

Hello, Is it possible to edit the .hex file somehow? I have two different Teensy based USB Midi devices that have the same VID/PID which can be an issue, so I was trying to see if I could change these. I've looked at the .hex files of each of these devices, and I can see the data bytes that...

Woah! Woah! Slow down there. You're shorting Ground to 5v!!! Remember that the numbered rows on a breadboard are electrically connected. No wonder your Mac ain't liking it. Remove that ground wire next to the cap, and just put the capacitor across pin 5 and pin 8 of the 6N138. But I'd double...