What are some examples of good anti-counterfeit strategies? And, if you’re comfortable, which applied for JamCorder?

The number that stuck out was 200K lines of code. Can you expand on why so much code had to be written and which parts were the longest (time and/or code) and hardest bits?

I recognize the "esp32 perched on top of a circuit board" from the picture. I've got a couple of those at my house right now, I'm on the second version of one board and the third of another. I think I'm going down a very similar road for a different product. Would you be willing to some paid advising? I'm an EE so I don't need hand-holding on the actual boards or programming, really just looking for more information on everything else around the edges. Either way, thanks for the article. It was nice to get some validation of my development process.

Really cool project. As someone from the software side who is just getting into hardware, this is very inspiring!

How did you find customers?

How did you get your hardware design verified?

Have you considered supporting other MIDI instruments like e-drums and pad controllers?

Interested. I got far emough on the site to have a couple of questions. (Maybe the answers are on the site?)

1) Does device record ALL MIDI sent to it? (Including e.g. SYSEX and non-registered parameters?

2) I edit MIDI on a Desktop (NOT a phone). a) Are sessions recorded into separate files? Named and/or dated? b) Can I inspect & load sessions from the card?

The website gives a very nice and captivating intro to the device.

But why do you spell MIDI in lowercase there?

> plugs into your piano via midi

>>> Have a strong anti-counterfeit strategy. Don’t overlook this.

Can you expand? What counterfeits do you see (literally someone selling boxes labelled jamcorder? How do you handle that? Lots of scanning amazon and sending cease desist letter?

Is the app Apple-only?