Search results

Have a look at posts 14 to 16 in this thread: https://forum.pjrc.com/threads/34697-Midi-usb-raw-input-question-and-possible-bug-in-usb_midi-h

I'm not quite sure what uniform-partitioned means but the idea of operating on a single 128 block at a time seems like a much better idea than filling the buffer with 4 blocks. I guess shortening the impulse is out of the question ... 512 samples is, I guess, reasonably close to the wind...

Hmm... that's an 11 milisecond impulse 513/44100???? I use redwire impulses (and kefir 2 vst) for all of my recording .... I'll have a look how long the impulses are... I had in my mind that they are about a second long .... they do have a very small active footprint, though, as you say, a lot...

awesome. congratulations! I will test when I have time. I am guessing that the .wav file has to be exactly the right length for this to work?

Hi midi serial to midi usb requires repackaging, transcoding if you like. here is a thread with working code etc etc. for a 2 x 2 interface post 14 / 16

Thanks ...very interesting ... I will have to digest. Thanks for the compiler flag help. very much appreciated. I'm not sure that virtual functions are flexible enough for what I am doing... I like the functional approach without the demands that an inheritance scheme impose .... passing...

There you go ... no master...you need the right nordic softdevice for master / central ... s120 ...certainly not impossible to put onto the feather, I am guessing, although maybe you have to use the swd port or something??? Not sure how you would do it over the spi interface, but I guess there...

I feel like a traitor .... there is an excellent SAMD based solution from adafruit.... its called the feather M0 bluefruit LE or some such. Adafruit feathers and teensy's are close cousins ...Anyway the feather has a nRF51 (or is it 52?) Nordic ble module wired into the spi port ...and adafruit...

dimitre yes you are right it always is on the left side ... you have to factor in the front labelling versus the rear labelling difference between the pictures too .... ...I got confused... the pictures are upside down... I was thinking it was like doing a nut up from the wrong side (which way...

elapsed millis is the way to go ... Also maybe you could think about restructuring to use callbacks ... I guess button10.fallingEdge function returns true if there is a falling edge. Why not rewrite it so that instead of returning true, it calls a function pointer that you have passed to...

I think it is the fact that the photograph is upside down and labelled from the front as compared to the schematic (which is looking from the back of the din socket.... positive is to the power supply , pin 5 is to the teensy... I got confused as well ...horribly confused

Thought I'd post... you can't capture "this" in the lambda default parameter per se ... makes sense. But you can rearrange things ... I haven't tested this code, since I don't have a teensy at the moment!!! but it should print "5" ...it compiles (once you change the teensy compiler settings)...

Hey tni .... awesome help there buddy!! I see what you mean about runtime vs compile time .... run time binding is what I need, to keep everything encapsulated how I want, as it turns out. Forced me to re-evaluate some design decisions, so I have a bit of refactoring to do. You can't...

Thanks so much for this .... I'll digest ...I can kind of see the difference between runtime and comiple time polymorphism, and I don't think it is anissue for my program. Thanks so much for helping out. I'm just starting with all this c++ stuff.

thanks ....I have linked the library. When I remove the declaration, I get "std::bad_function_call", as if the std::function is not capturing the target lambda. I can handle that exception easily enough, but why is it getting thrown? I tried another approach auto default_parameter = []() {...

Hello I have this strange error when compiling the following: #undef max #undef min #include <functional> bool rule0 (std::function<bool()> application = []() -> bool {return true;}); bool rule0 (std::function<bool()> application = []() -> bool {return true;}) { if (application())...

WOW! I remember hearing that chrome added midi hardware support like last year ... who knew it worked (badly)

yes it is beta and not a complete implementation of every call, according to the interweb.... I use a rpi 2 headless, running raspberian and their lightdm display manager ... its rigged to use xdmcp, which is not secure, but it is on my own network behind a firewall (obviously Xming is...

it runs nice on a rpi 'desktop' environment, and you can xming it over your lan from there I do that 'all the time'. I think Kurt E has done a similar thing ...chmod 755 should work?? that is everyone execute isn't it ???

If teensyduino relies on anything in the "Linux install" that has not been nativised to a windows call by the subsystem, you will be shit out of luck. maybe that is what you are seeing? As you say .... "MSFT maps the Linux systems calls to Windows". If there is a missing call (because most...

There are two separate things going on here .... using X11's networking capability, and using a soft framebuffer and vnc. It seems a virtual machine would be a better option (you will have to tinker otherwise!!) ... I have used Xming on Windows and it works really well, so if the windows...

This is very interesting .... thankyou for taking the time to look at this area of teensy programming .... is this primarily a function of fixed point maths? the teensy 3.6 is floating point I think .... will that make a difference? or is a function of 'word length'. I know in the audio...

would the Apollo AGC make a good midi controller?

I reckon you would probably be alright with the LC, but you should buy an LC and a 3.2 .... having a spare teensy is a must, in my books, in case of accident. And that way you can test the difference in speed if there is any..... Also, you would be surprised at how fast you can fill up the LC...

you just got 3145 (in case you weren't watching ....:D)

Maybe you need to consider pullup resistors on the i2c lines?? I think i2c on teensy requires that?

You should rejoice!! those must be the keyboard matrix mcus you identified earlier! I suppose you will be able to press a key and see what change in the i2c traffic occurs, maybe using an oscilliscope or some simple print to serial i2c program.... Hopefully an i2c expert will happen along ...

looks like I'm the first to say ...THAT IS FREAKING AMAZING! ES INCREIBLE

@defragster .... the feeding of the 5000.

@MichaelMeissner I think of tee-shirts as clothing, and I want one. Give me a teensy tee-shirt now. in XL

I am going to spam until I get a tee-shirt.

I want a tee-shirt now.

give me a shirt and I will give you money

I want a tee-shirt

Nice job !

Stellar first post

Jimmy Hugh's method looks very stable ..it is a bit of work ... extracting pins from those header strips can be tricky, but if you get organised, it wouldn' be too hard

thanks ... will check it out edit: very cool ... perfect for breadboarding ... I guess you could use the teensy upside down to utilise those groovy underside rightangle headers, with female breadboard wires.

Nice ... thanks for sharing

Yes ... I was gently trying to get to this point!

@MichaelMeissner ... the volatile keyword ... is it necessary if global variables are not used in an interrupt? I ask for my own information. OP How about this ... if (note < 60) {note = 60}; if (note > 69) {note = 69}; That way you always get some sound. Please give us some soundclips!!

Glad you have worked it out .... be aware that anything but notes 67 - 60 will give an array out of bounds error and everything falls over ... the code is fragile ... funnily enough, I originally only did a note on short spike, but I thought you might want to time it off the release event...

Hey I have a working usb_desc.h file here for teensy 3.x

Interrupts with 'average' mechanical rotaries can do that. smoothing is good... ignore fast changes and only record an event if there is '4 in a row' or something like that

I think this is a pretty good guess Sounds like a plan....!

Yes, I didn't read it thoroughly enough

I am confused about the bus too ....the joys of reverse engineering ... I guess that it is serial!!! but even then I'm not sure! good luck!

how about something like this ..... it is fragile, since it will only work properly if you have restricted midi input to notes 67 to 60. Note that elapsedMillis overflows after some days or something, from memory // USB MIDI receive example, Note on/off -> LED on/off // contributed by...

Maybe try input pull-ups too, just to be safe... And yeah the waveform of the encoder ... its the internal mechanics of the switch ...you kind of get the feel of two detents for one on some of the rotaries I've used ... and of course if you want 127 steps for midi you are limited by the...

should have used my library :rolleyes:..... ... why not just Serial.println (myEnc.read()); see what you get. I think the encoder library just returns a count .... I have a 24 alps encoder too... maybe a different model .... works fine..