It sounds like Windows enters into the 'condition' not Teensy.
Very possible its Windows. As mentioned above, no problem when using iPad as host.
It sounds like Windows enters into the 'condition' not Teensy.
It sounds like Windows enters into the 'condition' not Teensy.
if ((gMIDI_Count + 18) % 24 == 0) { // 18 is 75% (of 24) gate time
usbMIDI.sendNoteOff(67, 0, 1, 0);
usbMIDI.sendNoteOff(67, 0, 1, 1);
usbMIDI.sendNoteOff(67, 0, 1, 2);
usbMIDI.sendNoteOff(67, 0, 1, 3);
usbMIDI.send_now();
//Serial.println(F("Stop Note..."));
}
Defragster - wrt to the monitoring app, it hasn't mattered if the app is running or not, or which app is used to monitor. In other words, for MIDI it doesn't seem to matter if we "consume" the data in Windows. Besides MIDIClock, we've used MIDI-OX and various Windows MIDI instruments such as DEXED and Arturia instruments to observe behavior. We've tried lots of permutations but the only thing with an observable effect is opening a serial terminal which causes it to recover briefly.
I'll check the GPU, but I haven't had it fail in the past two days. Going to try a reboot now. Oh, I just rebooted my music desk PC and it got the .228 update but my work desk PC hasn't updated.
Please give this fix a try. Does it help?
On Windows, the default location is C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy3.
I'm running it here, up to 12000 seconds now, still 120 bpm.
I have one still running at about 4500 secs, the other croaked at about 2700 secs . I'm going to reboot the system and restart the test.
Any chance that file didn't get installed or used? I ran it here for 20000 seconds.
Started a 2nd test, already up to ~3400 seconds. So far, so good.
In a few days I'm going to make the first 1.43 beta installer. Maybe give that a try?