I assume it works properly, I tested a few different programs with compile and uploads that all went through without any problems, at least nothing different from my other Arduino installs from...
Type: Posts; User: vjmuzik
I assume it works properly, I tested a few different programs with compile and uploads that all went through without any problems, at least nothing different from my other Arduino installs from...
The Teensy Loader from post #28 has dark mode support while the new one doesn't, is that something that can be added back?
I didn't have to right click while connected to the internet or while off of it, it verified the app seemingly fine, and I know even with SIP off I do have to right click + open for some other...
It’s likely different because you may have still been connected to the internet, mine normally look like that when I’m connected the internet.
It appears to have worked fine without being connected to the internet.
18324
18325
I can certainly test stuff on Catalina since it is what I use to dev with so if there is any problems I’m sure I’ll run into it at some point, I do have SIP disabled so I don’t normally worry about...
I recently updated to MacOS Catalina and using my previous installs of Arduino after giving them access in the system preferences I have had no problems with it.
Based on Ohms law your 100 ohm resistor allows 33ma to be drawn from the Teensy which is likely much more than the 4.0 can handle. 300 ohm also seems a little high at 11ma, I don’t know what the max...
As long as your wires have a solid connection you can get away without soldering for prototyping, I typically use alligator clips so I know the connection has some strength to it. If your Teensy is...
That would be especially useful if it had a bi-color LED so it would light up a different color when it’s wired backwards, the circuitry is the exact same that you already have built just using a...
USB controllers: https://forum.pjrc.com/threads/49099-T3-6-USB-Host-Joysticks
Bluetooth controllers: https://forum.pjrc.com/threads/49358-T3-6-USB-Host-Bluetooth
Looks like they work already.
You don’t need a shield so the library doesn’t apply to this.
This is the library you want to use with the second USB port for host functions: https://github.com/PaulStoffregen/USBHost_t36
I believe it already has support for Xbox and PS controllers.
Are these pictures reversed from your webcam, based on the resistor photo it looks like it. If so then you have it wired backwards, here’s a photo from sparkfun that may help your orientation:
18250...
If all you need is to emulate a keyboard a Teensy LC can easily handle that.
Making every control mappable is a thing you can do and it’s a really useful feature to have, a company called Open Labs used to make custom controllers like this with software to map every control....
With the Teensy 3.2 it is sort of possible to do it using USB OTG and there is some software support for it: https://github.com/felis/UHS30
Not many people have used it and I have no experience with...
In your current configuration you have no host to control the USB devices, to have the Teensy send messages to the Helix the Helix has to be connected the the Teensy's USB Host port and not the USB...
To support SD Express we would need PCIE which isn’t supported by these microcontroller processors as of yet and likely won’t be any time soon.
This should do the trick:
// Button Toggle In Code
#include <Bounce.h>
const int channel = 1;
boolean toggleState = HIGH;
Delete this part from the if statements and it should work:
.fallingEdge() returns true if it’s a falling edge so you shouldn’t test if it’s not high.
Does it only send a stream when pressing the button or constantly?
I believe this should be uncommented:
//bankSelect = false;
And this:
++ClockCount;
Should be this:
ClockCount++;
Well it did work for the 3.6 so I guess it’s undefined but happens to work out correctly.
I guess the compiler for that architecture doesn't interpret the syntax correctly.
Perhaps this line is causing an issue and not actually incrementing on the 2.0 hardware:
++ClockCount = ClockCount%24;
This is the only line that could stop it from working as far as I can tell,...
I wouldn't think so, it's something that's pretty basic so it shouldn't be broken between devices.
Start on timing clock with 100 BPM, I also confirmed that I can do it manually by just sending timing clocks.
I can confirm that it does function with the code from post #15, fresh upload to a Teensy 3.6 with MIDI Tools, the only modification I did the code is fixing the onClock parenthesis so it's actually...
If you install this program: https://mountainutilities.eu/miditools
You can use it to manually send MIDI commands so it’s easy to troubleshoot certain things and one thing you can do it send the...
Could probably be causing issues, onClock shouldn’t have anything in its parenthesis and if you delete that it’ll clear up the error.
void onClock(byte channel, byte note, byte velocity) {
if...
Should the else statement be wrapped in SetTempoActive as well?
void onClock(byte channel, byte note, byte velocity) {
if (ClockCount<=3){
if (SetTempoActive){
...
USB Host firmware is already fully working on the Teensy 4, the only hard part is that all the hardware for it isn’t already builtin to it like on the Teensy 3.6. There are several breakout boards...
The limit is actually (2^14)*6, but you are right it won’t overflow, I forgot how numbers worked.
Looks good and yeah just making it 32 bit solves the problem, though it should be unsigned so it doesn’t go negative.
What would be the reasoning behind using i=i++ as opposed to just i++? For pointers I understand the difference, but I’m lost as far as regular variables go.
I don’t believe values get truncated until they are actually written to a variable, I’ve definitely not seen it happen with other stuff that I’ve done. As long as you know what you are going for it...
Never mind that, you have access to a few commands you can use to identify what USB device is assigned to which object, the easiest to test against are the Vendor and Product IDs so once you figure...
Yes you can communicate with multiple USB devices at once through the use of a USB hub, all you have to do is add more USB MIDI devices to your USB Host object. In fact there is an example for this...
Technically your thinking is close, modulus 4 would be the number of 1/16 notes, but we need the number of Clocks and not 1/16 notes. So to get the number of Clocks we have a multiply our number of...
Besides your SPP callback the rest is fine, one SPP or MIDI Beat equals 6 MIDI Clocks so modulus by 4 won’t give you the right value. What you normally do to find the the total number of Clocks is...
You can pause off beat most of the time when you do not have the MIDI Beat Clock on, some DAWs behave differently when you have it turned on because of the loss in resolution. If you take into...
There does happen to be one port with 16 IO pins available, pins 0-1 and pins 14-27 are all on GPIO6 so it could be possible. You will have to do some bit shuffling to get them in the right order for...
Also, in my opinion the best way to keep track of the LED state is to just turn it off after a certain number of clock cycles, so if you turn it on at Clock == 24 then you can just turn it off at...
You don't necessarily want to stop counting clocks on stop, since some DAWs will still send clocks even while stopped so for just tempo I would only worry about Clock, Start, and Continue. I don't...
What you use for tempo is called the MIDI Beat Clock and most DAWs will support this since it’s needed to sync external MIDI sequencers together. This is supported in Teensyduino already and there...
I added a function to turn on promiscuous mode so all ethernet messages come through instead of just the matching MAC address or broadcast messages. This does come at the cost of increased USB...
Interesting, I wonder what changes are being made with debug that stops it from working.
Yeah it was pushed to GitHub a while ago, I don't remember which version had the issue but I know there have been several more commits since that issue was fixed.
Also yes there was an issue a while ago where the small delay that was added from printing debug information allowed it to work, but that was fixed. I’ve done my fair share of testing with it on and...