Search results

Edited link above.

More info here:- http://www.hardwarebook.info/S/PDIF_output

Perhaps when uploading, Windows does not have enough time to sort out the initial device disconnect (Cache flushes included) before Teensy usbMIDI is back online pestering Windows for a connection.. Make sure all your stuff is backed up!

Fell into a rabbithole remarkably similar to this a while ago. Synth Host system,Win7, Reaper, Presonus, MIO-10 and MidiSport usb-Midi interfaces and my Teensy usbMIDI project. Everything worked until adding and using the IDE. From a cold start, Win7, Reaper, Presonus, MIO-10 and MidiSport...

Another thought:- Depending on the ambient light source, actual light levels are gonna be modulated by the means of production. Jurassic incandescent will carry some mains frequency component. CFLs often run at some higher frequency. LED lighting, usually pulsed at who knows what frequency...

Perhaps sensor changing Backlight current/PWM alters the noise profile on V+. Some series L between V+ and Pots+ may help. Are we using Star grounds?

MIDI_Crab_v2.ino in attachment above is incomplete in that two Tabs are missing. These would be named Controller.cpp and Controller.h. Most compile errors in the OP are a consequence of those missing tabs. The sketch looks like (part) of a modified version of Notes and Volts...

For lots of multiplexed encoders check out the EncoderTool library Thread by @luni found here:- https://forum.pjrc.com/index.php?threads/encodertool.70264/

Unplug MFC > AXE-FX Midi. Boot up AxeFx then MFC then re-plug Midi, theoretically ruling out the MFC sending spurious stuff during startup confusing AxeFx's read handler. Not explored AxeFx here but have seen this scenario mess up other gear.

Your code is probably working but sending on TX1. usbMIDI examples are found in File>Examples>Teensy>USB_MIDI

Something like this? :- https://www.digikey.com.au/en/products/detail/knowles-voltronics/JZ060/6021618

Um, I think that needs to be:- - with 3 10pF caps in series, you could test approximately 3pF. - with 2 10pF caps in series, you could test 5pF. - with 3 22pF caps in series, you could test approximately 7pF. - with 3 10pF caps in series, connected in parallel with 2 10pF caps in series, you...

Neotrellis needs +5v for Vin. Onboard I2C level shifter is set for 3.3v by default.

For the PCB, Adafruit Product ID 3954, and the Silicone elastomer 4x4 button keypad Product ID 1611. A couple of strategically placed elastic bands can be used to to strap the two parts together for experimentation. If you want to play with 8x8 Neotrellis then you need 4 x each of the above...

The Neotrellis library code is blocking and depending on what you may be trying to do, painfully slow and is probably the culprit messing up audio. My Midi controller project has an ILI9341 screen, 18 encoders and two hardware buttons wired to a T4.0. The whole thing fell into a heap when I...

Double check solder bridge on address select pads, the pic is unclear. Try inserting 150R in SCL and SDA lines as close as possible to T4.1 SCL and SDA pins.

You need to call read to get some action. void loop() { usbMIDI.read(); }

Or is something in code sending wayyy too much stuff that overwhelms the signal pathway's ability to handle it. You might try replacing usbMIDI() calls with some Serial.println(" Some message"); or whatever and see what serial monitor has to say.

How about external SPI Fram eg. Fujitsu MB85RS64V?

This may be worth checking out:- https://www.arduino.cc/reference/en/libraries/midier/

Forum Rule: Always post complete source code & details to reproduce any issue! - so we don't need to go looking for what you might be looking at.

Here are some links to other threads on this forum relating to similar questions. https://forum.pjrc.com/threads/54820-USBHost_T36-hosting-USB-MIDI-devices-with-virtual-cables-(ports)...

Updated, coming to life, Stop/Start buttons, blinken lights sequencer, Moog ladder, LFO, encoders working. The fun begins, thanks again!

Thank you Mark, much appreciated. Will update to 1.59b3 and play.

Great work @MrCanvas. Used similar knobs on my late 70's Synth, a mess of stripboard and clip leads. One controlled Osc Mix level to VCF Fc, and the other controlled VCF Out level VCF Fc. Probably easy to implement for the sake of what your ears think, perhaps?

Thanks in advance for reading, hopefully a clear picture. Convalescing 100 miles from workshop using the opportunity to dive in and play with the Audio library running various examples on a T3.6 , Pin 2 has a button. Pin 3 has level shifter driving 40x Neopixels. Without any audio hardware am...

Assuming that you have used a Teensy LC or later, try reducing the value of the 47R resistors to 33R or 27R.

Maybe use a T4.0 and connect the underside pins between Pin 2 and Pin 23 to the SD?

Chances are that the T3.2's RX pin is fairly deaf to what the XBee XSC S3B emits. The T4.x is faster everywhere so I bet it aint so deaf to the XBee XSC S3B. With a baudrate of 57600 I think there's scope to kludge some low-pass between XBee XSC S3B TX and T4.x RX. Ferrite bead? Some series R...

@NeoBender, you started another thread here https://forum.pjrc.com/threads/73470-How-to-use-teensy-4-1-and-interface-with-a-5v-synth which gives a pretty clear idea of what you want to accomplish. Have posted a few thoughts.

Snuffling around the Matrix, thinking out loud:- Table at the bottom of page 7 of the service manual looks to me like the whole thing is addressed with a 10x8 matrix so am thinking that 18 mcu pins might do the trick. Looks feasible with a T2.0 and being a +5v mcu, bypasses any need for level...

Here's some Roland Sysex at the press of a button or receipt of Midi CC#32 Value 127 extracted from my T4.0 project. Has a couple of tabs.

Making the assumption that you want to turn off MIDI Thru wrt Serial or Din Midi. The MIDI library instantiates with Thru turned on by default. To turn it off, you need to add:- MIDI.turnThruOff(); After MIDI.begin();

Seems similar to this thread:- https://forum.pjrc.com/threads/73065-BUG-in-USBHost-MIDI-Code-found-with-workaround

Thank you. After sleeping on it, I get the idea. Current 16 track 32 step sequencer works well. Neopixels are used to display a single track and the Launchpad is currently used as a single dumb set of buttons to control the thing. Need to work on expanding the launchpad's scope - multi page...

Me neither, but this tickles the curiosity of my creative thinking matrix. Have a Launchpad mini plugged into a T4 host and would dive in for a play if we can politely twist your arm for some working code?

You might look at EncoderTool. A few links: Repo: https://github.com/luni64/EncoderTool Documentation: https://github.com/luni64/EncoderToo...on/Overview.md Schematics: https://github.com/luni64/EncoderToo...sources/Extras

First up, Teensy4x pins are not +5v tolerant so is potentially hazardous to Pin 14. is a better idea. Next, Serial3.begin(9600); // Initialize Serial3needs to be:- Serial3.begin(31250); // Initialize Serial3 to MIDI's baudrate Hope this is helpful.

Worst case with a jug heating element is to do with it's positive coefficient of resistance so will suck more current when cold. For the sake of the exercise you might cover the element with cold water, perhaps toss in some ice blocks and measure it's resistance.

Thank you @rvh, that inspired building an adapter to shoehorn a T4.0 into my project. Browsing the FortySevenEfects git repo found this in Issues:- https://github.com/FortySevenEffects/arduino_midi_library/issues/170 Which speaks of Transmitted SysEx messages with three or six bytes missing...

Something similar popped up on a Roland JV-XP related forum recently and the solution boiled down to allowing some 80ms for the ProgramChange to fully instantiate before sending a note message. Some other synth may handle this situation differently and who knows if it's gonna leave a hanging...

Look into the uClock library, syncs to external clock and if I remember correctly tracks Beat.

My screenshots above show that three consecutive bytes go missing from around byte 124 of a 140 byte message. Thinking of adjusting @rvh's test in MSG# 100. First to replace the Zeros with consecutive numbers 0 - 127, makes it easier to spot when things go awry. Second to test with progressively...

Gets more interesting. Switched focus to my own project, an editor/control surface for the Roland JV XP series. Communicates with the rest of the kit via Serial MIDI. Has edit buffers for 16 patches. A patch consists of one 85 byte and four 140 byte Sysex Messages. Using a 50ms gap between...

Been playing with the sketch in MSG# 100 on a T3.6. Using a two year old Lenovo laptop, Win10 upgraded to 11, fresh IDE1.8.19 TD 1.58. No edits have been done on any library. Monitoring with Bomes. After many button presses eventually do see Sysex messages with three bytes missing...

WRT low level midi input buffer configuration in MidiOx, I recall reading on a forum post several years ago discussing Sysex issues a recommendation to set Size 2048 and Num 32 for both Input and output. Back out and reboot.

You're welcome, glad it's making sense now. Am puzzled about MidiOx's apparent behavior, not seen it after four years of extensive midi - bashing using Win 98, ME, XP, 7, 10 and 11. Have seen odd Midi behavior on older (2017) desktop PC motherboard with Via usb host hardware.

Okay. Looking at the EXACT example Interface_3x3.ino running on your hardware. The Midi library instantiates with THRU turned on by default so anything received on MIDI1, MIDI2 and MIDI3 will be transmitted on MIDI1, MIDI2 and MIDI3 respectively as well as usbMIDI Cables 0 - 2. MIDI2 and...

If externally clocked and Start has been received then count ticks to create a beat Pulse. Then use beat Pulse to trigger Arpeggiator into action when incoming NoteOn == true or something. Gizmo's Arpeggiator and Sequencer found here:- https://github.com/eclab/gizmo/ do not use...