gofakeit VS arduino_midi_library

I have to admit that I fell into a rabbit hole, and I noticed that popular tools like fakerjs or gofakeit[0] did not meet my needs.

I needed to generate realistic-looking identities; the person's photo must match the gender, same for the age, the skin color of the person must correspond with the origin of the surname, the first name should be common in the targeted country, and the residential address must be real, among other things.

You would not use this for test data btw, a common use case for this would be for marketing or spamming operations where you need realistic data. My consciense does not accept the later however ;-)

[0] https://github.com/brianvoe/gofakeit

Thank you! No, it’s just random data (here’s a link: https://github.com/brianvoe/gofakeit/blob/master/data/address.go)

So, is JR yet another faking library written in Go? Yes and no. JR indeed implements most of the APIs in fakerjs and Go fake it, but it's also able to stream data directly to stdout, Kafka, Redis and more (Elastic and MongoDB coming). JR can talk directly to Confluent Schema Registry, manage json-schema and Avro schemas, easily maintain coherence and referential integrity. If you need more than what is OOTB in JR, you can also easily pipe your data streams to other cli tools like kcat thanks to its flexibility.

Tangentially related, but there is a package out there called go-fakeit github.com/brianvoe/gofakeit.git for generating random data, which doesn't sound like it entirely maps with what you're doing, but there may be some overlap.

Its not much but I have had success with a random data generator package for golang called https://github.com/brianvoe/gofakeit. Its not live changing but hopefully it helps out enough developers.

Using mock data is a great way to speed up the prototyping process. We will use the GoFakeIt package to create a little dummy data generator to insert into our PDF.

The new v6 release now supports the ability to have localized rand that allows for concurrent generating of random data. Crypto/rand has now been integrated as well as if you have a custom rand that fulfills the math/rand source64 interface you can use it with gofakeit. Let me know your thoughts.

https://github.com/brianvoe/gofakeit

That makes me wonder how often one runs across a synth that doesn't support running status. I'm working on a MIDI controller myself, and that's a thing I probably ought to enable if I want the lowest latency.

It seems the standard MIDI libraries that Arduino uses don't enable it by default, but it's a configuration option you can turn on, along with a note not to try to use it with USB[1].

[1] https://github.com/FortySevenEffects/arduino_midi_library/bl...

take a look here

The Arduino MIDI Library [1]. Back in 2009, I learned C++ to build it and control my guitar effects pedals with custom electronics as part of my engineering degree.

[1] https://github.com/FortySevenEffects/arduino_midi_library

Your project can be broken up into a number of subprojects. For keyscanning you don't need additional hardware, just the pins from the ribbon cables going to the arduino's digital pins and ground. Since the keys are just switches (two per key, the time difference between the two switches closing giving the source of velocity), you could start with some examples from the Arduino MIDI library (https://github.com/FortySevenEffects/arduino_midi_library). To test MIDI sending you don't even need to start from the keybed just yet, and if you do, you can start with a single key. Once you've got that part figured out end to end (key press/release generates note on/off events) you can work on iterating through the matrix, CC controls etc. MIDI out can be done in different ways. With a 5 pin DIN plug you'd just need two 220 ohm resistors.

On an Arduino compatible platform the configuration of the baud rate at the bare metal layer is taken care of by the library when you call its begin() method. Looking at the example code included with the library it appears that there are no timer interrupts or anything like that required of you in order to use it. Another thing that jumps out is that the call to read() returns a non-zero value if anything has been received that you should use to predicate whether any further attention needs to be spent on it by your code. You may know this but it wasn't apparent from the loop() { MIDI.read\`() }` example that you gave above.

As i have started to combine this with Midi Implementation from FourtySevenEffects lib, i only have done a quick test with two/three strips and did discover follwing issue(s):

Using a library for the midi shield you can register two functions as callbacks. One callback for NoteOn(...) messages and one for NoteOff(...) messages. But thre is much more. In the end the source of truth should always be the docs for the library itself.

Click the link to github (second link in the article) and there's all the source code: https://github.com/FortySevenEffects/arduino_midi_library

Here’s a library that might work.