Search results

That pretty much says it. It's a pity. Capacitive sensing is such a useful feature! I guess the newer chips just don't do it natively. I believe the CapacitiveSensing library would still work on the 4.x but it requires 2 pins and 2 resistors. Still, it would be worth adapting Flicker for it if...

Version 1.1.4 of the Flicker library is now available either from the Arduino Library Manager or https://github.com/joshnishikawa/Flicker/releases/tag/1.1.4. This update includes a previousDuration() method that will give you the duration (in milliseconds) of the previous state. As AlainD...

Good point! The (newer) Bounce2 library has a previousDuration() function that provides that info. I'll work on implementing that in this library.

The only reason they're fixed values is for the sake of simplicity. You can instantiate with a specific value as a threshold but a specific percentage would be pretty complicated to implement. As for why it's 1.2 and 1.1, also mainly for simplicity but also for stability. Touch readings can get...

Done Thanks very much. I followed up on your suggestion and this library is now available in the Arduino Library Manager.

Just to clarify, will calling SPI.setSCK(14) automatically set pin 14 to be *SCK0* and calling SPI.setSCK(20) automatically set pin 20 to be *SCK1*? In other words, is it not necessary (or even possible) to specify which SPI bus because that happens automatically depending on which pin number...

No, that 'timer' is an elapsedMillis so it should be fine. I don't think you're using the TouchVelocity class anyway (you only had functions for TouchSwitch and TouchVariable). You can use those functions with specific values too. myPowerSwitch.setThreshold(int threshold)...

Yes, that looks fine. There was a known issue that caused the quiescent touchRead() value to go above the offThreshold when using the ADC. This meant that the input would never go off. Two questions... Is that what you are experiencing? Do you happen to be using analogRead() anywhere in your...

Switches with enough poles can be wired in a 4 x 4 matrix. That'll save you 8 pins without having to use a mux. Just a thought.

Nope. It should be just that simple. Try the InputFunctionsBasic example in the Arduino IDE. Edit those callback functions using 'if' or 'case' statements to handle only the messages you care about and have them sent to the light controller along with the Serial prints (or instead of them).

If you're only interested in reading the MIDI that's coming from the computer that your Teensy is plugged into, then you shouldn't need a shield or a hub or any other hardware. If you want to extract the channel data from a note ON, note OFF or CC message, use the InputFunctionsBasic example. If...

I'm not 100% sure what "purpose" it is. Can you get the InputFunctionsBasic example to work? To read USB MIDI from the computer and do stuff with it, you'd just change the functions myNoteOn(), myNoteOff(), and myControlChange() to do whatever you like. If that example does work but isn't what...

Are you actually using the USB *host* now? That would mean you’ve wired your Teensy to have a second USB cable running to it.

How about just letting onControlChange() set a boolean that uses or doesn't use the lights? // LED #include "Adafruit_TLC5947.h" #define NUM_TLC5974 1 #define data 11 #define clock 13 #define latch 10 #define oe -1 // set to -1 to not use the enable pin (its optional) Adafruit_TLC5947...

Great! I'm very glad to hear that. I'm still developing this so I'm interested in any feedback. If possible, please use the following thread instead of this one... https://forum.pjrc.com/threads/58532-Bounce-responsiveRead-and-velocity-for-touchRead() (This thread was an accidental duplicate...

Yes. I've got the "InputRead" example working here on a 3.6 using "Play Notes From the Computer Keyboard" in MIDI Ox on windows. In MIDI Ox, under Options/MIDI devices, do you have the Teensy selected as MIDI output? You have to re-select it every time you upload a sketch. UPDATE: Hmmm, maybe...

Wow! It looks like this aims to be fairly comprehensive. Like a MIDI controller design tool that rivals Teensy's Audio Design Tool. Definitely let us know where to find the repo!

Building my own controllers has certainly been worth it in terms of experience I've gained but I've ended up paying twice as much money for something half as good as a commercial product (which I don't mind at all!) I've tried to make my experience useful for others by writing a wrapper library...

Thanks for the thorough response. I went ahead and added a line to StartCalibrate() in the TouchPad class. void StartCalibrate() { qval = 0; hiThold = 0; loThold = 0; analogRead(A0); } This seems to solve the problem just fine! Also raising lo_tfact to...

analogRead() interferes with the calibration of the touch input Thanks for putting the work in on this. I'm mainly interested in the calibration aspect. I run into a problem on my Teensy 3.6 that, as soon as I add an analogRead() to the loop, the quiescent reading of the touch input rises above...

Very nice! It's awesome that you can do vibrato and pitch bend with the same fingers that play the notes. Are the FSRs on the joystick? I'd love to see the code that runs touchRead side of it.

I just wrote a simple library for this kind of thing and wouldn't mind some feedback on how it works for other people. Try the "variable_stable" example from this library. github.com/joshnishikawa/Flicker

Thank you! The controller is literally just 5 pieces cut from a biscuit tin and sandwiched between a strip of sponge tape and a strip of duct tape. Next time I won't run the wires under the pads though. You can probably imagine that there's a lot of interference. But, if done right, it could...

[Originally posted in the wrong thread. Sorry!] I thought there should be something like the Bounce library for touchRead() inputs. So I adapted all those functions: risingEdge(), fallingEdge(), duration(), rebounce() etc. and added a few other features like the auto detection of the usable...

I thought there should be something like the Bounce library for touchRead() inputs. So I adapted all those functions: risingEdge(), fallingEdge(), duration(), rebounce() etc. and added a few other features like the auto detection of the usable touchRead() range (as it varies depending on your...

*any source files SOLVED! It turns out that, when you have multi-file sketches, you can use the .h extension for header files but you shouldn't use a .cpp extension on any source files. For some reason it doesn't get the linking right. So just omit the extension altogether. In my case, I...

Specifically, I have a Teensy 3.6 setup as a USB host. I'm successfully sending the incoming MIDI through to a 5-pin MIDI connector on pin 1 via callbacks. The problem is that, when I move the callbacks out of the main sketch, I get the following error. Arduino: 1.8.5 (Windows 10), TD...

I see the amp object in the online version of the audio design tool but it doesn't look like it was included in Teensyduino 1.42 beta 3. It doesn't appear in the bundled audio design tool and, if I copy code into Arduino from the web-based version, "AudioAmplifier" isn't highlighted as a keyword.

Thanks for the info. Yeah, I probably should have specified that the “pot” is actually wired as a rheostat. I read that the sensitivity could be adjusted by swapping out that resistor with different values so I figure why not just use a variable resistor. I should probably throw another 470 Ohm...

I was happy to find the Piezo MIDI drum example in Teensyduino especially the notes on how to wire up the Piezo. It’s quite different than any of the info I’ve found so far and this slight mod I did works GREAT! I have a 10k pot hooked up here which works well to adjust sensitivity on the fly...