ithinu

I have the latest UDEV rules for teensy, the same which you listed, and there are no other UDEV rules in /etc/udev/rules.d/. I think that these rules are correctly set. My guess: Someone took T3.6, made a product (?) out of it named Niteto...

Thank you Nantonos, but what it has to do with libmtp? See the two last lines of the log. Maybe it does, because MTP shows these dialogs only after MIDI is enabled. A problem with teensyduino? A problem with libmtp? Whatever else?

Fortunately Teensy can be restored by using the button so I made some tests and it turned out that this: void startup_early_hook() { } is already enough to freeze Teensy 3.6, even that it should work according to the documentation. Maybe...

It turned out, T3.6 usb id is registered in libmtp database.

I added the code above to my sketch, after #include "usb_names.h". The T3.6 is dead now, as in no reaction in syslog after a connection.

Hi, I have a Teensy 3.6 project with some references to usbMIDI. When I select the port type Serial and comment out these references, the device connects properly as Serial. However, when I change the port type to Serial + MIDI, the device...

Would it work as a weak pull-up in 3.6? The wires have less than 10 cm. digitalWrite(SCL, 1); digitalWrite(SDA, 1); edit: It got stranger, the above makes the workaround loop run twice each time, while digitalWrite(SCL, 0)...

You may be right @mjs13, I assumed that 3.6 uses internal pull-up resistors on its I2C bus, just like 4.1 does. I'll add external ones and hopefully I won't need my suspicious workaround anymore. I'll write tomorrow.

@ithinu Ok just found a BNO085 from adafruit and hooked up to a Teensy 3.6 and used the latest Adafruit BNO08X library. Setup was hooking up I2C via the QWIIC connector to wire using pins 18/19 and adafruit skethces worked with mods to either...

Ok works, my fault.

I am trying to use the Adafruit's BNO085 board, their library and a Teensy 3.6. - directly after an upload in Arduino: works in 70%, in 30% shows "I2C address not found" - if plugged into a power supply via USB: works in 100% However, once it...

Looks interesting. Something for earphones with a binaural microphone, I guess.

Thank for pointing it out, but it's a code which illustrated a different problem. Later I corrected it as you suggested, yet it did not work. As for getting rid of these direct references to AUDIO_BLOCK_SAMPLES in F32, it makes sense, but I have...

This will be updated when i'll have time to get through all the new components and add the separate constructors using settings. The plate reverb should actually work, since in the update function uses the block->length instead of...

I use AudioConnection_F32 everywhere. I already removed all F16 components. Modifying AUDIO_BLOCK_SAMPLES in AudioStream.h works fine with F32 even for small values like 4 if only the set of components AudioInputI2S_F32, AudioOutputI2S_F32...

Thanks, works well. However, I would also like to decrease the number of audio blocks. In the case of F16, at least some time ago, one needed to modify files outside the sketch, either AudioStream.h or platform.txt. Anyways, it only worked for...

Hi, The second one doesn't work because, in your setup(), you only allocated AudioMemory_F32. If you are using the non-F32 audio library (which is the regular Teensy Audio Library), you also need to explicitly give it some memory, too. So...

Hi, I cannot make the I16 -> F32 conversion work. For example, this does play the sine: #include <Audio.h> #include <OpenAudio_ArduinoLibrary.h> AudioControlSGTL5000 audioShield; AudioSettings_F32 audio_settings(44100, 128); AudioOutputI2S_F32...

Yes. It is /etc/udev/rules.d/00-teensy.rules: ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04*", ENV{ID_MM_DEVICE_IGNORE}="1", ENV{ID_MM_PORT_IGNORE}="1" ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789a]*", ENV{MTP_NO_PROBE}="1"...

I would like to use Pico as a display driver for Teensy. But it turns out, while unplugging Teensy, then plugging Pico (the same USB port), then moving to the Pico sketch and uploading works flawlessly, it does not so in the other direction...

Mark, it's only your will to guess that helped me here. Otherwise, I might still be stuck. Thanks again. Moreover, I'd say that the problem is with the public API and not with your interpretation.

@ithinu: I had another look at your sketch in post #21 above, and this time I may have found something for you to look at. I don't believe that you should be making a call to hostMidi.begin() in your setup(). AFAIK, the only calls that you...

Hi Mark, yes that helps but I used your example at https://forum.pjrc.com/index.php?threads/t4-using-usb-host-with-midi.66835/post-275864 MIDIDevice_BigBuffer usbhostMIDI(thisUSB); ... usbhostMIDI.setHandleNoteOn(USBhandleNoteOn); ... // start...

USBHost or the MIDI driver? The USB host demo which uses multiple drivers to recognize different devices (but not the MIDI driver) did not hang after connecting a MIDI device. Also, the loop while(!hostMidi); did not hang when connecting one...

I was hoping for some debugging hints so that I could find out for myself. Like, where to look into for printf debugging. Seeing no such suggestion, I asked myself if it is really the same subject or I wrote to some unrelated thread from January...

Hi, I posted the problem details to an old thread https://forum.pjrc.com/index.php?threads/usb-host-library-midi-hanging.74203/ as it seemed a possibly related issue but maybe not and now I do not know if the lack of reaction is because no one...

I made Teensy stuck with its USB host and then suspended an Ubuntu system to which Teensy was connected. An hour later I tried to wake the system up. It woke up, then apparently freezed. So I reset the computer. BIOS was booting up longer than...

I defined USBHOST_PRINT_DEBUG in USBHost_t36/midi.cpp (required the removal of the two print_hexbytes inside) and that's what gets printed before the freeze: MIDIDevice claim this=20002220 len = 150 MIDIDevice claim this=20002220 len = 115...