tomas

MIDI Capability Inquiry (MIDI-CI) exists exactly for that purpose. A MIDI 2.0 implementation does not just assume MIDI 2.0 support in the devices it talks to: it sends a capability inquiry to find out exactly what features are supported. A MIDI...

Any proper implementation of MIDI2.0 has to be able to fall back to MIDI1.0, otherwise it's not in spec. It'd be a nightmare otherwise. I don't think you can even patch a piece of gear that totally relies on DIN MIDI connectors to handle MIDI2.0...

I do plan to support MIDI 2.0. I just waiting for those 3 things before starting any work.

I mean that I hope that Teensy 4.x USB MIDI (when Teensy libs are upgraded to MIDI2.0) will continue to work with MIDI 1.0 drivers and devices, so we can continue using old devices and "old" OS (I don't know what plans does Microsoft have for...

Zipper noise occurs when you change a parameter of sound synthesis path such as oscillator freq, amp, filter cutoff, delay time, etc, in a "stepped" way. Analog signals are smooth, so when you turn say frequency knob in analog circuit the...

I just hope that MIDI 1.0 will continue to be supported. I have lots of hardware using good old midi that just work. Also I have my own projects that I use good old MIDI and 127 different values per potentiometer is more than enough (can't move...

I finally found the time to work on the LastCall class. This class is used to measure the time of update- and isr- calls. The goal was to increase the performance of the class but also keep the outlier detection. (An outlier in this context is...

Simplicity. Embedded hobby projects usually don't have gazillions of files and name conflicts therefore namespaces are rarely used. Historically embedded projects did not use C++ at all because modern C++ with templates, std lib might bring...

Is beginning of the table guaranteed to have value of zero? Cosine for example doesn't. In such cases crossfading over single buffer length might be better.

Heap allocation is never guaranteed to succeed. Heap fragmentation is real thing and dlmalloc is not magical cure. I have seen it fragmenting memory too. So as long as you do hobby project, or music app that will just stop playing and you will...

For context, part of my motivation here is that I’ve already implemented a full UAC2 asynchronous device on STM32H723, including: Async isochronous endpoints with feedback Device-driven audio clock High sample rates USB → SAI with DMA So I’m...

It does not matter what @whitebengal meant or not. I suggest that any thread on Adafruit vs Sparkfun (and this one) is closed immediately. If there is a need to enter into a Teensy development due to non PJRC events, than this should be named...

Yeah.. Yamaha engineers implemented clever tricks to even avoid multiplication. Their custom FM chips did just additions and ROM lookups. The first ROM was a log-sin waveform table, containing one quarter of a sine wave, 256 samples long. The...

IMHO, a small FPGA might be a better fit for such a task. Or programmable state machine like PIO in RPico with its wait instruction.

Please. Not another thread about the kids spitting the dummy.

Since my goal is to be able to play live as much music as I can, I implemented advanced arpeggiator and split keyboard feature and multi-timbrality. I also worked on some recreation of famous Solina String Ensemble sound. A little demo is here.

You just can’t help but love this ’80s vibe.:)

btw there is still a lot of new progress in microdexed touch

There is a technical note by NXP covering lifetime vs temperature subject: https://www.nxp.com/docs/en/nxp/application-notes/AN12253.pdf Expected lifetime drops drastically with the increase of junction temperature from 75C to 95C and there is a...

Just a quick note before this thread is locked and in case Phil does not reply by the cut off: If you're curious, there is no thread on their forum. I just checked. There may be posts elsewhere but on their own forum, there are zero threads about...

Quick reminder, this thread will close Monday, January 19. Duplicate threads are not allowed. Phil, twice I have asked (msg #153 and msg #160) for you to create a thread on your own forum to continue this conversation. If this really has been...

You would just need to specify "Teensy 3.2 Compatible" for example. Sorry, I thought this was implied since each version has it's own specs. Paul> I agree with what you posted from the law firm's definition. When the Teensy LC was discontinued...

To me, "Teensy-compatible" brings up the question: Which Teensy? There have been a bunch. And even then, it doesn't seem like Adafruit is making something compatible with any of them. And this probably goes without saying, but I'll say it anyway...

I've been reluctant to write on this thread, because it really is about drama between Adafruit and SparkFun, or perhaps between Phil/Adafruit and a number people may or may not actually be connected to SparkFun. I have some strong feelings...

The other approach would be to fix measurement time and each core should be allowed to do as many iterations as it can within given time. Then the sum of number of iterations done on each core should be used to calculate total performance. This...

Cache size also really matters. An 8K instruction cache is the reason why Teensy 3.6 scores 66% faster than Teensy 3.5, even though is has the same Cortex-M4 processor running at only 50% higher clock speed. If instruction and data caches are...

Yes, the version of the compiler has a major impact. Optimizations are constantly being worked on.

Also benchmarks don't tell the whole story. FPU on ARM M7 (Teensy 4.x) seems to be pipelined better than on RISCV

That is very true..In fact ESP32-P4 does not seem to have any safety margin at all. Their 400MHz part can only run stable at 360MHz at least with currently available chips.

In my opinion it does not make sense to use overclocked results (at least for sake of comparison of different processors ) because overclocking is subject to silicon lottery and reliability is questionable. If comparison is meant to be fair...

I'm wondering why all the "RP2350 Due Core" results end in .00?

Thank you Tomas, i've added your Benchmark results to the readme, and made the detection code more robust. Indeed, build_flags= -DMULTITHREAD=2 (or 1) in platformio.ini is enough.

There is a #define MULTITHREAD that must be defined via platformio build_flags to allow multithreading. For two threads: build_flags= -DMULTITHREAD=2

Single core ESP32-P4 @360MHz result ( -DMULTITHREAD=1) CoreMark Performance Benchmark CoreMark measures how quickly your processor can manage linked lists, compute matrix multiply, and execute state machine code. Iterations/Sec is the main...

Are you using Platformio by chance? If you have ESP32-S3 code/project I can run on newest ESP32-P4 and post the results.

Exactly. Getting Teensy in Europe was expensive already (shipping). It is quite absurd that two good companies can't just talk. Adafruit has done a lot of good stuff and Sparkfun too. There is a place in the market for both. Really people maybe...

Sad story. I fear that this gives less sellers in the EU and thus more difficult to get a teensy with some other stuff. A Teensy alone and thus with shipping, will be a lot more expensive.

.... Or i.mx rt 1170 + MIPI + more / other pins broken out.

When I received my ESD training at HP, I was taught that pink plastic does not generate static electricity inside the bag like a normal plastic bag. However, it is totally ineffective at preventing a static discharge from OUTSIDE the bag...

My assumption is that Sparkfun purchased exclusive licensing rights to produce and sell Teensy boards, and Paul would be violating the royalty contract he signed by doing what you suggest. Honestly though if you’re going through the trouble of...

Yes, that could be a problem. And no one knows how long Sparkfun will continue to produce Teensy. I fear that if difficulties arise—such as renewed delivery problems with certain parts (which don't even have to affect the CPU)—it will disappear...

It sounds like Sparkfun wants to keep Teensy retail margin to themselves & not allow Adafruit to distribute Teensy profitably at the retail price - basically not selling them to their competitor at wholesale pricing. I think the reason this...

Trying to understand this - the third party would want a reseller discount so they can make a profit, and then Adafruit would also want a reseller discount so they can make a profit. I struggle to see how Adafruit would then be able to remain...

That's probably the main reason. Adafruit is competition for Sparkfun. Sparkfun isn't covering itself in glory in this matter either.

At this point, I would recommend both sides to just quit engaging. Go out and enjoy the coming weekend. Touch grass. Spend time with your family. Work on new cool projects (with a teensy!) Arguing the same point over and over is not changing...

I call myself a hobbyist (even though I have EE degree) and bought plenty of Teensy 4.x and going to buy way more ! @ptorrone - initially I wasn't understanding what this is all about, but after what you have said and done it become clear that...

Well, I really hoped that it would not escape you, but, you missed the point. ... ... Correct & no disagreement (that it possibly affects users and developers). ... ... Again, correct, but here's where your understanding falls rather short...

Confessions are good for the soul! Sorry for your loss :( I don't use the IDE setting (or rather, have it set to 600), just what I set in code. I poll the tempmon each second and have a graph overlay available that stays on top of my UI showing...

FWIW - I have been running my Teensy 4.1at 816Mhz for 4-5 years now, for long periods at a time each use. All my Teensys subjected to this are still operational. I have a small (10mm x 10mm x 4mm) cheap, copper heatsink sitting on the processor...

Hi, (no idea, what the Baby has to do with all of this....) Thanks for sharing the benchmark! In my opinion, the numbers without overclocking are most interesting. On the Github, we can find them though and this is given as 600 for Dualcore Pico2...